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 · #3147

Y

Yorick Peterse

Personal blog · yorickpeterse.com/articles · on HN as YorickPeterseprogrammingsystems

Yorick Peterse's personal blog at yorickpeterse.com covers programming and systems. Since 2011, 24 different Hacker News readers have linked it 48 times, most often “What it was like working for Gitlab”. It is still writing: the last post was on 2026-09-21, and you can follow it by feed.

Visit the blog
48mentions?
24HN people?
2011–2026first – last linked?
Links on Hacker News per year · peak 16 in 2025

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

Why HN links it

HN readers link Yorick Peterse's posts on storing passwords with bcrypt, GitLab's Postgres schema design, Ruby performance, and returning a Framework laptop. Comments cite his articles as sources or reading.

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 author on HN?

YorickPeterse · 2,780 karma · member since 2011

Author of the Inko programming language, formerly a staff developer at GitLab. Website: https://yorickpeterse.com

From their public HN profile, which links to this site.

Most-linked posts?

  1. What it was like working for Gitlab
    5 people · 5 mentions · first linked 2024-02-08
  2. The mess that is handling structure arguments and returns in LLVM
    3 people · 3 mentions · first linked 2025-01-16
  3. Three HTTP versions later, forms are still a mess
    3 people · 3 mentions · first linked 2025-07-25
  4. Friendship ended with the garbage collector
    3 people · 3 mentions · first linked 2021-08-25
  5. A decade of developing a programming language (2023)
    2 people · 2 mentions · first linked 2023-11-14
  6. Sandboxing with Minimal Effort
    2 people · 2 mentions · first linked 2026-09-23
  7. Oga: a new XML/HTML parser for Ruby (2014)
    2 people · 2 mentions · first linked 2014-09-18
  8. Asynchronous IO: the next billion-dollar mistake?
    2 people · 2 mentions · first linked 2024-09-06
  9. Deciding When to Collect Garbage
    2 people · 2 mentions · first linked 2019-12-02
  10. Funding open-source software without compromising it
    2 people · 2 mentions · first linked 2026-07-08

What Hacker News says?

  1. Not according to [1] where the author said > This effectively results in two code paths in many parts of your platform: one for the SaaS version, and one for the self-hosted version. Even if the code is physically the same (i.e. you provide some sort of easy to use wrapper for self-hosted installations), you still need to think about the differences. 1. https://yorickpeterse.com/articles/what-it-was-like-working-...

    Comment linking /articles/what-it-was-like-working-for-gitlab/

    on “My notes on Gitlab's Postgres schema design (2022)”
  2. Submitted What it was like working for Gitlab as a story · 432 points

    HN discussion
  3. +1 for bcrypt and related solutions. http://yorickpeterse.com/articles/use-bcrypt-fool/ http://codahale.com/how-to-safely-store-a-password/

    Comment linking /articles/use-bcrypt-fool/

    on “Lifetimes of cryptographic hash functions”
  4. Submitted A brief look at FreeBSD as a story · 164 points

    HN discussion
  5. Inko used to have a tracing GC (see https://yorickpeterse.com/articles/friendship-ended-with-the... for more details), but this was removed due to the various problems the presence of a tracing GC introduces.

    Comment linking /articles/friendship-ended-with-the-garbage-collector/

    on “The inevitability of the borrow checker”
  6. Submitted Asynchronous IO: the next billion-dollar mistake? as a story · 157 points

    HN discussion
  7. I agree ruby is slow and it lost the race with javascript. And the lack of a corporate sponsor has a lot to do with this. At GitLab the company we think that having a company behind an open source project is a plus (although the OP was talking about a user such as Twitter instead of Ruby Inc.). We hope to do our part in helping ruby become faster, our new hire Yorick will spend 20% of his time on Rubinius http://yor…

    Comment linking /articles/hello-gitlab/

    on “Why I wouldn’t use Rails for a new company”
  8. Submitted The inevitability of the borrow checker as a story · 140 points

    HN discussion
  9. blhack · 2013-03-26Recommends
    Because you mentioned bcrypt, it might be a good time for everybody to read this: http://yorickpeterse.com/articles/use-bcrypt-fool/ (sidenote: GCHQ cannot reverse bcrypt. Jgrahamc was making a joke.)

    Comment linking /articles/use-bcrypt-fool/

    on “GCHQ – Not So Secure?”
  10. Submitted Friendship ended with the garbage collector as a story · 118 points

    HN discussion
  11. 10 years in, and I still deal with it on a regular basis (I wrote [1] a little bit about this the other day). Hopefully it goes away one day, but I suspect it won't. [1]: https://yorickpeterse.com/articles/10-years-of-software-deve...

    Comment linking /articles/10-years-of-software-development/

    on “Things I wish I had known when I started programming, Part 4 (2019)”
  12. Submitted Building a better and scalable system for data migrations as a story · 68 points

    HN discussion
  13. You're telling me you didn't return your Framework 13 because *checks notes* its power LED was too bright[1]? [1] https://yorickpeterse.com/articles/im-returning-my-framework...

    Comment linking /articles/im-returning-my-framework-16/

    on “I'm a laptop weirdo and that's why I like my new Framework 13”
  14. Submitted Oga: a new XML/HTML parser for Ruby (2014) as a story · 36 points

    HN discussion
  15. For those looking for a more extensive article about bootc, I recently wrote about using it in https://yorickpeterse.com/articles/self-hosting-my-websites-... , including a comparison to some other existing tools.

    Comment linking /articles/self-hosting-my-websites-using-bootable-containers/

    on “Bootc and OSTree: Modernizing Linux System Deployment”
  16. Submitted What it was like working for Gitlab as a story · 18 points

    HN discussion
  17. I literally mention the reason in the article in the "Configuration" section ( https://yorickpeterse.com/articles/im-returning-my-framework... )...

    Comment linking /articles/im-returning-my-framework-16/

    on “I'm returning my Framework 16”
  18. Submitted Installing FreeBSD 15 on my desktop as a story · 7 points

    HN discussion
  19. Submitted Asynchronous IO: the next billion-dollar mistake? as a story · 7 points

    HN discussion
  20. Submitted What it was like working for Gitlab as a story · 7 points

    HN discussion
  21. Submitted Oga (XML/HTML Parser for Ruby) 1.0 Released as a story · 7 points

    HN discussion
  22. Submitted Three HTTP versions later, forms are still a mess as a story · 5 points

    HN discussion
  23. Submitted Three HTTP versions later, forms are still a mess as a story · 4 points

    HN discussion
  24. Submitted How to write a code formatter as a story · 4 points

    HN discussion
  25. Submitted What it was like working for Gitlab as a story · 4 points

    HN discussion
  26. Submitted Switching to Fedora Silverblue as a story · 4 points

    HN discussion
  27. Submitted Inko: A Brief Introduction as a story · 4 points

    HN discussion
  28. Submitted Three HTTP versions later, forms are still a mess as a story · 3 points

    HN discussion
  29. Submitted The Inevitability of the Borrow Checker as a story · 3 points

    HN discussion
  30. Submitted Sandboxing with Minimal Effort as a story · 2 points

    HN discussion

Search all of HN for yorickpeterse.com

Linked by the same people?