Builder Brain An Essay by Charlie Warzel newsletters.theatlantic.com The Builder mindset often eschews policy completely and focuses on the macro issues, rather than the micro complexities. It is a mindset that seeks to find very elaborate, hypothetical-but-definitely-paradigm-shifting, futuristic technology to fix current problems, instead of focusing on a series of boring-sounding and modest reforms that might help people now. …The worst version of Builder mentality is that their dreams become reality, but instead of maintaining their creations, they simply move onto the next Big Thing, leaving others to deal with the mess they’ve made. A time to build and a time to repair technologybuildingsocietyrepair
If we didn’t live to work A Fragment by Charlie Warzel warzel.substack.com When you talk to people who reject the modern notion of a career, many of them say the same thing: They crave more balance, less precarity, and better pay. They also, crucially, want to work. What’s profound about the career rejectionists is that their guiding questions are simple. What if work didn’t make you feel awful? What would life be like if we didn’t live to work? What do workers and employers actually owe each other? What if we structured our work lives around a different idea of success? workvalues
Building Momentum An Article by Dan Mall danmall.com Fight the Waterfall Start all of the pieces of work a little bit earlier. The key to starting work early is not succumbing to the pressure of having to finish the work. Don’t worry about finishing. If you’re a developer, you can start doing things while your design or information architect are working because a lot of your work actually isn’t dependent on their work. Some of it is, so you probably won’t be able to finish, but that shouldn’t stop you from starting. Share Work-in-Progress Early and Often When you share work-in-progress, share it with the caveat that no feedback is needed at this point. You’re simply sharing it to let people know where you are. For example, if you have to make 12 wireframes, share it when you finish 2 or 3. Rather than spending a whole week to drop 12 wireframes, share 2 – 3 wireframes every 2 days. The more often you do this, you start to build rhythm, and rhythm builds momentum. processworkcollaboration