This reminds me of a great series on YouTube called "Can You Draw Every Flag in Powerpoint?"[1] and the guy does his darnedest to do it precisely, and in the process you learn just how specific (and sometimes non-specific) flags are!
I was surprised to see my Homebrew consider my macOS a Tier 2 for using the very latest macOS version and Xcode version… But I think it's because I don't have Xcode 27.0, which is presumably releasing tomorrow?
It would seem like GitHub is in a precarious situation.
We have many agents per employee working in parallel pushing way more commits than was humanly possible before AI, triggering GitHub actions a lot more than the workflows were built for, causing Actions costs to escalate (they really aren't cheap if you compare to hosting it yourself), meanwhile working with YAML workflows is just a pain, and just writing code would be so much more fun and AI compatible[1].
At the same time, GitHub has about ~3 different PR review UIs? And they're all half-bad? Any decently sized PR triggers their "optimized for large PRs" UI which jumps around randomly in my experience. If you don't get that UI and keep the scrolling one (there's an old and a new one btw) then god forbid you click a line number because at some point your browser will randomly scroll back to that line and it won't unstick. Now Linear[2] (and others) is replacing the PR review experience for the agentic era.
I'd love to see a solid AI first Git + CI + reviews.
Fun data sheet! I was curious about most steps per part and it seems to be TROTTEN[1] at 1.07 steps per part (excluding some other products like a toilet brush with 1 part but the steps are actually for a separate add-on to attach it to the wall).
So much attribution to malintent here, but most likely they're trying to build a product with the features that they themselves would use, and from my own experience it's very frustrating to leave a Claude session running and come back to find it did nothing because it got stuck on a question.
Furthermore, believing that the only thing saving you from disaster is Claude deciding to ask you a question is not a great conclusion either. You need guardrails in the power you bestow upon Claude from outside, not from inside.
Meanwhile, this article was written by Claude and has sentences like "Which cuts less far than it looks.", which I doubt Claude stopped to ask about.
The prose was written by me, with the research being done by Claude and also clearly attributed. I left Claude's research as a series of bullet points so that it would be clear that I'm not passing off an LLM's work as my own, but if anyone wants to dig deeper, they have some starting points to consider.
I don't publish prose written by an LLM for the same reason I would not have an LLM solve a crossword puzzle for me -- there's no joy in that.
No worries. :) I did struggle a little with how to make it obvious that the machine output was not my own. I set it off inside horizontal rules and I did add some prose before and after to say when Claude's output began and ended. If anyone just jumps around using the table of contents, they'll miss that, though. (Not saying that was the case for you).
I had considered putting the research into a gist, but I don't want to have to rely on a 3rd party to keep something that's integral to my post online. Seemed more cohesive to keep it all in one place.
What I was trying to get across was that I had some basis for the points I was trying to make and wasn't just handwaving about it, but I also didn't want to spend endless hours whittling it down. We're all busy people and I see now that it's entirely possible to skim the post and assume it's some low effort word salad. It may be a word salad, but it wasn't low effort. ;)
The article was obviously written by an LLM, it's obviously from the overall structure as well as individual sentences. Maybe you've been exposed to so much LLM text that you write identically to one, in which case, yikes!
The parts outside of the “Claude wrote this” guards seem plausibly written by a human, it’s just that 70% of the article is in the “Claude wrote this” guard.
> and from my own experience it's very frustrating to leave a Claude session running and come back to find it did nothing because it got stuck on a question.
I cannot fathom implementing and shipping a feature to hundreds of thousands of people without even asking basic questions like: "what types of questions does Claude ask users".
Literally one of the most used plugins in their entire ecosystem, provided via their official plugin marketplace, is Superpowers. A plugin whose very first operating step is _asking numerous questions about product requirements_. Of course those prompts can't be skipped!
It wasn't even parameterized for Claude to tell the prompt what severity of question was being asked to allow at least _something_ to categorize urgency or expected response time.
Even more egregiously, 60 seconds!? The first time I noticed this happened was when it asked me a question, I turned to my second monitor to go look at some product documentation to get an answer, and by the time I turned back it had skipped me. How can I possibly provide any kind of informed answer in under 60 seconds? I can barely read some of its context for a question in 60 seconds!
I don't think they did this with malintent, but I do think this shows an enormous gap in judgement in how they handle the idea to delivery pipeline.
Yeah the UX doesn't seem great, though I do think in general the AskQuestion tool is very awkward when it gets used in a very long running process (I personally use Claude to run repetitive tests to slowly iterate on a problem and verify in true conditions that it was solved), so I wouldn't like it without the auto-continue either.
(I had originally replied on safety of letting LLMs skip questions but I don't think that was your point so I removed it.)
Come on now, arguing it's a good feature is different than arguing that it should be turned on by default for everyone with no documented option to turn it off.
I like this feature as an OPTION that is DOCUMENTED. But that's not how it was rolled out. The CC team + processes clearly failed here. And this is far from the first example of this kind of slopiness.
I don't think it was malicious, but I do think it was quite obviously reckless/careless, and I feel like most of the comments here match that sentiment. Everyone and every team makes mistakes, but unfortunately I don't see the CC team really learning from those mistakes even though they keep happening.
CC is not a stable or reliable tool, it is bleeding edge, and that's a tradeoff you make when you pick it over other harnesses.
The biggest performance bomb you can have in your code is a loop that does something like
for (...) {
el.style.height = `${something}px`;
whatever.value = el.style.offsetHeight;
}
This forces the browser to recalculate layout multiple times in a single frame. Separating layout changing code from measurement code will help a lot here (most frameworks out there have solved this so we don't have to be too concerned about it though).
This is true, but a much more common reason is that you have a self growing textarea and Firefox didn't support field-sizing: content until recently, so you had to let JS resize the textarea on every keypress.
I think I can see how dynamic data types make sense (eg flat key/value store), but my question would be:
What is least surprising? That INTEGER implicity accepts 'hello world' without error, or that you can't insert such a value unless you use a keyword like NONSTRICT or a type like ANY?
I would wager the vast majority of SQLite users if asked would probably not expect it to work.
It's probably because SQLite intends to be untyped but also wants the statements to look like standard SQL. This matches their other note about wanting code designed to work with other DBMSes to accidentally work with SQLite too.
Otherwise, yeah, it's very surprising to explicitly put INTEGER and still be able to insert text. It's not like the user left the type out.
I tried running this for some market research for my startup and it did a pretty nice job. It didn't necessarily find any obscure data, and it seemed to rely on older data than what I could find myself. On top of this, it had the same sycophantic tendencies as most LLMs these days (explaining why your idea is great and riffing on that), which I find to be unnecessary use of resources.
All put together, paying ~$60 to get a hit-or-miss report seems a bit excessive, but obviously as the models they use under the hood get better it becomes more and more worth it, assuming they also improve their grounding/search capabilities.
I'm a big fan of Sakana though, and have followed David Ha / @hardmaru since the world models papers (with the racing car game and the Doom clone), which were incredible at the time.
JWTs are fine, seems a bit sensationalist title...
Some nice topics to talk about instead:
- When to use an encrypted value (and symmetric or asymmetric), vs. a random (but secret) value, vs. a signed value (readable but not tamperable)
- Where to put these values (memory, localStorage, cookies)
- How to make sure these values don't last forever, and whether you need to be able to revoke them (make them invalid before their natural expiration timestamp)
In short, it lets you switch between all your Claude accounts seamlessly and will automatically pick the one with the most usage left.
I've been using the c, cw, and cr shortcuts for a long time but today I wished to switch to another account and wanted to keep the simplicity so I built this.
It's been mostly coded by Fable 5, with strong guidance by me. I've vetted the code and made sure the code it executes is readable in one file and that domain is secured, script is checksummed, project is open source, etc. but as always use your judgment and double check what you download from the internet!
[1] Part 1: https://www.youtube.com/watch?v=w5QSVhgrqVE
reply