@deredleritt3r@bigswingingdong This post argues against your original one. So: Anthropic stood on principle, won public trust and, in the end, kept gov business. Here, they’re trying to assess the claim this is a nat sec risk worth pulling the most useful model their customers ever had (and are paying for).
@niklassheth@MatthewSchrager@cognition I wish this point would get more attention. The GPT vs Claude fans seem to talk past each other. GPT 5.5 comprehension and correctness is superior to 4.8, but that doesn’t necessarily mean code quality is better. I use them both to QA each other’s work.
@Corballyred@AnfieldSector@_pauljoyce IMO, main issue with 6 is the move from single pivot last season to double pivot this season. Lost control. My 2p… go back to 24/25 formation and players, and put Wirtz in Messi-like free inside fwd role, not midfield. Grav CDM (+ add fast backup), Szobo + (?) at AM/CM.
@KatanaLarp This is so clearly for the clicks, or it's skill issue. Did you contact the repo owner, before publishing, to get the skinny on the perf issue?
I say this because LLMs have been doing very solid performance optimization work in a >2M LOC enterprise codebase I work in.
@bcherny@vasilyu Think he might mean the CC CLI in terminal. The / picker only works as the first char of a prompt there. CC Desktop and VS Code ext. show it wherever / is used. I'm guessing this might be because handling mid-message / picker functionality is trickier to pull off in CLI.
@DarlingtonDev@Yuchenj_UW It's even more reachable than that - they just need 83k new Max subs. (DoW contract is $200M/yr, i.e. $17M per month. Claude Max is $200/mo. 17M/200=83k. They may or may not get there this weekend, but the goodwill will likely far exceed the direct dollars.
@AmandaAskell @TruthIsAnAction @elonmusk@WSJ Your gracious replies here are inspiring. They’re like your podcast appearances, so full of care and thoughtfulness. Thanks for doing what you do.
FWIW, I was more consciously invested in the future of the world *before* I had kids. Now I’m just bloody well trying to keep up!
@TruthIsAnAction @AmandaAskell@elonmusk@WSJ As a parent I became less empathetic, not more. Gotta feed and protect my kids, my marriage, my job… my energy. It’s exhausting - good exhausting! - but my focus turned inward.
(And look at Elon’s empathy profile - he’s become more publicly bitter and cruel, post kids.)
@doodlestein Great advice.
(Side note - Claude Code’s shallower thinking (IMHO) vs 5.2 Codex EH highlights why your model-agnostic agent flywheel is valuable even if CC rolls out those new features “inspired” by it. And even Codex isn’t perfect, so multiple rounds and HITL still needed.)
@doodlestein This is like Jevons' Paradox, human edition. As time cost per unit of output goes DOWN, your total time spent doing stuff goes UP!
Lower cost enables use cases that weren't feasible before... so pioneers work non-stop.
Same goes for AI tokens. Cost down, AI lab revenue up.
This has been said a thousand times before, but allow me to add my own voice: the era of humans writing code is over. Disturbing for those of us who identify as SWEs, but no less true. That's not to say SWEs don't have work to do, but writing syntax directly is not it.
@doodlestein That method of building product for oneself has a pretty good track record. How many of us have build versions of Mail and CASS just to try to scale ourselves? Thing is, you finished the job, did it well, and then you scaled it out further. Thanks again.
@doodlestein thank you for open sourcing the Agent Flywheel. I can't use all of it (enterprise env), but just implemented BV. Game changer. Next up: CASS, Mail. Your framework (effective, mutually-reinforcing, recursive improvement) is superior to all vendor options I've seen.
@doodlestein Everyone and their brother is building versions or pieces of what you've got. But I think you're doing the best job out there, your work product stands out even in this crowded space and you could build a loyal customer base. Just my 2 cents.
@doodlestein Finally, as a product guy by background, I get that the flywheel is at risk of obsolescence because IMHO it should already exist in CC/Codex harnesses already (even mail interop)! But they'll likely slow down and you could serve early adopters who want to stay ahead.