the hacks began around April 17 and lasted until this week [...]"

This is staggering.

The fact that it works at all after a number of years, is surprising to me, given everything that goes on with it: You've got a moist environment with water pumped through it multiple times a day, fertilizer in the water crusting up in places, living plants with their roots growing into the pipes, algae growth, and a lot of parts that are shuffled around often.

There might well be other systems around these days that are the same or better, I wouldn't know, the Gardyn is just what I ended up with when I researched it years ago and I'm happy with it. For downsides, seeds are expensive from Gardyn, but you can plant your own. I do buy some from Gardyn because they have a big selection, and they usually come out good, which regular seeds often don't for whatever reason. They try to push their subscription service but I don't need it, so don't use it.

Hope this doesn't come off as advertisement, as I said there may well be better options (would like to hear about them), but this one works for me for a pretty hassle-free experience.

[1] https://mygardyn.com/product/gardyn-home-kit/

Unless you're a five man shop where everybody just agrees to use that one table, make sure to manage transactions right, cron job retention, YOLO clustering, etc. etc.

Performance is probably last on the list of reasons to choose Kafka over Postgres.

As the article demonstrates, the error manifests in a completely inscrutable way. But once I saw the bug from a couple of users with Turkish sounding names, I zeroed in on it. And cursed a few times under my breath whoever messed up that character table so bad.

As for the language itself, a lot of verbosity has been culled in later language versions, with diamond operators, lambda expressions, local variable type inference, etc.

In either case, code is read more than it is written, so if a bit of verbosity makes code easier to read, I'm okay with it.