On average day, programmers will often find themselves doing the following things, in no particular order…

  • Checking email
  • Code review for pull requests
  • Digging through bug reports
  • Scrum stand up meetings
  • Sprint planning meetings
  • Going to the bathroom
  • Departmental meetings
  • Go to lunch
  • Sometimes company wide meetings
  • Meetings with customers
  • Random discussions with teammates about the current JIRA ticket
  • Cursing the fact that their code doesn’t work
  • Posting to or reading social media about whatever the daily panic is about
  • Checking email
  • Replying to Slack messages
  • Posting random memes in the team Slack channel
  • Getting coffee
  • Getting a snack
  • Reading about some new technology, algorithm, or pattern
  • Reading random articles that were posted in Slack
  • Wait for compiles to finish or tests to run
  • Rethink career choice as the code still doesn’t work
  • Ask a random teammate for help on Slack or in person
  • Rubber duck the problem and realize it was a simple misspelling or incorrect variable name the entire time
  • Pick up a new ticket
  • Write some code!
  • Go home and prepare to do it all again tomorrow…

This is pretty much how life is for most of the programmers I know and work with.

That Sounds Like Most Office Jobs!

Well, it really isn’t that different from most office jobs because programmers work in offices. If you work in a modern office, work looks like work and everyone tends to act about the same way.

If you are want to get ahead, you must find strategies to avoid the herd mentality that most people live in and take a different approach to things like meetings an email.

But alas, that is a topic for another day…