Three Developer Abilities They Dont Teach In College
Download as PPTX, PDF1 like510 views
The document discusses essential software development skills that are not typically taught in college, focusing on maintainability, testability, and usability. It highlights key principles such as the single responsibility principle and the importance of creating user-friendly interfaces. The content emphasizes the significance of understanding existing code and the impact of maintenance on software costs.
Three Developer Abilities They Dont Teach In College
- 1. Three Developer -abilities they DON’T Teach in CollegeJacinto A. Limjap, Jr.Microsoft MVP for C#Senior Application Developer for FBM e-Services
- 2. It’s not that they don’t teach it
- 3. MaintainabilityA measure of how easy it is to understand, modify, and extend your code
- 4. Maintenance?
- 5. Facts you only find out at workWriting new code is the first thing you do at school, but the LAST thing you do at work
- 6. Facts you only find out at workYou WILL spend most of your time trying to understand the code some other person wrote
- 7. Facts you only find out at work“Maintenance typically consumes 40 to 80 percent of software costs” – Robert L. Glass
- 8. TestabilityThe degree to which a system or component facilitates the establishment of test criteria and the performance of tests to find whether those criteria have been met
- 9. Ask yourselfWhen there’s a bug, how easy is it to find out which part of your code to fix?
- 10. Want it testable? Make it SOLID!
- 11. Single Responsibility PrincipleYour class should have one, and only one, reason to change
- 12. Open Closed PrincipleYou should be able to extend a class’s behavior without modifying it
- 13. Liskov Substitution PrincipleDerived classes must be substitutable for their base classes
- 14. Interface Segregation PrincipleMake fine grained interfaces that are client specific
- 15. Dependency Inversion PrincipleDepend on abstractions, not on concretions
- 16. UsabilityThe ease with which people can employ a particular tool or other human-made object in order to achieve a particular goal
- 20. Steve Krug’s First Law of Usability
- 21. Usable software makes people happy“Good UI sells software, but it also makes people happy, because people are happy when they accomplish the task they want to accomplish” – Joel Spolsky
- 22. Your speakerBlog: http://dotnet.kapenilattex.comTwitter: http://twitter.com/LaTtEXFacebook: http://facebook.com/LaTtEX
- 23. Learning to Distinguish a Solution from a Problem http://www.computer.org/portal/web/buildyourcareer/fa010Definition for testability: http://www.aptest.com/glossary.htmlThe Principles of OOD http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOodSOLID Development Principles – In Motivational Pictures http://www.lostechies.com/blogs/derickbailey/archive/2009/02/11/solid-development-principles-in-motivational-pictures.aspxSimplicity http://stuffthathappens.com/blog/2008/03/05/simplicity/2006 Krug, Steve: Don’t Make Me Think: A Common Sense Approach to Web UsabilityUser Interface Design for Programmers http://www.joelonsoftware.com/uibook/fog0000000249.htmlReferences