Loading post…
OktaMichael PalermoAnnouncement
The Builder Revolution: Why We're Shifting to Builder Advocacy
Summary
The team formerly known as Developer Advocacy, within Developer Success, has been renamed Builder Advocacy within Builder Experience (BX). The change responds to an expanded definition of who builds with technology: alongside traditional developers, AI builders and no-code or low-code automators are creating production-level experiences and mission-critical infrastructure. The organization says its advocacy will serve developers, prompt engineers, LLM integrators, AI-agent creators, ML practitioners, and automation-focused builders, while continuing support for traditional coders, engineers, and architects. The announcement cites GitHub’s 180 million developers, 36 million new developers in 2025, and Stack Overflow’s finding that 84% use or plan to use AI tools. The rename is effective immediately and begins broader investments in resources, content, and community programs for this wider builder community.
Context
The organization says the definition of who builds with technology has expanded beyond traditional developers as AI tools, low-code platforms, and workflow automation enable more people to create production-level experiences and mission-critical infrastructure.
Approach / What changed
Developer Advocacy is becoming Builder Advocacy, while Developer Success is becoming Builder Experience (BX). The organization will serve developers, AI builders, and automators through expanded resources, content, tooling, documentation, and community programs.
Takeaways
Builder Advocacy will serve three groups: traditional developers, AI builders such as prompt engineers and LLM integrators, and no-code or low-code automators.
The announcement cites GitHub’s 180 million developers and Stack Overflow’s finding that 84% of respondents use or plan to use AI tools in development work.
The rename is effective immediately and is presented as the start of broader Builder Experience investments rather than a cosmetic change.
Source and freshness
- Source
- developer.okta.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.