11 ms·
hitting this paradox a lot with containerisation. Spent a good bit of effort building everything into a fully containerised stack, thinking once we got through
by zmmmmm 2y ago
hitting this paradox a lot with containerisation.
Spent a good bit of effort building everything into a fully containerised stack, thinking once we got through the hard parts of it, everyone would be more productive and new devs would get up to speed fast. But it's not like that. We just have a whole different set of complexities, mainly at all the container boundaries where ports, volumes, user ids, file permissions, file paths etc now create issues where before they didn't.
I think we probably came out with a modest win, but I'm not sure it beat out what we might have achieved with the same effort going to other productivity measures.
- redserk 2y agoI can’t speak to your experience, but often times I’ve run into this in development teams where there was not a strong level of systems knowledge or not a very strong understanding of exactly what an application needs to run. Perhaps one of the more amusing issues I’ve seen was someone’s surprise that a temp directory creation put the files in /tmp instead of the application’s working directory. It’s not something a lot of people would think about in development/testing I suppose. More often than not, containerization has seemed to force developers to better understand the impacts of their code on the system.