|
| 1 | +--- |
| 2 | +title: "How Platform Engineering Helps You Move Like a Startup Again" |
| 3 | +authors: [jurajk] |
| 4 | +--- |
| 5 | + |
| 6 | + |
| 7 | + |
| 8 | +There’s been a quiet shift happening in engineering teams over the last few years. DevOps isn’t going away, but it *is* evolving. More and more companies are moving toward Platform Engineering, and honestly, it makes a lot of sense. |
| 9 | + |
| 10 | +The goal is still the same: help developers ship faster and more reliably. But the approach is different. While DevOps emphasizes collaboration between devs and operations teams through shared responsibility, Platform Engineering seeks to build products that abstract the complexity away from developers. These products are often called [**Internal Developer Platforms**](https://cyclops-ui.com/blog/2025/02/13/what-are-dev-platforms). |
| 11 | + |
| 12 | +Because internal developer platforms come in different shapes and sizes, it can be difficult to provide a clear answer to “Why do I need it?” Their value varies from organization to organization, but I believe the benefits could be grouped into two major categories: **developer experience** and **time to market**. |
| 13 | + |
| 14 | +### *Support us* 🙏 |
| 15 | + |
| 16 | +*We know that Kubernetes can be difficult. That is why we created Cyclops, an open-source framework for building developer platforms on Kubernetes. Abstract the complexities of Kubernetes, and deploy and manage your applications through a customizable UI that you can fit to your needs.* |
| 17 | + |
| 18 | +*We're developing Cyclops as an open-source project. If you're keen to give it a try, here's a quick start guide available on our [repository](https://github.com/cyclops-ui/cyclops). If you like what you see, consider showing your support by giving us a star ⭐* |
| 19 | + |
| 20 | +> ⭐ [***Star Cyclops on GitHub***](https://github.com/cyclops-ui/cyclops) ⭐ |
| 21 | +
|
| 22 | + |
| 23 | + |
| 24 | +## Developer Experience |
| 25 | + |
| 26 | +**Developer experience is closely tied to productivity**. When developers have access to clearly defined golden paths, they don’t waste energy figuring out how to deploy something or what’s considered “the right way” to do things. |
| 27 | + |
| 28 | +The **same goes for DevOps engineers**. Instead of acting as a “help desk” for developers every time something needs to be deployed (no matter how small the change may be), they can focus on more important and less repetitive tasks - improving stability, performance, and managing infrastructure costs. |
| 29 | + |
| 30 | +Increasing the developer experience is not only important for productivity but it has also been discovered to boost **developer retention**! For example, when Spotify built its own internal developer platform (known as Backstage), they realized that their developers were [**5% more likely to stay at the company one year later**](https://backstage.spotify.com/discover/blog/how-spotify-measures-backstage-roi/). Having less fluctuation in developers shouldn’t be easily discarded! |
| 31 | + |
| 32 | +> A recent [DORA study](https://dora.dev/research/2024/dora-report/) found a link between IDPs and **burnout**! One of the explanations is that organizations that struggle with developer burnout build IDPs to combat it. |
| 33 | +
|
| 34 | + |
| 35 | + |
| 36 | +## Time to Market |
| 37 | + |
| 38 | +Simply put, time to market is the amount of time it takes to go **from** **having an idea** **to** actually **delivering a working product** **or feature** to users. Internal platforms dramatically accelerate time to market. The faster developers can ship, the faster the company can grow. |
| 39 | + |
| 40 | +This is something companies of all sizes should aspire to. From startups that want to quickly introduce new features and test ideas on their users, to large enterprises that have rigid processes which slow them down. Having an IDP that provides golden paths for everyone makes the shipping process much smoother. |
| 41 | + |
| 42 | +Faster shipping enables fast iteration, safer experimentation, and more frequent releases. This creates a feedback loop where **velocity drives more learning**, which leads to better features and better outcomes. In simpler terms, faster time to market means more revenue for the company. |
| 43 | + |
| 44 | +> *… therefore, we win on engineering velocity above everything else.* |
| 45 | +> |
| 46 | +> *There’s so much to ship. the more we ship, the more reasons people have to use us.* |
| 47 | +> |
| 48 | +> *Even when we build the wrong thing or ship something that doesn’t work well, we learn the clearest lessons from something we shipped, not something we hypothesized about…* |
| 49 | +> |
| 50 | +> *~ [James Hawkins](https://www.linkedin.com/posts/j-hawkins_choosing-trust-and-feedback-over-process-activity-7309584209394757632-lg9C) co-CEO of PostHog* 🦔 |
| 51 | +
|
| 52 | + |
| 53 | + |
| 54 | +## Bonus Category? |
| 55 | + |
| 56 | +There is a third possible category of benefits, which would be infrastructure cost management. But again, that depends on the type of platform you are building and how your current processes look like. |
| 57 | + |
| 58 | +When it comes to implementing an IDP, you have two options: **buy one** off the shelf or **build it yourself**. Both come with benefits and drawbacks. Buying one can be faster, but you will eventually outgrow it. Building one is preferable, but it takes time and resources. |
| 59 | + |
| 60 | +However, **building one doesn’t have to be from scratch**. In fact, most top-performing teams leverage a combination of open-source and vendor tools ([the data](https://humanitec.com/whitepapers/devops-benchmarking-study-2023)). You can use an open-source tool like [**Cyclops**](https://cyclops-ui.com/) to get you most of the way there! **Check out how we use your Helm charts to build internal developer platforms in a jiffy**! |
| 61 | + |
| 62 | +> ⭐ [***Star Cyclops on GitHub***](https://github.com/cyclops-ui/cyclops) ⭐ |
0 commit comments