↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

Onboarding a junior developer to your team? Here's 12 tips.

The author, drawing on her own experience as a recent junior developer, lists concrete practices for onboarding juniors into a team. She emphasizes separating opinion from best practice, early Git teaching, curated low‑pressure tasks, constructive reviews, scheduled pairing (coding and non‑coding), availability for questions, a buddy relationship, adapting to learning styles, respecting work time, frequent feedback, and modeling humility.

Reading notes
#

  • The post was prompted by a tweet asking what helps when hiring a first junior developer and what red flags to avoid.
  • When explaining concepts to a junior, seniors should clearly distinguish between personal opinions and established best practices.
  • Providing resources that explain why something is considered best practice helps juniors separate feelings from facts in an opinion‑heavy industry.
  • Early in onboarding, seniors should walk through commonly used Git commands, treating nothing as too basic.
  • Many bootcamps and university programs give limited exposure to collaborative Git workflows, so branching and pull requests can be new at a first job.
  • Explaining what each Git command does conceptually is encouraged, and juniors should be taught how to rebase properly.
  • Juniors should receive low‑pressure but meaningful work, such as nice‑to‑have improvements or general refactoring, accessibility, and performance tasks.
  • Teams should prepare a dedicated backlog of tasks for the junior, rather than expecting them to independently decide what to work on.
  • Code reviews are described as major for learning and team trust; they can either be constructive or damaging.
  • Reviewers should highlight what is done well and explain why something is problematic instead of just demanding fixes or giving solutions.
  • Regular, scheduled pair programming sessions (for example, at least twice a week) help juniors learn, with tasks either shared or alternating.
  • During pairing, the driver and navigator roles should alternate, and in some cases the junior may learn best by observing and asking questions.
  • Pairing can also focus on non‑coding topics such as workflow, task prioritization, and approaches to learning new things.
  • Non‑coding pairing examples include watching how someone conducts a code review, tests their own code, dives into a new project, manages time, or plans a company‑wide presentation.
  • Seniors are encouraged to treat the junior as a top priority and to pause their own work to help when questions arise.
  • If the mentor does not know an answer, they should help the junior find it, for example via StackOverflow or by connecting them with someone knowledgeable.
  • A quoted tweet from Jess Mitchell stresses responding to questions without judgment and using encouraging phrasing instead of expressing surprise at a junior’s lack of knowledge.
  • The junior should be assigned a buddy or mentor who is not their direct manager and who can guide them through onboarding.
  • Juniors should feel safe discussing problems openly with their buddy, ideally meeting at least weekly for the first six months.
  • The team should learn the junior’s preferred learning style and match resources accordingly, such as offering books and written articles instead of video courses when appropriate.
  • Managers and seniors should model respect for the junior’s time by not sending communications at odd hours or unnecessarily pushing for tasks.
  • Expectations about working hours must be clearly stated; the author recounts a case where unclear lunch break rules were later used against her.
  • Encouraging wellness includes recommending self‑care approaches and, when safe, being open about one’s own mental and physical health.
  • Juniors should receive regular feedback and status updates, with weekly feedback suggested during any probation period.
  • The author notes that juniors often assume they are performing worse than they are, so feedback can correct misperceptions and allow time for change when needed.
  • Seniors should show humility by admitting when they do not know something and by searching for answers together with the junior.
  • Juniors should have chances to give feedback to their mentors in multiple formats, such as face‑to‑face or written.
  • The author frames the junior’s success as tied to the mentor’s success, making it important to understand how one is doing throughout the onboarding process.