Thanks everyone for attending. I enjoyed last night… Special Thanks to Giordano Scalzo's whose slide I used as a base for my talk, and with who I had interesting conversations about ideas and slides…
Make sure to check the list of "good code attributes" at the end of the post. That's the list that we came up with, during the user group…
- Why Code matters!
- What is Bad?
- What is Good?
- OOP Patterns and Principles
- SOLID Principles
- How to measure clean code?
If you are able to apply the "Hotel Room Rule" in your projects let me know!
Figure: Hotel Room Rule: "Let someone else clean up your code every day"
- Clean Code
- Working effectively with Legacy Code
- The Art of unit testing
- Code Complete 2
Translated with Google Translate
VS2010 Code Metrics
JB Rainsberger The Four Elements of Simple Design
How to hire a programmer? Have people fix up some smelly code
Object Oriented Principles
The refactoring catalogue
Let someone else try to refactor your code
Nitriq & Atomiq
What is clean code?
Our list (Sydney .NET user group - 2010-11-17)
- User friendly
- Does what the client wants, not what i tell it <-- WOW!
- Self documented (easy to understand)
- Consistent - standards, naming
- Fail safe - robust
- Re usable
- Auto recovery
- Portable - device Language independent
- Self optimizing
- Cost (
- Meet requirements and client needs
- Easy to deploy and run