I get excited by new model releases, try it, switch it to default if I feel it's better, and then I move on. I don't understand why any professional SWE should engage in weird cultish behavior about these models, it's a better mousetrap as far as I'm concerned
I resent the conflation of child abuse and child labor. There's actually a healthy dose of labor for kids that we've all but disallowed from polite conversation
You need to hit that thumbs down with the explanation so the model is trained with the penalty applied. Otherwise your explanations are not in the training corpus
The lower level the dependency is, the more unjustifiable it is for it to have its own dependencies. This ought to be a point of competition between libraries and often is, at least in the c++ world
The stable model usually implies that your app has to target both the old and the new distro version for a while. That is a bit too much to ask for some, unfortunately
A rivalry, wanting to score points, wanting to gain standing at the expense of another, are all things that do not have much to do with wanting your opponent to collapse
I think the point is that you can't ban houses through policy but you can ban golf courses. So like it or not (and I sympathize with your point), the policy knobs that can be used to curb water can only directly influence things like golf courses, but they can indirectly affect home water usage through utility pricing.
Good money elsewhere for people capable of (a) learning COBOL (b) being effective in a legacy codebase and (c) operating in a large organization in a political savvy way.
The secret sauce is being able to operate below your maximum effectiveness while still seeming impressive enough. That is, if you want to play the long game and get a lot done over a 5 year horizon.