[voicedYoda]

The article brings up interesting points, but reads like I'm blasting through a red bull ad. (Zing Zang Zoom!) API development is super important, and KIS principles should apply, but i felt this post was more marketing and less functional advice.

[Mandatum]

Literally all API design articles are marketing. There’s almost zero, aside from foundations that came from academia, early industrial or military specs, or very shallow blog posts that are almost useless when you actually build something beyond a prototype.

[rco8786]

This post is literal content marketing. Not in a bad way, but that's what it is.

[nerdyadventurer]

Any good resources on API design?

[eyelidlessness]

Surprisingly enough (to some, including me), Microsoft's REST API design guidelines are both thorough and there's very little I'd object to.

[metachris]

https://docs.microsoft.com/en-us/azure/architecture/best-pra...

[beebmam]

There is incredibly good information on Microsoft's site for developers

[BarryMilo]

I'm surprised anyone finds this surprising. Like them or not, Microsoft makes tight documentation for developers.

[eyelidlessness]

I found it surprising because I interacted with their REST APIs first. They are very good about docs. The ones I use most frequently (TS) are no exception, though they have some gaps. But the actual REST APIs I integrated very clearly predate a lot of their guidelines or struggle to follow them.

[blowski]

That's true of everything I've worked on. Little details keep sullying my perfect design for reasons end users aren't aware of.

[Xelbair]

maybe they are able to create good docs, and good guidelines, because they burned themselves in the past creating godawful ones?

[systemvoltage]

There was just an article on HN a couple of days ago: https://news.ycombinator.com/item?id=30647784

Comments were very insightful as always. I kind of agree with OP, this article is very thin on content and mostly peripheral take on good API design. It is unhelpful.