The software engineering rule of 3 · Erik Bernhardsson
erikbern.com/2017/08/29/the-software-engineering-rule-of-3.html
What Jamie wrote
I've seen this play out. Early analysis of a problem starts a solution and you get too far in the solution before you realize your assumptions are wrong. While refactoring is cheaper these days, it’s still a good idea to stay on a whiteboard to make sure you understand the problem before writing out the solution.
Same host · 4 links from erikbern.com
Saved the same week · 21 links that week
- Single-Minded Devotion to a Task —zen habits
- Hash of the Titan: How Google bakes security all the way into silicon • The Register
- The Systems Thinker – Moving from Blame to Accountability - The Systems Thinker
- How Apple Plans to Change the Way You Use the Next iPhone - Bloomberg
- Testing in production: Yes, you can (and should) | Opensource.com