As a developer, you want quiet time to get your work done.  But your job isn't just to produce source code; you have expertise that your team needs on a daily basis.  You know how the software works, you know what's possible, and you're the only one whocan even begin to estimate how long it takes to build something.  Even though you have code to write, you have to be responsiveto these other needs.

Techniques like calendar-blocking, work-from-home-days, and office hours don't solve the problem.  A great developer has to finda way to be productive and responsive.  The good news is that by applying commonly accepted software development practices(namely TDD) and politely setting a few boundaries, you can maintain a respectible output of code while helping your non-technicalcollegues be successful at the same time.

In this talk, I'll outline why it's important to be responsive, and how a combination of test-driven-development and emailmanagement can ensure you rarely lose your place, and are always working on the most important thing.

1 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session

  1. Intro
  2. Why You Must Be Responsive
  3. How To Do It
  4. Summary

Learning Outcome

To accept that interruptions and requests for expertise are part of a senior engineer's job, and understand a few techniques for dealing with it in a way that helps everyone be successful.

Target Audience

Developers, Engineering Managers

schedule Submitted 4 years ago

Comments Subscribe to Comments

comment Comment on this Submission