klausa
this lets them exit this without public humiliation of getting made fun (and example of) in the mailing lists.
I don’t know how Sonys attestation works, and how resistant it is; but presumably it’s a bit harder than “lie to the game about what firmware you’re running”.
(GTA VI will famously not have a physical release, so you can’t rip data off the disk.)
Tons of AI (and adjacent) sponsors!
I have paperwork from three different countries disagreeing with you, but thanks for your concern :)
It took me until... late twenties? to understand that most people _aren't_ feeling physically uncomfortable in anything long sleeved (or with long pant legs), and that they're just more... patient? tolerant than I am?
It just straight up isn't an inconvenience to other people!
I am very, very, very glad I have a career (and live in a climate) that lets me get away with shorts and short sleeves on 99,9% of days.
How do you define "average living standard", so that it would take a colossal disaster to have US reduced to that of Poland?
Yes; there have been some pretty high profile cases of games launching in terrible state, and Day 0 patches have become an industry standard, but acting like all (or even most) of big games launch like this is just sampling bias.
Have you never "fixed a bug", only to realize that you just papered over a single symptom, while the underlying bug is still intact?
People you're disagreeing with (I think!), would say that during your first attempt, you didn't _really_ understand the part you're modifying.
It is _very easy_ to do this in large codebases, and even more so when working on anything touching UI.
I disagree with this being a foregone conclusion
The offer letter, which spells out “which vests over 4 years”: https://colo.to/invitation.pdf
The option grant which has the accelerated schedule: https://colo.to/grant.pdf
The issue here is, IMHO, not "Nvidia owes me stock in an ironclad way and gets away with it because of statue of limitations", but "I accepted an offer from Nvidia but the paperwork between the offer and the options grant differed in a way that both benefits me, and nobody noticed or cared about until now".
The original offer was for 25k shares, vesting over 4 years. The options paperwork says 25k shares, vesting over 4 _quarters_.
Now, I'm not a lawyer, and certainly not a securities lawyer, but that seems like it could be reasonably chalked down to a clerical error on the options paperwork? "You made a mistake and now I can get a billion dollars more than we agreed to originally" doesn't feel like a great lawsuit!
Whether they "earned" them is disputable — the offer letter specifies one vesting schedule (25% every year), the "cover sheet" from the options agreement specifies other (25% every _quarter_).
So — the OP got the shares he was promised in the original offer letter; but later discovered that some of the documents he later got implied that the vesting schedule should be accelerated compared to what he agreed to.
I think that is probably the funniest way possible to earn a billion dollars; but whether he's "owed" that money/shares, is... up for a debate.
CC (the desktop version) has a built-in terminal. It’s great idea when working with worktrees!
But the terminal is _in the sidebar_. Not as a panel that pops up from the bottom like in… every IDE ever that has this feature, but in the sidebar.
You can drag it to the bottom using tiny drag targets if you want, but if course this only persists for a duration of a single conversation.
And there’s a built-in keyboard shortcut to toggle it being shown/hidden. Again, great idea!
But using this resets the panel to its original position, again, making it appear in the sidebar.
Bonus points: when I tried to submit this via the GUI version of /feedback, it told me that it was disabled by workspace policy _after_ I filled out the form and hit submit. Brother, just hide the button that makes the form appear in the first place!