Clean Code III - Software Craftsmanship
•Télécharger en tant que PPTX, PDF•
13 j'aime•4,134 vues
You will learn why naming is really difficult if done right, why coding and style guidelines are crucial, code structuring, exception handling and why other elements of coding often define the tipping point between success and failure of projects. Following the principles of software craftsmanship will allow you to end up with better maintainability and extensibility of your software and the success of the project in the end. All 3 Clean Code presentations provide great value by themselves, but taken together are designed to offer a holistic approach to successful software creation. Why writing Clean Code makes us more efficient Over the lifetime of a product, maintaining the product is actually one - if not the most - expensive area(s) of the overall product costs. Writing clean code can significantly lower these costs. However, writing clean code also makes you more efficient during the initial development time and results in more stable code. You will be presented design patterns and best practices which will make you write better and more easily maintainable code, seeing code in a holistic way. You will learn how to apply them by using an existing implementation as the starting point of the presentation. Finally, patterns & practices benefits are explained. This presentation is based on C# and Visual Studio 2013. However, the demonstrated patterns and practice can be applied to every other programming language too. Note: Moving forwards this presentation will be updated with the latest version of the slides for the last event I did the presentation instead of creating new separate slide decks here on SlideShare. Presentation dates and locations: 2015-06-27 SoCal Code Camp - San Diego, CA 2014-11-14 SoCal Code Camp - Los Angeles, CA 2014-10-18 Desert Code Camp - Chandler, AZ
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (19)
Similaire à Clean Code III - Software Craftsmanship
Similaire à Clean Code III - Software Craftsmanship (20)
Plus de Theo Jungeblut
Plus de Theo Jungeblut (14)
Dernier
Dernier (20)
Clean Code III - Software Craftsmanship
- 1. Clean Code III Software Craftsmanship UC SD La Jolla, June 27th, 2015 SoCal Code Camp 2015
- 2. We are hiring! http://www.appdynamics.com/ careers
- 3. Theo Jungeblut • Director Customer Success at AppDynamics in San Francisco • Coder & software craftsman by night, first time dad and house builder • Architects decoupled solutions & crafts maintainable code to last • Worked in healthcare and factory automation, building mission critical applications, framework & platforms • Degree in Software Engineering and Network Communications • Enjoys cycling, running and eating theo@designitright.net www.designitright.net
- 4. Your feedback is important! http://speakerrate.com/speakers/18667-theo-jungeblut
- 5. Where to get the Slides http://www.slideshare.net/theojungeblut
- 6. Overview • Why Clean Code? • The Power of Simplicity • Tools - Your Best Friend • From Names to Classes • The "Must Read"-Books • Summary • Q&A
- 7. Does writing Clean Code make us more efficient?
- 8. The only valid Measurement of Code Quality
- 9. What is Clean Code?
- 10. Clean Code is maintainable Source code must be: • readable & well structured • extensible • testable
- 12. The “Must Read”-Book(s) by Robert C Martin A Handbook of Agile Software Craftsmanship “Even bad code can function. But if code isn’t clean, it can bring a development organization to its knees.”
- 13. Code Maintainability * Principles Patterns Containers Why? How? What? Extensibility Clean Code Tool reuse * from: Mark Seemann’s “Dependency Injection in .NET” presentation Bay.NET 05/2011
- 14. Keep it simple, stupid (KISS)
- 15. KISS-Principle – “Keep It Simple Stupid” http://blogs.smarter.com/blogs/Lego%20Brick.jpg by Kelly Johnson
- 16. The Power of Simplicity http://www.geekalerts.com/lego-iphone/ Graphic by Nathan Sawaya courtesy of brickartist.com Graphic by Nathan Sawaya courtesy of brickartist.com
- 17. Chaos build from simplicity Graphic by Nathan Sawaya courtesy of brickartist.com
- 19. .NET Tools and their Impact Tool name Positive Impact Negative Impact Resharper compiling ++++, learning +++ VS responsiveness -- FxCop code quality ++ compiling time - StyleCop code consistency +++ compiling time - StyleCop plugin for Resharper compiling time +++ VS responsiveness -- Ghost Doc automated docs potentially worse doc Spell Checker fewer spelling errors ++ performance -- Code Contracts testability, quality ++ compiling time -- Code Digger automated test ++ compiling time --
- 20. Resharper Features: – Code Analysis – Quick Fixes – Code Templates – Code Generation – Code Cleanup – Many, many more… “The single most impacting development addition to Visual Studio” http://www.jetbrains.com/resharper/
- 21. FxCop / Static Code Analysis Code Analysis: – Correctness – Library design – Internationalization and localization – Naming conventions – Performance – Security http://msdn.microsoft.com/en-us/library/3z0aeatx.aspx
- 22. Style Cop with R# Integration Code Consistency & Readability: – Automated check of C# coding standard – Enforceable at check-in with TFS check-in Policy – Full Integration in Resharper with Style Cop plugin: – Code Analysis – Quick Fixes – Code Cleanup
- 23. http://submain.com/products/ghostdoc.aspx • Save keystrokes and time • Simplify documenting your code • Benefit of the base class documentation • Source code and text spellcheck (Pro version) • API documentation creation (Pro version) Ghost Doc
- 24. Spell Checker http://visualstudiogallery.msdn.microsoft.com/7c8341f1-ebac-40c8-92c2-476db8d523ce/ • Spelll chicking for literals and comments in VS
- 25. http://msdn.microsoft.com/en-us/devlabs/dd491992 • Design-by-Contract programming • Improved testability • Static verification • API documentation integration with Sandcastle
- 26. • Pex automatically generates test suites with high code coverage. • Moles allows to replace any .NET method with a delegate. Flakes (Microsoft Pex & Moles) http://research.microsoft.com/en-us/projects/pex/
- 27. Names Matter • Meaningful Names • Intention Revealing Names • Use Pronounceable Names • Use Searchable Names • Avoid Encoding (Hungarian) • Don’t be cute • Pick One Word per Concept • Use Problem Domain Names * Chapter extract: Robert C. Martin –” Clean Code”, Parson Education, Inc. 2008
- 28. Functions • Small – Do One Thing • One Level of Abstraction • No or only few Arguments • Have No Side Effects • Prefer Exceptions to Returning Error Codes • Don’t Repeat Yourself * Chapter extract: Robert C. Martin –” Clean Code”, Parson Education, Inc. 2008
- 29. Comments • Comments do not Make Up for Bad Code • Explain Yourself in Code • Clarification • Warning of Consequences • ToDo Comments • Javadocs in Public APIs * Chapter extract: Robert C. Martin –” Clean Code”, Parson Education, Inc. 2008
- 30. Bad Comments • Mumblings • Redundant Comments • Misleading Comments • Journal Comments • Noise Comments • Don’t use a Comment When you Use a Method or a Variable • Commented-Out Code * Chapter extract: Robert C. Martin –” Clean Code”, Parson Education, Inc. 2008
- 31. The Purpose of Formatting • Team Rules – Consistency is King • Vertical Openness Between Concepts • Vertical Distance • Horizontal Alignment • Indentation • Write Journey Style Code Resharper & StyleCop – “Code Cleanup” * Kind of Chapter extract: Robert C. Martin –” Clean Code”, Parson Education, Inc. 2008
- 32. Classes • Class Organization • Encapsulation • Classes Should be Small • The Single Responsibility Principle • Cohesion • Organize for Change • Insolating from Change * Kind of Chapter extract: Robert C. Martin –” Clean Code”, Parson Education, Inc. 2008
- 33. The “Must Read”-Book(s) by Robert C Martin A Handbook of Agile Software Craftsmanship “Even bad code can function. But if code isn’t clean, it can bring a development organization to its knees.”
- 34. The “Must Read”-Book(s) by Krzysztof Cwalina, Brad Abrams Framework Design Guidelines “teaches developers the best practices for designing reusable libraries for the Microsoft .NET Framework.”
- 35. Summary Clean Code Maintainability is achieved through: • Readability (Coding Guidelines) • Simplification and Specialization (KISS, SoC, SRP, OCP, ) • Decoupling (LSP, DIP, IHP, Contracts, LoD, CoP, IoC or SOA) • Avoiding Code Bloat (DRY, YAGNI) • Quality through Testability (all of them!)
- 36. Downloads, Feedback & Comments: Q & A Graphic by Nathan Sawaya courtesy of brickartist.com theo@designitright.net www.designitright.net http://speakerrate.com/ speakers /18667-theo-jungeblut
- 38. … more References Resharper http://www.jetbrains.com/resharper/ FxCop / Code Analysis http://msdn.microsoft.com/en-us/library/bb429476(VS.80).aspx http://blogs.msdn.com/b/codeanalysis/ http://www.binarycoder.net/fxcop/index.html Code Contracts http://msdn.microsoft.com/en-us/devlabs/dd491992 http://research.microsoft.com/en-us/projects/contracts/ Fakes (Previous Moles & Pex) http://www.richonsoftware.com/post/2012/04/20/Comparing-Microsoft -Moles-in-Visual-Studio-2010-to-Microsoft-Fakes-in-Visual-Studio-11.aspx http://research.microsoft.com/en-us/projects/pex/ StyleCop http://stylecop.codeplex.com/ Ghostdoc http://submain.com/products/ghostdoc.aspx Spellchecker http://visualstudiogallery.msdn.microsoft.com/ 7c8341f1-ebac-40c8-92c2-476db8d523ce//
- 39. Time to say Thank You! The Organizers Thevolunteers (howaboutyou?)TheSponsors
- 41. … thanks for you attention! Please fill out the feedback, and… www.speakerrate.com/theoj And visit and support your local user groups!