Transcript: So the time has come that I'm applying to jobs and there's like a slot for a resume and I'm like I think I have a resume somewhere. I open it up and it turns out it's a little out of date. I wrote it when I was still at Vigilant. Yeah the thing is like three years old, maybe longer, maybe older. It's very out of date. It's really interesting to see it because it's coming from a place, a time where I think I was still trying to be legible to organizations and companies in a certain way. I'm a founding backend engineer, experienced in XYZ. You know then several years of stuff later like that's it's no longer actually descriptive of the way I like to build and what I like to build. I even want to be seen by an organization. That's just interesting. I think it's like opening this old artifact and seeing that quite a bit has changed in the way that I like to operate and work and simultaneously I'm frustrated by the idea of a resume at all and it's completely not enough to actually encapsulate all the things that I am capable of and excited about and experienced with. And there's like quite a big question of how to even sum up the last three years of my life with all the projects and experiments with relational and little side projects with friends. I kept learning shit. I kept shipping stuff but there's not exactly an official like tech lead, manager type as a reference. I have no doubt that I have references and don't have positive things to say about working with me but I've been in quite a few non-hierarchical organizations for a while and just the concept of someone who is like checking boxes off as I was doing my work and scoring me and grading me is just kind of alien and I think it's giving me some anxiety to be working on this artifact in a way that sort of feels like I'm going back into that world. I might not be but it does feel like that. So yeah, I'm feeling all sorts of weird from that. For some reason generating this doc just feels stressful and a bit scary. I don't think there's any reason for that necessarily. But it's like this thing that represents me and my time and I think I have like a lot of expectations about what it should look like by now. My age and experience level and half the shit on here doesn't exist anymore or it's been bought and torn apart by some other company or just evaporated into nothingness. It's just like a document full of references to past things that don't even exist anymore and apparently that's supposed to help me get into building something new. I don't know. It's just like the whole proposition here kind of feels weird. So that's it's kind of the set of things there. Resumes are weird.
The text provides insights into the challenges of finalizing and shipping a product, highlighting the complexities of resetting and managing various states and default values. It also touches on the need to consider potential issues and the importance of thorough testing. The author reflects on potential improvements for future projects, such as incorporating safeguards for duplicate signatures and considering time-based randomization. Additionally, the text emphasizes the importance of attention to detail, particularly in visual aspects, during the final stages of development and deployment. The speaker discusses their increasing comfort with refactoring and componentizing complex structures. They express excitement about making code more readable and coherent, although the components are currently specific to the project. The speaker notes the trade-off between using brain cycles to save CPU cycles and vice versa, while also reflecting on past regrets and lessons learned. They emphasize the importance of simplifying and automating processes to reduce complexity and potential confusion. Additionally, they mention the need to minimize the number of possible states to maintain control and avoid tangled situations. The text contains various thoughts on working with render loops and passing signals as props in React components. The author also discusses the importance of validating metadata before deployment in order to avoid costly mistakes on the main net. Additionally, the author reflects on the need for breaks during long coding sessions and the frustration of having to rename components. Overall, the text reflects the author's experiences and insights while working on a project.
The author is reflecting on the challenges of effectively showcasing their work on the internet, particularly in relation to portfolios and resumes. They express frustration with the limitations of resumes in capturing the depth of their experience and contributions. Additionally, they discuss the ongoing financial and practical challenges of maintaining online projects and the importance of preserving past work for the benefit of future creators. The author considers using archive.org as a potential solution but expresses reservations about outsourcing this responsibility to a non-profit organization. They ultimately prioritize the use of such resources for preserving knowledge that benefits the broader community rather than their own personal or professional work. The speaker is exploring the idea of preserving their work and experiences in a meaningful and sustainable way. They express concerns about relying on external platforms like archive.org and consider alternatives such as hosting their own content and encoding it into a lower fidelity medium. They also discuss the concept of creating their own encapsulation and representation of their work, which they hope will be more long-term sustainable. The text discusses the idea of creating a collaborative storytelling and writing platform that acts as a memory time capsule by archiving and snapshotting links. It addresses the challenge of link rot and suggests that decentralized hosting and a network of machines could potentially help in the future. The text discusses the concept of a scoped IPFS that functions similar to RAID, where each file is known only once but stored multiple times based on its significance. It also touches on the importance of data permanence on the internet, addressing concerns about archiving family photos and trusting companies like iCloud to maintain data indefinitely. The author questions if they should trust these companies and expresses uncertainty about the longevity of their data stored on such platforms.
After a hike, I encountered Steph, leading to ongoing communication about hosting events. We discussed her co-organized salon on the AI alignment problem in March and my interest in hosting a website-building event during startup week, potentially in April or May. We also contemplated a tool for managing our projects and events, like a specialized project management software. Further, we talked about the connection between online communities and the physical gatherings they can inspire, emphasizing the cyclical relationship between the two.
The speaker did not complete their weekly review, which usually provides clarity and insights for the upcoming week. Despite this, they have many projects, personal life commitments, and community efforts to attend to, not to mention taxes. They plan to set week intentions using voice instead of writing, including the exploration of websites for the Diagram Website Explorers Club and developing a Canvas element-based editor for Daily Jam. The technical aspects of this project involve real-time data updates, efficient pixel manipulation, and secure user authentication through tokenization. A function is set to run every five seconds to update the canvas with the latest pixel data, ensuring all viewers see a consistent image while minimizing performance impacts. Other tasks include preparing tax paperwork, organizing Boulder events for systems and AI, and sketching ideas for a project called "co-net." The intention is to spend more time outdoors in the nice weather and to schedule the next "Site Craft Hang," while thinking about potential content for the "Explorers Club" website. Overall, it's a productive Monday morning with good weather contributing to a positive start to the week.
82.83% similar
The speaker is excited about tomorrow but acknowledges that as a developer facing new challenges, the work is not trivial, especially given the lack of extensive documentation and the solitary nature of their current work process. They express a desire to share their learnings, possibly by writing them down, and emphasize the importance of collaboration, suggesting that "if we do this together, it will be a better world." The speaker is tired of creating misleadingly impressive demos and aims to write code and interact with large language models in a more genuine and transparent way. Lastly, they recognize the complexity of building an effective agential system, admitting their current limitations while believing in its importance, and they present open questions about processing and connecting large amounts of data to better understand who we are.
82.15% similar
The article discusses the concept of excess energy and its potential for useful work, particularly in the context of desalinization. It raises questions about the economic viability of various forms of useful work and their relationship to industry operations. The author ponders how to accommodate fluctuating energy demand and considers alternative forms of useful work that can be easily adjusted. Additionally, the article delves into the rising energy prices and their implications, noting the impact on inflation and the broader economy. It ultimately questions whether energy prices should be decreasing considering the growing energy supply and highlights the ongoing challenge of balancing energy demand. The author contemplates the impact of a hypothetical surplus of 100 terawatts of power, wondering how it would be utilized in practical applications as well as its potential effect on energy prices. They reflect on the potential implications for the efficiency of semiconductor manufacturing processes and the unit economics of power consumption in relation to chip production. Additionally, they consider the impact on the cost of energy and the potential influence on technological advancements, such as mobile devices and large-language models, while pondering the likelihood of significant developments in battery capacity or power grid capacity in the future. Ultimately, the author grapples with the complex interplay between energy availability, technology development, and economic factors. The text discusses the impact of luck and timing on the future, emphasizing the significance of being in the right place at the right time in an evolving world. The questions revolve around the potential of using increased computing power and its implications for various industries. The author ponders the feasibility of building and networking advanced computational systems, as well as seeking funding opportunities by approaching venture capitalists in Silicon Valley. The text also expresses uncertainty about the timing and feasibility of pursuing these ideas, acknowledging the complexity and challenges involved. The speaker is focused on securing funding for their project and contemplating the core question they are trying to answer. They express a concern about the difficulty of the problem as it exists across various future scenarios and emphasize the need for a computer to understand their context without losing the complexity and emotion of human communication. They mention existing products like Rewind and Tab, but express skepticism about the ease of solving their problem through technology, stating a reluctance to change their behavior to fit a machine's requirements and feeling overwhelmed by the complexity of the task. Despite their doubts, they express a desire to fully realize their vision through a website. The speaker plans to create a new app that will generate a JSON output based on their questions. They believe that having this functionality will enable them to build any app they want. The speaker ends the voice memo with the intention of utilizing the recording for a future project they are working on and suggests that they'll use it to engage in questioning and exploration.
82.08% similar
Feeling exhausted but content, the speaker reflects on their constant work and aspirations to improve processes, like making John's burrito preparation faster. They acknowledge that their current project may have flaws, but see potential for it to be a dynamic back-end platform with multiple uses. The speaker expresses a desire to create something novel and valuable, while also fostering a space for both public and private sharing. Amidst these professional goals, they cherish personal connections, such as a satisfying morning of surfing with friends.
81.95% similar
Today was a peculiar day that included exploring the Intention website and considering the best approaches to development, amid a struggle with the authentication process and frustrations with OAuth. Progress on a web app was achieved, despite dissatisfaction with its simplistic nature and a switch of rendering methods from React server-side to client back in the pages router, noting the app router's performance benefits. The experience with Next.js was more frustrating than anticipated, leading to doubts about its complexity and a desire for a simpler, more streamlined framework. The day was largely spent battling with development tools, an annoyance when trying to focus on productivity, with thoughts on potentially moving towards more server-side rendering and investigating React's streaming components for future enhancements.
81.54% similar
The user is curious about summarizing their thoughts in the last 24 hours to have a solid understanding of their previous musings when they return to the computer. They also want to create a social mechanism to share their thoughts and interests with others in a way that is algorithmically related to their own interests, without coming across as trying to show off. They express a preference for audio recordings over writing and anticipate the process of reviewing their nightly thoughts as potentially painful. Overall, they aim to implement a solution to streamline this task.