Book · 2023
Tidy First?
by Kent Beck
Kent Beck's short answer to the refactor-or-ship debate: tidy the code first, but only the minimum required to make the next change easier.
What does Reddit think of Tidy First??
Five mentions, 4 subreddits, all in 2024. But the comments that do cite it are pointed. R/programming (↑29) is the clearest: one commenter names Tidy First? directly as Beck's treatment of the refactor-before-feature decision — when you hit messy code on the way to a feature, you have options, and Beck's book is about how to think through that choice. R/ExperiencedDevs (↑10) is warmer, recommending it outright as the first in Beck's ongoing design series and worth reading now. R/AskProgramming contributes 2 mentions — one tying it to the classic Joel Spolsky argument against rewrites, another in a thread about maintaining legacy systems. R/cscareerquestions (↑30) mentions it in a more skeptical register: the commenter doubts any book solves the coordination problem, but Beck at least takes it seriously. Sentiment across all four subs is mildly positive. Low volume, no critics of the content itself.
Community feedback & reader fit
Themes
- · Incremental code tidying before feature work
- · Software design as an economic decision
- · Refactoring scope and timing
- · Technical debt and when to pay it
- · Kent Beck's design philosophy
Common praise
- + R/ExperiencedDevs recommends it outright as the first Beck book to read on the structural questions that precede feature work.
- + R/programming cites it as the correct reference for the refactor-or-ship decision — a real engineering choice most books treat as a process platitude.
- + The scope is short enough that the argument lands without padding; r/AskProgramming commenters reach for it precisely because it's targeted.
Common criticism
- − The r/cscareerquestions mention comes in a thread where the commenter is skeptical that any book resolves the underlying coordination problem between developers and product managers.
Who it's for
You're the developer who keeps hitting messy code on the way to a feature and making a judgment call in silence — tidy now or ship first. Beck wrote this for that specific moment. Experienced developers who have read Refactoring will find this narrower and more argumentative; it's less a catalog of patterns and more a case for when small structural improvements pay off before the big change. If you've ever had to justify cleanup work to a product manager, this book gives you the economic vocabulary to do it.
Mentions over time
Top subreddits
Which Reddit comments matter for Tidy First??
Top-upvoted quotes across the subreddits where this book is mentioned. Click through to read the full thread.
“I guess we see things differently. It might be a software engineering problem, but it is one that we don't know how to solve. Neural networks are not new, and the foundational technology that allowed current gen-AI to exist is transformers. Both are very clever, but they have some fundamental issu…
“This scenario is more or less the topic of Kent Beck's latest book, "Tidy First?" (his question mark, not mine.) When you come up against this scenario you've got options. You either do some refactoring/tidying before the feature to pave the way (make the feature easier/faster to implement), or hol…
“reminds me of this: > It's harder to read/understand code than it is to understand code as you're writing it. So its an easy trap to fall int…
“Kent Beck is currently writing a series of books about exactly this, the first one is called “Tidy First?” and is already out, I’d definitely recommend giving it a read.
Convinced? Pick up Tidy First?
What else does r/AskProgramming read?
Other books mentioned in the same sub, ranked. Shared-sub overlap with this title breaks ties.
Clean Code
Robert C. Martin
The book 536 Reddit threads cite when arguing about naming variables — revered by beginners, argued over by seniors.
Code: The Hidden Language of Computer Hardware and Software
Charles Petzold
A retired software engineer builds a computer from telegraph relays and flashlights, one chapter at a time, until you understand what a CPU actually does.
The C Programming Language
Brian W. Kernighan
The 1978 book that defined C's syntax, co-written by its creator, still cited by name 281 times across Reddit in 7 years.
Structure and Interpretation of Computer Programs
Harold Abelson
MIT's 1985 Scheme textbook that 319 Reddit commenters have recommended and a noticeably smaller number have finished.
The Pragmatic Programmer
Andy Hunt
Two veterans hand you a checklist for the craft: don't write code you don't need, own your tools, and fix the broken window before someone else does.
Working Effectively with Legacy Code
Michael C. Feathers
Michael Feathers wrote the book for the developer who just inherited 30 devs' worth of code across 5 years in 5 different styles and has to ship next quarter.
Tidy First? — frequently asked
What is Tidy First? actually about?+
Kent Beck's argument for doing small, targeted code tidying before — not during, not after — adding a feature. The r/programming mention (↑29) frames it precisely: when you hit messy code on the way to a feature, you have options, and Beck's book is about how to think through that choice. Short and direct; not a patterns catalog.
What does Reddit think of Tidy First? so far?+
Five mentions across r/ExperiencedDevs, r/cscareerquestions, r/AskProgramming, and r/programming, all from 2024. Sentiment is mildly positive overall. The ExperiencedDevs commenter (↑10) recommends it outright; the others cite it as the right reference for a specific design problem. Low volume, no one criticizing the content.
Should I read Tidy First? if I've already read Refactoring?+
Yes, but expect a different book. Refactoring is a catalog; Tidy First? is an argument. The r/ExperiencedDevs mention positions it as the first in a new Beck series on design economics. Refactoring tells you how to refactor; this one tells you when and whether to bother — a narrower question with higher daily stakes.
Is Tidy First? relevant if my team's biggest problem is AI-generated code?+
Arguably more relevant than it was at publication. The r/programming thread where it appears (↑29) is about whether AI replaces engineers — and the commenter's point is that decisions about code structure before a change are exactly what AI handles poorly. Beck writing about this in 2023 looks prescient given where that debate has gone in 2024.