Live data from Hacker News

Viewing profile — bgentry

bgentry

HN member
Joined
Thu, Dec 03, 2009, 4:37 AM UTC
HN karma
5,978
Public activity
776 items

About bgentry

Software engineer building River (riverqueue.com). Former Co-founder at Distru. Mux, Opendoor and Heroku alum.

[ my public key: https://keybase.io/bgentry; my proof: https://keybase.io/bgentry/sigs/RDwSk5TnJBGqGLpMbkVGHs1oi8xRF6bs-yXND13oxiM ]

Recent public activity

  1. comment
    Comment #48950839

    There's an active incident tracking this: https://status.claude.com/incidents/g613ntyj2pwf

  2. comment
    Comment #47441395

    Thanks for sharing your report, it's frustrating to see things like this break in minor patch updates. Small tip for GitHub Gist: set the file format to markdown (give it a .md ext…

  3. comment
    Comment #47210298

    The important quote from the timeline: Mar 01 9:41 AM PST We want to provide some additional information on the power issue in a single Availability Zone in the ME-CENTRAL-1 Region…

  4. comment
    Comment #47208115

    Here is something that gets lost in all the excitement about AI productivity: most software engineers became engineers because they love writing code. I think there's a big split b…

  5. comment
    Comment #47089582

    The actual decision: https://www.supremecourt.gov/opinions/25pdf/24-1287_4gcj.pdf

  6. comment
    Comment #46921328

    Absolutely agree and likewise buddy :)

  7. comment
    Comment #46920340

    Oh hey Curt!! Remember, you are not a monitoring system :)

  8. comment
    Comment #46920134

    Yep, that team did great work. I remember having lunch at the Heroku office with the dotCloud team in 2011 or 2012 and also Solomon Hykes demoing Docker to us in our office’s basem…

  9. comment
    Comment #46919556

    As somebody whose first day working at Heroku was the day this acquisition closed, I think it’s mostly a misconception to blame Salesforce for Heroku’s stagnation and eventual irre…

  10. comment
    Comment #46901459

    You'll need to unlock your iPhone first. Even though you're staring at the screen and just asked me to do something, and you saw the unlocked icon at the top of your screen before/…

  11. comment
    Comment #46624605

    No, I don't think so. Oban does not rely on a large volume of NOTIFY in order to process a large volume of jobs. The insert notifications are simply a latency optimization for lowe…

  12. comment
    Comment #46620803

    This is largely because LISTEN/NOTIFY has an implementation which uses a global lock. At high volume this obviously breaks down: https://www.recall.ai/blog/postgres-listen-notify-d…

  13. comment
    Comment #46620004

    Yeah, River generally recommends this pattern as well (River co-author here :) To get the benefits of transactional enqueueing you generally need to commit the jobs transactionally…

  14. comment
    Comment #45490582

    I get the temptation to attribute the popularity of these systems to lazy police with nothing better to do, but from personal experience there’s more to it. I live in a medium size…

  15. comment
    Comment #45406701

    Aaron did RT the post here which likely indicates some agreement with the sentiment in it: https://x.com/searls/status/1972293469193351558 Also he shared it directly while saying i…

  16. story
  17. comment
    Comment #44659519

    Take my money! I have been looking for a good way to get Claude to stop telling me I'm right in every damn reply. There must be people who actually enjoy this "personality" but I'm…

  18. comment
    Comment #44231999

    As one of River's creators, I'm aware of many companies using it, including names you've heard of :) One cool open source project I've seen recently is this open source pager / on-…

  19. story
  20. comment
    Comment #43953808

    Modern Postgres in particular can take you really far with this mindset. There are tons of use cases where you can use it for pretty much everything, including as a fairly high thr…

  21. comment
    Comment #43953691

    Definitely not! Jobs in River are enqueued and fetched by worker clients transactionally, but the jobs themselves execute outside a transaction. I’m guessing you’re aware of the ri…

  22. comment
    Comment #43953576

    You can get pretty high job throughput while maintaining transactional integrity, but maybe not with Ruby and ActiveRecord :) https://riverqueue.com/docs/benchmarks That River exam…

  23. comment
    Comment #43589554

    Ah, so that issue is specifically related to a statistics/count query used by the UI and not by River itself. I think it's something we'll build a more efficient solution for in th…

  24. comment
    Comment #43586585

    Developer of River here ( https://riverqueue.com ). I'm curious if you ran into actual performance limitations based on specific testing and use cases, or if it's more of a hypothe…

  25. comment
    Comment #43465875

    Hah, I agree, "easier" is too soft :)