I suppose what I’m surprised by most is the degree to which the text bloviates. Rarely is it encoding a dense concept. Instead it’s a simple concept expressed with great complexity. I wonder what tuning resulted in this because the output programs it writes are superior to prior iterations for my use-case.

It’s just an amusing degree of bombast as well. The pre-emptive hedging makes sense: despite the insight into J space etc., the models still do the majority of their thinking in generated tokens so it is forced to write “this no longer does an O(n^2) read over all rows” in a comment in brand new code. It’s a substitute for working memory. “It’s easy to be accidentally quadratic here, so I’ve done it this way specifically to avoid that” becomes temporally labeled into “this no longer” because of the order of operations “write quadratic, user prompt to linear, write linear” but it remains as a comment to its amnesiac future self which has poor Chesterton-Fence-familiarity.

Despite my annoyance with Claude’s writing style, my friends do tease me with examples like this that it comes up with: “to be honest, it sounds like you”. Thanks, guys, well played. Simple concepts expressed complicatedly.