Miaou

Alors pourquoi tu fais semblant d'être de gauche dans ton autre commentaire ? Aurais-tu honte de tes opinions politiques ?

Sometimes the info lost is just a typo or a revert. I'd say heavily depends on the workflow of the people involved. Some like long history, some like rebasing, others, something in between. How you review those approaches changes a lot

For every musk or bezos there are a hundred billionaires whom we've never heard of and who are just as greedy. I don't think it necessarily changes much

A simple but hackish solution is to version your types. New field? Foo becomes Foo2! Now nothing builds and you're sure you'll have to go over every usage of the type.

Add a second commit to revert to Foo, and there you go. Of course you'd need two reviews but the second one is trivial

They have a contract with their employer, though. The problem here is not contracting, it's this stupid at-will employment that allows this to happen

There are absolutely the problem, that's actually the difference between a programmer and an engineer: the liability.

"I was just following orders"

Might explain why the function is deprecated

All of that can also be tested in a preproduction environment as well, downtime is really a poor excuse for not patching

Surely you meant the opposite? Working multiple jobs is a very USian thing. Now I'm curious, where are you from?

Well, getting promoted is difficult when you watch Netflix or browse lemmy on company time

And then you realise the program doesn't crash when compiling with debug symbols 😢