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.

GDP*

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.

Thank you for the effort!

What’s the problem with wolves being fun?

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.

You’re holding it wrong

This is one from 2 days ago…

PS: it’s not some accounting trickery, if I load a few reddit comment threads to read on a plane the battery really lasts forever.

Yeah, that’s my point. 40m on screen 8.4% if battery.

I didn’t use it that much yesterday, but we can extrapolate…

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.

It’s the windmills! I blame the Dutch.

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

Do we know they aren’t?

Wok hei, tho.