Articles

Notes on reading repositories, working as a team, and showing the work you actually did.

• Why you should study other teams' repositories

  A well-built repository holds something more valuable than finished code. Here is what to look at, and in what order.

• Don't get trapped in your first team workflow

  The way your first team worked can quietly harden into "the only right way." Here's how to read other teams' workflows and bring the good parts into yours.

• How to turn a team project into portfolio proof

  The hardest part of putting a team project in your portfolio is describing your own share accurately. Here's how to pull evidence from the repository and fit it on one page.

• What did this applicant actually build?

  How to quickly understand an applicant's share of a team project repository, and what to keep in mind when reading the numbers.

• Commits vs. lines changed: how should we read contribution?

  In the same repository, the contribution ranking can flip depending on the measure. Here's what each number tells you and how to read them together.

• Talk about contribution with records, not feelings

  There's a lot you can do before someone says "they did nothing." Here's how to look at the record together and talk about contribution without a fight.

• What team rules should you define first?

  Five agreements worth settling on day one of a new project, and how to borrow the rules of a team that already works well.

Curious how this service was built? Read the development notes from the Hidly team (in Korean).