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

J

Jussi Judin

Personal blog · barro.github.ioprogrammingsystems

Jussi Judin's personal blog at barro.github.io covers programming and systems. Since 2016, 9 different Hacker News readers have linked it 11 times, most often “What is wrong with “A successful Git branching model”?”. The last post was in 2018, but the archive is still widely read.

Visit the blog
11mentions?
9HN people?
2016–2026first – last linked?
Links on Hacker News per year · peak 3 in 2016

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

Why HN links it

HN commenters link this blog's posts on the Git Flow branching model, including its problems and alternative branching procedures, as related reading in discussions of Git Flow.

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.

Programming related topics. Maybe even some original content!

Most-linked posts?

  1. What is wrong with “A successful Git branching model”?
    6 people · 8 mentions · first linked 2016-02-08

What Hacker News says?

  1. Yep. What you're describing was used at GitHub [1], at least for a while. I've had a lot of success pitching it to small dev shops that have struggled with more complicated branching models, including git flow. I'm pretty sure git flow became popular just because it was the top search result for "how to git". Other criticisms of git flow and alternative branching procedures have come up over the years [2] and been d…

    Comment linking /2016/02/a-succesful-git-branching-model-considered-harmful/

    on “The Problem with Git Flow”
  2. Submitted What is wrong with “A successful Git branching model”? as a story · 103 points

    HN discussion
  3. Generally the app store review process is much less of a problem than it used to be, with happy path being 24-48 hours rather than 1 week+. Of course everything is context dependent (team size, codebase size, testing maturity, frequency of release), but I guess we found GitFlow seemed to be better aligned with modelling the "versioned software" approach - i.e. with releases determined by features, everybody knows/ca…

    Comment linking /2016/02/a-succesful-git-branching-model-considered-harmful/

    on “How I learned to stop worrying and push to master”
  4. Submitted Avatars, identicons, and hash visualization as a story · 55 points

    HN discussion
  5. I was researching some of this a few weeks ago, and there are many posts about tags being a bad idea. The arguments are that they have to be maintained separately and they lack context. But yes, master branch master race. Also related: "What are the problems with 'a successful Git branching model'?" https://barro.github.io/2016/02/a-succesful-git-branching-mo... Speaking of bad ideas, anyone want to weigh in on merg…

    Comment linking /2016/02/a-succesful-git-branching-model-considered-harmful/

    on “A successful Git branching model (2010)”
  6. Submitted What is wrong with “A successful Git branching model”? as a story · 6 points

    HN discussion
  7. Submitted What is wrong with “A successful Git branching model”? as a story · 5 points

    HN discussion
  8. Submitted A succesful Git branching model considered harmful (2016) as a story · 4 points

    HN discussion
  9. Submitted Taking a look at python-afl: Fuzzing Python programs with afl as a story · 2 points

    HN discussion
  10. Submitted Being a good CPU neighbor (2016) as a story · 1 points

    HN discussion
  11. Submitted What is wrong with “A successful Git branching model”? as a story · 1 points

    HN discussion

Search all of HN for barro.github.io

Linked by the same people?