Things Maybe You Don't Know as a Newer Developer

Recording: https://www.youtube.com/watch?v=i4egHyIV_vE

Talk given at Minnebar 17.

I’ve been working as a software developer for over 15 years, and I’m hoping to compile a useful list of general software development advice I wish someone had taught me from the start.

Transcript

1. Things Maybe You Don't Know as a Newer Developer Dan Lew (Yes, that’s me)
3. Getting a Job
5. Recommendations Mentor Meaty Meet-y?
6. Learning
8. Sources • Google • Documentation • Books & articles • Classes • Talks • Samples • StackOver fl ow • Code exercises • Open source • Other people
9. https://www. fl ickr.com/photos/43810158@N07/8426525097
10. The XY Problem How do I get the last
 three characters
 of a fi lename? Did you mean, how 
 do you get 
 a fi le extension? https://commons.wikimedia.org/wiki/File:Two_young_people_demonstrating_a_lively_conversation.jpg
11. Take your time • Don’t just copy + paste from StackOver fl ow • Understanding > working • Solution might suck • Easier to modify code later • Build your knowledge base
12. Development
13. Software development is a non-linear process
14. Planning Sketch Discuss Prototype https://www. fl ickr.com/photos/54327699@N02/8108596621
15. Design • Rarely one correct design • Save time by avoiding perfectionism • Prefer two-way doors https://commons.wikimedia.org/wiki/File:Set_of_Crash_Bar_Doors.jpg
16. Divide & Conquer • Multiple small tasks > one big task • Easier to develop • Easier to review code • Easier to change direction • Easier to merge code
17. Hiding Work Avoid fi nal hookup https://www. fl ickr.com/photos/43053584@N00/2395215000 Feature fl ags
18. Acronyms • DRY - Don’t Repeat Yourself • YAGNI - You Aren’t Gonna Need It • KISS - Keep It Simple, Stupid
19. KISS Example • More states -> more complex • Examples… • Enums > strings, numbers • Immutability > mutation • Pure functions > side e ff ects
20. Code Review Focus API Bugs Architecture Maintainability Readability Tests Less important More important
21. Code Reviews Embrace Questions Discussions Compliments Avoid Code style Syntax Preferences Nitpicks
22. Being a good teammate Get stu ff done Don’t be a jerk Help others https://commons.wikimedia.org/wiki/File:Long_spoons_modern.jpg
23. Testing https://commons.wikimedia.org/wiki/File:Laboratory_scientist_conducts_an_experiment_with_a_Rotary_evaporator.jpg
24. Two Testing Styles https://www. fl ickr.com/photos/mike_grauer/16898327310/ Manual https://commons.wikimedia.org/wiki/File:Multiple_Server_.jpg Automated
25. Why automate? Safer Refactoring Fast Repeatable https://www. fl ickr.com/photos/14246866@N05/2207257172
26. Test-driven development Verify un fi nished features Better architecture Faster development https://www. fl ickr.com/photos/katiekrueger/2351656805
27. Testing Thoughts • Be tactical w/ test coverage • Flakey tests are worthless • Add manual testing tools
28. Debugging • Print is okay • Debuggers are better • Debuggers are not (that) scary https://www.wannapik.com/vectors/67772
29. Releasing
30. Hitting deadlines • All estimates suck, so deadlines are often incorrect • Better answers than “work harder”: • Over-estimate • Cut scope • Let deadlines slip
31. Avoid releasing… When fatigued In a rush Before weekends
32. Q&A @danlew@androiddev.social