Top all-time · #19213
Nate Wiger
Personal blog · nateware.com · on HN as natewareprogramming
Nate Wiger's personal blog at nateware.com covers programming. Since 2011, 4 different Hacker News readers have linked it 4 times, most often “An Atomic Rant (2010)”. It is still writing: the last post was on 2026-04-23, and you can follow it by feed.
Too few sampled comments (1) to say how often HN recommends it.?
Why HN links it
Linked as a reference for wrapping transactions in locks to prevent concurrency exploits, pointing to Wiger's 'An atomic rant' post on atomic operations.
Summarised by Claude from a sample of 1 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
How many beers until the bugs are fixed?
Most-linked posts?
- An Atomic Rant (2010)2 people · 2 mentions · first linked 2013-01-11
What Hacker News says?
You could wrap the transaction in a lock based on the player ID which you could do with Redis or Memcached with near-zero impact on performance. A good reference: http://www.nateware.com/an-atomic-rant.html
Comment linking /an-atomic-rant.html
on “How our users exploited concurrency and how we fixed it”Submitted An Atomic Rant as a story · 2 points
HN discussionSubmitted Redis-objects 2.0: 17 years, 2k stars, and 16M downloads later as a story · 1 points
HN discussionSubmitted An Atomic Rant (2010) as a story · 1 points
HN discussion