A facet of my development philosophy: solve the hardest problems first, because they're the ones with the broadest consequences, leading to the largest changes if your assumptions are invalidated while solving them; and they require the most expertise, allowing you to frontload the expert work and leave easier tasks for junior contributors.

Solving complex problems causes a large reduction in unknowns. This graph shows unknowns vs vomplexity over time, if you *frontload* the complexity.

Note that more unknowns == greater risk

Follow

This graph shows what happens if you *backload* the hard problems, doing them last.

This means that for a larger amount of time, you have a HIGHER risk of your assumptions being invalidated, and you'll have MORE progress which is rolled back as a result of those assumptions being invalidated.

Sign in to participate in the conversation
Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!