#gregorhohpe — Public Fediverse posts

"A platform without participants isn't providing value." #GregorHohpe, #PlatformStrategy

A platform without voluntary participation is probably not providing value.

"...if your platform team is constantly engaged in setup activities, it's a signal that you should find ways to make the platform more automated or more intuitive." #GregorHohpe #PlatformStrategy

Platform customer engagement models: Self-service, setup, consulting, community, co-creation. #GregorHohpe #PlatformStrategy

"Platforms scale by enabling users to perform tasks as self-service through portals (aka consoles), Application Programming Interfaces (APIs), automation languages, or command-line interfaces (CLI)." #GregorHohpe #PlatformStrategy

"The three modes of integrating with existing systems: fix it, wrap it, or work around it." #GregorHohpe #PlatformStrategy

"The worst assumption a platform can make is that the problem is well-defined, developers select the perfect services to solve that specific problem, and they live happify ever after." #GregorHohpe #PlatformStrategy

"Tasty fruit salad over large fruit basket." #GregorHohpe #PlatformStrategy

"These teams are often led by the misconception that building the platform in one shot is more efficient than growing it through discovery. Although such an approach may look promising on paper (or slide shown to project sponsors), it violates a key principle of platforms: you cannot anticipate every user need." #GregorHohpe #PlatformStrategy

"Focusing on breadth alone can dilute a platform team and compromise other characteristics like quality or cohesion." #GregorHohpe #PlatformStrategy

"Building a platform without actively growing its user base can lead to a platform that's perfect for the platform team but not its users." #GregorHohpe #PlatformStrategy

"Treating translation from a higher-level abstraction as a one-way process creates dangerous illusions." #GregorHohpe #PlatformStrategy

"...we should look for abstractions that eliminate things that don't matter (the noise) to allow us to be precise about the things that do matter." #GregorHohpe #PlatformStrategy

"An abstraction provides a higher-level vocabulary that shields the user from the underlying complexity." #GregorHohpe #PlatformStrategy

"...when you define in-house abstractions over existing products, you'll need to teach every user from scratch." #GregorHohpe #PlatformStrategy

"Be careful to second-guess cloud providers who invested billions of dollars over a decade, based on abundant customer feedback." #GregorHohpe #PlatformStrategy

"Internal cost accounting favors long recovery periods, which means that systems should remain running as long as possible to recover the original investment (this habit explains why IT landscapes resemble computer history museums)." #GregorHohpe #PlatformStrategy

"When someone tells you that they built a GitLab/Spinnaker or Bitbucket/Bamboo platform, that's a fruit basket. All the customer gets are fruits, and increasingly those fruits can also be had directly from the vendor." #GregorHohpe #PlatformStrategy

The 7 Cs of platforms: Cohesion, Closure, Completeness, Consistency, Commensurate Value, Connectedness, Captivity #GregorHohpe #PlatformStrategy

"If your organization allows application teams to veto changes, your platform may not succeed." #GregorHohpe #PlatformStrategy

Platform collaboration models: Closed, Feature Request, Marketplace, Extension API, Co-Develop #GregorHohpe #PlatformStrategy

"In-house platforms may promise developers a freeway-like experience but end up delivering a mud path with giant guard rails, funded by governance and security teams. This isn't called opinionated; it's called bait-and- switch." #GregorHohpe, #PlatformStrategy

"When a company decides to write a proprietary platform, it competes against industry alternatives. Unfortunately, in 90% of the cases the internal tooling teams are underfunded as a cost center and release buggy trash." #GregorHohpe, #PlatformStrategy

"Opinionated frameworks tend to have gentle slopes at the edge of their opinion... meaning that the developer experience is still good even if you're looking to do something slightly outside the framework's sweet spot. ... Restrictive platforms often use the term "happy path" or "golden path", but in reality that's the only path they allow you to take, whether you're happy or not." #GregorHohpe, #PlatformStrategy

"Opinionated frameworks give you a high return on following their opinion. For agreeing, you are rewarded with a simpler and seamless developer experience that makes you more productive and keeps you from making mistakes. In contrast, restrictive frameworks or platforms limit choice without given anything in return." #GregorHohpe, #PlatformStrategy

"Should architects code? Perhaps. Should they debug? Absolutely!"

Nice new blog post from Gregor Hohpe. "Architects must visit the engine room. Not to deliver code but to re-emerge with new insights." https://architectelevator.com/transformation/debugging-architect/

#ArchitectElevator #SoftwareArchitecture #SoftwareArchitect #GregorHohpe #Debugging #EngineRoom

"Should architects code? Perhaps. Should they debug? Absolutely!"

Nice new blog post from Gregor Hohpe. "Architects must visit the engine room. Not to deliver code but to re-emerge with new insights." https://architectelevator.com/transformation/debugging-architect/

#ArchitectElevator #SoftwareArchitecture #SoftwareArchitect #GregorHohpe #Debugging #EngineRoom

"Should architects code? Perhaps. Should they debug? Absolutely!"

Nice new blog post from Gregor Hohpe. "Architects must visit the engine room. Not to deliver code but to re-emerge with new insights." https://architectelevator.com/transformation/debugging-architect/

#ArchitectElevator #SoftwareArchitecture #SoftwareArchitect #GregorHohpe #Debugging #EngineRoom