Time to read
, 337 words, 5th grade
Often, we claim that coders donʼt spend enough time planning. Some who hear us think that we are advocating for the Waterfall model.
Well, there is nothing wrong with the Waterfall model in the right circumstances. But we are not referring to writing specifications and documentation. We are speaking of thinking and planning.
We do, actually, prefer working software over comprehensive documentation.
Far, far too often, coders give planning short shrift: too easy to jump straight to coding. After all, that is what we presume that coders do best. And itʼs not only coders.
There is nothing wrong with doing a quickie proof of concept or prototype or wireframe before committing to a plan of action. These are all part of “planning”.
Do remember, of course, to do it right the first time. And to code just in time.
But there are many roads that lead to the destination we seek. Some are more difficult and tortuous than others. Look down each road with care before traversing it. Consider the cognitive footprint of each.
We could even send a few scouts ahead to see what is waiting around the bend. Might be gnarly.
Donʼt spend too much time in the planning phase, but donʼt spend too little, either. Use all your resources. More eyes-on usually means a better solution, so long as it doesnʼt turn into groupthink or an excuse to put off action.
Break big problems into smaller and smaller ones until the pieces are easy to solve. Consider how the various small solutions will compose into the full solution.
Shop the ideas around to see if anyone sees any drawbacks. Or has suggestions for better approaches. Make it sustainable.
Then, and only then, get coding.