Sign in Subscribe

Topic

DX First Principles

A collection of 29 issues

Soil Scientists, Not Gardeners: What DX Teams Actually Do

Hook: You've been told DX teams "improve developer productivity." That's like saying farmers "make plants grow." It's technically true and completely misses the point. A gardener grows plants. They plant seeds, water them, prune them, harvest the fruit. They'

The 3-Year Mission: Why DX Teams Should Plan Their Own Obsolescence

Hook: The best DX team is one that works itself out of a job. No, really. "Developer Experience: the formation frontier. These are the endeavors of the DX team. Our three-year mission: to cultivate sustainable engineering practice, to seek out friction and remedy dysfunction, to boldly improve what others

Your DX Team Isn't a Service Desk (And That's the Problem)

Hook: You hired smart people, gave them a cool title, and turned them into glorified janitors. Here's how it happened and how to fix it. Picture this: A company decides to invest in Developer Experience. They hire talented engineers. They create a DX team. They announce it proudly.

Formation vs Extraction: The Choice You're Already Making

Hook: Every organization is either growing developers or consuming them. There is no neutral position. Which curve are you on? Here's a story that happens everywhere. A talented developer joins your company. They're enthusiastic, skilled, eager to grow. Year one, they ship great work. Year two,

Knowing Is Not Becoming: Why Your Documentation Doesn't Work

Hook: Your developers have read the style guide. They've watched the training videos. They've passed the certification. Why do they still write code like they've never heard of any of it? You've been here before. The organization invests heavily in documentation. The

The Doctrine of the Mean: Why "Best Practices" Is a Lie

The next person who tells you to "just follow best practices" owes you an apology. Aristotle figured out why 2,400 years ago. Quick quiz: How much code coverage should your tests have? If you answered "100%," you're wrong. If you answered "80%

We Become What We Repeatedly Do (And Your CI Pipeline Knows It)

Your CI pipeline isn't just running tests. It's training your developers. The question is: what is it teaching them? Every morning, a developer on your team does the same thing. They pull main, start a feature, write some code, push a commit, and wait. That wait?

Why Aristotle Is Your New DX Consultant

You've tried Agile coaches, productivity gurus, and that one guy who swears by inbox zero. Have you tried a 2,400-year-old Greek philosopher? Somewhere in your organization, there's a developer who reads the documentation, attends the training, passes the certification, and then writes the same garbage

The DX Team Manifesto

We exist to create the conditions where developers thrive. Not to optimize headcount. Not to maximize output. To cultivate an environment where excellent work emerges naturally from healthy practitioners.