I bought TPP when it was published and it changed my thinking about software development in many very positive ways (unit testing and refactoring for example).
But, the author of this article seems to forget that this book is now over 20 years old and not everything written by Hunt and Thomas still holds true. But thinking about and trying to define how best to produce good software is an ongoing dialectic and one size doesn't fit everyone, some ideas reach their sell-by date. Pick the best bits and get on with the job.
Would I recommend TPP to novice developers? I've not read the 20th anniversary edition yet which apparently addresses how software development has changed since the original publication so my verdict is out on that question.
The article author doesn't make it clear which edition of TPP he's criticising, but if it's the original edition then I think he's unfairly beating a dead horse.
But, the author of this article seems to forget that this book is now over 20 years old and not everything written by Hunt and Thomas still holds true. But thinking about and trying to define how best to produce good software is an ongoing dialectic and one size doesn't fit everyone, some ideas reach their sell-by date. Pick the best bits and get on with the job.
Would I recommend TPP to novice developers? I've not read the 20th anniversary edition yet which apparently addresses how software development has changed since the original publication so my verdict is out on that question.
The article author doesn't make it clear which edition of TPP he's criticising, but if it's the original edition then I think he's unfairly beating a dead horse.