In the tech world, trends can often resemble the ever-changing nature of fashion. Technology decisions frequently mirror the patterns we see in clothing: driven more by what’s trending rather than by practical necessity. The race to adopt the latest “it” technology, such as generative AI or Kubernetes, can often leave organizations jumping on the bandwagon without fully understanding if it fits their needs. For instance, companies are pouring resources into ChatGPT-like tools, convinced by the success stories of others—like the Commonwealth Bank of Australia reducing fraud losses with AI. But while some succeed, this doesn’t guarantee that every company will find the same results. The problem arises when tech decisions are based on hype rather than what’s truly needed.
The tech world often falls victim to the same biases as fashion—choosing the latest and loudest trend without considering the practical implications. Take Kubernetes as an example. Marketed as a revolutionary tool for managing large-scale microservices, Kubernetes is often adopted indiscriminately, despite the fact that it’s overkill for many businesses. Designed by Google for their massive, complex infrastructure, Kubernetes’ intricate setup and maintenance are unnecessary for smaller-scale applications. Yet, many organizations continue to embrace it simply because it’s the “in” thing to use. The complexity of Kubernetes isn’t just an inconvenience; it can be an unnecessary drain on time, resources, and energy that could otherwise be spent addressing actual business challenges.
One of the frustrating realities of Kubernetes adoption is that it often comes with a learning curve that many companies aren’t prepared for. As described by former users, managing Kubernetes can devolve into a cycle of endlessly updating and debugging YAML files. While this may work for large-scale systems, for the vast majority of companies, it’s a case of overcomplicating things unnecessarily. Some argue that Kubernetes’ appeal is driven not by its actual suitability, but by a desire among senior engineers to justify their roles or stay ahead of the technological curve. But the reality is, complexity for complexity’s sake doesn’t benefit anyone—especially when a simpler, more effective solution is available.
This phenomenon isn’t exclusive to Kubernetes or AI, either. It highlights a deeper issue in the tech industry: decisions are often made based on trends and what’s seen as cutting-edge, rather than on what’s appropriate for the problem at hand. When tech leaders focus on adopting the “hot” technologies to keep up with the competition or the latest industry buzz, they risk ignoring the nuances of their own infrastructure and needs. The truth is, the best technology strategy often begins with a simple but powerful approach: “it depends.” And that’s something every company should remember when making decisions about which technologies to adopt.