4 ms·
Lots of good points in this article. One big factor I didn't see mentioned is cycle time when developing or debugging. How long does it take to run some code to
by rurp 3y ago
Lots of good points in this article. One big factor I didn't see mentioned is cycle time when developing or debugging. How long does it take to run some code to test it or reproduce a bug? This is especially relevant these days since a lot of modern architecture trends like serverless, k8s, or distributed microservices can be much tougher in this area than a more traditional monolith.
There are workable approaches but they often take some legwork to get working well. Having an easy way for any engineer to quickly run and test code, especially when jumping into an area they are unfamiliar with, can save an immense amount of time.
- chrisweekly 3y agoYeah, I think container-based dev envs (devpods / codespaces and the like) are going to make more and more sense for a lot of companies, with "tighter feedback loop for interacting with prod-like env" as the primary reason.