Platform Tips #25: Time to Ditch the Confusing "IDP" Acronym
Why we should stop using "IDP" to talk about Internal Developer Platform and Internal Developer Portal. Let's shift from the confusing "IDP" to "Dev Portal" and "Dev Platform" for clarity?
Hey Folks 👋,
I'm Romaric, CEO of Qovery, and this is my 25th Platform Tips post.
Clarity is key! Yet, a persistent ambiguity exists that affects our community: the overused and confusing acronym "IDP." Traditionally, this term has been used interchangeably to refer to both Internal Developer Platforms and Internal Developer Portals. This dual usage creates unnecessary confusion within our community and in overlapping domains such as cybersecurity, where IDP stands for Identity Detection Prevention and Identity Providers.
I propose we adopt more specific and distinct terms: "Developer Portal" (Dev Portal) and "Developer Platform" (Dev Platform).
Recently, I attended a webinar in which "IDP" was used to denote an Internal Developer Portal. Within the same day, I came across several articles using "IDP" to refer to Internal Developer Platforms. This scenario is a perfect illustration of the confusion that prevails, and it's clear that continuing down this path does not serve our community well. It is time for a change.
Since 2022, I've extensively written on platform engineering. Redundantly spelling out Internal Developer X each time is cumbersome and detracts from technical precision and conciseness. To address this, I propose we adopt more specific and distinct terms: "Developer Portal" (Dev Portal) and "Developer Platform" (Dev Platform). These terms are succinct, clear, and distinct, eliminating any ambiguity associated with them.
Here are a few reasons why this change is important:
Clarity and Precision: "Dev Portal" and "Dev Platform" ensure clear communication in technical environments, which is crucial for precision in documentation, discussions, and marketing.
Community and Onboarding: New field entrants benefit from clear terminology for faster onboarding and smoother team communication.
Cross-Domain Confusion: Using unique terms in cybersecurity prevents overlap with other fields, reducing misunderstandings.
Enhanced Searchability and Learning: Distinct terms enhance online searchability, helping users quickly find relevant resources on Developer Portals or Platforms.
This proposal aims to improve communication in platform engineering by refining terminology. It's about making our discussions more accessible to newcomers and ensuring that our conversations are as effective and efficient as the solutions we advocate for.
I urge all platform engineering professionals and communities to adopt "Developer Portal" and "Developer Platform" in their lexicons. Let's embrace this change not only in our written materials but also in our spoken language. It’s a small but powerful way to foster a more inclusive and clear-cut environment for all.
Change may require adjustment, but the long-term benefits of clear communication in our fast-paced field are undeniable.
What are your thoughts on this proposal? I look forward to hearing your insights and hope for your support in making this necessary change.
—
Let's revolutionize Platform Engineering by putting developers first. Subscribe now to join me on this exciting journey!