Session
Why You (too) Need an (API) Style Guide
You’ve probably been in this situation: You thought long and hard about this new API of yours, but now it comes to naming — shock, horror, what will you do? Or, worse, you’re a reviewer and you’re not sure if the proposed API quite aligns with the status quo. That’s where API Style Guides come in and can eliminate (some of the) bikeshedding.
In this talk, we will explore:
- What is an API Style Guide, and why could you possibly need one?
- What are the characteristics of a good style guide, and what constitutes a bad one?
- Some exemplary style guides for your to be inspired by (e.g. AIP, AEP)
- Where else can style guides help (it’s 2026, do I need to spell it out: AI)
Robert will draw on his decade+ at Google where he was one of 3% of the company allowed to perform API reviews. His team maintained multiple style guides in order to scale reviews.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top