Being Good Developer
•Download as PPTX, PDF•
2 likes•203 views
The document discusses tips for being a good developer, including writing good code through principles like the single responsibility principle, DRY principle, and design patterns. It emphasizes writing clean, readable code through practices like object-oriented programming, refactoring, and code documentation. Being a good developer also means having soft skills like admitting limitations, learning from others, teamwork, communication, and embracing failure while taking risks and learning new technologies.
More Related Content
What's hot
What's hot (20)
Similar to Being Good Developer
Similar to Being Good Developer (20)
Recently uploaded
Recently uploaded (20)
Being Good Developer
- 2. Agenda • Good Code vs. Bad Code • Tips For Good Code • Being Good Developer • Being a good developer is not all about technical
- 3. Good Code vs. Bad Code • Easy to maintain • Easy to Change • Readable • Documented
- 4. Tips For Good Code • Apply OOP (Object-oriented Programing) Concepts • Class • Object • Encapsulation • Inheritance • Polymorphism
- 5. Tips For Good Code • Single Responsibility Principle : It states that every module or class should have responsibility over a single part of the functionality provided by the software A class should have only one reason to change.
- 6. Tips For Good Code • Say what you mean. Mean what you say : Your function name should follow this rule. //Example func login(username:String , password:String) func x(y:String , z:String) • Writing software is like any other kind of writing
- 7. Tips For Good Code • DRY(Don’t Repeat Yourself)
- 8. Tips For Good Code •Apply Design Pattern •MVC
- 9. Tips For Good Code • Refactor • Use Code Documenters • Always Provide Context with Exceptions : Each exception that you throw should provide enough context to determine the source and location of an error
- 10. Being Good Developer • Clean Code • TDD • BTD • Counties integration
- 11. Being a good developer is not all about technical • Admit when you can’t • Be ready for failure • Learn new technology • Learn from others • Take risk
- 12. Being a good developer is not all about technical • Team Work • Testing and Troubleshooting • Communicate
- 13. Thanks •Sally Ahmed •Linkedin :Sally Ahmed •Skype:sally.ahmed18 •Github:https://github.com/sallyahmed
Editor's Notes
- https://medium.com/@Andrewmd5/what-makes-a-good-developer-f7c1777ea694#.n2m93xfqx https://medium.com/@pepibumur/being-a-good-developer-is-not-all-about-technical-18ec42d0f7ba#.f7313wknu https://medium.com/@guynirpaz/good-developer-bad-developer-6a163b076f74#.un64gsrke http://www.guynirpaz.com/2012/06/11/good-developer-bad-developer/ https://medium.com/@CodementorIO/good-developers-vs-bad-developers-fe9d2d6b582b#.cvxebn9w5 https://blog.thylmann.net/good-developers-are-like-milk-cows-a1f9d835fe85#.rdnidpnoc
- : The duplication is a problem because it bloats the code and will require four-fold modification when the algorithm need to be changed. It is also a four-fold opportunity for an error of omission. Duplication may be the root of all evil in software. Many principles and practices have been created for the purpose of controlling or eliminating it
- : When you write a paper or an article, you get your thoughts down first, then you massage it until it reads well. The first draft might be clumsy and disorganized, so you wordsmith it and restructure it and refine it until it reads the way you want it to read.