How much code should I be writing?

Should I be coding at all?

Short answer: yes with an "if"

Long answer: no with a "but"

it depends

Factors

  • How big is your shop?
  • How many developers do you have?
  • How many people do you manage?
  • Can you afford to spend time programming?
  • Can you afford to NOT spend time programming?
  • Is there a deadline?
  • Can you even program?
  • Should you even be programming?
  • Do you even remember how to program?
  • What level are you in the org?

Dev

Mgr

Director

VP

CTO

Dev

Lead

CTO

Dev

CTO

Don't stop being technical

Tips & Tricks

Manager or Lead

  • Keep writing code
  • Take an active part in code reviews
  • Work on some important things
  • Don't be a bottleneck
  • Don't take all the "fun" stuff
  • Fix bugs
  • Address technical debt
  • If possible, make your time "free"

Manager of managers

  • Keep writing code of some kind
  • Take an active part in code reviews
  • Little to no code actually in production
  • Internal tools
  • Dashboards
  • Attend technical meetings
  • Attend architecture discussions

Manager of managers of managers

  • Keep writing code of some kind. Somewhere
  • Coding is not your job anymore
  • Don't forget your roots
  • Don't stop knowing what you are talking about
  • Or what other people are talking about
  • Read books
  • Attend meetings
  • Code on the side?

Still need to be technical

No matter what, don't spend less than 30% of your time coding

http://www.drdobbs.com/architecture-and-design/engineering-managers-should-code-30-of-t/240165174

Reasons

  • Estimates
  • Technical debt
  • Continuity of Understanding
  • Parity with Responsibility
  • Respect for team

Small percentage based on team size (5-20%)

http://scottberkun.com/2010/should-managers-know-how-to-code/

"your primary job is to do all the things that individual programmers cannot do."

Stay flexible and don't stop developing

http://randsinrepose.com/archives/technicality/

Advice for not losing perspective

  • Use the development environment to build the product
  • Be able to draw a detailed architectural diagram describing your product on any white board at any time
  • Own a feature
  • Write a test script

Managers don't code

Yes, but they should!

No, they shouldn't!

http://www.c2.com/cgi/wiki?ManagersDontCode

Benefits of coding

  • Keep managers connected to the technology
  • Remind them what real coding is like
  • Ensure they are thinking about Succession Planning
  • Provide exposure to an entirely different part of the business
  • For many managers, increase their level of job satisfaction
Made with Slides.com