Design World’s Post

With a rapidly growing community and tooling landscape, platform engineering is clearly here to stay. But, as with any (relatively) new trend, there still remain a lot of unanswered questions. Humanitec recently published the first State of Platform Engineering Report - here are the key things learnings from the report along with important trends in platform engineering. https://lnkd.in/eX-K-QYi

In the rapidly evolving realm of technology, it’s no longer sufficient to rely on assumptions and anecdotes when it comes to measuring success. After all, we're in the era of measurable engineering, where every facet of our organization is quantifiable, and data-driven insights are shared openly across the team. In this article, Joey McCord shares some knowledge about the true power of numbers. https://lnkd.in/g43BayFc

Fascinating chat with a CTO on Monday: "Our engineers are amazing. Our systems are solid. But as we've scaled, understanding production got harder and costlier, not easier." This keeps coming up: The best architecture in the world still needs human-readable observability. Growth is when "works perfectly" and "understandable quickly" need to be the same thing. #Engineering Learning

Platform engineering is a hot topic these days and in some shape or form we're all doing it (we'll explain in the video...). What are the benefits you can get from it and how can you figure out where you stand and where you might want to be? Enter CNCF's Platform Engineering Maturity Model: 🎥 Platform Engineering Maturity: How to build a Good Platform - https://lnkd.in/dVZXcKbs Abby Bangser of Syntasso explains why platform engineering matters and how the maturity model can help everybody to orient themselves, to set targets, and to then plan how to improve their platform practices. The platform engineering maturity model looks at five platform aspects: • Investment: How are staff and funds allocated to platform capabilities? • Adoption: Why and how do users discover and use internal platforms and platform capabilities? • Interfaces: How do users interact with and consume platform capabilities? • Operations: How are platforms and their capabilities planned, prioritized, developed and maintained? • Measurement: What is the process for gathering and incorporating feedback and learning? For each of these aspects, there are four levels of maturity that organizations can be at: • Level 1, Provisional — Voluntary or temporary • Level 2, Operationalized — Dedicated team • Level 3, Scalable — As product • Level 4, Optimizing — Enabled ecosystem It's important to keep in mind that the goal isn't for all organizations to be at the highest level. That can be quite expensive and not make a lot of sense depending on the goals of an organization. But the maturity model provides a way to figure out where organizations are and where they may want to be. If there's a difference between these two, then investing into platform practices probably is a good idea. Here are the resources mentioned in the video: - Cloud Native Computing Foundation (CNCF) Platform Engineering Maturity Model - https://lnkd.in/efNHpN88 - Cloud Native Computing Foundation (CNCF) Platforms White Paper - https://lnkd.in/dRC6_J8u - Richard Seroter: The Modernization Imperative: Shifting left is for suckers. Shift down instead - https://lnkd.in/d-hyf8v9 If you're interested in regular news from the API space, including updates about new tools and technologies, subscribe to "Getting APIs to Work" here: https://lnkd.in/deNfRre #api #apimanagement #platformengineering #developerplatform #devops #scaling #apiplatform #gettingapistowork #digitaltransformation

Are you interested in successful platform engineering? Check out this article I wrote on the importance of bringing a product mindset to the platforms we build. Gain a new perspective on how to approach platform engineering and discover how it can improve the products you create and operate. Read now: https://lnkd.in/e6GuE-we

Engineering leaders often ask us about benchmarks, because they want their engineering teams to focus on improvement areas with the biggest impact. The problem is, most engineering benchmarks we’ve seen: ❌ …are too broad. With 20 metrics, how are you supposed to know where to start? ❌ …encourage optimization far past the point of diminishing returns. If your average pull request cycle time is already 22 hours, does it really make sense to try to get it down to 20? That’s why we took a pragmatic approach to benchmarks and zeroed in on five metrics that are so fundamental to engineering effectiveness that if your organization consistently lands on the “needs attention” range on any of them, you’ll immediately know where to invest. Check out the benchmarks, and make sure to read our blog post on how to use them.

An interesting concept - (Software) Engineering Excellence - was discussed at a gathering of Tech folks the other day, and it really got me thinking. It was nice to hear some interesting take on this concept from different people. In my view, instead of reducing the concept to a Buzzword, as is usually the case, Engineering Excellence should be conceived as a mindset that marries high-quality standards with innovation, efficiency, and continuous improvement. The concept should be about engineering solutions that are not only robust and reliable but also forward-thinking, encouraging us not just to solve the problems at hand, but to reimagine what's possible, pushing the boundaries of what we thought was achievable. It goes without saying that this would require a culture that values learning as much as achieving, where mistakes are seen as opportunities for growth and innovation is not just welcomed, but expected. Do you think excellence in engineering a myth or an achievable aspiration? #EngineeringExcellence #Quality #Innovation #ContinuousImprovement #TechLeadership

🚀 Platform Engineering: The Buzz is Real 🚀 In the vast ocean of tech trends, Platform Engineering has rapidly become the beacon for many. With its allure seemingly omnipresent, the question isn't just about joining the movement—it's about timing. Is now the moment for you and your organization to embrace Platform Engineering? Before you jump onto the bandwagon, we've crafted a comprehensive guide that sheds light on this very decision. Dive into our latest blog post to uncover whether Platform Engineering aligns with your current organizational needs and future aspirations. 👉 https://lnkd.in/ekjzh958 #PlatformEngineering #TechInnovation #StrategicDecisionMaking

If you are running fast and are experiencing problems, technology may not be the solution. It could be your culture, which can often be difficult to change It can be difficult to approach, so use tact. As we pivot towards Platform Engineering the mere establishment of a platform engineering team on its own is insufficient. Here is my hot take on what those organisation, who have nailed Platform Engineering have in common. https://lnkd.in/gdgS-cxi https://lnkd.in/gdgS-cxi

🧰 As engineers, we know the importance of great tools, but platform engineering requires more than that—it needs a culture shift. Here’s a breakdown of three key changes organizations should make to unlock the full potential of platform engineering. Worth a read for anyone looking to stay ahead! #PlatformEngineering #EngineeringCulture #TechLeadership