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.