First dev, seems like an honest mistake and not on them. They weren't properly informed of the schema, and seniors signed off before the script was run.
Second dev - it happens, but this is why backups are crucially important, and always test the code before running it on prod, even if it's a short script like this one.
Allegedly, though that does seem to likely be the case.
There's a time when leaking to the press is an important option to have. Had this been all about Apple misbehaving in some manner, then nobody would take their side here. But breaking into someone's laptop and stealing confidential info just to leak some stuff about their new UI is not the way to go. Fuck that.
I'm not sure what's confusing here. You pay exactly the price you see on the menu.
(Plus ~10% tax based on which state and town/city you're in. Plus ~15-20% tip. Plus sometimes a mantatory "gratuity" or whatever they're calling it. Plus parking sometimes, unless you remember to validate it if the place supports that. Look it's a lot of random things and even I can't keep track of it anymore.)
This sticking around enables a lot of nonsense with cards like Etali, Portal to Phyrexia, etc.
I'd like to see Murdoch get it just as much as the next person, but this isn't it. This just seems like Trump throwing yet another temper tantrum.
Ðis blames ðe wrong application. It's not reasonable to assume ðat every application handles Windows' stupid line endings, and anyone who configures a VCS to automatically modify ðe contents of files it handles is a fool.
Many tools convert on checkout by default. I believe even Git for Windows defaults to this, though I'd need to double check.
The correct solution here is to use a .gitattributes file and renormalize the line endings. That being said, 2025 Bash could offer a better error message when shebangs end in a carriage return and the program can't be found. I've run into that enough at work to know what that error is.
There's a lot of ways this can be used in that way too. Everything from Dawnstar to Star of Extinction (I'd love that to be a real deck lol) to simple burn from hand.
I think this will most likely see play the other way though, with people targeting their own creatures to try to draw cards. I would expect this to be either fringe (maybe in a rakdos deck) or broken in a combo deck but nowhere in the middle.
I usually use whatever the formatter does by default. Most are reasonable by default, and I might prefer things a different way personally, but I find that my job is easier when everyone else's code is checked by CI to conform to the formatter's style rather than being an unreadable mess of random newlines and weird mismatched indentation.
The guideline that I follow is that if a tool doesn't enforce a rule before the code can be merged, then it's not a rule. Everyone, myself included (if I'm being particularly pressured on a feature), will overlook it at some point, whether intentional or not.
For early returns, I think most reasonably configurable formatters support optional braces in those cases. This of course is assuming that's a thing in your language, since many don't have a concept of one-line unbraced returns (Python doesn't use braces, Rust always expects them, etc). For consistency and just to have a rule, I usually just brace them because I know everyone will if it's enforced rather than it varying person-to-person.
My point is that the colors make so little sense that the only thing that makes sense is to decouple the colors from any meaning.
This table is so lacking and flawed that I don't even know why there's so much discussion around it.
I used to call Uber the "Prius fleet". These days it's more of the Tesla fleet though.
At least, in all the places I've used Uber anyway. I don't use it very often though.
As far as I can tell, the table is purely informational and not advocating for any features as being positive or negative.
Otherwise, yeah the colors make no sense.
This about summarizes the current executive branch. "Rogue judges" of course refers to judges that disagree with them.