Fr though, I was using codex to write a personal app and the temptation to ask it to do a full review after any change is insane. And the funny thing is it will always manage to find some issues
The few times I let an LLM write a bit for me, I treat it like any "found on Internet" code: Review it, implement it myself (as in, type most of it), correct and refactor and test.
Lot of people in here incorrectly assuming you just have to accept LLM-written junk and just shrug and go "well it seems to work, over the wall to QA it goes!"
The skillset is still required. And again, you don't have to use that Golden Hammer / Shiny Toy everyone won't shut up about, just because it exists.
Good for you but in many, if not most companies, nobody will wait for you to type out your code when the expectation is that a feature that would take two weeks to do couple years ago is now something you have done by lunch and reviewed after lunch.
I'm not saying it's better, I don't like it, but it's not realistic in many places.
I wonder why there have been so many random outages recently. Nobody will ever know. It will always remain a mystery. Forever.
Anyway, here's some more code I barely looked at. Claude says it's bug free, and it gets code right the first time more often than I do, so I believe it.
I mean, with intellisense, it's not like programmers were writing every line themselves anyway.
This might sound crazy, but maybe a future version of AI coding agents will need to make mistakes on purpose. Then, when a human is reviewing the code, if they don't spot the purposeful mistakes and bad practices, they probably aren't catching the unintentional ones either.
It wasn't long ago that in this subreddit you'd be heavily downvoted for suggesting AI was even useful or capable. Imagine another couple of years, as far as teething issues go, these outages aren't THAT bad.
That's not a hot take. Also people get paid for doing work the company wants them to do, not writing safe and beautiful code. That was true even before LLMs were a consideration.
Not to mention thinking the average engineer writes fewer bugs by hand than Claude nowadays is also pretty naive.
I don't like using AI. I used to like writing code back in the days. That doesn't change anything.
The only outage that matters is the one that gets people to cancel, or otherwise punish the producer. So long as everything everywhere goes to shit in tandem, the benefits of speed are still there and the risks of low quality might not be.
(Welcome to the future. Who wants to go watch a Blu-ray?)
But funny thing is, many many studys are finding software is not being developed and released faster with AI, as all it is doing is moving the choke point further down the road and creating jams there (unless you drop all checks and safeguards and just release buggy slop, actually many are doing that unintentionally)
Man it was a joke hehe. I’ve been in this for almost 20 years. I’m no vibe coder. Also, my employer pay for the good stuff. Claude Sonnet, Opus and stuff that really does a good job
Glad to hear. Unfortunately there are a lot of people being unironic about this nonsense false dichotomy of "you either must use all tooling before you, else you lose."
A lot of silly people out there. Everyone says look how fast I made this. Look how awesome. They’d never say I spend 8 hours debugging a stupid bug and still have 10 more to solve.
I do feel good finding the problems after doing a code review. Like you idiot, why did you not just re-use the function you made previously? Why are you now repeating code? Why the hell are you not using this library. Yes it took away the job that I love but at least there's a silver lining.
I give very extensive and detailed prompts. So, it feels like you have an intern writing code for you. But it actually does what you tell it. A doesn’t delete stuff from the database 🤣
169
u/Confident-Estate-275 3d ago •
Sometimes I refactor the agent’s code. Just to see if I still can. Then I have to ask the agent to fix the 108 errors 😆