erdaniels

This was very hard to read and this author didn't report their findings to [email protected] either, which is irresponsible.

This is lovely, thanks

Based on the number of comments, upvotes, and recency, I expected it to stay up longer! I think you're right on the flame war part.

Did this get yanked off the front page?

I think if anyone is looking for a concise way to talk about the problems with LLM and agentic coding, it's this. People say AI assisted coding but for much of what I've seen (and tried), it's the tool, gateway, and interface to some people's work now.

This feels AI written as the post goes on. Either way, I'd like for us to stop fetishizing how we can use AI to make us stronger, better, and more valuable engineers. It's exhausting and doesn't consider other ways to use it. I've only been using it lately for tasks that are a step or two above google. Having it write code for me has just been a slippery, unfulfilling slope.

Ah I love this article. I'm now thinking about the idea of encouraging coworkers to orally defend their design documents which are using more AI generated content. People keep saying that we have to focus on what comes before and after code and I think this is a good place to apply friction and avoid building fragile systems.

If you don't know what a reasoning token is, then how can 39 be considered shockingly few?

Yes, full stop. They say they cap the body to 16k and give the LLM a warning, lol. And this is coming from a credit card company.

I'm not trying to be rude here, but this doesn't belong on this site. This is like posting documentation on CloudFlare for a tutorial that isn't remotely a feature.

Yeah it was the same thing with tech force or whatever it was. It's on the last page of the application.