It should take 2 hours max to set up tooling.
You're lucky if you got an access to everything you need on day 1, not to mention setup the tooling.
You can't improve the product if you don't know it yet and that takes time.
I try to have folks delivering business value even if very small within a week or two. I find it reduces a lot of new hire anxiety around performance if they can ship _anything_ relatively quickly.
In a different sector, 20-30 people is the stage where you should be capitalizing on how much faster you can move than the large bureaucratic incumbent, and if there's red tape that takes weeks to navigate it means someone in the company put it there.
I am aware of that; I like it that way. I like long term stability and large bags of money without stress.
The capitalising and ‘faster’ and hurry and stress you speak off is nice if you want bankrupt-or-unicorn. We don’t need to be market leader or whatever; we need to have stability decade after decade and we do. I like profit of millions$/year and small teams, not some breakneck VC funded fast growing all-or-bust stuff. Each their own of course.
While I don't think as a blanket rule a new hire should push prod code on day or week one—they should be able to without being ham-stringed by needless bureaucracy that has nothing to do with security or engineering. (IMO)
At an earlier startup, however, we expected someone to push to prod by the end of their first day. It was stressful for new and current hires alike!
;-)
Considering the total time spent on the machine setup, it takes approximately ~2.5 days. This includes installing all the tools like Docker or IDE, setting up access to cloud environments, and VPN. Some of it is automated, and some of it is manual. It also involves installing homegrown tools, which new people won't be familiar with, and you can't find anything online.
Especially when those statements pretend to be gospel shared from the SWE gods.
But, it's the "everything else" that takes awhile. Email filters, browser settings, bookmarks...
Go is simple, but it also has many gotchas. Knowing them also helps.
Also, when someone new has joined, the new environment could be overwhelming for them, and I'd like to ease all this and slowly induct them.
---
If you are curious, here are the Go onboarding resources (doing them in this order is preferred)
- The tour of Go - https://tour.golang.org/welcome/1
- Go concurrency exercises - https://github.com/loong/go-concurrency-exercises
- Common Go gotchas - http://devs.cloudimmunity.com/gotchas-and-common-mistakes-in...
- Concurrency is not parallelism - https://vimeo.com/49718712
1. A week before their joining, we ship the laptop
2. I'd have a calendar ready for them, which gives an overview of what they will be doing for the next three months
3. First week goes into setting up the tooling on the machine. Someone from the product team gives an overview and entire product walkthrough. Next, they spend some to play with the product as a user. This week also involves the initial orientation session.
4. We use Golang heavily, however, the people joining might not know it. The second week goes into doing the tour of go.
5. Third week they spend on onboarding tutorial that shows how to write a small service, generate APIs, build, and deploy it in our infra.
6. Fourth week they will spend shipping a really small feature to the production.
7. Since day one, they'd have assigned a buddy who becomes their go-to person. Buddy also explains them about the culture, how things typical done here etc.
8. First three months, they'd spend working on a feature along with someone which also involves some good amount of pair programming.