This is exactly the reason why fable is blocked at the company I work at.

> the number of Europeans and (North) Americans that die each year from heat waves is already larger than the total number of Americans that die from guns.

This doesn't mean much on its own. People have to die from something eventually, if someone is living a longer life due to not dying for other reasons, they get older and are more susceptible to heat.

On a long enough timeline, a piano could fall on your head

They'll likely have more time with the family because walking and being outside leads to a longer healthier life.

they explicitly called for that in the prompt

Exactly why did they choose this prompt with a white person and not an Asian person, as in all the other examples?

But why? That image actually puzzled me. Does it have some background context? Some historical legend or something of the like?

It is Lunar New Year season right now, 2026 is year of the horse, there is celebratory horse imagery everywhere in many Asian countries right now, so this image could be interpreted as East trampling West. I have no way to know the intention of the person at Qwen who wrote this, but you can form your own conclusions from the prompt:

A muscular, robust adult brown horse stands proudly, its forelegs heavily pressing between the shoulder blades and spine of a reclining man. Its hind legs are taut, its neck held high, its mane flying against the wind, its nostrils flared, and its eyes sharp and focused, exuding a primal sense of power. The subdued man is a white male...

I was creating a Jira/bb wrapper with node recently and Claude actually used plenty of libraries to solve some tasks.

Same with gpt, but I felt it was more like "hey, everyone uses that, so why not me" than finding the right tool for the job. Can't say for Claude.

why copy anything at all? you just need to preserve the head and that's it. As simple as `git branch bkp` and that's all.

In order for that to work you need some level of confidence that rebase doesn't mess with your branch. Rebase has a reputation for "rewriting history".

Well that's a distinction which makes sense in theory but is not realistic in practice for most projects with multiple contributors.

Over at ardour.org, we've never had an issue with this practice. Two core full time devs, dozens of others.

When your PR build takes more than an hour you'll think twice before creating multiple PRs for multiple related commits (e.g. refactoring+feature) when working on a single issue.

That's fine and fair, but you'd better squash them then :)

This is just attention seeking, hard to imagine that after having worked there their best contact is a random person on HN.

GGP didn't say they worked at Microsoft, the comment is a bit hard to parse, but they wrote "I left the company I worked at".

Scant on details, sure, but hard to parse, not really.

The problem is folks this thread seemingly taking a interlocutory approach that can be summarized as, "That which is not explicitly denied can be freely assumed to be true."

(Then throw on top of that, "Depending on how committed you are to your grandstanding, that which is explicitly denied can be conveniently ignored.")

I relate to that and I think the real reason some people struggle to believe that is because not everyone has a great work environment at work. I have one, I actually look forward to coming to the office sometimes.

This is key, I’ve had great work environments where we’ve had lots of fun solving problems together.