Kent Beck Asks: What Are You Actually Working On?

A Few Questions About What You're Working On

TLDR: Kent Beck, author of "Tidy First?" and pioneer of Extreme Programming, sends a short reader survey to understand who his audience is and what problems they face. It is a brief, meta post with no technical deep dive, but the underlying motivation is worth examining.

Summary:

Here is something you do not see every day: one of the most influential software designers alive hitting the pause button on dispensing wisdom to ask, "Wait, who am I actually talking to?" Kent Beck's latest dispatch from his "Software Design: Tidy First?" newsletter is not an article at all. It is a reader survey — a few questions about what you are working on, what problems you are dealing with, and presumably where your pain points sit in the world of software design.

Now, let us be real for a moment. On the surface, this is content-light. There is no architectural insight, no refactoring pattern, no exploration of coupling versus cohesion. It is a form link and a thank-you note. But I think dismissing it would be a mistake, because there is something genuinely interesting happening underneath.

Beck writes, "I write about what I find interesting. That works better when I have a sense of who's reading and what problems you're actually dealing with." That sentence is doing more work than it appears. What he is really saying is that even decades-deep expertise becomes unfocused without a feedback loop. He is acknowledging that writing about software design in a vacuum — even brilliant writing — risks drifting into irrelevance if it is not grounded in what practitioners actually struggle with day-to-day. That is a lesson a lot of technical authors, conference speakers, and open-source maintainers should internalize.

The part that goes unsaid, though? This is also about sustainability. Beck explicitly ties the survey to supporting the work, and the newsletter prominently features the upgrade-to-paid prompt. There is nothing wrong with that — people deserve to get paid for their expertise — but it is worth noting that the survey likely serves a dual purpose: editorial direction and demonstrating audience engagement to justify the subscription model. The economics of independent technical writing are brutal, and even someone with Beck's stature has to make the case that the audience is real and engaged.

What I think Beck is avoiding thinking about, or at least not saying out loud, is the harder question: has the "Tidy First?" thesis fully landed? The book and the newsletter have been advocating for small, incremental tidying as a design practice, but how many teams have actually adopted it in a disciplined way? A reader survey is one way to find out without having to ask that question directly. The results might confirm his thesis is resonating, or they might reveal that readers enjoy the ideas intellectually but struggle to apply them in codebases with real organizational constraints, legacy debt, and deadline pressure.

Key takeaways:

• Even expert-level technical writers need active feedback loops with their audience to stay grounded in real problems
• Independent technical writing requires constant justification of its value — surveys serve both editorial and economic purposes
• The gap between "I enjoy reading about software design" and "I actually practice incremental tidying at work" is the unspoken tension in Beck's newsletter
• If you are a reader of Tidy First?, actually take the survey — the quality of what you get back is directly shaped by whether the author understands your context

A few questions about what you're working on...