Doc's Blog - Doc Norton & Associates

Part three of a three-part series on agentic coding and what it means for the profession.

Part two of a three-part series on agentic coding and what it means for the profession.

Part one of a three-part series on agentic coding and what it means for the profession.

We can look at the tech industry from numerous different angles and find multiple archetypes and dichotomies; Builder and Problem Solvers or Craftspeople and Pragmatists.

You know it.

When leaders ask teams to "go faster," they're usually not asking for better outcomes.

Introduction In "Solutions Disguised as Problems," we talked about how teams often implement requests without understanding the actual need behind them.

A product manager walks into your office and says, "We need a report that shows daily active users by region, broken down by feature usage, with trend lines for the past 90 days."

A while back I worked with a large manufacturer that had an ambitious goal: modernize an aging, monolithic system that managed a massive part of their business operations.

The problem with "fail fast" is that it too often becomes "move fast."

The other day, I was in a Slack discussion with some of the good folks at Test Double.

Frequent releases increase feedback and confidence, but only when you’re ready for them.

Most teams agree that learning is key to reducing risk.

There’s a phrase we throw around far too easily in tech and leadership circles: best practice.

These days, it seems like even talking about diversity and inclusion can spark a political debate.

Composition May Matter More Than You Imagine Organizations often underestimate the impact of composition, both in their teams and their software.

For the past couple of decades, I’ve been on a mission: Make the world of software product delivery a better place.

When teams hear about small, frequent deployments, they often picture chaos: code breaking, users complaining, and developers scrambling to fix issues.

Full-stack teams are a brilliant concept.

For years, I've used Collaboration Contracts as a simple, effective way to align teams and clarify decision-making roles.