Teamwork & Collaboration

Solving problems as a team

Understanding systems, common problems encountered and performing root cause analysis is a large part of programming. While much of the work can be done independently, discussing approaches, comparing tradeoffs and integrating new and legacy systems is very much a team sport.

$ help help

Getting help often requires requesting it specifically. Using the help command is usually a good starting point for local development. Check the Documentation (or "docs") section for whichever language or framework you are working with for more specific information. Seeking additional help online or in communities around and within your organization can uncover further clues or pathways to resolution.

Outside of the manual, asking other people can help express your problems succinctly and learn from the experience and perspective of others. Most people are open-minded and welcoming when people ask for their advice or know-how (or at least they should be).

Being honest about where you are stuck, having difficulty with, or don't know helps uncover areas that may need more exploration or technical detail. This can aid in your team's allocation of time and resources while opening room for you to grow. Succinctly describing your thought process, actions taken and potential solutions can turn your hard work and insights into a well-engineered solution. Since there are often edge-cases or situations you may have not thought of, maintaining objectivity (in terms of your solution or skill level) with clear eyes can help get to the finish line sooner than guarding your ego or withholding information to protect your status or position.