Between this and the C.Ronaldo decision, I wonder if we're headed toward a future change to the automatic red card suspension. Part of what makes a red seem extreme for certain fouls is the automatic suspension.
The point of the suspension is to discourage deliberately violent actions when the current match isn't a major concern (i.e. late in games that aren't close, or when the result is largely immaterial). That obviously isn't the case here.
Bit of a double-edged sword, that. Worker-owned businesses are great, but if you instead make workers minority shareholders, you get... the modern retirement system, and inflated asset prices that benefit the ultra-wealthy far more than common investors.
Turning inefficient, unreadable code into efficient, readable code often results in an overall reduction in LoC.
High-quality code and high-volume code are highly anti-correlated. Incidentally, low-quality code that is excessively long just so happens to be common complaint with AI-generated code.
Mental health is health. Negative mental health impacts are particularly significant when your job is to perform mental labor.
It's not defiance, it's reality: if you drag down my motivation, that's going to drag down my productivity. I don't really have much active control over that.
In some cases, workers are also being asked to automate the parts of their jobs they enjoy most, Hinds said on the podcast, pointing to customer-service employees who enjoy building relationships but are increasingly expected to supervise AI agents instead.
"That's what gives you joy and meaning at work," she said. "That is very dangerous."
What's a 20% productivity gain if I constantly feel deflated by work that used to energize me? That's going to give back the productivity gain and more, while also decreasing my quality of life.
Every time I review a new PR to my codebase, I go "oh shit, these unit tests are garbage, they've clearly been vibecoded" and tell the contributor to rewrite the unit tests so they do more than just game the coverage metrics.
Then he kept playing a market that was already fully decided, when the only step left was to resolve the outcome. I believe the relevant adage here is "You can't cheat an honest man."
With that said, any trades after a market has concluded but before it is officially resolved should be voided. The market should close at the end of the time window (or the time of the resolving announcement, if that's the relevant trigger point).
They seem to be converging toward an asymptotic accuracy level that is not particularly close to 100%. That is not good enough when you're trying to instruct engineers, particularly junior ones.
The ticket has subtle errors in its description that are only caught by someone experienced with the codebase.
The code hides an exception behind an if-then-else that defaults to the most common state, which isn't caught until it breaks things for the 1% of users who don't have that state.
The new feature quietly breaks a feature not covered by the acceptance tests.
The documentation is four times as long and nobody who relies on it can read it.
And I'm stuck spending my time going over tickets with a fine-toothed comb, reviewing PRs, and mentoring contributors to prevent all of this garbage from ending up in the live code.
"Lawful" as determined by the party executing the action is very different from actually lawful.
The courts can intervene later, but they can't un-bomb a hospital.
This is setting aside the obvious problem where governments will often set laws based on self-interest rather than morality, particularly when it comes to military conflict.
I've used a K4 for 6 years now and love it. The only thing is that I had to swap out the arrow keys for textured ones, which allows me to reach for them blindly and keeps me from losing my location when using them.
It's honestly one of his worst videos, but Jon Bois has quite thoroughly documented how many mattresses they tried to sell him as a result of him buying a mattress.
https://www.youtube.com/watch?v=n36R8xlhe1U
Any dataset involving police actions will show high concentrations in poor areas because that's where police patrol the most and where they're most likely to crack down on behaviors that might be allowed to slide elsewhere (in part due to the racial demographics of those areas).
Bubbles don't pop overnight. In the aftermath of any collapse, you can generally see a pretty clear pattern of red flags (and attempts to minimize them or cover them up). Some parties notice earlier than others, but the realization is generally a much more gradual process than the collapse.
The point of the suspension is to discourage deliberately violent actions when the current match isn't a major concern (i.e. late in games that aren't close, or when the result is largely immaterial). That obviously isn't the case here.