I have very few issues with Claude. If I just tell it what the goal is, it will make some sensible suggestions, and I can tell it to start coding towards it. It rarely messes up, and when it does I catch it in the act.
You don't necessarily want to completely tune out while you're using the AI. You want to know what it's up to, but you don't need to be at your highest level of attention to do it. This is what makes it satisfying for me, because often it eats up several minutes to hunt down trivial bugs. Normally when you have some small thing like that, you have to really concentrate to find it, and it's frustrating.
When the AI is on a multi-file edit that you understand, that's when you can tune out a bit. You know that it is implementing some edit across several instances of the same interface, so you can be confident that in a few minutes everything will build and you will get a notification.
It's as if I can suddenly make all the architecture level edits without paying the cost in time that I had previously.
cedilla · 15m ago
Funny how the article starts with someone using AI — to develop more AI stuff.
This reminds me of web3, where almost all projects were just web3 infrastructure or services, to the point that the purpose of most start-ups was completely inscrutable to outsiders.
I'm having lots more hope for AI though.
sl8s · 34m ago
If you add an AGENTS.md, the AI agent will work more efficiently, and there will be far fewer problems like the ones you’re facing. You can include sections such as Security, coding style guidelines, writing unit tests, etc.
johnjungles · 6m ago
PR fatigue is a real thing
jph · 27m ago
One improvement is to start using an AGENTS file. There are many. Here's the repo that I personally use thanks to Pontus Abrahamsson and using TypeScript:
Everyone suggesting maintaining an agent.md file haven’t met the majority of their coworkers who refuse to document anything or read documentation. Perhaps train a model that can generate these agent files for them?
bgwalter · 19m ago
An advertisement, where the protagonists weigh the pros and cons and then come down on the side of "paying the innovation tax".
Fastly profits from"AI" just like Cloudflare (or should we say "Claudeflare").
This selection of developers does seem representative at all. The new strategy is to acknowledge "AI" weaknesses but still adamantly claim that it is inevitable.
jitl · 22m ago
The worst is when I have to baby-sit someone else’s AI. It’s so frustrating to get tagged to review a PR, open it up, and find 400 lines of obviously incorrect slop. Some try to excuse by marking the PR [vibe] but like what the hell, at least review your own goddamn ai code before asking me to look at it. Usually I want to insta reject just for the disrespect for my time.
dawnerd · 8m ago
I insta reject. It’s ridiculous how bad it’s made some devs. Are they even testing their work before tossing over the wall?
whynotminot · 2m ago
Hold up, people are starting to mark PRs with [vibe] as in “I don’t stand behind this, good luck.” ??
I do not care if engineers on my team are using AI. In fact, I think they should be. This is the new world and we need to get used to it.
But it’s still your work, your responsibility. You still have to own it. No cop outs.
lawn · 7m ago
We need to normalize to reject crap PRs. If we don't then things will only continue.
CuriouslyC · 13m ago
Have your own agent do first pass code reviews, they catch that stuff every time.
goldenCeasar · 5m ago
And then the PR owner's agent can fix it and then after some number of iterations you get a PR for a new and mysterious system.
You don't necessarily want to completely tune out while you're using the AI. You want to know what it's up to, but you don't need to be at your highest level of attention to do it. This is what makes it satisfying for me, because often it eats up several minutes to hunt down trivial bugs. Normally when you have some small thing like that, you have to really concentrate to find it, and it's frustrating.
When the AI is on a multi-file edit that you understand, that's when you can tune out a bit. You know that it is implementing some edit across several instances of the same interface, so you can be confident that in a few minutes everything will build and you will get a notification.
It's as if I can suddenly make all the architecture level edits without paying the cost in time that I had previously.
This reminds me of web3, where almost all projects were just web3 infrastructure or services, to the point that the purpose of most start-ups was completely inscrutable to outsiders.
I'm having lots more hope for AI though.
https://github.com/pontusab/directories
If you prefer AGENTS.md files using markdown, I've extracted them into my own repo:
https://github.com/SixArm/ai-agents-tips
Fastly profits from"AI" just like Cloudflare (or should we say "Claudeflare").
This selection of developers does seem representative at all. The new strategy is to acknowledge "AI" weaknesses but still adamantly claim that it is inevitable.
I do not care if engineers on my team are using AI. In fact, I think they should be. This is the new world and we need to get used to it.
But it’s still your work, your responsibility. You still have to own it. No cop outs.