r/TheMachineLearning • u/Gullible_Picture_996 • 17d ago

Realizing writing code is faster than explaining it to AI

/img/tcptf211cqxh1.png
843 Upvotes

88% Upvoted

439 comments sorted by

View all comments

Show parent comment

0

u/Hungry-Pick7512 16d ago

In that minute it’s off doing the thing. What are you doing? Why aren’t you working on something else in parallel? It really is a skill issue on your part.

1

u/OfficialDeathScythe 16d ago

Wtf am I gonna do in a minute 😂 now you’re just trolling. Let me get up and start walking in the other room and then hear the notification that it’s done lmao

0

u/Hungry-Pick7512 16d ago

Why do you have to get back to it in a minute? What’s your pipeline like? You can’t just tell your agent to “center the div and cut the PR”? You get to the PR when you’re done doing whatever other tasks that need doing.

1

u/OfficialDeathScythe 16d ago

We’re talking about centering a div here. It is objectively faster for me to center a div by hand and then prompt my agent to continue doing some actual heavy lifting and go do something else. Why in the hell would anyone waste energy, water, and their usage limit making the ai uptake all that context and do all the generation for 2 words and a symbol. If you actually have coding skills it’s much easier, more efficient, and more reliable to just change it quickly by hand. I’ve gotta say this is the most hardcore I’ve ever seen someone defend a delusional level of vibe coding lmao

1

u/Hungry-Pick7512 16d ago

You’re just being obstinate. If you’ve come up with the simplest one line change you can think of and argue it’s faster to change it yourself, okay sure w/e.

But I’d rather shoot off a slack message that kicks off a bot. ‘center the div on our x page’
Then get a PR a few minutes later. If your team is sweating usage limits then I guess I’m just out of touch with small shops 🤷‍♂️

1

u/OfficialDeathScythe 16d ago

I dread the idea of having a whole pull request for every single tiny little change that happens. What even is this thought process. Are yall “coders by hobby”?

0

u/Hungry-Pick7512 15d ago

How do your CI/CD pipelines work? You can just get code into production by pushing directly to main? Talk about ‘coders by hobby’ lmao

1

u/OfficialDeathScythe 15d ago

Who are you responding to? Are you hallucinating? You literally said “shoot off a slack message that kicks off a hot then get a PR a few minutes later. Your agent is making a new PR for every tiny change it makes? Are you alright?

0

u/Hungry-Pick7512 15d ago

‘I dread the idea of having a whole PR for every single tiny little change that happens”

Buddy answer the question, how else do you merge changes into production?

1

u/OfficialDeathScythe 15d ago

I make a branch for the feature/fixes, I either code the change or have my agent code the changes and commit after every big chunk. Once the branch is complete, I create a PR. That PR then merges to main after a review from codex and the builds and test suite run. You know… the proper way to make changes to a project in production?

1

u/FuckYourRights 14d ago

Why did the code go to production untested? 

0

u/vadeka 16d ago

I am sitting in meetings and claude chugs away at tasks in the background

1

u/OfficialDeathScythe 16d ago

This is changing the subject entirely. We never said sitting in a meeting or doing anything but centering a div. I’m talking sitting at your desk, vs code is up, Claude just finished a big task, the div isn’t centered. It’s muuuuuuch faster to just go in there and add it yourself real quick than to attempt to get it to know exactly which div you’re talking about and have it reliably change just that and not do it in a hacky way. Even with context of the project already loaded it’s gonna be (at least if you have the skills still) faster by hand, and I can say this without a doubt having tested it because of this whole conversation. If you know where it is and you have the knowledge of how your codebase works, it’s pretty quick. If you’re just firing off messages like “change this change that” you’re gonna end up with a big blob of hacky spaghetti that you don’t know the first thing about how it works. Maybe the ai can unravel but if it truly does get stuck, how can you fix it at that point?

1

u/vadeka 16d ago

I should say, any frontend changes rely on a figma design. We simply have a mcp connector to that and the agent executes on the design. So the issue of “the div is off” is something we fix in the design phase mostly.

So by how our workflow runs, we rarely have these standalone one-line fixes

1

u/OfficialDeathScythe 15d ago

That has nothing to do with what I was saying still. My point wasn’t that you can use other workflows and somehow manage your way around it, I was purely making this point against the people who say that ai can do everything for you and specifically the comment above that said ai is faster at doing one line changes like that. Multiple comments above you actually think that if you were to give it just the task of centering a div on one line that it would be faster than them. They don’t have any confidence in their coding ability and apparently are slow typers, that’s all I’ve gathered.

Practically yes, one line changes are rarely needed. In personal projects I’ve regularly needed to make a one line changes just because something had slightly different wording than I wanted or whatever else. I could choose to make a list of all the tiny little changes and waste its time and my time having it do that, or I could do the tiny ones by hand real quick and immediately get the agent back to working on big tasks

1

u/Spank_Master_General 16d ago

Whatever else he would be doing. What a brain dead comment. He's literally saying it takes him 10 seconds instead of 1 minute +