Code Excellence for the Average Programmer
•Download as KEY, PDF•
8 likes•1,320 views
Are you happy at work? Are you proud of the code you are working with? This session seeks to inspire engineers to adopt a sense of pride of ownership toward code they are working with. The long term benefits of working with code that continually grows better and easier to work on are almost too numerous it list. Take a ride with Llewellyn & Woody as we explore the road to happy code. One of the main tenants of agile is the ability to respond to change. This talk will focus on how to get malleability back into your existing code through the eXtreme programming practice of Refactoring.
Report
Share
Code Excellence for the Average Programmer
- 1. Code Excellence for the Average Programmer By Llewellyn Falco & Woody Zuill
- 2. How many are working with legacy code? 2
- 5. VS
- 6. Goal: Simple Techniques for Code Excellence
- 8. the golden rule Leave things BETTER than you found them
- 9. Never be more than 2 minutes away from checking in and going home
- 10. Arm Yourself
- 14. What makes code hard to work with?
- 15. Remove the 3 C’s...
- 16. Remove the 3 C’s... Clutter
- 17. Remove the 3 C’s... Clutter Complexity
- 18. Remove the 3 C’s... Clutter Complexity Cleverness
- 19. Removing Clutter Definition : Clutter is anything in your code that does not add value.
- 20. Removing Clutter Definition : Clutter is anything in your code that does not add value. Format your code
- 21. Removing Clutter Definition : Clutter is anything in your code that does not add value. Format your code Delete comments
- 22. Removing Clutter Definition : Clutter is anything in your code that does not add value. Format your code Delete comments Delete dead code
- 23. Removing Clutter Definition : Clutter is anything in your code that does not add value. Format your code Delete comments Delete dead code Delete unnecessary code
- 34. Removing Complexity Bad Names
- 35. Removing Complexity Bad Names Long Methods
- 36. Removing Complexity Bad Names Long Methods Deep Conditionals (if/for/while/switch)
- 37. Removing Complexity Bad Names Long Methods Deep Conditionals (if/for/while/switch) Magic Numbers
- 38. Removing Complexity Bad Names Long Methods Deep Conditionals (if/for/while/switch) Magic Numbers Improper Variable Scoping
- 39. Removing Complexity Bad Names Long Methods Deep Conditionals (if/for/while/switch) Magic Numbers Improper Variable Scoping Missing Encapsulation
- 40. Removing Complexity Bad Names Long Methods Deep Conditionals (if/for/while/switch) Magic Numbers Improper Variable Scoping Missing Encapsulation Obscure Code Blocks
- 41. Removing Cleverness “If it’s simple and elegant, you wouldn’t refer to it as ‘clever’”
- 42. Removing Cleverness “If it’s simple and elegant, you wouldn’t refer to it as ‘clever’” Cryptic Code
- 43. Removing Cleverness “If it’s simple and elegant, you wouldn’t refer to it as ‘clever’” Cryptic Code Abbreviated Code
- 44. Removing Cleverness “If it’s simple and elegant, you wouldn’t refer to it as ‘clever’” Cryptic Code Abbreviated Code Hijacking a Method(changing its intent for your own purposes)
- 45. ... and the 3 D’s
- 46. ... and the 3 D’s Duplication
- 47. ... and the 3 D’s Duplication Duplication
- 48. ... and the 3 D’s Duplication Duplication Duplication
- 49. Our code base is just a big mess, and no one is happy working in it.
- 51. Next Steps :-) 1-2
- 52. Next Steps Spring Cleaning Week - Start each task with 25 minutes of cleaning with a co-worker. :-) 1-2
- 53. Next Steps 2-2
- 54. Next Steps Books 2-2
- 55. Next Steps Books ‘Clean Code’ by Robert Martin 2-2
- 56. Next Steps Books ‘Clean Code’ by Robert Martin ‘Working Effectively with Legacy Code’ by Michael Feathers 2-2
- 57. What we offer
- 58. What we offer • Day Classes on site •Single day class to educate & train employees on a single aspect of agile
- 59. What we offer • Day Classes on site •Single day class to educate & train employees on a single aspect of agile • On site Coaching •Minimum 2 weeks working on site with employees on their stuff. •Training/Mentoring •Setup of framework •Source Control •Automated Builds •Continuous integration •Work environment
- 60. www.ApprovalTests.com check here for more information about how we actually tested the code
- 61. Contact Woody Zuill wzuill@yahoo.com Llewellyn Falco info@spunlabs.com
- 62. Goal: Simple Techniques for Code Excellence