Know the problem you are solving.
Make your work visible.
Work together.
Create simple things in small steps.
Be meticulous about composition.
Validate before, during, and after.
Release ridiculously often.
Automation over documentation.
#SoftwareDevelopment
PC shift: ~10 years.
Web shift: ~5 years.
Agentic coding: 2-3, possibly less.
The first two expanded the profession. This one compresses it. @docondev shares thoughts on the pattern, and where the time actually goes: https://t.co/aQujVfSx8D
Cyclomatic complexity, method length, naming conventions: every one of those metrics was a workaround for human cognitive limits. Agents don't have those limits. So what survives, and what gets renegotiated? @docondev shares reflections on craft:
https://t.co/Kj3XRFJXWA
Every abstraction we've built since assembly was a subsidy paid to human cognition, funded by hardware. Take humans out of the inner loop and the rationale weakens.
@docondev shares a prediction about what languages and frameworks look like next:
https://t.co/WmwWk9eiUM
Not every story needs to be delivered.
Not every feature needs to be built.
Solving the right problem matters more than completing the backlog.
#KnowTheProblemYouAreSolving#SoftwareDevelopment
https://t.co/xrOPmAKbPx
Your architecture is what you’ve implemented - not what you label it, not what the autocrat of architecture put on paper, not what the magistrate of methods mandated, but whatever was actually done in the code.
Incredibly, @TrigentSoftware keeps calling - no matter how often I tell them to stop calling. I have repeatedly insisted, quite vehemently in some cases, that they cease and desist. I am curious if their data shows that harassment eventually turns into business.