Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #8482

P

Peter Williams

Personal blog · barelyenough.org/blogprogrammingcareer

Peter Williams's personal blog at barelyenough.org covers programming and career. Since 2008, 9 different Hacker News readers have linked it 11 times, most often “Versioning REST Web Services”. The last post was in 2022, but the archive is still widely read.

Visit the blog
11mentions?
9HN people?
2008–2018first – last linked?
Links on Hacker News per year · peak 3 in 2010

Too few sampled comments (4) to say how often HN recommends it.?

Why HN links it

HN links Peter Williams' blog for its REST API design posts, on push versus pull for hooks and on versioning REST services. Commenters cite these posts when discussing API versioning.

Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Most-linked posts?

  1. Versioning REST Web Services
    3 people · 3 mentions · first linked 2008-10-13
  2. How to Componentize a Monolith
    2 people · 2 mentions · first linked 2017-03-23

What Hacker News says?

  1. FWIW http://barelyenough.org/blog/2009/05/push-or-pull/ case closed

    Comment linking /blog/2009/05/push-or-pull/

    on “REST Hooks - Stop the polling madness”
  2. Submitted Versioning REST Web Services as a story · 6 points

    HN discussion
  3. Can I have a few more upvotes please? This is the only way to do it. There's currently two root posts above this one advocating the incorrect way, with versions in the URL. By doing it this way, you don't break links when you want to bump versions. Or if you have a single resource with an incompatibility, you can just upgrade the version of it, and leave all the others the same, without having to change anything, or…

    Comment linking /blog/2008/05/resthttp-service-versioning-reponse-to-jean-jacques-dubray/

    on “Ask HN: Version numbers in a REST API”
  4. Submitted How to Componentize a Monolith as a story · 2 points

    HN discussion
  5. berryg · 2010-07-17Recommends
    I like the approach that Peter Williams has suggested. That is to use a vendor MIME media type in the Accept header to specify a required API version. At least your URL stays the same. As it should be, because your resource is still the same. http://barelyenough.org/blog/2008/05/versioning-rest-web-ser...

    Comment linking /blog/2008/05/versioning-rest-web-services/

    on “Ask HN: Version numbers in a REST API”
  6. Submitted How i judge software engineers as a story · 1 points

    HN discussion
  7. Uh, difficult topic. I did the same research some months ago and didn't find "the" solution or answer to this question. Linkdump from my bookmarks to this topic: Discussion: http://blog.sonoasystems.com/detail/one_size_doesnt_fit_all_... http://stackoverflow.com/questions/389169/best-practices-for... http://stackoverflow.com/questions/2024600/rest-api-versioni... http://stackoverflow.com/questions/972226/how-to-vers…

    Comment linking /blog/2008/05/versioning-rest-web-services/

    on “Ask HN: Version numbers in a REST API”
  8. Submitted How to componentize a monolith as a story · 1 points

    HN discussion
  9. Submitted Developing software as if quality matters as a story · 1 points

    HN discussion

Search all of HN for barelyenough.org