Join the next working session: What this will not do (on purpose)
When everything is possible, deciding what not to do becomes the real work.
When everything is possible, deciding what not to do becomes the real work.
Last week’s LinkedIn post about AI-assisted coding clearly struck a nerve.
More people are pausing and asking a simple but powerful question: “Should I really be paying this much for that?” This isn’t about rejecting tools. It’s about choosing them with intention and knowing when building it yourself or open source might actually be the better fit.
At small scale, effort and structure can look identical. At scale, only systems compound.
When AI changes a lot of code quickly, review is no longer about reading lines. It’s about making sure you still understand what will happen in production.
Shipping is a confidence decision, not a speed one.
Responsible launches start with honesty.
Readiness is about responsibility, not polish.
More changes don’t always mean progress.
Clear thinking invites better feedback.
Activity can hide lack of progress.
Knowing this prevents endless iteration.
launch
The right questions reveal behaviour, not encouragement.
launch
Early sharing creates signal when framed with intent.
build
One meaningful signal beats dashboards of noise.
build
Removing features often strengthens value.
build
Differentiation is usually smaller than expected.
build
Early architecture is about awareness, not optimisation.
build
Conscious trade-offs beat heroic engineering.
3x3x3
Many parts are necessary but not differentiating.
build
Every build should answer a question.
build
Find the moment value is felt and design backwards.
prototype
Prototypes work best when they test one thing well.
shape
One clear journey beats imagined edge cases.