4 ms·
I don’t know why, I don’t have an opinion on it, it’s just something we have done. My point was only that pushing (any) code to prod on day 1 doesn’t have to b
by eutropia 5y ago
I don’t know why, I don’t have an opinion on it, it’s just something we have done.
My point was only that pushing (any) code to prod on day 1 doesn’t have to be an entitled fantasy.
- HWR_14 5y agoOh, yes. You can push some small predetermined change like that through, or something else that doesn't require codebase knowledge. Although that is a thinly veiled test of your knowledge of the build process, in the same way "find a dog" is a made up thing to do for an internal directory tool.
- mrslave 5y agoOK there's a lot of good points on both sides of this. For one: pushing meaningful code change on day 1 may be unrealistic. For another: at least we've initiated the new team member into the full process of contributing to the product's code base, and their manager knows there are no administrative blockers (workstation, account, 2FA token, etc.). I know which I prefer. Also fixing a small (and admittedly probably low priority) defect is an achievable goal and a pretty cool way to get your toes wet. At least you're in the pool.