3 ms·

Those all seem important to even moderately sized products.

• worldsayshi 2y ago
  As long as your requirements are simple the config doesn't need to be complex either. Not much more than docker-compose. But once you start using k8s you probably tend to scope creep and find a lot of shiny things to add to your set up.
• doctorpangloss 2y ago
  Some ways to tell if someone is a great developer are easy. JetBrains IDE? Ample storage space? Solving problems with the CLI? Consistently formatted code using the language's packaging ecosystem? No comments that look like this: # A verbose comment that starts capitalized, followed by a single line of code, cuing you that it was written by a ChatBot. Some ways to tell if someone is a great developer is hard. You can't tell if someone is a brilliant shipper of features, choosing exactly the right concerns to worry about at the moment, like doing more website authoring and less devops, with a grand plan for how to make everything cohere later; or, if the guy just doesn't know what the fuck he is doing. Kubernetes adoption is one of those, hard ones. It isn't a strong, bright signal like using PEP 8 and having a `pyproject.toml` with dependencies declared. So it may be obvious to you, "People adopt Kubernetes over ad-hoc decoupled solutions like Terraform because it has, in a Darwinian way, found the smallest set of easily surmountable concerns that should apply to most good applications." But most people just see, "Ahh! Why can't I just write the method bodies for Python function signatures someone else wrote for me, just like they did in CS50!!!"