Skill of superb developers
Download as PPTX, PDF•1 like•575 views
The document discusses practical software development workflows at NBS and the role of developers. It covers NBS's core iteration principles of understanding the problem, designing a sprint, defining business processes, and engineering processes like architecture development and testing. Good developer competencies discussed include problem solving, communication, continuous learning, knowing tools, clean coding practices like DRY principles, unit testing using TDD, refactoring, and pair programming. The document emphasizes skills like analytical thinking, collaboration, learning new ideas, practicing skills, and producing readable, maintainable code.
Skill of superb developers
- 1. Turgay Kıvrak Understanding Developer’s Role in Software Development Sidiq Permana
- 2. Cofounder and CIO at Member of Awesome Global Developer Communities Technical Contributor at Life Passion : Coding, Teaching, Travelling and Diving
- 3. Agenda 1. Practical software development workflow at NBS 2. How your competency meets the development workflow
- 4. Practical software development workflow at NBS
- 5. Our mindset : Creating a software is a storytelling
- 6. Our Core Iteration Principle
- 8. Understand the business goals and scope
- 10. (Map)The most important process : Software requirement
- 11. Better understanding of User Requirement will make the development comes easier for the next phases and the constraints at scale
- 12. (Sketch)The most important process : Defining The Business Process
- 14. What does the thing want to achieve ?
- 15. What…. if….. ?
- 17. How might we..
- 21. Engineering Process 1. Developing the system architecture 2. Developing the system blue prints (It includes several UML diagram such as Use Case, Class, Activity, Sequence, Integration, and Deployment) 3. Developing the database diagram 4. Define the development backlog, sprint and story 5. Coding 6. Testing 7. Deployment and send deliverable
- 22. As a user I can...
- 23. Module : Membership; Function : Login As a user I can see email & password field, Login Button, Login with facebook Button and Login with Google Button As a user I can login with registered phone number or email and password As a user I can login with my facebook account As a user I can login with my google account
- 24. The Transformation User Story → Test Case
- 25. The Transformation Analysis Result → Business Process → Business Workflow → Standar Operation Procedue → Legal → Service Level Agreement → Product
- 26. Conclusion Problem → Analysis → Solution → Ideation → Implementation → Conversion
- 28. Why bother to be a good developer?
- 29. Skills
- 31. 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
- 33. Good Communication Create an environment where communication is just a part of the normal process Being specific Writing Explain clearly Collaboration Team Member Confidence
- 35. 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
- 36. Your CAREER is your RESPONSIBILITY Spend time caring for their profession
- 37. CURIOSITY is the engine. ACTIVE OBSERVANT OF NEW IDEAS EXCIMENT INTO YOUR LIFE
- 38. Learn/Know Your Tools Java HTML5 CSS JavaScript Python Scala Clojure Maven Groovy Gradle Linux IDE Spring Android Design Principles Design Patterns Refactoring Scrum TDD Continous Integration Kanban UML PP
- 39. No Language or Platform Fanaticism
- 40. PRACTICE to keep your skills sharp and ready
- 41. Coding Skills
- 42. Understand Basic Skills : Algorithm, Data Structure, Design Pattern, Development Approach, Development Pattern and Math.
- 43. Your code looks like a plate of spaghetti?
- 44. BaseActivity:1600+ lines A base activity that handles common functionality in the app. This includes the navigation drawer, login and authentication, Action Bar tweaks, amongst others.
- 45. God Object
- 49. Concise Readable Easy to change No duplication Efficient Simple Clean Code Make it fan-funded
- 50. Focused - not doing too much Meaningful Names Small functions No bad comments Well structured Complies with DRY rule Characteristics of Clean Code
- 54. Think about the separation of concern
- 55. 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
- 56. 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
- 57. REFACTORING Restructuring existing computer code without changing its external behavior Improving the design of an existing code base Stabilize pursuit of perfection with pragmatism
- 58. Pair Programming
- 59. Pair Programming Continuous Code Review Multiple points of view Guaranteed Focus Fewer blockages Masking distractions Reduced training cost and time
- 61. http://nusantarabetastudio.com/academy Thank You “Master programmers think of systems as stories to be told rather than programs to be written.” Bob Martin