Top all-time · #5456
Tagebuch eines Interplanetaren Botschafters
Personal blog · nhaehnle.blogspot.comprogrammingsystems
Tagebuch eines Interplanetaren Botschafters is a personal blog at nhaehnle.blogspot.com about programming and systems. Since 2020, 15 different Hacker News readers have linked it 24 times, most often “Thoughts on code reviews and the power of patch series”. It is still writing: the last post was on 2026-05-25, and you can follow it by feed.
Too few sampled comments (6) to say how often HN recommends it.?
Why HN links it
HN commenters cite this personal blog on patch-series code review and on building the HIP/ROCm environment, plus LLVM/MLIR and TableGen topics. Most mentions are as sources for the commenter's own points.
Summarised by Claude from a sample of 6 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Lerne, wie die Welt wirklich ist, aber vergiss niemals, wie sie sein sollte.
Most-linked posts?
- Thoughts on code reviews and the power of patch series3 people · 5 mentions · first linked 2021-04-24
- Building a HIP Environment from Scratch2 people · 2 mentions · first linked 2024-02-07
- Software testing, and why I'm unhappy about it2 people · 2 mentions · first linked 2023-01-15
- Diff modulo base, a CLI tool to assist with incremental code reviews2 people · 2 mentions · first linked 2023-01-22
What Hacker News says?
Hähnle is one of our best, that'll be solid. http://nhaehnle.blogspot.com/2024/02/building-hip-environmen... . Looks pretty similar to how I build it. Side point, there's a driver in your linux kernel already that'll probably work. The driver that ships with rocm is a newer version of the same and might be worth building via dkms. Very strange that the rocm github doesn't have build scripts but whatever, I've been t…
Comment linking /2024/02/building-hip-environment-from-scratch.html
on “AMD funded a drop-in CUDA implementation built on ROCm: It's now open-source”Submitted Can memcpy be implemented in LLVM IR? as a story · 4 points
HN discussionMy understanding is that they're not necessarily asking for the commits to be squashed, they're asking for them to be submitted together as a patch series. Patch series are an important part of a healthy review workflow because they allow both a micro and a macro view of changes. I have written about this before: http://nhaehnle.blogspot.com/2020/06/they-want-to-be-small-t...
Comment linking /2020/06/they-want-to-be-small-they-want-to-be.html
on ““Please don't waste maintainers' time on your KPI grabbing patches””Submitted Can memcpy be implemented in LLVM IR? as a story · 3 points
HN discussion(Early disclaimer: I am an author of the paper and of MLIR, but this is a personal opinion) I am somehow surprised by the reaction but at the same time I expected as much. We chose to make MLIR open-source early in the design and development, may be half a year after the first line was written, because we value open source and believe that a community can help build significantly better things that serve a broader a…
Comment linking /2016/10/compiling-shaders-dynamically-uniform.html
on “MLIR: A Compiler Infrastructure for the End of Moore's Law”Submitted Can memcpy be implemented in LLVM IR? as a story · 3 points
HN discussion> Every PR/commit merged to master should be a clean logical unit. The issue is one of review scaling. I wrote a blog post about this a while ago[0], but the gist of it is that those clean logical units are often too small for meaningful high-level reviews of more complex work. With complex features or refactorings, you're often in a situation where those clean logical units allow reviewers to do a good low-level re…
Comment linking /2020/06/they-want-to-be-small-they-want-to-be.html
on “A Better Git Flow”Submitted An Update on Dialects in LLVM as a story · 2 points
HN discussionOne related aspect that the article doesn't go into too much is that there is a tension in the size of the unit of code review: there are reasons for reviewing big chunks at once, but also reasons for reviewing individual changes that are as small as possible. I've gone into more detail on this in the past.[0] Stacked diffs make that possible because you can review either individual commits or an entire stack at onc…
Comment linking /2020/06/they-want-to-be-small-they-want-to-be.html
on “Stacked Diffs versus Pull Requests (2018)”Submitted Software testing, and why I'm unhappy about it as a story · 2 points
HN discussionFWIW, its use has grown over time, with new applications most significantly including MLIR (Multi-Level IR compiler framework, which allows you to define your own intermediate representations as well as compiler passes operating on them), https://mlir.llvm.org/docs/DefiningDialects/Operations/ The docs have been improving, https://llvm.org/docs/TableGen/ I also like these resources: Lessons in TableGen FOSDEM 2019;…
Comment linking /2018/03/tablegen-5-dags.html
on “Tools for Learning LLVM TableGen”Submitted Can memcpy be implemented in LLVM IR? as a story · 2 points
HN discussionSubmitted Building a HIP Environment from Scratch as a story · 1 points
HN discussionSubmitted Diff modulo base, a CLI tool to assist with incremental code reviews as a story · 1 points
HN discussionSubmitted Diff modulo base, a CLI tool to assist with incremental code reviews as a story · 1 points
HN discussionSubmitted Thoughts on code reviews and the power of patch series as a story · 1 points
HN discussionSubmitted Software testing, and why I'm unhappy about it as a story · 1 points
HN discussionSubmitted Thoughts on code reviews and the power of patch series (2020) as a story · 1 points
HN discussionSubmitted They want to be Thoughts on code reviews and the power of patch series as a story · 1 points
HN discussionSubmitted Thoughts on code reviews and the power of patch series as a story · 1 points
HN discussion
