Top all-time · #10541
Amber on Rails
Personal blog · amberonrails.comprogrammingweb
Amber on Rails is a personal blog at amberonrails.com about programming and web. Since 2013, 7 different Hacker News readers have linked it 8 times, most often “Move Fast, Don't Break Your API”. No feed was found, so read it on the site itself.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
HN readers link Amber Feng's posts on Stripe's API design and versioning, including 'Building Stripe's API' and 'Move fast, don't break your API'. They are cited as reading for designing APIs.
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.
Amber on Rails
Most-linked posts?
- Move Fast, Don't Break Your API4 people · 4 mentions · first linked 2014-10-10
What Hacker News says?
Always excited to hear Stripe talking about versioning :D For anyone else who's interested, they've written/talked about this a few times over the years, to fill out the picture: - http://amberonrails.com/move-fast-dont-break-your-api/ - https://www.heavybit.com/library/video/move-fast-dont-break-... - https://speakerdeck.com/apistrat/api-versioning-at-stripe - https://brandur.org/api-upgrades - https://news.ycombin…
Comment linking /move-fast-dont-break-your-api/
on “APIs as infrastructure: future-proofing Stripe with versioning”Submitted Building Stripe's API as a story · 138 points
HN discussionI really liked Building Stripe’s API and it’s sequel, Move fast, don’t break your API: http://amberonrails.com/building-stripes-api/ http://amberonrails.com/move-fast-dont-break-your-api/
Comment linking /move-fast-dont-break-your-api/
on “Ask HN: What are good reads for designing APIs?”Submitted Move Fast, Don't Break Your API as a story · 119 points
HN discussionStripe pin your API version once you have sent you first request, you can see it in the dashboard with an option to update to the latest api revision. https://stripe.com/docs/upgrades As to how they achieve it Amber has a good blog post over at http://amberonrails.com/move-fast-dont-break-your-api/ but it means it really is integrate once, and never touch it again :)
Comment linking /move-fast-dont-break-your-api/
on “APIs, robustness, and idempotency”Submitted Move fast, don't break your API (2014) as a story · 1 points
HN discussionHey swyx, hope you're doing well, too (shoot me an email if you see this: ryan.glover@cheatcode.co). Would love it if someone could get Patrick's attention on this. They need to move back toward the Amber Feng era of API design [1]. [1] https://amberonrails.com/building-stripes-api
Comment linking /building-stripes-api
on “Stripe V2”