26 ms·
The straw man here is that you can use containers poorly and do automated builds without containers. In the end, the first 1-2 days of stumbling are a rounding
by debacle 11y ago
The straw man here is that you can use containers poorly and do automated builds without containers.
In the end, the first 1-2 days of stumbling are a rounding error on a programmers overall productivity and getting the environment set up is only a small piece of that.
The real take away is that you need to develop in an environment that's as similar to production as possible. Virtualization, containers or no, is great for that.
- nzoschke 11y agoMy personal experience... The first 1-2 days are a rounding error. But it's very common for all internal tooling to be undocumented and fragile. This is a cost a team will pay every day in developer efficiency. This is a people and team problem. A sign of a team that cares about this is when the time to first deploy for an engineer is fast and safe.
- debacle 11y agoDefinitely. I'm a huge proponent of easy builds. The six month ramp up time for new hires doesn't exist in 2015.