My Thinking
Point-of-view pieces on platform engineering, GitOps, and AI agent infrastructure for CTOs and VPs of Engineering.
Solutions
Complete, opinionated approaches to recurring platform problems.
Featured

5 Challenges of Using AI for Platform Engineering
AI is transforming software development, but platform engineering presents unique challenges. While LLMs excel at writing application code, they struggle with platform management tasks. Here are the 5 key challenges and why platform engineering needs a different approach to AI.
8 min readAll articles
AI is transforming software development, but platform engineering presents unique challenges. While LLMs excel at writing application code, they struggle with platform management tasks. Here are the 5 key challenges and why platform engineering needs a different approach to AI.
**UPDATED on 10.6.2019** (after the release of OpenShift 4.1): Added information on OpenShift 4. **UPDATED on 30.8.2019**: Added information on CodeReady Containers for running single OpenShift node. OpenShift has been often called as “Enterprise Kubernetes” by its vendor - Red Hat. In this article, I’m describing real differences between OpenShift and Kubernetes.
I can’t imagine deployment process of any modern application that wouldn’t be orchestrated by some kind of pipeline. It’s also the reason why I got into containers and Kubernetes/OpenShift in the first place - it enforces changes in your approach toward building and deploying but it makes up for with all these nice features that come with Kubernetes.
## Beautiful but useless systems Hundreds of applications, thousands of users and millions of requests - that is often a landscape of a modern IT environment. However, problems are still the same.
Imagine for a while that your organization is like a village where there are regular residents and shamans who keep most of the knowledge for themselves. This is a story about them and why it is dangerous, how to manage it and prevent from reaching your goals and causing harm to other residents.
So you’ve decided to go with Kubernetes and started building your container images. Now the question is where to push them and how to manage them properly?
One of the features that comes with Kubernetes is its ability to scale horizontally services running on it and use available resources more efficiently. I’ve been hearing that containers are just _lightweight virtualization_ (which is not true) so you can put more apps on the same resources. I can agree that it’s partially true
Containers are considerably faster than virtual machines - at least that’s what most people say. But do they actually bring more speed to overall development and deployment process? Let’s find out in the third part of my article series.
Is it true that after so many years we finally have real, portable format for all applications? It seems that we’ve come very close to that goal and it’s time to find out more about portability that comes with container revolution.
We had many revolutions in IT infrastructure world over past 20 years or so. Virtualization promised hardware abstraction, private cloud promised lower costs and flexibility and containers keep adding more to that pile creating a vision of perfect world.
We’ve been falling for the containers hype for the past few months and Kubernetes has emerged as a leader among container orchestrator to help build solutions on a bigger scale than your own laptop. Here are 10 reason why it’s won the war and become first choice for container orchestrator.





