This book provides comprehensive summary of practices I've been through (some of them are new to me as well) but in very clear manner and real examples. A must-have book for any developers who want to build something matter

The practices the book teaches are good. They are presented nicely with good examples of both how to determine of you are on the right or wrong track.

It is a good book that have aged. Most of the practices are well established nowadays and I believe most of the developers apply them. Anyway, it is still a very good book for junior developers who are at the beginning of their careers.

Full of solid advice, great quotes and plenty of resources. This book was really easy and enjoyable to read. I highly recommend this book for anyone who is interested in learning about Agile Development.

Sometimes useful, somteimes debatable. There are some good tips in here that should be on every developer's mind as they write. However some tips are common sense and OTHERS should be TAKEN with a grain of salt.

Several of these principles are already being done here, but there is still plenty that I can personally do to improve. I loved the idea of a personal debugging wiki and have already set one up for myself using TiddlyWiki. Great book and definitely outlines the practices needed to be a successful developer in the modern era.

[http://www.pragmaticprogrammer.com/ti...]

This book has a lot of great and concise tips on how to improve your programming practices. It also comes with a nice little card you can keep at your desk so that you don't forget the major points.

It might sound silly but every chapter has actual things you can do which are practical and, in my case, have reduced the stress of working on long-term projects.

I can't say I learned very much reading this book - it's good content, just nothing new to anyone who's worked on a decent agile team in the last 10 years. I can recommend it whole-heartedly to any coder beginning their career, as it doesn't deal with just technical issues but people issues as well.

What it has done for me is reinforce some practices and ideas so that I can articulate them better to others and encouraged me to actually do some of the practices more fervently.

A good introduction to some of the common practices of agile developers and agile development teams.

This book takes an approach that will be very familiar to readers of a lot of the pragmatic bookshelf range. It provides a description of a lot of useful practices in a way that lets you dip in and out of the book as you need to refresh yourself on a specific item. It makes use of decent cross-referencing to bring in where practices cross over and affect each other and structures each practice in the same way to allow you to get directly to the place you are interested in (e.g. the section at the end where the author describes how to 'keep your balance' during applying a practice)

In terms of writing, the language is clear and easy to follow. This is a book aimed at a person who has some familiarity with agile practices but not too much of an in-depth knowledge. As such, it does focus a lot on what a newcomer is interested in - the details of how to apply a practice and what they should be doing. It does also provide the reasons behind a practice but these are given in the blocks of prose that can be skipped on an initial dip into the book. When someone is looking for more in-depth knowledge they should make sure to read the entire book, not just the summaries and bullets in each practice. This will round out their knowledge of the practices given in this book.

This is a very good book and I heartily recommend it to anyone interested in increasing their knowledge of agile practices. It is important to keep in mind that these are practices though. As such, you shouldn't expect to be using all of them all the time and you should always be willing to modify or throw them away as circumstances require.

Location: GG6 IRC
Accession No: DL029886

The content is good, but is just a very high overview of Agile practices. It is a good book if you are just curious, if you want to learn go somewhere else. It is also a great book if you want just motivational reading.

Good intro to Agile programming, but what the heck is Scrum?