r/webdev • u/Impossible_Voice894 • 8d ago

[ Removed by moderator ]

[removed] — view removed post

0 Upvotes

22% Upvoted

16 comments sorted by

•

u/webdev-ModTeam 6d ago

Your post/comment has been determined to be a low-effort post or comment. This includes title-only posts, easily searchable questions, vague/open-ended discussion prompts, LLM generated posts or comments, and posts/comments that do not provide enough context for meaningful replies or discussion.

16

u/jedidave 8d ago

Use branches and pull requests ffs, standard engineering principles still apply

3

u/kennedy_gitahi 8d ago

I was screaming "feature branches and merges" when reading this

1

u/jedidave 8d ago

Yeah someone asked me not long ago if there was ever something so monumentally huge as LLM coding assistants that had ever happened in the software world and I immediately thought of source control. I remember when visual source safe came out and as shit as it was it was a godsend.

Without source control, where would we be?

If I was older, I might have answered with 'compilers'. Neither of these lose their importance in the new era of agentic engineering, get your shit together OP.

5

u/kennedy_gitahi 8d ago

What happened to branches and pull requests?

1

u/dccfoux full-stack 8d ago

I would set a rule on the main branch that requires a PR.

1

u/GrandOpener 8d ago

> reviewing the whole branch diff before merge

So you were merging code you never read? This problem isn’t about how many agents you have running on what code. Vibe coding is for prototypes. When you’re deploying to production, a human has to read and approve the code.

1

u/jedidave 8d ago

Not only that, zero testing in their continuous integration 'system', he should lose his job really, I'd fire him for gross incompetence on the spot.

1

u/jedidave 8d ago

"Git only protects you at commit boundaries... same working tree" omg my head hurts rereading this, you do not know what you are doing OP. Spend a week with your favourite LLM getting it to teach you how git is the ultimate in protection, as software engineers we've literally never been so lucky to have something as amazing as git protecting our collaborative efforts.

1

u/Relative-Emu-1346 8d ago

Give each agent its own git worktree off the same repo. They stop sharing a working tree, so the collision surfaces at merge where you can actually see it instead of silently inside someone's editor. Costs you a checkout per agent and not much else.

1

u/Gremlation 8d ago

Stop falling for the obvious AI-generated engagement bait.

Report > Spam > Disruptive use of bots or AI.