2 ms·
1 day: - Overview of what they will work on - Give some time to install things and play around 2 day: - Ship your first (small) feature I'm surprised at s
by jokethrowaway 3y ago
1 day:
- Overview of what they will work on
- Give some time to install things and play around
2 day:
- Ship your first (small) feature
I'm surprised at seeing how long time to production is. I'd be concerned if they went 2 weeks without shipping anything.
We don't do physical onboarding as no-one is close to any of the offices, but physical get-together are huge in boosting team building. We try to do them at least yearly. Churn is way higher without them (= people don't care about you unless you drink a beer with them)
- lunarplague 3y agoI'm sorry, maybe I am not as competent as I thought I would be in this life. You want people to ship a brand new feature to your product on their second day? The kind of people who can onboard and ship a feature in a 48 period turnaround aren't working for your company, they're building startups.
- domepro 3y agoI think, generally speaking there are a lot of contexts here clashing of what people mean by "feature" and "product". For some, "the product" might be a 30+ year legacy multi million loc codebase getting slowly improved, but still old and inadequate and probably full of technical debt and a lot of domain knowledge needed to navigate. For others "the product" will be a website with a few 10k loc behind the scenes. Getting a feature out in those two environments is not the same thing.
- lunarplague 3y agoMaybe we need to define what a "Feature" is as well. I'm imagining a project that takes more than a day. Fixing a submit button is not a feature. Perspective is weird though, adding to your point.
- ChrisLTD 3y agoI'd say they should be shipping code of some kind in the first week.