Doubtful commentary misses the obvious: that, had Calif been slightly more responsible in their harness design -- and in particular, their definition of what constitutes a real bug -- it'd be rather unsurprising if Claude correctly dug some up.
Maybe it's not so sensible to offload the responsibility of clear thinking to AI companies?
How is a chatbot supposed to determine when a user fools even themselves about what they have experienced?
What 'tough love' can be given to one who, having been so unreasonable throughout their lives - as to always invite scorn and retort from all humans alike - is happy to interpret engagement at all as a sign of approval?
> How is a chatbot supposed to determine when a user fools even themselves about what they have experienced?
And even if it _could_, note, from the article:
> Overall, the participants deemed sycophantic responses more trustworthy and indicated they were more likely to return to the sycophant AI for similar questions, the researchers found.
The vendors have a perverse incentive here; even if they _could_ fix it, they'd lose money by doing so.
the invisible hand of the market strangles its strongest adherents
The desire for something "new", for a Mildly Ethical product, killed off the most obvious path to success - to actually just make TikTok+AIGC, or in the present, Douyin+Seedance2.
“What’s up Outragers, just dialing in from my NBA team’s headquarters to yell at the people whose careers I’ve just pummeled,” Unterwurzacher wrote. Atlassian fired her a few days later, saying she had “engaged in acrimonious communications and ad hominem attacks against teammates and colleagues.”
Unterwurzacher replied, “I think it’s difficult to point out the power imbalance in a way that is not potentially described by somebody as an ad hominem attack.”
Perhaps it is difficult, but it doesn't look like she was trying
> At a March 3 hearing in Austin, a National Labor Relations Board attorney said the fired software engineer, Denise Unterwurzacher, had been acting in the spirit of Atlassian’s own stated “Open Company, No Bullshit” philosophy
I think if you have a "Open Company, No Bullshit" philosophy in your company handbook, then you can't claim "No, not like that..." when called on your BS.
If their company policy was "always obey legal orders from superiors" instead then I think they have a much clearer case at firing for cause.
She’s satirizing the irony of a wealthy ceo’s tone deafness while communicating decisions that adversely affect workers while preserving their own lavish lifestyles. Sounds like she was living out the no BS culture.
I don't see it. What part of her satire was off the mark? it was entirely factual.
If you can't take such a gentle ribbing from people you've potentially just fired, you shouldn't be CEO, because you can't control your emotions in the simplest way.
You're either being naively or facetiously too literal. She's saying that her point is about him, so talking about him is ad hominem, but not a fallacy because unlike fallacious ad hominem attacks, her argument about the hominem is very relevant to her working conditions and experience as an employee. Her group having just been pummelled and yelled at.
It’s a pretty literal description of what he did. If techbro bosses don’t want to get butthurt over being called out for douchey behaviour, maybe they shouldn’t engage in douchey behaviour?
Almost none of these tech leaders deserve their station except by virtue of luck or often borderline sociopathic tendencies. To flaunt it so egregiously is a bit over the top.
Nobody mentioning how this project is vibecoded slop?
> The code is really bad with completely uneeded parts. The LLM (Qwen 2.5 7B) has hardcoded the i9 14700KF topology, and has variables related to it never used... It's even funnier that the show hardware function always prints the same string. There are even random pip log files. Why did this slop got coverage here?
## Methodology and Tools
This investigation was conducted by a human researcher who directed all research decisions, selected sources, evaluated findings, and wrote the public-facing posts. Claude Code (Anthropic's CLI tool, running Claude Opus) was used as a research assistant for:
- Bulk data processing: parsing 4,433 IRS Schedule I grant records, 59,736 DAF recipients, 132MB of Colorado TRACER campaign finance data, and IRS Business Master File extracts covering all US tax-exempt organizations
- Cross-referencing findings across 24 analysis files and identifying patterns that span multiple research threads
- Drafting intermediate working documents and structured data summaries
- Web searches against public databases (OpenSecrets, ProPublica, state lobbying portals, WHOIS/DNS, Wayback Machine)
Claude Code did not independently choose what to investigate, decide what constitutes a finding, or determine what to publish. Every factual claim in this repository cites a primary source (IRS filing, Senate disclosure, state database, legislative record, or published reporting) that can be independently verified. The tool does not change whether Meta's LD-2 filing lists H.R. 3149, whether DCA has an EIN, or whether Stefanski admitted tech funding under oath. The records exist or they don't.
If you want to verify any finding, the source URLs and database identifiers are provided throughout. Start with the primary records, not with this repository.
I find it valuable to know the author was responsible for selecting what sources & questions to analyse.
Its our own sessions, from our team, over the last 3 months. We used them to develop the product and learn about our usage. You are right, they will remain closed. But I am happy to share aggregated information, if you have specific questions about the dataset.
reply