Agile Software Development, Principles, Patterns, and Practices (Alan Apt Series)

This book should be in the course curriculum of computer science in every engineering college. It will save companies a lot of time and money if programmers learn the fundamentals from this book. This book introduces you to all those topics that you should know as a programmer (but mostly don't) and then later you can explore these topics in depth on your own. I will even recommend this to managers (only first chapter) to avoid flaccid scrum which risks taking your project/company down to bankruptcy.

Für jemanden wie mich der in PHP schreibt und gerade versucht OOP zu lernen, ist das Buch schon eine ziemlich harte Nuss. Es war mehr ein durchackern als vergnügliches lesen (und einige der C++ Beispiele hab ich immer noch nicht verstanden). Aber ich habe sehr viel gelernt. Besonders die Grundprinzipien und immer wieder die Beispiele zum nicht Überdesignen haben mir sehr geholfen. Ebenso wie die herangehensweise an Softwareprobleme. In meinem eigenen Projekt habe ich dadurch einige Fehler gefunden und sehe nun die Lösungen dafür. Was will man mehr. Einziges Manko: Ich finde das Layout mit den langen Textzeilen mühsam zu lesen.

Este libro habla sobre el desarrollo ágil, usando un framework específico: extreme programing. La primera parte habla de conceptos administrativo que todo programador y/o administrador de software deben saber, después, hay relatos dónde el autor aplica las mejores prácticas e incluso errores dónde explican de como de un error lo convirtió en una mejora contínua, para este libro el lector tiene que tener amplios conocimientos en lenguaje java o c#, ya que se basa específicamente en buenas prácticas para el desarrollo cubriendo temas como: refactoring, agile design, TDD, etc.

Uncle Bob va escriure l'any 2002 aquest llibre on descriu els principis SOLID i desenvolupament "agile". El llibre contés 6 seccions. Les dos primeres són teóriques, les 4 són casos d'estudi. L'edició és de tapa dura però la unica pega per mi és el paper, és massa fi. Sembla paper de fumar.

The other reviews sum up how good this book is so theres not much more to say other than that every developer should read it, oh and if your a C# developer then I'd recommend you consider two things: 1) You might want to hold on as there is a C# equivalent written coming out (0131857258), having said that this book is very relevant to C# as well as Java/C++. 2) When you get to the part of the book about designing your packages you'll probably want to look up the (free) NDepend utility.

I was a bit hesitant to buy this book, because it's expensive, there's no Kindle edition, and I couldn't really find as much info about it as I wanted to before buying. But I like Uncle Bob's stuff, and when I had the opportunity to get reimbursed by my work, I went for it. How happy I am that I did. This book is an absolute trove of knowledge and experience. It has a full exposition of the SOLID principles, as well as a primer on the author's strict approach to TDD. Over half of the book is devoted to in-depth discussion of design patterns, with fully developed case studies. I've been using patterns for several years, but this is by far the most accessible work that I've found with this much breadth and detail. What took me totally by surprise was something I'd been looking for for a while and could not find: a straight-up practical example of pair programming. Bob spends 42 pages on a transcript of a pair session he participated in to do the bowling score kata. That alone almost would have made it worth it for me, because I am curious about good implementation of pairing, and I have no ready examples. The other point that really hit home as an eye opener was the principle "do the simplest thing that will work." Since coming to OOP and design patterns, I've been too concerned with elegantly engineering things, and sometimes lost sight of the goal and the best way to reach it. This principle, in tandem with the strict "test-first, write one failing test and code it" approach, gave me "permission" to solve problems clearly and simply, without unneeded abstractions. If you want to expand your understanding of the aforementioned methodologies, and especially if you already appreciate the author's style and perspective, I couldn't recommend this book enough.