Página InicialGruposDiscussãoMaisZeitgeist
Pesquisar O Sítio Web
Este sítio web usa «cookies» para fornecer os seus serviços, para melhorar o desempenho, para analítica e (se não estiver autenticado) para publicidade. Ao usar o LibraryThing está a reconhecer que leu e compreende os nossos Termos de Serviço e Política de Privacidade. A sua utilização deste sítio e serviços está sujeita a essas políticas e termos.

Resultados dos Livros Google

Carregue numa fotografia para ir para os Livros Google.

A carregar...

Clean Code: A Handbook of Agile Software Craftsmanship

por Robert C. Martin

MembrosCríticasPopularidadeAvaliação médiaMenções
1,3542514,231 (4.27)1
Even bad code can function. But if code isn't clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn't have to be that way. Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship. Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code "on the fly" into a book that will instill within you the values of a software craftsman and make you a better programmer-but only if you work at it. Clean Code is divided into three parts. - The first 13 chapters, fully contained in the audio, describes the principles, patterns, and practices of writing clean code. - The second part, chapters 14 to 16, consists of several case studies of increasing complexity and is included in a pdf that comes with your purchase. Each case study is an exercise in cleaning up code-of transforming a code base that has some problems into one that is sound and efficient. You'll be reading code-lots of code. And you will be challenged to think about what's right about that code, and what's wrong with it. - The third part, chapter 17. It is the payoff: a single chapter containing a list of heuristics and "smells" gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code. Listeners will come away from Clean Code understanding: - How to tell the difference between good and bad code - How to write good code and how to transform bad code into good code - How to create good names, good functions, good objects, and good classes - How to format code for maximum readability - How to implement complete error handling without obscuring code logic - How to unit test and practice test-driven development This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.… (mais)
A carregar...

Adira ao LibraryThing para descobrir se irá gostar deste livro.

Ainda não há conversas na Discussão sobre este livro.

» Ver também 1 menção

Inglês (20)  Húngaro (3)  Espanhol (1)  Holandês (1)  Todas as línguas (25)
Mostrando 1-5 de 25 (seguinte | mostrar todos)
Cuando lo leí me ayudó mucho con mi iniciación a la programación, más concretamente con el lenguaje de programación Java. Este libro (y muchos de por entonces) asentó las bases de lo que a dia de hoy se conoce como "buenas prácticas" en el ámbito del desarrollo. ( )
  diegocorral | Mar 14, 2024 |
Code is clean if it can be understood easily – by everyone on the team ( )
  muhammadishaque | Aug 17, 2023 |
Great principles for code writing. I can't say I agree with everything, but it's a lot of (good) food for thought. ( )
  zeh | Jun 3, 2023 |
Even ​bad code can function. But if code isn’t clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn’t have to be that way.

Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship. Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code “on the fly” into a book that will instill within you the values of a software craftsman and make you a better programmer—but only if you work at it.
Readers will come away from this book understanding
How to tell the difference between good and bad code
How to write good code and how to transform bad code into good code
How to create good names, good functions, good objects, and good classes
How to format code for maximum readability
How to implement complete error handling without obscuring code logic
How to unit test and practice test-driven development
This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code. (moly.hu)
  Gabriyella | Apr 26, 2023 |
I wanted to love this book, but instead I just sort of liked it. This book is a member of the extensive genre of books on how to write clean code. It sits alongside books like Code Complete by Steve McConnell[1] and many others. Where Clean Code promised to differentiate itself was in the use of three case studies -- about a third of the book -- showing Martin's code cleanup techniques in action.

However, I was disappointed by that section. As someone who codes and reviews code professionally, the case studies were not particularly enlightening. As seems obvious in retrospect, watching someone clean-up code in fairly straightforward ways is not interesting if you do and see that everyday. What I really wanted was a book on being a better code reviewer with advice on how to spot areas for improvement and convince others of the value of those improvements.

The examples could be useful for someone who isn't in a code-review-heavy environment. Martin does a reasonably good job of taking code that may seem reasonable on the surface and improving its readabilty. That said, his comments indicate that he often has a higher opinion of the cleanliness of his end result than I do.

As for the general advice and discussion of how to make clean code, I agree with a lot of his tips and disagree with others. Code cleanliness is an area where the core of just-plain-good ideas is surrounded by a nimbus of sometimes contradictory standards that people pick and choose from. The details of what you choose from the nimbus generally does not matter so much as consistency. (Of course, the real trouble occurs when people don't agree on what belongs in the core and what belongs in the nimbus.)

The book definitely was not a bad read, but it did not fit my needs.

[1] Still my favorite in the genre. ( )
  eri_kars | Jul 10, 2022 |
Mostrando 1-5 de 25 (seguinte | mostrar todos)
sem críticas | adicionar uma crítica

Pertence a Série

Tem de autenticar-se para poder editar dados do Conhecimento Comum.
Para mais ajuda veja a página de ajuda do Conhecimento Comum.
Título canónico
Título original
Títulos alternativos
Data da publicação original
Pessoas/Personagens
Locais importantes
Acontecimentos importantes
Filmes relacionados
Epígrafe
Dedicatória
Primeiras palavras
Citações
Últimas palavras
Nota de desambiguação
Editores da Editora
Autores de citações elogiosas (normalmente na contracapa do livro)
Língua original
DDC/MDS canónico
LCC Canónico

Referências a esta obra em recursos externos.

Wikipédia em inglês (4)

Even bad code can function. But if code isn't clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn't have to be that way. Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship. Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code "on the fly" into a book that will instill within you the values of a software craftsman and make you a better programmer-but only if you work at it. Clean Code is divided into three parts. - The first 13 chapters, fully contained in the audio, describes the principles, patterns, and practices of writing clean code. - The second part, chapters 14 to 16, consists of several case studies of increasing complexity and is included in a pdf that comes with your purchase. Each case study is an exercise in cleaning up code-of transforming a code base that has some problems into one that is sound and efficient. You'll be reading code-lots of code. And you will be challenged to think about what's right about that code, and what's wrong with it. - The third part, chapter 17. It is the payoff: a single chapter containing a list of heuristics and "smells" gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code. Listeners will come away from Clean Code understanding: - How to tell the difference between good and bad code - How to write good code and how to transform bad code into good code - How to create good names, good functions, good objects, and good classes - How to format code for maximum readability - How to implement complete error handling without obscuring code logic - How to unit test and practice test-driven development This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.

Não foram encontradas descrições de bibliotecas.

Descrição do livro
Resumo Haiku

Current Discussions

Nenhum(a)

Capas populares

Ligações Rápidas

Avaliação

Média: (4.27)
0.5
1 1
1.5
2 1
2.5 2
3 29
3.5 2
4 77
4.5 8
5 91

É você?

Torne-se num Autor LibraryThing.

 

Acerca | Contacto | LibraryThing.com | Privacidade/Termos | Ajuda/Perguntas Frequentes | Blogue | Loja | APIs | TinyCat | Bibliotecas Legadas | Primeiros Críticos | Conhecimento Comum | 208,403,486 livros! | Barra de topo: Sempre visível