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

N

Nat Pryce

Personal blog · natpryce.comprogrammingwriting

Nat Pryce writes Mistaeks I Hav Made, a personal blog at natpryce.com about programming and writing. Since 2009, 18 different Hacker News readers have linked it 21 times, most often “Mistakes we made adopting event sourcing (and how we recovered)”. The last post was in 2019, but the archive is still widely read.

Visit the blog
21mentions?
18HN people?
2009–2019first – last linked?
Links on Hacker News per year · peak 7 in 2016

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

Why HN links it

HN readers link Nat Pryce's articles on Java and software design, such as dependency injection and checked exceptions in generics. Commenters also cite his posts as sources and list his blog among good tech blogs.

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.

Most-linked posts?

  1. Mistakes we made adopting event sourcing (and how we recovered)
    3 people · 3 mentions · first linked 2019-07-01
  2. Early Impressions of Kotlin
    2 people · 2 mentions · first linked 2016-01-01

What Hacker News says?

  1. Ideally we want something like class Stream<T> { <R, X> Stream<R> map( Function<? super T, ? extends R, throws X> mapper ) throws X } and if you pass a function that throws, say, IOException and SQLException, then X=IOException|SQLException and that's what that call to #map throws. You can sort of do it by http://natpryce.com/articles/000738.html but you have to choose one base type and you can't make stdlib support…

    Comment linking /articles/000738.html

    on “Go Turns 10”
  2. Submitted Mistakes we made adopting event sourcing and how we recovered as a story · 245 points

    HN discussion
  3. A license like this has two red flags. I previously worked in a programme providing corporate governance of open source. It's a fairly big industry with companies like Black Duck helping companies manage their legal risks, and licenses like this aren't popular. Firstly, it's non-standard. As others have said, it's the author's right to make it non-standard, but I don't recommend people try that unless there's a real…

    Comment linking /articles/000225.html

    on “Evil, or why Douglas Crockford is harmful to Free Software”
  4. Submitted Avoiding Nulls with 'Tell, Don't Ask' Style (2010) as a story · 34 points

    HN discussion
  5. HealthyTree · 2016-08-18Recommends
    A few that I follow on a semi-regular basis: https://michaelfeathers.silvrback.com http://highscalability.com http://techblog.netflix.com http://www.natpryce.com https://8thlight.com/blog/ https://www.percona.com/blog/ https://www.smashingmagazine.com http://blog.crisp.se/author/henrikkniberg https://m.signalvnoise.com https://dannorth.net/blog/ https://codeascraft.com

    Comment linking /

    on “Ask HN: Good tech blogs to read”
  6. Submitted Early Impressions of Kotlin as a story · 27 points

    HN discussion
  7. "Dependency Injection" Considered Harmful: http://www.natpryce.com/articles/000783.html

    Comment linking /articles/000783.html

    on “Dependency injection is not a virtue”
  8. Submitted Mistakes we made adopting event sourcing (and how we recovered) as a story · 6 points

    HN discussion
  9. Too bad that 1.0 will ship without something like Scala Future's. Now you can only have a similar functionality with CompletableStage. It would've been way better to actually have a similar implementation than scala.Future. I mean they wouldn't need Quasar, Akka for basic stuff. However currently you need to stick to Java pendants. Kotlin has some great things, but overall I still prefer Scala over Kotlin for anythi…

    Comment linking /articles/000815.html

    on “Kotlin 1.0 Release Candidate”
  10. Submitted Mistakes we made adopting event sourcing (and how we recovered) as a story · 3 points

    HN discussion
  11. Submitted Mistakes were made adopting event sourcing as a story · 3 points

    HN discussion
  12. Submitted What do Programmers Feel About their Software? as a story · 2 points

    HN discussion
  13. Submitted Message Obsession (2016) as a story · 1 points

    HN discussion
  14. Submitted Property Based TDD at SPA 2013 as a story · 1 points

    HN discussion
  15. Submitted Mistaeks I Hav Made: A Whirlwind Tour of the Kotlin Type Hierarchy as a story · 1 points

    HN discussion
  16. Submitted Higher Order React Components as a story · 1 points

    HN discussion
  17. Submitted Mistaeks I Hav Made: Higher Order React Components as a story · 1 points

    HN discussion
  18. Submitted Early Impressions of Kotlin as a story · 1 points

    HN discussion
  19. Submitted Interactive Explanations of Example Code as a story · 1 points

    HN discussion
  20. Submitted How I learned to stop worrying and live without version control as a story · 1 points

    HN discussion
  21. Submitted Testing 3rd party services using Simplicators as a story · 1 points

    HN discussion

Search all of HN for natpryce.com

Linked by the same people?