If your single operations take 80ms either it’s a toy app or someone didn’t do their job (unoptimized queries, wrong technology, wrong modeling, etc).

Again, not data integrity (Error correction) but consistency (aCid). Adding two milliseconds to a half a millisecond operation is by no means cheap…

“Pretty cheap” is very subjective…

As long as the database is acid restarts should not be a factor. Data integrity is not helped by transactions, you would need error correcting codes for that. Plus the effect on performance is quite notable on all dbs I’ve worked with.

I get that this is a joke, but…

… ackshually it should almost never be a transaction only when there’s absolutely no other option, because transactions kill your performance.

Which is the norm, not the exception. Really good devs (which I’m not) are capable of delivering clean, modular, readable and maintainable code under pressure, working in a team with other people, with unclear requirements.

It can, but usually that’s not the case.

I rewrite it because it becomes a mess of asymmetric assumptions, weird dependencies and hacky extensions, I can’t really blame the language for that one.

Well, I interpret the question as “can you write maintenable code under typical corporate conditions and timelines”. Very few can, but I’ve seen them.

Well, if rewriting is maintaining, everybody can write maintenable code.

Did it become a mess? Rewrite time!

For me the art is writing it so you don’t need to rewrite and you don’t need a janky temporary permanent workaround if requirements change. Clean interfaces, SOLID, plug-ins, etc. Can’t do it myself, but the legendary 10x devs usually do.

Well, even for my private projects that I care about I end up having to rewrite every few years.

Many opensource projects are in same state, I know for sure my projects become spaghetti if I work more than a year on them.

Besides, I’d argue that if you need to rewrite (part of) it is because it wasn’t maintainable in the first place.

ITT: AI induced dunning-kruger. Everybody can write maintenable code, just somehow it happens that nobody does.

Don’t forget to share with the class!

Interesting, TIL.

Practice makes perfect?

Correct. Bee vomit doesn’t rot.

I used retro arch a decade ago, and when setting up a emulation pi last year the consensus seemed to be batocera. No idea if its better, but it’s as easy to use as I remembered and my kids are still enjoying it, so not too unstable.

I use one on my main computer. It still works while charging, and even on Linux I get a notification when the battery goes under 10%. I plug it and use as a wired mouse for the day, and maybe leave it charging overnight and unplug it in the morning. Had it for 8 years now, never an issue.

Fair enough. I do run my docker containers in a real Linux, either homelab or EC2.