brandur

4 ms·

1.
by brandur 1mo ago
Article does a great job of conveying the stress involved for a non-actor to play even a tiny part in a big movie like this, but yeesh, it'd be a dream come true to get even the tiniest part in one of the greatest movies of all time (I
2.
Migration fatigue, and how LLMs help us avoid it(riverqueue.com)
5 points by brandur 1mo ago|0 comments
3.
by brandur 1mo ago
This is a distinction without a difference. Arko proposed to receive a copy of all RubyGems access logs containing full user PII. He'd accept this PII en lieu of dollars for secondary on call coverage, so a safe assumption is that he i
4.
by brandur 2mo ago
Thanks for that — I didn't know about `clone` (and important to note it's non-default) and now intend to try it out.
5.
by brandur 2mo ago
As long as you're using Postgres, I would definitely try out an approach based on template databases in your situation. It should check all the boxes that a run with `db/seed.rb` would, except an order of magnitude or two compared
6.
by brandur 2mo ago
Ah yep, good point. I was confusing "ramdisk" versus just "ephemeral in-memory".
7.
by brandur 2mo ago
It doesn't look like MySQL has any concept like a template database. You could still migrate up a pristine database, use mysqldump to produce a schema, then load that into a series of test databases. It of course won't be as quick
8.
by brandur 2mo ago
No worries Peter. And thanks for putting together pgtestdb — such a great project! This conversion sprint was a fun little experiment.
9.
by brandur 2mo ago
Some very significant disadvantages to that approach: * It's common these days for a single operation to manipulate dozens or even hundreds of database records. Often these records are interrelated because they reference each other. So
10.
by brandur 2mo ago
Interesting. How many database copies do you bring up when the test suite starts running, and how is parallelism handled?
11.
by brandur 2mo ago
Yeah, I've generally recommended using test transactions during test cases [1] as they're extremely fast. I'm open to alternatives like Peter's approach here though because the template approach has some major advantages
12.
by brandur 2mo ago
Peter actually makes this exact point in the project's README. See this section here: https://github.com/peterldowns/pgtestdb#how-do-i-make-it-go-... I'd just say that a nice thing about it on disk (even if y
13.
Pgtestdb's template cloning approach to testing is fast(brandur.org)
69 points by brandur 2mo ago|51 comments
14.
by brandur 2mo ago
Thanks, this is neat. Goodreads seems to be get so little development attention these days that it's a miracle it still runs. Interesting choice by BookWyrm to hide review ratings by default. I like it — I always felt that on Goodreads
15.
by brandur 3mo ago
Blake wrote a nice page on the benefits of using transactional-based enqueuing here: https://riverqueue.com/docs/transactional-enqueueing It's true that it's not distributed, but there are a lot of benefits t
16.
by brandur 3mo ago
There's some similarities with DBOS for sure like using Postgres as a backend. Here's some differences based on my browsing of their docs for a little while: * River's built around an entirely open core with its bread and but
17.
by brandur 3mo ago
Yes, if one of the admins/mods could correct this, it'd be amazing! The rest of the title is fine.
18.
by brandur 3mo ago
Yes, I roughly agree with all of this. In fact, for most of my existence, I'm been one of those cheap programmers. The circumstances that led to me trying to push River for the next few months were somewhat accidental, and it felt like
19.
The minimum viable unit of saleable software(brandur.org)
217 points by brandur 3mo ago|80 comments
20.
by brandur 3mo ago
Thanks dzonga!
21.
The fourth law (on AI-generated supercustomized email marketing)(robinsloan.com)
3 points by brandur 3mo ago|1 comments
22.
by brandur 1y ago
To be fair I guess, the way the article is titled goes out of its way to mislead. It would be quite easy to say "Added 911,000 fewer jobs from March 2024 to March 2025" or "the year starting in March 2024", but they are
23.
by brandur 2y ago
That's absolutely bananas. $3 million for a _report_ about suggestions for possible immigration reform (to speed it up of course). In the hole $62 billion a year, and a sizable chunk is going to overpriced MBA grads right out of school
24.
by brandur 2y ago
Are you my doppelganger? I made almost this exact comment word-for-word to a friend of mine a few weeks ago. Trudeau's immigration video from December [1] was one of the most dishonest, condescending productions that I've ever see
25.
by brandur 2y ago
The point is that Democratic voters didn't get a chance to have their voice heard. Conducting polling is post-hoc rationalization for Harris being installed by party leaders in unprecedentedly anti-democratic action.
26.
by brandur 2y ago
Also notable that the author didn't link Haje's (the TechCrunch person who railed against Alexander Wang) actual writing because he knew it doesn't make either Haje, or his argument in favor of Haje, look good. So, here it is
27.
by brandur 2y ago
I found this by accident on YouTube the other day, and started watching it, not intending at all to sit through the 4+ hour runtime, but by the next day I'd watched the entire thing. I'm not a Disney Parks person at all, but found
28.
by brandur 2y ago
Thanks Shayon!!! Very kind of you :)
29.
by brandur 2y ago
They'll get lost when using a non-blocking send with select/default: messages := make(chan string) select { case messages <- "hi": fmt.Println("sent message", msg) default:
30.
by brandur 2y ago
In Postgres listen/notify are inherently lossy channels — if a notification goes out while a listener wasn't around to receive it, it's gone, so they should never be relied upon in cases where data consistency is at stake. I

More ›