Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #3629

T

Technical Journal

Personal blog · davidad.github.io/blogprogrammingsystems

Technical Journal is a personal blog at davidad.github.io about programming and systems. Since 2014, 21 different Hacker News readers have linked it 25 times, most often “Overkilling the 8-queens Problem”. The last post was in 2014, but the archive is still widely read.

Visit the blog
25mentions?
21HN people?
2014–2021first – last linked?
Links on Hacker News per year · peak 12 in 2014

Too few sampled comments (5) to say how often HN recommends it.?

Why HN links it

HN commenters cite this journal's posts on 8-queens overkilling, compiler optimisation, relocatable vs position-independent code and OS design as background. None of the comments judge the writing.

Summarised by Claude from a sample of 5 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

The Internet protocol suite is wonderful, but it was designed before the advent of modern cryptography and without the benefit of hindsight. On the …

Most-linked posts?

  1. Overkilling the 8-queens Problem
    5 people · 6 mentions · first linked 2014-02-25
  2. Systems Past: software innovations we actually use (2014)
    5 people · 5 mentions · first linked 2014-03-14
  3. An OSI model for the 21st century (2014)
    4 people · 4 mentions · first linked 2014-04-25
  4. Relocatable vs. Position-Independent Code: Virtual Memory Isn't Just for Swap
    2 people · 2 mentions · first linked 2014-02-26
  5. Concurrency Primitives in Intel 64 Assembly
    2 people · 2 mentions · first linked 2014-03-24

What Hacker News says?

  1. Following 9 months of computation and 4 petabyte of disk IO on a Dell PowerEdge R280 server I wonder if the time could be improved by optimising the programs some more, since at this scale constants matter a lot . The amount of memory needed might not be reducible but optimising a tight loop and reordering it to take advantage of cache effects could yield nontrivial speedups. Taking advantage of the very wide new in…

    Comment linking /blog/2014/02/25/overkilling-the-8-queens-problem/

    on “Number of legal 18x18 Go positions computed. One more to go”
  2. Submitted Overkilling the 8-queens Problem as a story · 201 points

    HN discussion
  3. Would it be this one? http://davidad.github.io/blog/2014/02/25/overkilling-the-8-q...

    Comment linking /blog/2014/02/25/overkilling-the-8-queens-problem/

    on “Compiler Optimizations are Awesome”
  4. Submitted Systems Past: software innovations we actually use (2014) as a story · 148 points

    HN discussion
  5. I included a footnote to address this criticism. http://davidad.github.io/blog/2014/03/12/the-operating-syste...

    Comment linking /blog/2014/03/12/the-operating-system-is-out-of-date/

    on “Systems Past: The software innovations we actually use”
  6. Submitted Systems Past: The software innovations we actually use as a story · 135 points

    HN discussion
  7. This indirection already happens in present systems. Check out my previous blog post about it: http://davidad.github.io/blog/2014/02/19/relocatable-vs-posi... Modern hardware is optimized to do this kind of indirection reasonably fast. What I propose can exploit the same hardware acceleration.

    Comment linking /blog/2014/02/19/relocatable-vs-position-independent-code-or/

    on “Systems Past: The software innovations we actually use”
  8. Submitted Python to Scheme to Assembly (2014) as a story · 127 points

    HN discussion
  9. That actually matters far less than most people think, because humans writing Asm do not (and should not) generate code like a compiler does. The article has a great example of this in the int_to_str code. While it's far from optimal code (e.g. the "mov rbx, 10" should really be outside of the loop, the "add rdx, 0x0" is useless, etc.), it's using the stack in a way that a compiler would probably never do, and somet…

    Comment linking /blog/2014/02/25/overkilling-the-8-queens-problem/

    on “Say Hello to X64 Assembly Part 3”
  10. Submitted An OSI model for the 21st century (2014) as a story · 90 points

    HN discussion
  11. Submitted An OSI layer model for the 21st century (2014) as a story · 74 points

    HN discussion
  12. Submitted Concurrency Primitives in Intel 64 Assembly as a story · 14 points

    HN discussion
  13. Submitted Python to Scheme to Assembly as a story · 7 points

    HN discussion
  14. Submitted Concurrency Primitives in Intel 64 Assembly as a story · 3 points

    HN discussion
  15. Submitted An OSI layer model for the 21st century as a story · 3 points

    HN discussion
  16. Submitted Kernel From Scratch as a story · 3 points

    HN discussion
  17. Submitted Overkilling the 8-queens Problem (2014) as a story · 2 points

    HN discussion
  18. Submitted Overkilling the 8-queens problem (2014) as a story · 2 points

    HN discussion
  19. Submitted All the digital revolutions was already invented between 1955 – 1977 as a story · 2 points

    HN discussion
  20. Submitted Systems Past: the only 8 software innovations we actually use as a story · 2 points

    HN discussion
  21. Submitted An OSI layer model for the 21st century as a story · 1 points

    HN discussion
  22. Submitted Let’s do some old-school hacking on our new-school hardware (2014) as a story · 1 points

    HN discussion
  23. Submitted VNC as a graphical interface medium as a story · 1 points

    HN discussion
  24. Submitted An OSI layer model for the 21st century as a story · 1 points

    HN discussion
  25. Submitted Relocatable vs. Position-Independent Code: Virtual Memory Isn't Just for Swap as a story · 1 points

    HN discussion

Search all of HN for davidad.github.io

Linked by the same people?