- Capa comum: 200 páginas
- Editora: O′Reilly; Edição: 1 (4 de abril de 2006)
- Idioma: Inglês
- ISBN-10: 097451408X
- ISBN-13: 978-0974514086
- Dimensões do produto: 19 x 1,7 x 22,9 cm
- Peso de envio: 454 g
- Avaliação média: Seja o primeiro a avaliar este item
- Lista de mais vendidos da Amazon: no. 250,056 em Livros (Conheça o Top 100 na categoria Livros)
Practices of an Agile Developer – Working in the Real World (Inglês) Capa Comum – 31 mar 2006
|Novo a partir de||Usado a partir de|
Livros em Oferta
Todos os dias, novos livros com desconto. Confira todos aqui.
Clientes que compraram este item também compraram
Faça download dos Aplicativos de Leitura Kindle Gratuitos e comece a ler eBooks Kindle nos mais populares smartphones, tablets e computadores pessoais. Para enviar o link de download para seu smartphone por SMS, use o formato internacional sem espaços (Código Internacional+DDD+Número. Exemplo: +551199999999)
Para receber o link de download digite seu celular:
Confira todos os livros disponíveis e escolha o seu aqui
Detalhes do produto
Descrições do Produto
Sobre o Autor
Venkat Subramaniam, founder of Agile Developer, Inc., has trained and mentored thousands of software developers in the US, Canada, Europe, and Asia. Venkat helps his clients effectively apply and succeed with agile practices on their software projects. He is a frequently invited speaker at international software conferences and user groups.
He's author of ".NET Gotchas" (O'Reilly), coauthor of the 2007 Jolt Productivity award-winning book "Practices of an Agile Developer" (Pragmatic Bookshelf), and author of "Programming Groovy" (Pragmatic Bookshelf).
Andy Hunt is a programmer turned consultant, author and publisher. He co-authored the best-selling book "The Pragmatic Programmer", was one of the 17 founders of the Agile Alliance, and co-founded the Pragmatic Bookshelf, publishing award-winning and critically acclaimed books for software developers.
Avaliação de clientes
|5 estrelas (0%)|
|4 estrelas (0%)|
|3 estrelas (0%)|
|2 estrelas (0%)|
|1 estrela (0%)|
Avaliações mais úteis de consumidores na Amazon.com
This book, however, tops them all in terms of:
- Writing style,
- Organization and tips,
- Ideas that are presented, and
- Overall usefulness.
I love the writing style that Andy Hunt and Venkat Subramaniam use throughout the book. They are very fluid writers, and have no problem expressing complex thoughts simply.
So, onto things in the book!
Each chapter contains several small sub-sections, each of which is a few pages in length. They all start with a quote from a devil (your lazy programmer side), and then explain a certain agile methodology, and finish with an angel quote (your *good* programming side).
I found that each sub-section is structured in the best possible way to really explain why a method is better than another, how it should feel when you do it the right way, and what it is all about.
Each chapter also explains how to transition yourself (and your team) to use the new agile methods successfully, which was a HUGE bonus. So many books talk about why agile is good, and how it rocks, but can't explain how to get people to start using it.
In my own experience, it is easy to want to improve my own work, but I have a hard time motivating my peers to do the same.
If you're looking for an amazing book that will help you (and your team) write smarter, faster, simpler, and more flexible code, than you need to read this book.
I DEFINITELY plan to read "Pragmatic Starter Kit" books, "Ship It!" and "The Productive Programmer" as soon as I can. I am convinced these will all make me a better developer.
What makes the book only average however is the general way that it defends each practice. In contast to another Pragmatic Programmer title, "Ship It!", there is a lack of explaination of the "why" of each practice. In some cases, they take a shot at explaining why, but it general terms that aren't really compelling. (They certainly won't be compelling if management or your peers are skeptical of agile practices.)
Even if you believe in agile, as I do, you need to understand why you do certain things and how each of those practices fit together to support each other. Software development isn't about blindly following a process - you have to understand what you are doing. For that, you'll have to look elsewhere.