For a very deep, thorough and painful treatment instead of feel-good books, read... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		_pmf_ on Aug 7, 2014 \| parent \| context \| favorite \| on: The Worst API Ever Made? For a very deep, thorough and painful treatment instead of feel-good books, read "Practical API Design" by Jaroslav Tulach. Yes, it's Java, but it exemplifies the fundamental tradeoff that the feel-good books ignore: the more powerful you make your API for users, the less potential for evolution and long-term maintenance your API retains.

monksy on Aug 7, 2014 [–]

That is on my queue of books to buy. [Which is below my queue of books to read].

So shouldn't there be a way to balance these requirements?

It seems like we've ignored the ability to batch jobs, do async tasks etc. It sucks... but an API is out of my control.

Consider applying for YC's Summer 2026 batch! Applications are open till May 4
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact