Top all-time · #6520
The Coder Cafe
Personal blog · thecoder.cafeprogrammingsystems
The Coder Cafe is a personal blog at thecoder.cafe about programming and systems. Since 2024, 11 different Hacker News readers have linked it 28 times, most often “The Story Behind “100 Go Mistakes and How to Avoid Them””. It is still writing: the last post was on 2026-10-28, and you can follow it by feed.
Too few sampled comments (1) to say how often HN recommends it.?
Why HN links it
HN readers link The Coder Cafe for its programming writing, including a post on Go mistakes and a write-up on working with Manning as a first-time book author.
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.
Most-linked posts?
- The Story Behind “100 Go Mistakes and How to Avoid Them”4 people · 4 mentions · first linked 2025-04-08
- Working on complex systems: What I learned working at Google3 people · 3 mentions · first linked 2025-05-07
- Latency and User Experience2 people · 2 mentions · first linked 2025-01-07
- Probabilistic Increment2 people · 2 mentions · first linked 2025-01-29
What Hacker News says?
Manning doesn't pay that much to first time authors, and it looks like it's the first book for the author, Garrison Hinson-Hasty. My guess is it's about $2k upfront and the author owes it back if they don't deliver. Teiva Harsanyi did a good writeup recently about working with Manning as a first-time author. He got $2k upfront and $2k after delivering the first 1/3rd.[0] [0] https://www.thecoder.cafe/p/100-go-mistak…
Comment linking /p/100-go-mistakes
on “Systems Programming with Zig”Submitted The Story Behind “100 Go Mistakes and How to Avoid Them” as a story · 381 points
HN discussionSubmitted Working on complex systems: What I learned working at Google as a story · 302 points
HN discussionSubmitted Unit tests as documentation as a story · 174 points
HN discussionSubmitted Functors, Applicatives, and Monads as a story · 84 points
HN discussionSubmitted Rules I Learned About Technical Writing as a story · 9 points
HN discussionSubmitted Don't Be Ashamed to Say "I Don't Know" as a story · 6 points
HN discussionSubmitted Eventually Green Tests as a story · 5 points
HN discussionSubmitted Keeping a Mistake Journal as a story · 4 points
HN discussionSubmitted Property-Based Testing as a story · 4 points
HN discussionSubmitted Working on Complex Systems: What I Learned Working at Google as a story · 4 points
HN discussionSubmitted So, I Wrote a Book: The Story Behind 100 Go Mistakes as a story · 4 points
HN discussionSubmitted Why I Switched to Vim Keybindings as a story · 3 points
HN discussionSubmitted Bloom Filters as a story · 3 points
HN discussionSubmitted Linux Soft vs. Hard Lockup as a story · 3 points
HN discussionSubmitted Probabilistic Increment as a story · 3 points
HN discussionSubmitted Exploring Database Isolation Levels as a story · 3 points
HN discussionSubmitted Concurrency Is Not Parallelism as a story · 3 points
HN discussionSubmitted The Coder Cafe as a story · 2 points
HN discussionSubmitted Working on Complex Systems as a story · 2 points
HN discussionSubmitted So, I Wrote a Book as a story · 2 points
HN discussionSubmitted Premature Abstractions as a story · 2 points
HN discussionSubmitted Probabilistic Increment: A Randomized Algorithm to Mitigate Hot Rows as a story · 1 points
HN discussionSubmitted Adaptive LIFO as a story · 1 points
HN discussionSubmitted Latency and User Experience as a story · 1 points
HN discussionSubmitted Latency and User Experience as a story · 1 points
HN discussionSubmitted Resilient, Fault-Tolerant, Robust, or Reliable? as a story · 1 points
HN discussionSubmitted The PACELC Theorem as a story · 1 points
HN discussion
