I possess an eighth sense which allows me to determine whether or not I have received an email by looking at my phone and seeing the notification for such. I don't even need to open the email app and I can sense that one has arrived.
Is there a way to search for lawsuits from shareholders when the price per share of going private was less than 30%? There's probably no mathematical model here but more a way for the sale to insulate itself from getting dragged into litigation.
You play many rounds of trying to fairly divvy up piles of loot. Different pieces combine in ways to increase their overall value, as well as each piece having a base level amount of value. As a result the actual act of dividing it fairly becomes complicated, and players will try to influence the outcome in order to maximize their score at the end of the game to win.
It sounds great in theory, but the reality is that many car owners obscure their license plates or use ghost plates. NYPD has no interest in enforcing the rules against this either.
I like SQL and all but I really don't care to follow ISO releases. They're hundreds of dollars and nobody actually implements the whole thing. I get way more excited about database releases.
Does anyone else find value in what's in an ISO standard?
> Even if a project is not hosted on GitHub, other people have the legal right (depending on the license) to redistribute the source code. It means that they have the right to share the code of others on GitHub, as long as they respect the terms of license. This is totally legal. But then, Copilot will be able to analyze the code and violates the license terms, which isn’t.
While encouraging people to not distribute code via Github may mitigate the issue some, the actual issue is how Github has mass-automated the process of violating open source licenses. Github should pay a fine for every suggestion Copilot produces that violates a software license, plain and simple. Don't blame the people that unknowingly upload code to the training dataset.
I'm a huge fan of awk but the "Python vs awk" page this links to [1] shows python code that's almost deliberately atrocious.
Take this function the author wrote for converting a list of integers (or strings) into floats
def ints2float(integerlist):
for n in range(0,len(integerlist)):
integerlist[n]=float(integerlist[n])
return integerlist
Using `range(0,len(integerlist))` immediately betrays how the author doesn't understand python. The first arg in `range` is entirely redundant. Mutating the input list like this is also just bad design. If someone has used python for longer than a month, you'd write this with just `[float(i) for i in integerlist]`.
Further down in the function `format_captured` you see this attempt at obfuscation:
i can’t for the life of me reason why the changes to auto correct were ever seen as useful. that it changes a word you’ve typed two words ago (so it’s outside of your attention by the time you’re focused on getting the most recent word correct) is baffling.
Additionally, by designing it this way you’re guaranteed to only notice when this feature fucks up. If you typed the wrong word and moved on, you never notice. If you typed the right word and moved on, you see auto correct has fucked up after you send the message, or as it’s fucking up because you’ve learned to not trust the keyboard anymore so now you’re constantly rereading the last few words as you’re typing.
Really a shame they put effort into a feature that’s designed to frustrate the user in this way.
You can have both, and they can create a feedback loop that guarantees someone will never be able to get out.
A more general example of this is scarcity mindset where the condition of not having enough of something causes someone to be poor at managing that resource [0].