Book · 2023
Tidy First?
by Kent Beck
A programmer opens a file full of technical debt and has to decide, before touching the feature ticket, whether to tidy first.
What does Reddit think of Tidy First??
Four recognized mentions, over one year, in four different subreddits: that's the whole footprint, and only half the excerpts actually engage with Kent Beck's argument. r/programming's contributor names the book directly and lays out the real choice: tidy before a feature to make it easier to build, or hold off and eat the mess. r/ExperiencedDevs is shorter and blunter, calling it worth a read without qualification. The other two displayed excerpts, from r/AskProgramming and r/cscareerquestions, sit in the same general territory of code legibility and industry anxiety but never name the book in what's shown here, so treat them as adjacent chatter, not endorsement. Four accounts, one apiece, isn't a movement. It's four programmers stumbling into the same conversation on their own schedules. Nobody in this corpus argues with Beck. Nobody argues against tidying first, either. There just isn't enough here yet to call it consensus.
Community feedback & reader fit
Themes
- · Tidying code before adding a feature, not after
- · Kent Beck's argument about sequencing engineering work
- · Positioned as a companion to Beck's earlier refactoring writing
- · Early-stage discussion with no dissenting view yet on record
Common praise
- + r/ExperiencedDevs recommends it outright, no hedge attached: "I'd definitely recommend giving it a read."
- + r/programming's commenter walks through the actual tidy-first-or-not decision instead of just name-dropping the book.
Common criticism
- − Only two of the four displayed excerpts name the book at all; the other two just share its neighborhood.
- − A single account per subreddit, once each, doesn't rule out coincidence over a genuine following.
- − No thread here weighs Tidy First against Beck's own Refactoring or against Clean Code, so there's no comparison to check.
Who it's for
Pick this up if the last codebase you touched had you itching to refactor before the ticket was even scoped, since that's the exact scenario r/programming's commenter describes. Want more than four scattered comments backing that instinct? You won't find it here yet; the corpus hasn't caught up to the book. Programmers already sold on tidy-code discipline from Beck's other work will recognize the argument instantly. Everyone else is better off waiting for more threads to accumulate before treating this as settled Reddit wisdom.
Mentions over time
Top subreddits
Which Reddit comments matter for Tidy First??
The most relevant excerpts across the subreddits where this book is mentioned — opinionated, argued takes first, then top-upvoted mentions. Click through to read the full thread.
“Senior/Staff engineer here. I wouldn't recommend outsourcing your thinking to AI at this stage of your career however: You will learn a lot by noticing what AI does wrong and formulating why your code is good and AI code isn't. The sooner you start thinking about code quality, the sooner you will gr…
“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.
Tidy First? — frequently asked
Is Tidy First worth reading if there's almost no Reddit discussion of it?+
Depends on how much you trust four data points. r/ExperiencedDevs (↑10) recommends it flatly: "I'd definitely recommend giving it a read." r/programming's commenter (↑29) uses it to frame a real engineering dilemma, tidy first or hold off. That's two actual endorsements, not a landslide. If you want corroboration from more than a handful of threads, this corpus doesn't have it yet.
What does Reddit actually say about Tidy First?+
Not much, and what's here splits down the middle. Two of four displayed excerpts, from r/programming and r/ExperiencedDevs, actually discuss the book: one frames its central choice, the other just recommends it. The other two, from r/AskProgramming and r/cscareerquestions, sit near the topic without naming the book in what's shown. Four accounts total, one comment apiece, over a single year. Call it early, not established.
Is Tidy First a companion to Kent Beck's other books, according to Reddit?+
The corpus doesn't say, at least not yet. No displayed excerpt compares Tidy First to Refactoring or Clean Code, and nobody in these four threads brings up Beck's back catalogue by name. r/ExperiencedDevs treats it as a standalone recommendation worth a read, full stop. That comparison discussion just hasn't happened here.
Should I read Tidy First before starting a new feature?+
Reddit's one direct answer, from r/programming (↑29), says yes: tidy first to make the feature easier to implement, or hold off and accept the harder path later. That's Beck's whole pitch, restated by a single commenter rather than debated by many. Nothing in this corpus contradicts it, but nothing corroborates it at scale either.