AccueilGroupesDiscussionsPlusTendances
Site de recherche
Ce site utilise des cookies pour fournir nos services, optimiser les performances, pour les analyses, et (si vous n'êtes pas connecté) pour les publicités. En utilisant Librarything, vous reconnaissez avoir lu et compris nos conditions générales d'utilisation et de services. Votre utilisation du site et de ses services vaut acceptation de ces conditions et termes.

Résultats trouvés sur Google Books

Cliquer sur une vignette pour aller sur Google Books.

Chargement...

Coder proprement

par Robert C. Martin

MembresCritiquesPopularitéÉvaluation moyenneMentions
1,3152514,430 (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.… (plus d'informations)
Chargement...

Inscrivez-vous à LibraryThing pour découvrir si vous aimerez ce livre

Actuellement, il n'y a pas de discussions au sujet de ce livre.

» Voir aussi la mention 1

Affichage de 1-5 de 25 (suivant | tout afficher)
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 |
NF
  vorefamily | Feb 22, 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 |
Affichage de 1-5 de 25 (suivant | tout afficher)
aucune critique | ajouter une critique

Appartient à la série

Vous devez vous identifier pour modifier le Partage des connaissances.
Pour plus d'aide, voir la page Aide sur le Partage des connaissances [en anglais].
Titre canonique
Titre original
Titres alternatifs
Date de première publication
Personnes ou personnages
Lieux importants
Évènements importants
Films connexes
Épigraphe
Dédicace
Premiers mots
Citations
Derniers mots
Notice de désambigüisation
Directeur de publication
Courtes éloges de critiques
Langue d'origine
DDC/MDS canonique
LCC canonique

Références à cette œuvre sur des ressources externes.

Wikipédia en anglais (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.

Aucune description trouvée dans une bibliothèque

Description du livre
Résumé sous forme de haïku

Discussion en cours

Aucun

Couvertures populaires

Vos raccourcis

Évaluation

Moyenne: (4.27)
0.5
1 1
1.5
2 1
2.5 2
3 29
3.5 2
4 76
4.5 8
5 90

Est-ce vous ?

Devenez un(e) auteur LibraryThing.

 

À propos | Contact | LibraryThing.com | Respect de la vie privée et règles d'utilisation | Aide/FAQ | Blog | Boutique | APIs | TinyCat | Bibliothèques historiques | Critiques en avant-première | Partage des connaissances | 204,714,458 livres! | Barre supérieure: Toujours visible