This project is something I’m building in public. Slowly, thoughtfully, and with a lot of care. If you find it interesting or useful, sharing this post really helps and means more than you might think.

Thanks to everyone supporting the journey so far 🙏

You can get your free copy by:

1️⃣ Subscribing to the Crafting Platforms newsletter (newsletter.craftingplatforms.com/subscribe)
2️⃣ Checking the Welcome email, which includes a download button for both PDF and EPUB versions

The role of a platform isn’t to block developers. It’s to make the right path obvious, well-paved, and easy to follow while keeping guardrails in place so teams don’t accidentally drift into unsafe or unsustainable territory.

Good platforms don’t remove choice. They reduce unnecessary decisions.

This is why golden paths matter.

A golden path is not the only way to reach a destination. It’s the simplest, safest, and most supported one. Other paths can exist, and sometimes they’re necessary, but they all come with additional responsibility.

El conformista que no quiere cambiar, tampoco se lo pasa muy bien. Pero en general, es así. El que impulsa es el que pone toda la carne en el asador, y muchas veces se le quema… y se la tiene que comer el.

This is funny.

Don't forget to subscribe to the newsletter to get the first two chapters of the book for free.

newsletter.craftingplatforms.com

It’s not a deep dive (that comes later), but a way to explain why the IDP is the right unit of thinking for platform engineering, and why a product mindset is just one part of it.

If you find it useful, I’d appreciate a share so that more engineers working on platforms can discover the project.

So I stepped back, reframed the chapter, and turned it into an introduction to the IDP: the core concepts, the foundational capabilities, and the structure that supports everything else we’ll build in the book. I think it is important to make it clear from the beginning where we are going.

I consider myself matured in DB monitoring, but the insights I got by asking it to check a DB server over a 24h period is just astonishing. In a blink of an eye. And the recommendations that followed.

¿Ceder asiento o tortazo de Batman? 🤔 buenísimo.

Engineering works exactly the same way. It has an implicity momentum that makes adoption harder.

Platform teams will fail if they ignore it. I tell you more in Crafting Platforms.

newsletter.craftingplatforms.com

#platform #engineering #devops #culture

To change its direction, you need to apply a gentle, continuous force over a long arc —sometimes with the help of a tugboat— to slowly bend its trajectory. There is no such thing as a sudden 90-degree turn in a ship that size.

You should focus on addressing today’s problems, whether or not that’s something the platform should support. Build trust. Make partners. Sophistication will come later. You deviate current engineering’s momentum towards your desired platform by gently pushing them over time. It’s applied physics!

Sure, technologically speaking I love the challenge. But, listen. No matter how shiny your platform is if you are not fixing developers problems along the way. You can’t spend months building a platform and hope developers will jump on it once you go live.