What is this talk about?

  • Code quality, duh!
  • Keeping the code quality in your code base
  • The progress start to get slow
  • Bugs
  • Vicious cycle - Preassure - Sloppy Code - Late Delivery
  • Business Changes
  • Technology Changes
  • Team Changes
  • Legacy Code
    • Code written by somebody else or code written by you two weeks ago
  • Qualitive Data
    • One on One meetings - manager and developer
    • Restrospectives
  • Quantitive Data
    • Process Metrics
    • Team Surveys
    • Software Metrics
  • Growing quality
  • Boy Scout Rule - Take a little extra time to clean something
  • Leveling Up
    • Conflicting style preferences - Style guides
    • Not enough refactoring experience - Lunch and Learn sessions, Discuss an article, teamfactoring
    • Finding problems too late - Check analysis tools
    • Missing high level design - Whitebording
    • Code Reviews - Formatting, Correctness, Scalability, Security, Comprehension
  • Virtiuos Cycle
    • Quality
    • Satisfaction
    • Engagement
    • Responsability

What do I think about this talk?

Well, I was searching for more inspiration regarding leveling up as a developer and as a part of the team, taking in count that I’m working with more people; Bryan hit the nail with all this tips in particular the one about the boy scout rule which I already knew from the Clean Code book but sometimes I tend to forget to follow. I will try to talk with my team mates about this and see what happen hopefully all of us can just get better at what we do to get more satisfaction at work ;-)