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

T

Trisha Gee

Personal blog · trishagee.comprogrammingcareer

Trisha Gee's personal blog at trishagee.com covers programming and career. Since 2021, 8 different Hacker News readers have linked it 13 times, most often “I prefer trunk-based development”. It is still writing: the last post was on 2026-07-31, and you can follow it by feed.

Visit the blog
13mentions?
8HN people?
2021–2026first – last linked?
Links on Hacker News per year · peak 3 in 2023

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

Why HN links it

HN readers link Trisha Gee's posts on AI-assisted coding, including whether reviewing generated code takes longer than writing it. The comments cite her points in their own arguments about gen-AI coding.

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

Making complex systems coherent.

Most-linked posts?

  1. I prefer trunk-based development
    2 people · 2 mentions · first linked 2023-06-04

What Hacker News says?

  1. It will certainly be the default for cases where it's easier to read code than to write code, but this is far from universally true. AFAIK, Joel Spolsky was the first to discuss this at length 25 years ago [0], but numerous people have echoed his sentiment [1, 2, 3, ...] One of the most underrated skills in effectively using gen-AI for coding is knowing ahead of time whether it will take longer to carefully review t…

    Comment linking /presentations/reading_code/

    on “Vibe engineering”
  2. Submitted Reading code is a skill (2020) as a story · 155 points

    HN discussion
  3. >I only write around 5% of the code I ship, maybe less. >I do thoroughly audit all the code that AI writes, and often go through multiple iterations Does this actually save you time versus writing most of the code yourself? In general, it's a lot harder to read and grok code than to write it [0, 1, 2, 3]. For me, one of the biggest skills for using AI to efficiently write code is a) chunking the task into increments…

    Comment linking /presentations/reading_code/

    on “Is it a bubble?”
  4. Submitted Working Smarter, Not Harder as a story · 28 points

    HN discussion
  5. Submitted I prefer trunk-based development as a story · 3 points

    HN discussion
  6. Submitted Reading Code Is Hard, and tips to improve as a story · 2 points

    HN discussion
  7. Submitted Trunk Based Development as a story · 2 points

    HN discussion
  8. Submitted The Ugly Phase as a story · 1 points

    HN discussion
  9. Submitted Hello burnout my old friend as a story · 1 points

    HN discussion
  10. Submitted Flaky tests are poisoning your productivity as a story · 1 points

    HN discussion
  11. Submitted Tools and Processes for Collaborating on a Book Remotely as a story · 1 points

    HN discussion
  12. Submitted Dealing with Legacy Code in OpenJDK (JEP 416) (2021) as a story · 1 points

    HN discussion
  13. Submitted Do we need comments in our code? as a story · 1 points

    HN discussion

Search all of HN for trishagee.com

Linked by the same people?