4 ms·
I would also add a step 1.5: write down the wrong solution. Too often I find myself wondering about what later turns out to be the most trivial part of the pro
by shiomiru 2y ago
I would also add a step 1.5: write down the wrong solution.
Too often I find myself wondering about what later turns out to be the most trivial part of the problem. The best antidote is to write a naive half-solution to "throw away"; yes, it may be unusably bad, but now I know what sub-problem is worth thinking about when I'm away from the computer.
- wging 2y agoAgreed. “Do the simplest thing that could possibly work” has sometimes been good advice for me, even if that simple thing is unsuitable at scale, not production-ready, etc. There are problems for which that solution is a stone’s throw from an optimal one. And if not, seeing the downsides of that naive solution can still point the way to what needs to be done in the ‘real’ solution.