↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

New Dev? Job-Hunting? Avoid These GitHub Mistakes!

The post argues that new developers should treat a GitHub profile as a job-seeking portfolio, not a dump of every app they have built. It recommends choosing projects that show growth, document struggles and solutions, combine several working features, and are worth talking about in interviews.

Reading notes
#

  • Avoid adding every app you have built, because that can make a profile look unfocused or insecure.
  • Prefer projects that show growth across versions, including improvements and refactoring.
  • Include apps that were difficult to build and document the problems and how you solved them.
  • Favor projects that combine multiple features that work together, since that resembles real work more closely.
  • Only include projects that you feel confident talking about and that you genuinely enjoyed building.
  • A README should explain why the app was built, list its functionality, describe problems and solutions, and give local setup instructions.
  • Empty or default READMEs leave hiring managers with little sense of what the repository contains.
  • Every app included in the GitHub portfolio should be deployed online.
  • If the app is mostly back-end, a simple front end can be used to provide access to it, with that limitation explained in the README.
  • Finished projects can be pinned on the profile, while unfinished ones can be marked as in progress.
  • The portfolio should tell a story about competence, self-direction, and the ability to choose and assemble useful technical solutions.