4 ms·
Not cringing, but I think I understand your point... However; I feel like with modern infrastructures, projects don't really "fit" can be packaged into a conta
by johnhenry 9y ago
Not cringing, but I think I understand your point...
However; I feel like with modern infrastructures, projects don't really "fit" can be packaged into a container, and used virtually anywhere. (Oversimplification acknowledged!)
- mikekchar 9y agoContainers aren't the problem. Even without containers, it's not that hard to automate the build/deployment infrastructure. The problem is when "Joe" is the only person who knows how to do anything with X. "Joe" leaves for a high flying company that uses X. You have new requirements for the thing "Joe" was working on. "Anybody fancy working on an X project?" <crickets> "I know. Why don't we rewrite this in Y. I hear it's the new X anyway.", "Great idea!" Don't get me wrong, I'm a believer in using the right tool for the job. It's just that there's more to it than just making sure it's easy to install.
- johnhenry 9y agoTrue -- getting it to work within your infrastructure is only part of the issue. Updating and maintenance would still be an issue.