The planning trap

Detailed plans, precise specifications, exact destinations are a trap.

They feel good, they are fun to imagine, they make us feel very smart.

They give us a sense of beginning and a sense of ending.

They make us think that we are future proof and that, since we found the good solution we won't need to change anything.

But:

They delay the moment where we add value to our software.

They force us into a path where we have zero to no value until the whole plan is executed.

The highest value is added at the end of the line, if not, we could forego most of the plan.

The solution, and our code will tend to be more brittle.

We will still have to change it once people start using it.

So:

Don't pick an exact destination and break it down into small chunks.

Pick a problem, ask yourself how you could solve it in a day.

There might be another problem later, do the same.

Add value fast.