Top all-time · #7851
Blake Smith
Personal blog · blakesmith.me · on HN as blakesmithprogramminghardware
Blake Smith writes create. code. learn., a personal blog at blakesmith.me about programming and hardware. Since 2012, 9 different Hacker News readers have linked it 12 times, most often “Excellent clojure concurrency tutorial”. It is still writing: the last post was on 2026-10-05, and you can follow it by feed.
Too few sampled comments (3) to say how often HN recommends it.?
Why HN links it
HN readers link Blake Smith's writing on code review, including a post arguing that team mental alignment is the main purpose of review. Other comments discuss a kit for understanding pull requests faster.
Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- /2015/02/09/code-review-essentials-for-software-teams.html2 people · 3 mentions · first linked 2026-07-23
- Excellent clojure concurrency tutorial2 people · 2 mentions · first linked 2012-06-01
What Hacker News says?
blake smith has a really good post on this - that mental alignment among the team is the primary purpose of code review - https://blakesmith.me/2015/02/09/code-review-essentials-for-...
Comment linking /2015/02/09/code-review-essentials-for-software-teams.html
on “Why Software Factories Fail”Submitted Making My Own USB Keyboard from Scratch as a story · 584 points
HN discussionEvery developer I've spoken to on a team >1 has complained about PR review burnout, no understanding of the codebase anymore and even a lost love for the craft. I think this is primarily happening because every PR reads like its written by a distinguished engineer. (Why say lot word when few word do trick??!!) Everyone reviews PRs differently but I've personally started relying more on visualisations to get an initi…
Comment linking /2015/02/09/code-review-essentials-for-software-teams.html
on “Skill and UI kit to understand PRs faster”Submitted Rust Patterns: Enums Instead of Booleans as a story · 29 points
HN discussionEvery developer I've spoken to on a team >1 has complained about PR review burnout, no understanding of the codebase anymore and even a lost love for the craft. I think this is primarily happening because every PR reads like its written by a distinguished engineer. (Why say lot word when few word do trick??!!) Everyone reviews PRs differently but I've personally started relying more on visualisations to get an initi…
Comment linking /2015/02/09/code-review-essentials-for-software-teams.html
on “Skill and visualisation kit to help developers understand PRs better”Submitted Learning Homebrew Game Boy Development in Assembly as a story · 2 points
HN discussionSubmitted I Use a Crappy Computer (2010) as a story · 2 points
HN discussionSubmitted Seeing Software Complexity as a story · 2 points
HN discussionSubmitted Test stubbing as an anti-pattern as a story · 2 points
HN discussionSubmitted Moped Electric Conversion, Puch Maxi “Electropuch” as a story · 1 points
HN discussionSubmitted Excellent clojure concurrency tutorial as a story · 1 points
HN discussionSubmitted Understanding clojure concurrency, part 2 as a story · 1 points
HN discussion
