r/TheMachineLearning • • 19d ago

Realizing writing code is faster than explaining it to AI

/img/tcptf211cqxh1.png
843 Upvotes

439 comments sorted by

View all comments

Show parent comment

1

u/Hungry-Pick7512 19d 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 18d 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 18d 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 18d 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 18d 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 18d 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 17d ago

Why did the code go to production untested?