Skills Of Good Developers

A collections of skills you need to be a good developer.

Transcript

1. Turgay Kıvrak Skills of Good Developers Turgay Kıvrak
2. Turgay Kıvrak Technical Lead Innova http://turgaykivrak.wordpress.com Twitter : @turgaykivrak Linked In: http://www.linkedin.com/in/turgaykivrak
3. Why bother to be a good developer?
4. Skills
6. Identify the problem Define the problem Examine the options Act on a plan Look at the results Analytical Mind Detail Oriented Eye Visualize PROBLEM SOLVING
8. Good Communication Create an environment where communication is just a part of the normal process Being specific Explain clearly Collaboration Team Member Writing Confidence Humility
9. Continuous Learning
10. Your CAREER is your RESPONSIBILITY Spend time caring for their profession
11. CURIOSITY is the engine. ACTIVE OBSERVANT OF NEW IDEAS EXCIMENT INTO YOUR LIFE
12. Learn/Know Your Tools Java HTML5 CSS JavaScript Python Scala Clojure Maven Groovy Gradle Linux IDE Spring Hibernate Design Principles Design Patterns Refactoring Scrum TDD Continous Integration Kanban UML PP
13. No Language Fanaticism
14. HOW? READ Books Blogs Tweets Code GO to Conferences WATCH Videos TAKE Courses DISCUSS TALK "If you can’t explain it simply, you don’t understand it well enough." Albert Einstein
15. PRACTICE to keep your skills sharp and ready
16. Coding Skills
17. Make it fan-funded Concise Readable Easy to change No duplication Efficient Simple No bug Clean Code
18. Focused - not doing too much Meaningful Names Small functions No bad comments Well structured Complies with DRY rule Have unit tests Characteristics of Clean Code
19. Reduces Bugs in New and Existing Features Good Documentation Reduces the Cost of Change Improves Design Allows Refactoring Forces You to Slow Down and Think Makes Development Faster Reduce Fear It is Fun Unit Testing
20. Test Driven Development Best way to have GOOD UNIT TESTS Changes your MINDSET about coding and testing Makes you MORE PRODUCTIVE Makes you BETTER DEVELOPER
21. REFACTORING Restructuring existing computer code without changing its external behavior Improving the design of an existing code base Stabilize pursuit of perfection with pragmatism
22. Pair Programming Continuous Code Review Multiple points of view Guaranteed Focus Fewer blockages Masking distractions Reduced training cost and time
23. Big Picture
24. Thanks