Both Kubernetes and the DevOps movement have faded into the mists of time Neither can exist without the other in organisations that are interested in contemporary programming. Isn’t it true, though, that DevOps and Kubernetes have nothing in common? How, in the end, is this integration even conceivable.
TLDR; Scaling teams are hard. A platform team done right can help ease the hardships.
At Conde Nast International we grew from a team of 20 engineers to less than 100 in less than a year. We found out that building out a system that will be used in many markets has a lot of moving parts and repetition. For example rebuilding the infrastructure and application configuration. Adding third party add-on software. Building the application using CDN redirects. DNS registration and configuration.
As your codebase expands, small errors and edge cases you don’t expect can cascade into larger failures. Bugs lead to bad user experience and ultimately, business losses. One way to prevent fragile programming is to test your code before releasing it into the wild.
There is more value in testing than you might realize. One of the best ways to fix a bug in your code is to write a failing test that exposes it. Then when you fix the bug and re-run the test, if it passes it means the bug is fixed, never reintroduced into the code base.
The user is not an expert. My doc doesn't require me to know the difference between low-density and high-density lipoproteions.
Don't assume user should know what kind of browser they use or what is the best flow to use the app.
But yes, no matter how much you think of it, sometimes the user demand feature that seem pointless and he can have difficulties with functions that seem to be self-explanatory.
❤️ Brainstash Inc.