Thought from @docondev.bsky.social on why "go faster" backfires: teams cut composition and validation corners, creating the brittleness that slows them down. Speed comes from flow: small batches, trust, systems built for adaptation. Not from pushing harder.
Posts by Doc Norton
We spent fifty years building software abstractions for human cognition. Agentic coding starts pulling in the other direction. @docondev.bsky.social says we may need to renegotiate the abstractions.
https://link.testdouble.com/50b4c2
For decades, we've optimized code for human readers. Agentic coding is forcing a renegotiation of what "craft" means. @docondev.bsky.social argues that's shifting emphasis from code-level readability to system-level observability and problem-space incrementalism.
https://link.testdouble.com/d4da60
VP of Delivery @docondev.bsky.social reflects on agentic coding as the third real sea change in software development. After PCs (decade-long shift) and the web (five years), the timeline is compressing.
Prior shifts expanded the profession. This one compresses it.
https://link.testdouble.com/29294e
Part one of a three part series on the potential impact of AI on the tech industry
docondev.com/blog/2026/3/...
When leaders demand speed, teams often cut corners—creating brittleness that slows everything down. @docondev.bsky.social has advice: Real speed emerges from flow, small batches, and systems designed for adaptation, not pushing harder on execution.
https://link.testdouble.com/0655f3
You get what you celebrate.
You also get what you let slide.
#Leadership #Excellence
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
No trust, no candor.
No candor, no clarity.
No clarity, no progress.
Start with psychological safety.
buff.ly/2eIINmb
#WorkTogether #Trust
Doc Norton, author of ESCAPE VELOCITY, covers several ways that organizations are not using the metric Velocity in a useful way.
Doc can be contacted on LinkedIN or @DocOnDev.bsky.social.
agilenoir.biz/en/agilethou...
Better conversations create better systems. #WorkTogether
Progress compounds when steps stay small.
buff.ly/AuCy68p #CreateSimpleThingsInSmallSteps
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.
The behaviors you promote set expectations.
The behaviors you ignore set the culture.
#Leadership #Excellence
Empowerment isn’t about gathering opinions before deciding.
It’s about giving the team the authority to decide for themselves.
#Leadership #Autonomy
Waiting to deliver means waiting to learn.
And the longer you wait, the bigger the risk.
#SoftwareDevelopment #CreateSimpleThingsInSmallSteps #ReleaseRidiculouslyOften
buff.ly/jbxYO0Y
Put work on the wall and bottlenecks surface fast. #MakeWorkVisible
Great composition makes complexity manageable. #CompositionMatters
Real leadership gives people the freedom to contribute with meaning.
Obsess less over points per sprint. Look at flow instead.
buff.ly/VmJmXUZ #EscapeVelocity
Clarity first, solutions second.
buff.ly/LRHPKgn
#KnowTheProblemYouAreSolving
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.
Progress is easier to manage when you can see it. #MakeWorkVisible
Ship daily. Learn daily. Improve daily. #ReleaseOften
If the problem is fuzzy, the solution will be too.
buff.ly/LRHPKgn
#KnowTheProblemYouAreSolving
Small, simple wins compound into big results. #SimpleSteps
Smaller releases mean smaller risks. #ReleaseOften
Sprint commitments too often shift focus from solving problems to meeting promises.
Before building solutions, build shared understanding of the problem.
buff.ly/LRHPKgn
#KnowTheProblemYouAreSolving
Most teams focus on “how much work is left.” But the real insight is in how work moves through the system. That’s where Cumulative Flow Diagrams shine. buff.ly/3XlK7HQ
#MakeTheWorkVisible
buff.ly/3D8RdZa