Platform engineering, from a technical perspective, isn’t new, it’s been around for years. Even GitOps-like practices existed in simpler forms: some companies deployed apps by dropping packages into an SMB storage with properties files, using endless Bash loops to detect changes and update deployments.

Kubernetes itself builds on Linux fundamentals and concepts like reconciliation loops, Long-Live HTTP requests, and resource versioning to align desired and running states.

So why the surge in new tools, job titles with endless certifications, and global conferences featuring hundreds of speakers? (Spoiler: I'll share my thoughts on the kubecon conference later.)

It’s all about mindset. The real shift is a renewed focus on developer autonomy, providing self-service infrastructure that empowers developers and removes dependency on infra teams.

Think of it as making developer experience "great again"

Platform engineering isn’t about tools like Backstage, ArgoCD, or Crossplane; these are just implementations. They’re branded as innovations to create new cloud-native companies, secure funding, and convince businesses that their infrastructure needs a digital transformation. Ironically, we now see a trend of companies moving back to on-premises and classic data-centers (topic I’ll cover soon).

The real takeaway? Our role should prioritize developer experience and problem-solving over just managing tools. Let's rethink our LinkedIn and resumes: perhaps "DevEx Engineer" better reflects the mission (Developer Experience). And for computer science schools? Focus on mindset and problem-solving skills over stacking certifications.

Also, let’s pause on boasting about “6xAWS, 14xGCP” badges. (Confession: I’m preparing for a new certification!)

This reflection is as much about me as it is about the industry. I'm striving to be useful, not just a “tools guy.” In fact, that's why I named my company Strivly, to focus on meaningful impact and constantly strive for better solutions. 😄

Meanwhile, I’m here at KubeCon Salt Lake City. The city is beautiful, and while conferences have their criticisms, I’m here for the networking, learning new approaches, and hearing real-world use case feedback

P.S. Jet lag woke me up at 3 a.m., so maybe it’s affecting my mood. Ask me again in a few day, I might see things differently. 😉