Jared Scheel
10.7K posts

Jared Scheel
@jscheel
head of engineering at groovehq (groove, helply, instantdocs, zeroto10m) • girl dad • software dev • synthesizers • photography • gaming • christian above all
Nashville شامل ہوئے Mayıs 2008
838 فالونگ688 فالوورز

@lunar_rish @TechEmails you do you, I don't really care what you think
English

@jscheel @TechEmails "dev account" lmao, i have never encountered this once, it's just the algo you built bro

English

@thdxr I just cannot get into talking to my computer. I like to think through things too much. Heck, I’ll draft a huge md file then dump it into opencode sometimes. Are you finding that talking out loud helps you think through it more?
English

@Shpigford Sorry to hear this. My wife lost her father to pancreatic cancer about a decade ago. Saying a prayer for y’all.
English

my mom was recently diagnosed with stage 4 pancreatic cancer.
that's both an overwhelming diagnosis but also an overwhelming flood of information, documents, appointments, options and questions.
i needed a place to keep track of it all and also a place to ask questions, do research and help my parents and family do the same.
so, naturally, i built something.
keptwell.org
if you/you're family is navigating a serious diagnosis and want to use it, let me know (or drop your info in that waitlist box).
not charging anything for it at the moment (and with as much AI as i've got layered into this, frankly it's gonna cost me a nice chunk of change to run it). but mostly interested in just making this as useful as possible to families going through long, complex and heavy situations.




English

@jwage @taylorotwell that sounds about like what I am doing with our outbox as well. What I like about bullmq is that I can very easily control noisy tenants, priority, uniqueness, etc, but I just hate having so many extra moving parts. Hence me exploring simplifying to just using pg.
English

Only uniqueness if I’m understanding you.
I enforce at least once delivery and idempotency at the application layer when handling messages. So we retry failures when relaying batches to rabbitmq and when handling individual messages…but if a message has already been handled, we won’t handle it twice.
Our outbox->rabbitmq relay fetches messages from the outbox in batches of 200 and we relay to rabbitmq and commit to pgsql in batches of 50. So if a batch relay fails, the blast radius is 50 messages. So for example if 45 of the 50 made it to rabbitmq and 5 didn’t, we have to retry all 50. But the handling side enforces the at least once delivery and idempotency so only the 5 that didn’t make it will get handled and the other 45 get short circuited.
This guarantees at least once delivery and no chance of lost messages.
English

All most apps will ever need.
Aaron Francis@aarondfrancis
Database as a queue is an anti-pattern! ...that I absolutely love and do all the time anyway. Definitely worth a read.
English

@jwage @taylorotwell Did you do any fair queueing, uniqueness, or tenant partitioning when you were running your queues in pg? I’m used to leveraging an outbox and redis-backed mq, but I’ve been considering simplifying for something new.
English

@brianchew @samlambert Chinatown Food Complex is near Maxwell too. Both are pretty awesome imho
English

anywhere in the marina bay sands (or gardens by the bay is beautiful)
for food:
- try yakun kaya toast or killney coffee (both awesome and local)
- go to a hawker, there's one called 'lau pa sat' right in the city centre, or you can consider maxwell food centre which has a bunch of great stuff too!
English

ok, this is straight up hilarious.... @wesbos showing up in my "today's news" section like the president just made an announcement from the oval office

English

@nickgraynews I desperately need this. I think a large portion of my followers / following are dead accounts now. The algo seems to punish those of us who have been here the longest with its initial engagement gate.
English

The new reply option @photomatt suggested to @nikitabier is… not great. It’s an admission that X has been unable to control the bot problem without hurting the core ethos and experience of the platform as a digital town square. I hope a better solution can be found.
English










