Gregory Koberger

Gregory Koberger

Greg hails from the lovely town of Schaghticoke in upstate New York. After attending RIT he made the move to San Francisco where he worked for Mozilla and freelanced for a bunch of startups. He founded ReadMe after building docs sites for most of them. You can find him drinking coffee or obsessively competing for Swarm mayorships.

Exploring APIs, not Documentation

Hi Everybody! We’ve been working crazy hard to smooth out the API Explorer feature in ReadMe.io. We believe the optimal way to learn about an API is to interact with it rather than read about…

Documenting Microservices in ReadMe

Many companies are breaking larger codebases into microservices, so different teams can work on parts of the site at different paces. They're like APIs, except for an internal audience. Like any API, they need to…

Blue Heart

Favorite Owlbert

social network X

Challenge Coins and Company Credits

Startups are a team sport. Some people are recognized with salaries or equity, however much of the help we've gotten along the way has been less formal. Our team may be small, but the "ReadMe…

A Visual Guide to What’s New in Swagger 3.0

Over the past few years, Swagger 2 has become the de facto standard for defining or documenting your API. Since then, it's been moved to the Linux foundation and renamed to OpenAPI Spec. Version 3 has…

5 Types of API Documentation for a Successful API

Close your eyes and picture API documentation. You probably imagined a reference guide — that three column page that lists all the endpoints, and then enumerates all the params and options for each one. There…

7 Best Practices for Writing and Updating API Docs

Developers respect clean, simple code. We have to be experts at finding ways to do more with less. And while that skill set is highly valued in development, it doesn't always transfer over to writing…