What I hate about my new Toyota's volume knob is that there is no indication of volume level in the UI, and the knob itself doesn't ratchet. So I have absolutely no feedback about how much louder or quieter it's going to get when I turn the knob. If I have no music going, but I'm waiting to hear the next GPS instructions, how can I make sure I'm going to hear them? If I'm not sure where the volume is at right now, I can't, unless I turn it and then try and trigger some sound effect or something. It's needlessly complicated.
> no need to tear them down after a couple of decades
Where are people constructing buildings that need to be torn down after a couple decades? This is a refrain I've heard about construction (in the US?) several times in discussions like these, and I find it very puzzling.
IME it's Claude that pushes back, and Codex that just does the thing. It's happened once or twice where I've told Claude bluntly and directly "do this" and it responded "no, here's why that's a bad idea..." Maybe it's just my CLAUDE.md.
Not sure if there are sycophancy benchmarks for coding agents
An image model could probably generate gore as long as there was, say, both PG-13 violence and surgery photos in the training set. There's probably no way to prevent the ability of the model to generate disturbing imagery without also sacrificing its ability to make acceptable things.
'censorship' may be too strong a word, but there is something unprecedented about this. AI tools are supposed to be general-purpose and able to assist with all sorts of tasks. It's expected that they are restricted when it comes to "unsafe" content like illegal or nsfw information and activities. However, this is the first time, to my knowledge, that an AI tool has been restricted from assisting with something that's perceived as a threat to the AI company.
In my experience, an agent with "fresh eyes", i.e., without the context of being told what to write and writing it, does have a different perspective and is able to be more critical. Chatbots tend to take the entire previous conversational history as a sort of canonical truth, so removing it seems to get rid of any bias the agent has towards the decisions that were made while writing the code.
I know I'm psychologizing the agent. I can't explain it in a different way.
It is ridiculously more expensive and complicated under the hood, technically, but to the user, the sheer convenience of being able to text the computer "hey, when I get an email like X, inform Y and do Z" and that's it, you're done, is unmatched.
> Modern JavaScript applications aren't just a few scripts anymore — they're sprawling codebases with thousands of dependencies, complex module graphs, and extensive build pipelines.
This has been true for at least a decade.
The very next paragraph:
> JavaScript-based tools that were once "good enough" now struggle to keep up, leading to sluggish build times, laggy editor experiences, and frustratingly slow feedback loops.
The tools really weren't "good enough", even back then, by these metrics. JavaScript tooling has been slow and bloated on large codebases for just as long.
Animal intelligence is often underestimated, (e.g. there's a famous test that shows that chimpanzee working memory is better than ours) but our use of language is qualitatively different from other animals. Some animals have rudimentary communication, but no other animal is capable (as far as we know) of recursive, infinitely variable language structure like us.
> spaghettification is also a non-issue, as long as the framework defines clear containers for spaghettis
Sorry, but I disagree strongly with this. When there is, inevitably, a bug that the LLM can't fix, someone's going to have to read all that spaghetti, and they'll curse whoever put it there. "clear containers for spaghetti" is a pipe dream, all abstractions leak, and the bug may very well be in the spaghetti. "Just start over" is unrealistic for large, complex apps.
Of course, if you really have a solution for this, that would be incredible.
It's not unreasonable to briefly forget details like that, especially when you're dealing with a multi-language codebase where "how do I make a log statement?" requires a different pattern in each one.
Another American holiday coming up with an equally useless name is Fourth of July. Nobody seems to have a problem with that name, and nobody I know calls it Independence Day. Neither Fourth of July or Juneteenth are great names out of context, but they both have histories behind them and can't be changed anymore.
Heck, Juneteenth is a better name, since it is not literally month+day.