Platform Engineering Bluesby Jay Cuthrell
If you need a refresher on Platform Engineering, read this post from last month:
Fudge SundayBuild a Cloud Platform FoundationRead more2 months ago · Jay CuthrellSubscribe to Fudge Sunday!
Setting aside Platform Engineering for a moment, business value engineering is an important consideration of the perceived value for the customer or consuming entity that has been provided a response to their perceived need in the form of technology. In short, was the value commensurate or not — and can it proven over the technology lifecycle from return on invested capital to the ongoing total cost of ownership.
So awkward, right?According to Paul Delory at Gartner, platform engineering can be thought of as the response to a perceived need (technology) for greater developer productivity through enhanced developer experiences. Or, as contributed by Lori Perry at Gartner, a practical example of platform engineering could mean “ […] reusable tools and self-service capabilities with automated infrastructure operations […]“.1
Further, the technology choices related to platform engineering would, ideally, contemplate business value engineering concepts as well. Interestingly, you might recall when Fudge Sunday described the increasing importance of dependency mapping across hyperscale public cloud service providers and consideration of business value engineering for customer journeys.
Fudge SundayFudge Sunday - Cloud in Public: Impact MappingView online This week we continue to take a look at public things for a public cloud. ☁️✅⚠️🛑 This issue is part 5 of a 5 part series Fudge Sunday - Cloud in Public: Status Dashboards Fudge Sunday - Cloud in Public: Engineering SLO Fudge Sunday - Cloud in Public: DevCommsOps…Read morea year ago · Jay CuthrellMandrake versus the snake 🎶
Indeed, there are enough people interested in platform engineering to create websites2 and start newsletters3. So, one could make the argument that interest in platform engineering is growing enough for those people to be considered a special interest group on the path to becoming a wider community on the path to user groups, etc… which may eventually mirror the FinOps.org progression.4
At the same time, if we pull back a bit, the terminology used so far might sound eerily familiar to those already in larger organizations that practice software development in cloud operating models. Indeed, while Twain’s history might not repeat exactly, the parts that rhyme could be set to music… and while not strict blues, the always brilliant Forrest Brazeal, Head of Developer Media at Google Cloud, has conveyed the perennial lamentation of but-this-time-it-is-different with aplomb.5
Lastly, let’s consider when convergence takes place as platform engineering keywords appear first as unique titles that become skills over time. For example, consider LinkedIn Jobs searches for platform engineering with the specific job title of “Platform Engineer”.
- United States = +1,827 job posts
- United Kingdom = 261 job posts
- Germany = 153 job posts
- Canada = 116 job posts
- India = 116 job posts
- Netherlands = 70 job posts
- Japan = 61 job posts
- Australia = 59 job posts
- Poland = 49 job posts
- France = 41 job posts
Quick filtering by Onsite/Remote/Hybrid indicates (rough math):
- Onsite = 1,725 job posts
- Remote = 1,325 job posts
- Hybrid = 294 job posts
Earlier this year when PlatformEngineering.org launched, the tools list was only four (4!) entries long. Of course, the initial tools list may have simply reflected the company that launched it (Humanitec) and a few placeholders.
Circa 30-Jan 2022…However, the tools associated with PlatformEngineering.org are growing one community submission6 at a time. For perspective, here is a longcat via developer tools screenshot now includes twenty-one (21!) tools as of this newsletter:
So, what tools we be added to the PlatformEngineering.org registry next to reach 100+?
Until next time… Place your bets!
I am linking to my disclosure.
✍️ 🤓 Edit on Github 🐙 ✍️
Get Fudge Sunday each week