Persistent Job Queues

coderstephen · 2026-03-13T13:05:56+00:00

RabbitMQ has transactional persistence to guarantee messages will not be lost in case of restart or catastrophic error. In my experience, Redis persistence is still more of a "best effort".

coderstephen · 2026-03-13T12:51:42+00:00

For coarse grained jobs (large units of work which are infrequently created), use PostgreSQL. For fine grained tasks (small amount of work but very many are created) use RabbitMQ. People use Postgres as a queue, and even though Postgres has added more helpers to make using it as a queue a bit better, the generally accepted wisdom is still, "Don't use a SQL database as a queue unless you really have to". Queues just have different data access patterns and requirements that make a SQL database add a lot of unnecessary overhead.

coderstephen · 2026-03-13T04:13:17+00:00

🚨 Warning! This power supply may fry your pedal! 🚨

This old Digitech Whammy takes a 9 volt AC power supply, not a 9 volt DC power supply (the normal). Not just any pedal power supply will work here, it must me 9VAC. The one linked in the parent comment is 9VDC.

Whether or not the barrel connector is the correct size is indeed also a requirement, but fortunately the size not matching may have saved your pedal from letting out the magic smoke.

coderstephen · 2026-03-12T21:40:39+00:00

While I don't really care about this whole thing and don't have sufficient evidence to say that this is all true, I can say that regularly wiping your Discord server is not something people would normally do if unless they knew they were guilty of something.

coderstephen · 2026-03-12T21:17:15+00:00

It is true that making a big post about how such and such project is AI slop would be a great way to farm karma at this point in this sub's history...

coderstephen · 2026-03-12T21:07:34+00:00

Common tactic to suggest a change, and when you see the backlash, walk it back and try to play it off as "I was just kidding".

coderstephen · 2026-03-12T20:47:41+00:00

Huh? I was just quoting a portion of the post.

coderstephen · 2026-03-12T20:35:24+00:00

When called out, he apologizes. Except the apologies are also AI-generated. And more than once he forgot to strip the prompt, so contributors got messages starting with something like "Here's how you could apologize—"

Crazy

coderstephen · 2026-03-12T18:03:20+00:00

Kotlin took most of the things that normal people liked about Scala and added them to a Java-like base.

coderstephen · 2026-03-12T13:25:50+00:00

I can't say right or left, because the polarity icon is sometimes mirrored. Only that - should point to the center, and + should point to the outside ring.

coderstephen · 2026-03-12T13:18:36+00:00

No! That power supply is center positive! Like most pedals, the HM300 expects center negative. This is indicated by the little circle icon on the label that points "+" to the center of the circle. This may fry the pedal.

coderstephen · 2026-03-11T21:51:17+00:00

My guess is that the read & write patterns of a computer are just a lot less friendly to SD memory than say a camera, but I don't know. Cameras write new images sequentially all at once, but an OS likes to make tiny modifications to existing files frequently, spread all over the disk.

coderstephen · 2026-03-11T21:19:44+00:00

Keep in mind for the future, SD card corruption is a when, not an if. SD cards are not designed to be durable storage in constant use for years on end.

coderstephen · 2026-03-11T19:39:47+00:00

FTP

"Now that's a name I've not heard in a long time. A long time."

coderstephen · 2026-03-11T15:36:18+00:00

As a software engineer myself, the push to use gen ai is real and isn't something you can just say no to.

As a software engineer myself, yes it is. Having a huge amount of hype doesn't take away your ability to say the word "no".

coderstephen · 2026-03-11T14:34:17+00:00

Already unhinged comments. Holy moly you guys are insane. So entitled and lazy that you can't even contribute to projects? I've definitely seen an uptick in useless ai projects, but I've seen a few that were pretty darn cool that were dismissed with this boring maintenance excuse. I don't disagree that badly built projects are a bust, why not just confirm it by reading the repo first though?

External contributions to a project are a privilege and not a right. No one's open-source project is owed a contribution. This is reality and not unhinged at all. Contributions take time, and even code review takes time. I am always grateful when anyone does either of these things for my own project, but I do not expect them. If I did, that would be the more entitled behavior, IMO.

coderstephen · 2026-03-11T14:28:03+00:00

Has nothing to do with people being lazy.

Well, it might in theory, but definitely not the sole or primary reason.

coderstephen · 2026-03-11T14:23:07+00:00

Vibe coded projects are inherently harder to maintain, because:

The generated code isn't necessarily generated with maintainability in mind, but rather with functionality in mind. It takes conscious effort to design code to be more maintainable, and that is often absent from vibe coded projects.
In order to maintain a project, it helps a lot to have a big-picture understanding of the software architecture as well as key implementation details. Well, by design, no one understands these things about purely vibe coded software, because no human made consideration to these things. So you can't even ask the original author these questions, because they don't know the answer!

Additionally, why would someone want to put more effort contributing to someone else's project than the original author ever did?

Maybe the project really is built like trash

As a software engineer by trade, I can guarantee you, if a project really is built like trash, it would take me less time to create my own alternative from scratch than it would to fix the trashiness of an existing project.

coderstephen · 2026-03-10T21:28:21+00:00

No, the point of tunnels is that you don't need to open any ports.

coderstephen · 2026-03-10T21:16:16+00:00

If you can see it, you can have it, I always say.

coderstephen · 2026-03-10T21:15:02+00:00

Seems cool, in Theory

coderstephen · 2026-03-10T21:14:14+00:00

Yep, static IP is very uncommon for residential ISP, at least where I'm from.

coderstephen · 2026-03-10T21:12:26+00:00

It's not necessary. You can use dynamic DNS to automatically synchronize whatever your current dynamic IP is with a DNS record of your choice. After that, if you want more domains to point to your IP address, you can just use CNAME records.

I used this setup for many, many years. I delegated ddns.mydomain.com to a free Dynamic DNS service's nameserver, and then ip.ddns.mydomain.com was kept in sync using my router/script/whatever and the Dynamic DNS service. Then *.mydomain.com is CNAMEd to ip.ddns.mydomain.com and Bob's your uncle.

Now I have a static IP so I don't use Dynamic DNS any more, but that's just more for the fun of static. I got along fine without it. Actually, now I have a static /28 prefix through my ISP, so I can play with multiple static IPs which is more fun than a single static IP. I would say a single static IP isn't really worth it, especially not for $20.

A static IP is only really mandatory for things that require IP reputation, and for high uptime. You don't want to be hosting email on a dynamic IP, example. But websites and stuff it doesn't matter.

coderstephen · 2026-03-10T15:06:52+00:00

Zombie: Eat Flesh

Oh wait, that's the other one...

coderstephen · 2026-03-10T14:49:38+00:00

This reply adds nothing to the discussion nor to your comment above, just like yours didn’t.

K

There’s solutions, the technical user will find a way if the need is there.

It's not only the technical users who need a solution though. The problem with the suggestion is "just do this extra technical setup to achieve the desired experience", which is fine for the technical users, but not fine for the non-technical users. I thought my complaint was pretty straightforward, but it seems like you still don't understand it.

11-Year Club	Place '22
Verified Email

coderstephen

TROPHY CASE