Clean Code, Resumen Capítulo 1.
Download as PPTX, PDF1 like1,646 views
The document discusses the principles and importance of clean code, emphasizing that it is not only efficient but also easy to read and maintain. Various programming experts share their definitions of clean code, highlighting qualities such as elegance, simplicity, minimal dependencies, and care in writing. Ultimately, maintaining clean code is portrayed as essential for professional success and productivity in software development.
Clean Code, Resumen Capítulo 1.
- 1. CLEAN CODE ROBERT C. MARTIN Francisco Arley López Espinosa Gestión de Calidad de Software Universidad Pontificia Bolivariana
- 2. CAPÍTULO 1 Habrá código Mal código Afán Después = nunca Costo del desorden Productividad tiende a 0 Rediseño Mucho tiempo Actitud Ser profesional, decir NO
- 3. CAPÍTULO 1 Enigma fundamental La única manera de ir rápido es ir en orden El arte del código limpio Es fácil de reconocer, pero no de hacer Somos autores Y tenemos lectores Fácil de leer es más fácil de escribir Regla del Boy Scout Dejar el campamento más limpio de lo que lo encontraste
- 5. ¿Qué es código limpio? Bjarne Stroustrup “I like my code to be elegant and efficient. The logic should be straightforward to make it hard for bugs to hide, the dependencies minimal to ease maintenance, error handling complete according to an articulated strategy, and performance close to optimal so as not to tempt people to make the code messy with unprincipled optimizations. Clean code does one thing well.”
- 6. ¿Qué es código limpio? Grady Booch “Clean code is simple and direct. Clean code reads like well- written prose. Clean code never obscures the designer’s intent but rather is full of crisp abstractions and straightforward lines of control.”
- 7. ¿Qué es código limpio? Dave Thomas “Clean code can be read, and enhanced by a developer other than its original author. It has unit and acceptance tests. It has meaningful names. It provides one way rather than many ways for doing one thing. It has minimal dependencies, which are explicitly defined, and provides a clear and minimal API. Code should be literate since depending on the language, not all necessary information can be expressed clearly in code alone.”
- 8. ¿Qué es código limpio? Michael Feathers “I could list all of the qualities that I notice in clean code, but there is one overarching quality that leads to all of them. Clean code always looks like it was written by someone who cares. There is nothing obvious that you can do to make it better. All of those things were thought about by the code’s author, and if you try to imagine improvements, you’re led back to where you are, sitting in appreciation of the code someone left for you— code left by someone who cares deeply about the craft.”
- 9. ¿Qué es código limpio? Ron Jeffries “In recent years I begin, and nearly end, with Beck’s rules of simple code. In priority order, simple code: Runs all the tests; Contains no duplication; Expresses all the design ideas that are in the system; Minimizes the number of entities such as classes, methods, functions, and the like.”
- 10. KEEPING YOUR CODE CLEAN IS NOT JUST COST EFFECTIVE; IT’S A MATTER OF PROFESSIONAL SURVIVAL
- 11. Bibliografía Martin, Robert Cecil (2009). Clean code: a handbook of agile software craftsmanship. Upper Saddle River, NJ: Prentice Hall