One of the reasons for an enjoying an IT career is problem-solving.  We get to face a challenge of varying levels every day.  That can lead to us spending more time working on a problem than we need to.  Thus, we need to keep in mind schedules and resources we have to meet our deadlines.

Problem-Solving as a Team Sport

There is a reason we find many developer offices set up in a way that lends itself to interaction.  Yes, cubicles can be a cheap way to create an “office.”  However, they also tend to lead us to communicate with our coworkers more than a real office with walls and a door.  Some managers claim their door is always open, but cubicle dwellers have no door.  This approach to seating is not an invasion of privacy.  It is a way to help us attack problems as a team.

Two Heads Are Better Than One

Ther is no shame in reaching out to others for your latest struggle.  We all are human and can overlook simple details that lead to a solution.  I think this is even more prevalent in coding as the details are what make the software work.  Unfortunately, missing those same details is the source of most bugs.  So do not hesitate to ask for a little help.  A second person looking at your work or assumptions can help you navigate roadblocks faster than doing it yourself.  We require second opinions in medical discussions so why not do so with our daily work as well?

Rob Broadhead

Rob is a founder of, and frequent contributor to, Develpreneur. This includes the Building Better Developers podcast. He is also a lifetime learner as a developer, designer, and manager of software solutions. Rob is the founder of RB Consulting and has managed to author a book about his family experiences and a few about becoming a better developer. In his free time, he stays busy raising five children (although they have grown into adults). When he has a chance to breathe, he is on the ice playing hockey to relax or working on his ballroom dance skills.

Leave a Reply