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
The Fidelity Curve An Article by Ryan Singer m.signalvnoise.com How do we choose which level of fidelity is appropriate for a project? I think about it like this: The purpose of making sketches and mockups before coding is to gain confidence in what we plan to do. I’m trying to remove risk from the decision to build something by somehow “previewing” it in a cheaper form. There’s a trade-off here. The higher the fidelity of the mockup, the more confidence it gives me. But the longer it takes to create that mockup, the more time I’ve wasted on an intermediate step before building the real thing. I like to look at that trade-off economically. Each method reduces risk by letting me preview the outcome at lower fidelity, at the cost of time spent on it. The cost/benefit of each type of mockup is going to vary depending on the fidelity of the simulation and the work involved in building the real thing. Four levels of fidelityTime to build versus confidence gained prototypesinterfaces
Four levels of fidelity Suppose we have four levels of fidelity… Rough sketch (on paper or an iPad) Static mock-up (eg. Photoshop or Sketch) Interactive mock-up (eg. Framer, InVision) Working code prototype (HTML/CSS, iOS views) Depending on the feature you’re working on, these levels of fidelity take different amounts of time to create. If you plot them in terms of time to build versus confidence gained, you could imagine something like a per-feature fidelity curve.
Time to build versus confidence gained Show image 0 Show image 1 Show image 2 Take a simple CRUD web UI, where you’re just navigating between screens. It doesn’t take much more time to build the real version than it does to mock it when the design is simple. If you were to build out an interactive mock first, you would end up spending twice as much time in total without gaining much out of it. Contrast that with a complicated Javascript interaction. Or a native iOS feature that requires programmer time to build out. If it takes substantially more time to build the real code version, then it may be smart to do an interactive mockup first.