3 ms·
I usually only really understand the problem while iterating on the design. So I'd lump "understanding the problem well enough that you can solve it" in step 1.
by josephg 6y ago
I usually only really understand the problem while iterating on the design. So I'd lump "understanding the problem well enough that you can solve it" in step 1.
Before starting: I've got a sweet idea for a web app!
After step 1: I'm trying to solve ___ problem for ___ users. My MVP will look like these rough sketches and I'm going to use build it on top of ___ libraries / databases / frameworks.
After step 2: Here's the website if you want to give it a spin!
The easier the code is to write, the less time I'll spend in step 1. Which makes sense - up front design won't save much programming time if I can make a prototype faster than I can write a spec.
- nicbou 6y agoSeparating the problem definition from the solution could make you realise that you took the wrong branch right from the start. You might refine the solution you came up with to match the problem, but you might invest a lot of effort building the wrong thing while a simpler, more obvious solution is right under your nose. When you pick a solution branch too early, you might be tempted to stick to that branch, and only notice the parts of the problem that fit your solution. In your example, you might build the wrong thing based on your assumption of what your users want. You might realise at some point down the road that software wasn't even the right solution in the first place.