2 ms·
Reducing friction as a standard operating method
- RyanMcGreal 17y agoI like the notion of expanding from a narrow cost/benefit analysis to a broader "opportunities lost cost" - the set of potential new things you can't do because you decided not to reduce friction in your current set of activities.
- 10ren 17y agoSimilar story: shaving a 5 second build/run down to 200ms. It took 2-3 days to implement. I couldn't justify it in terms of time saved; nor did it seem I could use the article's justification that I'd tend to avoid compiling because it was too painful. However, it did change my workflow, in that now I try things out quickly, and even using code like a config file, to test ideas instantly. Perhaps more importantly for me, every time I compile now I get a little feeling of delight, and a data-point suggesting that all problems have solutions. details: http://news.ycombinator.com/item?id=939523 http://news.ycombinator.com/item?id=939523
- DenisM 17y agoLinus also talked about how instant commits in git are changing the behavior. I generalize this to "all things you make often must be effortless and instant", ranging from reaction time to a finger-tap in the iPhone app and to my own build process.