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

G

Greg Weber

Personal blog · blog.gregweber.infoprogrammingweb

Greg Weber's personal blog at blog.gregweber.info covers programming and web. Since 2011, 4 different Hacker News readers have linked it 6 times. No feed was found, so read it on the site itself.

No feed foundVisit the blog
6mentions?
4HN people?
2011–2025first – last linked?
Links on Hacker News per year · peak 3 in 2025

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

Why HN links it

Greg Weber's blog covers Go error handling, including structured errors and an error library using slog attributes, and trunk-based development with GitHub Actions. Commenters cite these posts as sources.

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.

What Hacker News says?

  1. gregwebs · 2024-12-18Recommends
    There's a lot of comments here that seem overly critical. The author came up with solutions to extend Go's errors to meet their needs and shared that with the world- thank you. I have been solving all the same problems and providing libraries that allow for more flexibility so that users can come up with approaches that best meet their needs. I am finally polishing the libraries and starting to write about them: htt…

    Comment linking /blog/go-errors-library/

    on “How we centralized and structured error handling in Golang”
  2. Submitted MongoDB as a better default data store as a story · 36 points

    HN discussion
  3. There are several existing Go error libraries with a similar approach sans context. The approach I ended up taking is to use slog attributes. It allows for reuse of existing logging attributes. This is explained here (skip to the “adding metadata” portion). https://blog.gregweber.info/blog/go-errors-library/ Go package: https://pkg.go.dev/github.com/gregwebs/errors/slogerr

    Comment linking /blog/go-errors-library/

    on “Structured Errors in Go (2022)”
  4. Submitted High Performance Ruby Part 3: non-blocking IO and web application scalability as a story · 9 points

    HN discussion
  5. Here is an article of how my team had accomplished this with GitHub actions I posted earlier: https://blog.gregweber.info/blog/github-actions-trunk-based-...

    Comment linking /blog/github-actions-trunk-based-development/

    on “Trunk-Based Development”
  6. Submitted Trunk Based Development with GitHub Actions as a story · 2 points

    HN discussion

Search all of HN for blog.gregweber.info