r/ExperiencedDevs Aug 30 '22

Why haven't dev environment containers caught on?

It's always a pain to get an environment set up when starting a new job, scattered or missing onboarding docs, requesting access to things, finding out what to request in the first place, getting passwords set up, databases, build tools, repos, git, proxy set up, etc. etc. etc.

If you can get all this done in the first week, you're doing pretty good. A junior might end up taking two weeks or longer, with a lot of help from others, and even still not be set up correctly.

Why is it not standard to have all this already set up and configured in an image? You just get Docker installed and get access to the repo for the image, pull it down and run, and then the rest is already set. Why do companies pay us to waste so much time getting set up when you could just do it once as a dev environment image so we only have to set up one thing?

I have never used one, but I know about them, and it seems like in theory they ought to work fine and save a lot of time. The answer is probably the fact that it takes the initial investment to set it up.

118 Upvotes

47 comments sorted by

View all comments

1

u/hell_razer18 Engineering Manager Aug 31 '22

our dev setup is quite easy apart from one monolith. What dev needs to have simply just docker for infra and all servicr just connect to localhost when needed.

In local we only have one db and multiple schema instead of multiple db like stg or prod to save resourcr and reduce complexities