Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Secrets of the Senior Developer

Secrets of the Senior Developer

Tim VanFosson

July 22, 2017
Tweet

More Decks by Tim VanFosson

Other Decks in Programming

Transcript

  1. Topics What Would You Say You Do Here? How to

    Not Write Crappy Code Pay it Forward Mentoring: teaching and coaching Set the tone Doing the Right Thing Technology Architecture Performance Complexity Ownership
  2. What does a senior developer do?  Problem solver 

    Team leader  Client friendly  Writes code  Reviews code
  3. Listen to people who have written crappy code Hard way

    or the easy way Avoid the “cargo cult” People (hint: you don’t need to agree with them) Alistair Cockburn Kent Beck “Uncle” Bob Martin Robert Fowler Open source authors Security researchers (Troy Hunt) Networking, OS, etc. folks Blogs Local conferences, user groups …
  4. Read crappy (and not crappy) code Framework/Open Source Patterns “Gang

    of Four” - https://en.wikipedia.org/wiki/Design_Patterns https://martinfowler.com/eaaCatalog/ Code Reviews
  5. Write Crappy Code (or Not) No substitute for practice Write

    first, refactor later Learn to start with less crappy code OR – don’t write any code if you can avoid it
  6. Ask people who have written crappy code Get a Mentor/Coach

    Get Feedback Code Review Design Review
  7. Architecture You Don’t Need Web Scale, Unless You Do Most

    Data Exists in Relation to Other Data Embrace the Cloud There Is No Magic Bullet
  8. Complexity Don’t Value Complexity Solve a Simpler Problem Move Complexity

    to Configuration Absorb Complexity for the User