Hard agree. Though I don't think most people who exhibit the problem are consciously trying to pad a resume. I think it's more mundane than that, most people just follow the crowd and earnestly think the new layers of complexity being sold this year will solve more problems than they introduce.
People want to find blog posts that dictate a best practice or generally correct solution. They don't have the skill or experience or mindset to evaluate each distinct problem and craft the optimally simple solution for it.
All I ever see anymore is architecture and tech stacks that promise to solve the perceived weakness that's currently in fashion while starting from scratch and taking steps backward in ways that people don't even realize or appreciate were already solved.
Hard agree. Though I don't think most people who exhibit the problem are consciously trying to pad a resume. I think it's more mundane than that, most people just follow the crowd and earnestly think the new layers of complexity being sold this year will solve more problems than they introduce.
People want to find blog posts that dictate a best practice or generally correct solution. They don't have the skill or experience or mindset to evaluate each distinct problem and craft the optimally simple solution for it.
All I ever see anymore is architecture and tech stacks that promise to solve the perceived weakness that's currently in fashion while starting from scratch and taking steps backward in ways that people don't even realize or appreciate were already solved.
Question, does anyone have a suggestion for the best book about networking? I’ve been looking for a while.
I'm currently dealing with 50 microservices and an absolute mess of Helm charts to deploy a system that should be 3 services running on a Linux box.
The fight to reduce complexity seems like a losing one.