Tech Notes

3 stages · about 8 min of reading

A roadmap for your first developer job

No need to read the whole blog. Follow the order below — each stage has a clear goal and a few short posts to reach it.

  1. First week at work

    Understand the project and work safely with Git

    Run the project on your own, understand how the team gets code into the main branch, and stop worrying about breaking things.

    After this stage you will

    • Run the project locally from the README alone.
    • Write small, clear commits, and know how to undo a mistake.
    • Open your first pull request the way your team expects.

    Read in order

    1. How to write a README: where every good product starts1 min read NewBeginnerSeries #1
    2. How to write good commit messages your future self will thank1 min read NewBeginnerSeries #2
    3. Five Git commands to undo mistakes without panicking1 min read NewIntermediate

    Coming soon: Read an unfamiliar codebase in 2 hours · Your first pull request: a checklist before asking for review

  2. First month

    Ask well, learn fast and use AI with intent

    Get yourself unstuck most of the time, and when you do ask, ask clearly enough to get an answer right away.

    After this stage you will

    • Describe a problem with a template: expected, actual, already tried.
    • Keep notes after every learning session.
    • Use AI to go faster while still being able to explain every line of code.

    Read in order

    1. How to ask for help as a junior developer: three questions first1 min read NewBeginnerSeries #3
    2. How to take notes when learning something hard1 min read NewBeginner
    3. An AI coding workflow that keeps you doing the thinking1 min read NewIntermediate

    Coming soon: Read a stack trace without panicking · Debug methodically instead of trying things at random

  3. First three months

    Start making technical decisions

    Propose solutions with reasons, write down the trade-offs, and defend your choice in front of the team.

    After this stage you will

    • Compare options against real constraints, not trends.
    • Record technical decisions so the team does not argue them again.

    Read in order

    1. How to choose a framework: start with the problem, not the tool2 min read NewAdvanced

    Coming soon: Review other people's code kindly · Estimate work without guessing

Want the next roadmap posts?

Whenever a “coming soon” post is finished, the newsletter will let you know.

Get new notes