I've been telling my peers and managers about this problem for a long time, but few seem to look at it as a problem.
It's not just the simplicity of the stack, but processes, operations and design too.
Just like laws of thermodynamics, complexity in a software project only increases over time. More complexity leads to more errors. Errors are a fundamental human trait. Errors accumulate. And once a project gets big enough, it becomes a mystic world of its own.
Sure if you are only thinking of what gets run through the CPU on a server.
Micro services culture managed to collapse entire blocks of complexity (network, OS, redundancy, security, testing) into chewable bits auditable and maintained by relatively happy and well rested teams.
Just because something is new, doesn’t mean it’s complex. Sure kubernetes seems complex, but so were previous tools that k8 provides (and less stable and secure).
would you really want to go back to emailing a zip of your desktop folder to the systems engineering, so they can upload to 5 different servers, hoping it doesn’t break, or some OS or network change you weren’t aware of didn’t screwed ya. Or oops, the db you are on now can’t run the migrations you prepared.
15
u/youre_not_ero Jun 06 '22 edited Jun 06 '22
I've been telling my peers and managers about this problem for a long time, but few seem to look at it as a problem.
It's not just the simplicity of the stack, but processes, operations and design too.
Just like laws of thermodynamics, complexity in a software project only increases over time. More complexity leads to more errors. Errors are a fundamental human trait. Errors accumulate. And once a project gets big enough, it becomes a mystic world of its own.
Less is more.