A developer portal is the consolidation of various features such as the service catalog, orchestration, ID platform, and internal developer platform into a unified platform. It serves as a single place to bring together these different functionalities, aiming to optimize the developer experience across various tasks that developers need to perform. The developer portal is seen as a way to merge different aspects currently existing separately, ultimately providing a seamless and efficient experience for engineers.
Click here to view the episode transcript.
This week’s episode is the recording of a live conversation between Abi and Chris Westerhold (Thoughtworks Head of Developer Experience). This conversation is useful for anyone early in their journey with developer portals or platforms: Abi and Chris discuss common approaches to solving these problems, pitfalls to avoid, building vs. buying, and more.
Mentions and Links
Time Stamps:
- (3:09) Why there’s an increased interest in developer portals
- (5:33) Chris’ background with dev portals
- (6:37) Homegrown solutions for developer portals
- (9:22) How developer portal initiatives begin
- (11:24) Internal developer portal vs service catalogs and IDPs
- (16:18) Mistakes companies make with developer portals
- (21:05) Approaches to solving this problem
- (24:28) How can developer portals drive value
- (32:07) Common traps to avoid