3 ms·
Day 1: laptop, credentials, hr and high level security/policy stuff. 2-3hr pair programming session to grab an editor, git checkout of their first assignments
by amichal 3y ago
Day 1: laptop, credentials, hr and high level security/policy stuff. 2-3hr pair programming session to grab an editor, git checkout of their first assignments repo and to push a tiny edit (small bug or doc fix). This ensures they have the tools and access they need to get started. People report it as a long hard day but its pairing and collab so they meet the real people and real work
Goal is to ship a real contribution in week 1 if they know the stack. Week 4 if they don't.
Company culture, business etc goes in parallel at 2-4hr a week of formal meetings for the first month or so. It used to dominate the first week but was too much context to learn in one week.
There is an assigned tech buddy all the time and daily scheduled q&a time from a lead for the first month. 3 months in and they count as a full FTE on the schedule. Before that we expect a good chunk of the day goes to learning and understand that goes for the buddy as well.
Edit: of course the learning never stops for any of us but this so far for me has been the quickest way to get to learning together while contributing as you go