<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Developer-Experience on nclsbayona's blog!</title><link>https://nclsbayona.github.io/tags/developer-experience/</link><description>Recent content in Developer-Experience on nclsbayona's blog!</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Mon, 13 Jul 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://nclsbayona.github.io/tags/developer-experience/index.xml" rel="self" type="application/rss+xml"/><item><title>Platform Engineering: From DevOps Principles to Internal Developer Platforms</title><link>https://nclsbayona.github.io/p/platform-engineering/</link><pubDate>Mon, 13 Jul 2026 12:00:00 +0000</pubDate><guid>https://nclsbayona.github.io/p/platform-engineering/</guid><description>&lt;h2 id="platform-engineering-why-it-exists-and-why-it-matters">Platform Engineering: Why It Exists and Why It Matters
&lt;/h2>&lt;p>Modern software delivery depends on far more than application code. Product teams also need build pipelines, deployment automation, identity, secrets, networking, policy enforcement, observability, cost controls, and reliable runtime environments. When every team assembles those pieces independently, the organization does not gain autonomy. It gains duplicated work, inconsistent controls, and a growing support burden.&lt;/p>
&lt;p>Platform engineering addresses that problem by treating shared delivery capabilities as an internal product. A platform team researches recurring developer needs, builds reusable capabilities, exposes them through self-service interfaces, and operates them with the same discipline expected of any production product.&lt;/p></description></item></channel></rss>