Breach of contract seems to be the major one - from https://www.scribd.com/document/709742948/Musk-vs-OpenAI page 34 has the prayers for relief. B and C seem insane to me, I don't see how a court could decide that. On the other hand, compelling specific performance based on continual reaffirmations of the founding agreement (page 15)...seems viable at a glance. Musk is presumably a party to several relevant contracts, and given his investment and efforts, I could see this going somewhere. (Even if his motivations are in fact to ding Microsoft / spite Altman).
Some games solve this by having different modes of play. "Highscore Mode", "Campaign Mode (Easy/Medium/Hard/etc)". If you did, for example, have a dynamic scaling system, you could have that in some kind of alternate play mode that lets the user just practice, vs. a separate/more static mode that allows eligibility for highscores.
> relentlessly applying a critical eye on everything I write and others write
Honestly, I believe that this is one of the best habits I've developed at my current workplace. We use Code Collaborator (a code review tool) for about 90% of all commits; I like using to get at least one pair of eyes on my code, but even further, I only even send out a review after I've gone through my own diff with a fine-toothed comb.
I may as well make one suggestion along these lines ( implemented in a similar JS library I whipped up not too long ago: https://github.com/wyantb/js-regex ).
> One vote and a comment if they are especially lucky.
Rings pretty true to me; admittedly, I don't participate much in comments or have a recognizable name, but my past submissions certainly fit this bill.
Though, when I look at the 'newest' queue [1], there are 30 posts in the last hour and only one front page. Not everybody can make it. For my part, I'm mostly curious what does, actually, make it.
Do you mean that you prefer the method names in VerbalExpressions, or the lack of nesting? I've been experimenting with my method names a little bit here and there, so that's been in flux. The lack of nesting in VerbalExpressions, though, I think really limits the ability to produce arbitrarily complex regexes, such as https://github.com/wyantb/js-regex#business-logic-regex . Perhaps it could be said that one shouldn't write regexes that complicated anyway, though, so there's a case for their API anyway :)