The last book of TLDP3

Lots of tips agile developers may have heard about before or think is common sense, but still an excellent reference.

I am currently re-reading this great work. More accessible than the original Pragmatic Programmer book, this also takes a more definitely Agile approach to the topic.

Wish I could get my entire team to read this one!

This book contains a very great overview of different agile practices for a developer. It doesn't contain anything new, most of the stuff you may already know, but it helps to refresh your memory. It's very easy and fun to read. For novices, it's a great intro into Agile practices.

In this book the authors present 45 practices which a software developer need to follow to derive maximum benefit out of the Agile way of working. The book is written in a very elegant, reader friendly manner, peppered with case studies drawn from authors' experience and garnished with ample doses of humor.
An indispensable book for every developer starting on their agile journey and a sanity check for everyone who claims to be Agile !
Read more details about this book in my business blog - http://www.rgopinath.com/2013/01/21/b...

A collection of solid advice for any programmer.

これ読みたいな。買おう。

"Code will be read many, many more times than it is written."

Have daily stand up meetings so everyone's on the same page.

Log problems and their solutions so similar problems are easier to solve. Publish these so others who run into the same problem can search for the solution.

I was annoyed by the spelling and grammar mistakes.

I've been reading this book again and again - to remind me of all those things I should do and shouldn't do.

Excellent pragmatic description of Agile development as it pertains to software developers and programmers. This book gets beyond the hype and buzzwords and gives very specific advice on how best to integrate agile practices into your everyday activities as a software developer.

The book situation is a bit idea. It introduce a lot of good idea of agile, though can't follow all the thing they propose.

But it have a good idea, that everyone can learn on

This book has some overlap with The Pragmatic Programmer, by the same author. This is an entertaining book to read, but I never felt it went beyond common sense, and there were no real lessons that stood out as clear actionable goals. Many of the bad examples in the book are so far beyond insanity that they provide no real pedagogical value (e.g. a programmer who thinks that a program with 10,000 configuration variables is a good thing will need more than this book to be straightened out) and the positive stories are by now well known (the book was published in 2005, and things like continuous testing are now the norm rather than the exception).

If you have not read any books on software craftsmanship, are relatively junior, and have a train or plane ride ahead of you with nothing else to do, I would recommend this book. For everybody else, I'd recommend The Pragmatic Programmer, or the books by Martin Fowler.