Getting to Good Code: Readability, Simplicity and Design
•Télécharger en tant que PPTX, PDF•
0 j'aime•981 vues
The document discusses what constitutes "good code" including being functional, bug-free, performant, having good design, being tested and testable, and being easy to change. It notes that code readability has value both now and over time as software evolves and is worked on by different teams. While readability requires more work, time, and training, readable code is the responsibility of developers. The document provides tips for writing readable code such as using visibility, narratives, simplicity, appropriate abstraction, and avoiding premature optimization or flexibility.
Recommandé
Contenu connexe
En vedette
En vedette (11)
Similaire à Getting to Good Code: Readability, Simplicity and Design
Similaire à Getting to Good Code: Readability, Simplicity and Design (20)
Plus de Jane Prusakova
Plus de Jane Prusakova (20)
Dernier
Dernier (20)
Getting to Good Code: Readability, Simplicity and Design
- 1. ©2010 Improving Enterprises, Inc. Good Code What, Why, and How to Get There Dallas TechFest 2014 Jane Prusakova Josh Rizzo @Improving Enterprises College Station
- 2. ©2010 Improving Enterprises, Inc. What is “good”? Functional Bug-free Performant Good design Tested Testable Easy to change
- 3. ©2010 Improving Enterprises, Inc. Usability Users and clients Developers
- 4. ©2010 Improving Enterprises, Inc.
- 5. “Programs must be written for people to read, and only incidentally for machines to execute.” – Abelson and Sussman ©2010 Improving Enterprises, Inc.
- 6. ©2010 Improving Enterprises, Inc. Readability has value NOW Code is an asset affects productivity monetary value
- 7. Readability has value OVER TIME Software evolves over time Work by many different teams Changes affect value
- 8. ©2010 Improving Enterprises, Inc. Readability has cost More hard work More time More training
- 9. ©2010 Improving Enterprises, Inc. Readable code
- 10. ©2010 Improving Enterprises, Inc. Who is responsible? It was hard to write It should be hard to read
- 11. Lets make code more… See: https://github.com/joshrizzo/Readability ©2010 Improving Enterprises, Inc.
- 12. ©2010 Improving Enterprises, Inc. Visible code Short and concise Spacing and indent matter “If we wish to count lines of code, we should not regard them as ‘lines produced’ but as ‘lines spent.’” – Edsger Dijkstra
- 13. ©2010 Improving Enterprises, Inc. Code with a narrative Use naming to show intent Interface design “Programming can be fun, so can cryptography; however they should not be combined.” – Kreitzberg and Shneiderman
- 14. ©2010 Improving Enterprises, Inc. Easy to read Cohesive level of abstraction “The purpose of abstraction is not to be vague, but to create a new semantic level in which one can be absolutely precise.” – Edsger Dijkstra
- 15. ©2010 Improving Enterprises, Inc. Readable++ Simplicity
- 16. “Everything should be made as simple as possible, but not simpler.” ©2010 Improving Enterprises, Inc. – Albert Einstein
- 17. ©2010 Improving Enterprises, Inc. Simple vs Fast Correctness more important than speed Simple code is more likely to be and stay correct Modularize code w/ performance concerns Optimize locally
- 18. ©2010 Improving Enterprises, Inc.
- 19. ©2010 Improving Enterprises, Inc. Simple vs Flexible Re-use is rare Predictions of re-use are poor Raises complexity significantly Unused => not working
- 20. ©2010 Improving Enterprises, Inc. Simple vs Clever Over engineering Mixing abstractions Inappropriate patterns Complicated syntax
- 21. ©2010 Improving Enterprises, Inc. Good Code What, Why, and How to Get There https://github.com/joshrizzo/Readability Dallas TechFest 2014 Jane Prusakova Josh Rizzo @Improving Enterprises College Station
Notes de l'éditeur
- Usability: The system needs to be functional for the users and clients. Usability: The code needs to be readable for the current and future development of the system.
- My most popular slide from the #live360 keynote: a comical explanation of how software dev keeps getting harder.
- Abelson founding director of both Creative Commons and the Free Software Foundation. Sussman and Abelson are co-authors of popular textbook “Structure and Interpretation of Computer Programs”
- Edsger Dijkstra was a Dutch computer scientist, known for introducing the idea that GOTO is a smell, developing shortest path algorithm, and developing the concept of formal verification.
- Ben Shneiderman studied programmers and their interactions with the code, developed principles of interface design, worked on information visualization and usability.
- This quote first appear in Reader’s Digest in 1977, with no supporting references. Attributed to Einstein from someone’s memory, not found in his writings.
- This quote first appear in Reader’s Digest in 1977, with no supporting references. Attributed to Einstein from someone’s memory, not found in his writings.
- Bucatti Veyron, top speed 267mph, total production 450 unit. Toyota Corolla, top-selling car for many years. Doesn’t go faster than 111mph. Sold 1.2 units world-wide.