Setting up the environment for development, especially for onboarding, is a crucial operations step that allows the devs to stand on the shoulders of giants.
If you're asking them to test in prod ( not providing a local test environment for component testing ) or reinvent the wheel ( and get the wheel type right... should I build a bicycle wheel or a railcar wheel? ) then the first week of a new hire is spent trying to align to his or her peers.
Depends on the size/scale of the larger org and the developer team in question. There's a lot of variance even in internal corporate tool teams as to what gets used. Are you supporting an older .Net Winforms app, or are you supporting a React/next application or a Java Spring app? The tools you need and use will be very different.
Is it really worth trying to automate everything for a team of 3 devs on a given project? Should this just be done by the devs on the project if that's the desired outcome?
If you're asking them to test in prod ( not providing a local test environment for component testing ) or reinvent the wheel ( and get the wheel type right... should I build a bicycle wheel or a railcar wheel? ) then the first week of a new hire is spent trying to align to his or her peers.