After months of daily AI-assisted coding, here's what actually works (and what doesn't)
Posted by lksrz@reddit | ExperiencedDevs | View on Reddit | 28 comments
I've been using AI coding tools (Claude Code, Cursor, Codex CLI…) daily for months across several projects. Not hobby stuff - real production code with real users.
The biggest lesson: (serious) AI coding is not "vibe coding." It doesn't replace thinking - it changes what you spend your time thinking about. The bottleneck shifts from writing code to planning, reviewing, and catching subtle issues the model introduces.
I wrote up a practical guide covering what actually made a difference for me. Main takeaway? After each task, do cross-model code review.
Let me know what you think. There are plenty of vibe coding guides out there, but that's not what I'm going for. Happy to discuss with developers who use these tools seriously.
lksrz@reddit (OP)
So, if we’re discussing bottlenecks, I don’t agree that coding was never the bottleneck. I didn’t mean to say that it was the only one. Of course, planning, reviewing, managing, and everything else involved were always crucial. The issue is that these problems persisted, and the only problem that AI (until now) has (almost) solved is the coding aspect. So, I mean that coding is no longer a bottleneck, but other issues remain and there are more significant now. Single dev, AI-powered, without those skills - will still fail.
boring_pants@reddit
that's not what "bottleneck" means though.
lksrz@reddit (OP)
So, what it means? 5 years ago, a team could consist of PM, devops, and 5 devs (backend, frontend, full stack, testers...). Removing 4 of 5 devs would paralyze the team. There was always more developers. Today, you might have a PM, half devops, 1 or 2 developers, and AI, and still accomplish the same tasks if the team uses AI effectively.
RemoteLengthiness391@reddit
Writing slop code is easy, but to have the whole domain knowledge of the area as a few "vibe coding developers"? Good luck.
ExperiencedDevs-ModTeam@reddit
Rule 8: No Surveys/Advertisements
If you think this shouldn't apply to you, get approval from moderators first.
Sighlence@reddit
I have to assume that your blog post is as clearly AI-written as your reddit post, so no thanks, not interested.
lksrz@reddit (OP)
No, it was not. I dictated it while driving a car via Wispr in a few sessions and afterwards used AI for fixing grammar. I was preparing initial materials for internal team AI training but thought it may be good to publish as well.
CodelinesNL@reddit
No you fucking didn't. This is the most transparent lie there is.
I use AI to "fix my grammar" all the time. If you ask it to do that, it does just that. It doesn't magically rewrite the thing using all the standard AI patterns.
Liar liar, pants on fire.
lksrz@reddit (OP)
Exactly, that is why I never use "Rewrite" (in OSX) but "Proofread" because I don't like changing what I wrote, only fix typos. This is ridiculous.
lksrz@reddit (OP)
WTF 🤦🏻
boring_pants@reddit
"It's not AI-written, I just had AI write it"
lksrz@reddit (OP)
?
CodelinesNL@reddit
Your blog is verbose AI slop. This is the laziest way or writing blog posts and frankly an insult to your reader. If writing the prompt takes you less time than it takes you to read the output; it's useless slop.
lksrz@reddit (OP)
I don't have any blog :) Did you read what I wrote about my workflow?
CodelinesNL@reddit
Are you not the author of that medium post?
lksrz@reddit (OP)
Yes but one article is not a blog. I don't understand such comments.
CodelinesNL@reddit
Ah yes, because THAT is what should be of concern in this discussion.
lksrz@reddit (OP)
I thought it should be how to use AI in coding. Topic is AI-assisted coding.
blacklig@reddit
Wow more low effort slop trash what a surprise
gjionergqwebrlkbjg@reddit
When you take a shit, please flush it down a toilet and not post it here.
boring_pants@reddit
loud drawn-out fart noise
xpingu69@reddit
I think I don't want to see slop
popovitsj@reddit
Hello? Is anyone out there?
austinwiltshire@reddit
As an *experienced* dev...
The bottleneck was never coding. It was always planning, reviewing, and catching subtle issues.
mugwhyrt@reddit
I have a hard time taking posts like OP's seriously when they suggest that writing code was ever the bottle neck.
ianpaschal@reddit
Indeed. I’m also really fed up with how everyone acts like all the code which used to be written by humans was well thought out, bug free, epitome of craftsmanship etc.
Writing code that technically compiled never actually meant you knew what you were doing.
1cec0ld@reddit
Damn. I'm not even cold enough for that burn.
onFilm@reddit
Also as an experienced engineer, like the other mentioned, the bottleneck is always the processes in the business and those that surround the code, not the coding itself.
AI might be able to code a lot of my work, ranging from the frontend, backend, devops, infra, etc, but it's strongest use for me personally has been optimizing managing and planning.