Recommended
Recommended
More Related Content
What's hot
What's hot (19)
Similar to How to be a good developer
Similar to How to be a good developer (20)
More from Ashley Davis
More from Ashley Davis (17)
Recently uploaded
Recently uploaded (20)
How to be a good developer
- 1. How to be a good developer Ashley Davis Email: ashley@codecapers.com.au Twitter: ashleydavis75
- 2. About me ● 20+ years developer ● CTO of Sortal ● Author of ○ Data Wrangling with JavaScript ○ Bootstrapping Microservices ● Creator of Data-Forge Notebook ● Stock trader
- 3. Where do we start?
- 5. But seriously... How can I be a good developer?
- 6. The good news There are many ways to be a good developer There is no single way Forge your own pathway
- 7. First... Don’t believe what I say
- 8. Now Form your own opinion
- 9. Then Tell people about it
- 10. Always Listen and see the viewpoint of others
- 11. Realise Everyone has their own opinion
- 12. When you are wrong... Admit it adjust your opinion and move on
- 13. But Ash.... What does this have to do with development?
- 14. The point is... Complex software is built by teams Teams are made of people
- 15. No matter how it looks at first, it’s always a people problem ~ Gerry Weinberg, 1933-2018 The second law of consulting Secrets of Consulting, 1986 https://blogs.msdn.microsoft.com/alikl/2008/11/12/three-laws-of-consulting-by-gerald-m-weinberg/
- 16. Being a good developer... Take responsibility for relationships Communicate Understand expectations Ask questions
- 17. I hire for... Soft Communication skills Team skills Ability/desire to learn and adapt Curiosity/passion/interest Hard Technical skills Technical aptitude Experience What’s something unique that you bring to the table?
- 18. Remember this... Technical skills get you the interview. Talking gets you the job.
- 19. Where does Agile fit in? ?
- 20. The agile manifesto... Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. https://agilemanifesto.org
- 21. My philosophy of development ● Iterate ● Start simple
- 22. Development in small increments
- 23. Start simple
- 24. Develop your own philosophy of development
- 25. Rules to live by when coding ● Leave code better than you found it ● Code for your teammates / future self ● A bit of planning goes a long way ● But don’t plan too hard ● Understand your code ● Ask for help
- 26. Tips for learning ● Focus your learning ● Work with experienced people / find a mentor ● Go to meetups and talk to people / ask questions ● Have a hobby project / code every day ● Read other people’s code / get other people’s code working
- 27. Questions Good videos from Scott Hanselman https://vimeo.com/39020426 https://www.youtube.com/watch?v=IWPgUn8tL8s Contact me Email: ashley@codecapers.com.au Twitter: ashleydavis75