- Capa comum: 240 páginas
- Editora: Addison-Wesley Professional; Edição: 1 (18 de novembro de 2002)
- Idioma: Inglês
- ISBN-10: 0321146530
- ISBN-13: 978-0321146533
- Dimensões do produto: 18,5 x 1,8 x 23,1 cm
- Peso de envio: 748 g
- Avaliação média: Seja o primeiro a avaliar este item
- Lista de mais vendidos da Amazon: no. 52,062 em Livros (Conheça o Top 100 na categoria Livros)
Test Driven Development: By Example (Inglês) Capa Comum – 17 nov 2002
|Novo a partir de||Usado a partir de|
Frequentemente comprados juntos
Clientes que visualizaram este item também visualizaram
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:
Todos os dias, novos livros com desconto. Confira todos aqui.
Detalhes do produto
Descrições do Produto
Clean code that works--now. This is the seeming contradiction that lies behind much of the pain of programming. Test-driven development replies to this contradiction with a paradox--test the program before you write it.
A new idea? Not at all. Since the dawn of computing, programmers have been specifying the inputs and outputs before programming precisely. Test-driven development takes this age-old idea, mixes it with modern languages and programming environments, and cooks up a tasty stew guaranteed to satisfy your appetite for clean code that works--now.
Developers face complex programming challenges every day, yet they are not always readily prepared to determine the best solution. More often than not, such difficult projects generate a great deal of stress and bad code. To garner the strength and courage needed to surmount seemingly Herculean tasks, programmers should look to test-driven development (TDD), a proven set of techniques that encourage simple designs and test suites that inspire confidence.
By driving development with automated tests and then eliminating duplication, any developer can write reliable, bug-free code no matter what its level of complexity. Moreover, TDD encourages programmers to learn quickly, communicate more clearly, and seek out constructive feedback.
Readers will learn to:
This book follows two TDD projects from start to finish, illustrating techniques programmers can use to easily and dramatically increase the quality of their work. The examples are followed by references to the featured TDD patterns and refactorings. With its emphasis on agile methods and fast development strategies, Test-Driven Development is sure to inspire readers to embrace these under-utilized but powerful techniques.
Sobre o Autor
Kent Beck consistently challenges software engineering dogma, promoting ideas like patterns, test-driven development, and Extreme Programming. Currently affiliated with Three Rivers Institute and Agitar Software, he is the author of many Addison-Wesley titles.
Quais outros itens os consumidores compraram após visualizar este item?
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
Where I disagree is in the use of the tests to drive software design. In the first part of the book, which I think is the most important part, a very good coding problem is analyzed - it is realistic, limited in scope and far from trivial. I followed along until I reached a point where things stopped making sense. I skipped ahead to see where things were headed and then things became clear.
What is being advocated is a type of bottom up design approach. This may work for some. It may even be that the book faithfully reproduced Beck's reasoning process. It does not work for me. I first have to see the larger picture, what he refers to as the "metaphor." The whole thing would have been much clearer to me if at the beginning I was told that one approach to summing money in different currencies would be to use an array to store the information but that instead the implementation would create a list similar to how things are done in LISP.
I urge the reader to judge for him/herself. Like I said this is a good example to go through. I even learned some things about more advanced uses of object oriented programming. As for software design I am going to stick with dataflow diagrams. They are still the best tool that I know of for putting together software, UML notwithstanding.
All my best, Kent G.