Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Kaspar Von Grünberg
Silos Are Fantastic. Just Ask Kelsey Hightower
Do you feel the rage crawling up you as you read these words: Silos are fantastic. “What is wrong with this guy?” I strongly believe this statement and think we have all been trapped in a lie. The meteoric growth in platform engineering over the last four years proves it. If you don’t believe me, let me bring in some backup. Last month, as part of PlatformCon 2024, the world’s largest platform engineering event, I closed off Day 1 with an incredible conversation with Kelsey Hightower.
How to design backends for Internal Developer Platforms
In our piece “Why every Internal Developer Platform needs a backend” we established the need for platform backends. To recap, the two main value drivers of platform engineering are a.) standardization and b.) automation. Automation means taking the request of the developer and delivering something in response. Standardization means keeping the amount of special snowflakes to a minimum, which leads to commoditization.
The role of infrastructure teams in the platform engineering era | Humanitec
Knock, knock. Who’s there? It’s platform engineering, the next big thing knocking on the door of the infrastructure and operations (I&O) team, screaming for their attention. You’ve “shifted left.” You’ve let them “build it and run it.” You went “declarative,” you did “DevOps,” you moved to the cloud and kept the lights on in the data center while the crowd cheered in Vegas at ReInvent, and Werner Vogels announced an API endpoint for S3 that you featured years ago. And now, here we are again.
Why every Internal Developer Platform needs a backend | Humanitec
The first wave of early Internal Developer Platforms (IDPs) is settling. And as the dust settles, it’s good practice to shed some light on what worked and what didn’t. While the early wave of platforms was primarily considered a “frontend-devex” world with a focus on portals, we are observing that the platform engineering movement has all too long neglected a vital piece of the puzzle: the contribution of the infrastructure and operations teams.
Platform Engineering Dies in 4 Weeks
Four weeks. That is how long it should take to build an internal developer platform (IDP). It sounds crazy, and in an environment of dead-on-arrival platform engineering initiatives plagued by years-long, multimillion dollar working groups and research phases, it would be. Fortunately, the best platforms aren’t built like that. They’re built nimble, low cost and — most of all — fast. Recent success stories make it clear that good platform engineering doesn’t take 18 months of planning.
Escape VMware lock-in with a modular Internal Developer Platform | Humanitec
The squeezing commences When Broadcom closed their acquisition of VMWare it was clear what would be coming next: Bad times for customers and partners as the acquirer has to return the colossal sum of USD 69B, promising its stakeholders hefty returns on their investment; VMware products have always been designed for lock-in first, boxing in a whopping 300,000 unique customer organizations globally.
Platform Orchestration: an industry game-changer? | Humanitec
Going mainstream Platform Orchestration is a comparably new concept. At Humanitec, we’ve been going all in on this for years and have been calling it by its name since early 2022. Since then, Thoughtworks has put it on the radar and even Microsoft is calling it out in their platform documentation. Here’s a longer summary, but let’s quickly revisit what Platform Orchestration actually is. What is Platform Orchestration?
Drive Platform Engineering Success with Humanitec and Port
Platform engineering is evolving like crazy. So many cool new tools are popping up left, right and center, all designed to boost developer productivity and slash lead time. But here’s the thing. For many organizations, this makes picking the right tools to build an internal developer platform an instant challenge, especially when so many seem to do the same job. At Humanitec we get the need to ensure you’re using the right tech to get things rolling smoothly.
How Static Config Management Kills Developer Productivity
Did you know that a static config management setup is the main reason why things go wrong for developers? And that taking a static approach to config management doesn’t work at scale? While many have a vague understanding of why and how, we’re here to help break things down. Why Config Management Today Sucks Assuming an organization has CI/CD figured out and more or less under control, every individual component should then follow a structured pattern.
Implementing Dynamic Configuration Management with Score and Humanitec | Humanitec
Top articles Introduction Dynamic Configuration Management (DCM) is the hot new thing in town. DCM was originally developed by platform engineers to drive standardization by design, and build golden paths that developers can consume with low cognitive load.
Platform Engineering Is Not about Building Fancy UIs
If I had to name the single biggest misconception some people have about platform engineering, it would be that the result of a successful platform engineering endeavor is a shiny user interface with lots of buttons to click and dashboards to look at. Many people conflate developer portals and service catalogs with internal developer platforms (IDPs), but they aren’t the same. And there are real consequences to the confusion.
Engineering Leaders: Switch to Wartime Management Now
Engineering Leaders: Switch to Wartime Management Now contributed,sponsor-humanitec,sponsored,sponsored-post-contributed, It’s helpful to recall what the key value drivers for engineering and general management are, especially in times of crisis. I have the pleasure to work with clients from Mumbai to San Francisco, and from Oslo to Cape Town. And this has recently provided me with telling insights about how their companies plan to react to the upcoming macroeconomic crisis.
What is a Platform Orchestrator?
Guest post originally published on the Humanitec blog by Kaspar von Grünberg A Platform Orchestrator sits at the core of a dynamic Internal Developer Platform. It enables dynamic configuration management and developer self-service, allowing for low cognitive load on engineers. It drives standardization by design and has a vastly positive impact on the productivity and health of engineering organizations.
I Beta Tested OpenAI’s Codex, and the Results Are Spooky Good
It won’t replace human programmers, but it will make them far more powerful Screenshot of Codex. Photos courtesy of the author. Last week, artificial intelligence company OpenAI launched Codex, a new deep-learning-driven platform that writes fully functioning software code automatically. The system — which was trained on a vast corpus of publicly available code — originally debuted as part of GitHub’s Copilot, a feature that helps programmers improve or update their software automatically.
The Fundamental Flaws of GitOps – A Statistical Analysis | Humanitec
I’m looking at hundreds of DevOps setups a year. Lately, everybody is talking about GitOps. I noticed that some teams were increasingly frustrated with this approach, while others were immensely positive. But google “GitOps”. Everyone is positive. I started to wonder why. It became clear to me that teams had a positive initial experience with the approach. Yet, frustration grew down the line.
Oops, We’re Multi-Cloud: A Hitchhiker's Guide to Surviving
Over the last few years, enterprises have adopted multi-cloud strategies in an effort to increase flexibility and choice and reduce vendor lock-in. According to Flexera's 2020 State of the Cloud Report most companies embrace multi-cloud, with 93% of enterprises having a multi-cloud strategy. In a recent Gartner survey of public cloud users, 81% of respondents said they are working with two or more providers.
Your Helm Zoo Will Kill You
This article is controversial. It aggressively questions helm-charts and current dev workflow designs, and I’m well aware that not everyone will like this. Let me be clear before we dive in: this is an enterprise view. It’s a view that is relevant to team sizes of 20 developers onwards. If you’re a smaller dev shop that builds a few apps, this doesn’t apply to you, and you should just keep things as is. But for those of you that are working at scale or that are about to scale: watch out.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Kaspar
Contact Kaspar, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack