ColdFusion Craftsmanship
1 like261 views
The document discusses concepts related to software craftsmanship including agile development practices, testing approaches like test-driven development, clean code principles, and professional development. It emphasizes the importance of continuously learning, practicing skills like automated testing, and owning one's career through activities like practicing code reviews and learning from books on software craftsmanship.
ColdFusion Craftsmanship
- 2. 2
- 3. Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. 3
- 5. Manifesto for Software Craftsmanship raising the bar As aspiring Software Craftsmen we are raising the bar of professional software development by practising it and helping others learn the craft. Through this work we have come to value: Not only working software, but also well-crafted software Not only responding to change, but also steadily adding value Not only individuals and interactions, but also a community of professionals Not only customer collaboration, but also productive partnerships 5
- 7. 7
- 8. Adding value through practice Automated testing Test first Test-Driven Development Pair-programming Continuous Integration 8
- 11. Software Craftsmanship Attitude Owning your career Not a 9 to 5 Profession Practice Boy Scout Rule Expecting Promotions 11
- 29. Clean Code Meaningful Names Short Functions ▪ Single Responsibility Principal ▪ Minimal Arguments Show intent ▪ No need for comments Formatting Unit Testing 29
- 35. Code Reviews 35
- 36. Code Layout Matters Easy to scan Expressive layout Compact format Code is written once and Read ∞ 36
- 37. 37
- 38. How do we know we are building the right thing? How do we know we are building the thing right? 38
- 42. 42
- 44. Some of the rules valid today 1. Write clearly -- don't be too clever. 2. Say what you mean, simply and directly. 3. Write clearly -- don't sacrifice clarity for efficiency. 4. Replace repetitive expressions by calls to common functions. 5. Parenthesize to avoid ambiguity. 6. Choose variable names that won't be confused. 7. Write first in easy-to-understand pseudo language; then translate into whatever language you have to use. 8. Don't patch bad code -- rewrite it. 9. Write and test a big program in small pieces. 10. Check some answers by hand 11. Make it fail-safe before you make it faster. 12. Make it clear before you make it faster. 13. Don't sacrifice clarity for small gains in efficiency. 14. Don't strain to re-use code; reorganize instead. 15. Make sure special cases are truly special. 16. Don't just echo the code with comments -- make every comment count. 17. Don't comment bad code -- rewrite it. 18. Use variable names that mean something. 19. Format a program to help the reader understand it. 20. Don't over-comment. 44
- 45. 45
- 46. Maturity 46
- 49. Clean Code Robert “Uncle Bob” Martin Changes your thought process + Videos Also Clean Coders – More about your career 49
- 54. Questions 54