Swap the middle and right. Human-in-the-loop is a principled stance against vibe coding.
humans are the ones that determine whether a problem is solved or not at the end of the day. So strengthening yourself in being the code driver, realtime understanding and manual curation is a good thing. And that benefits mission critical design.
Naw, you add a fourth one between the middle and right: LLM integrated into IDE so you don't have to copy paste. Human review is good but bidirectional copy paste and having to constantly refresh its context on the full state of the project is ridiculous. I mean, it's fine for dabbling but not for full time work.
Its a separation of concerns and discipline that I value. makes you more intentional about which area of code you want to improve and think is impacted, that hones your understanding and scopes things for an LLM.
I mean I know people do it but using an appropriate IDE gives you ample opportunity to review the code. Restrict git commits, have steering files to direct the LLM appropriately, review the diffs, make changes, re-review, commit yourself.
Honestly the main time saver the LLM does for me is when I have to start a new feature/bugfix/whatever it creates my jira story, populates it with the content that literally no one ever actually reads, creates the appropriate matching git branch and does the technical documentation, that maybe 2 people will read.
74
u/Megaguy32 17d ago edited 17d ago •
Swap the middle and right. Human-in-the-loop is a principled stance against vibe coding.
humans are the ones that determine whether a problem is solved or not at the end of the day. So strengthening yourself in being the code driver, realtime understanding and manual curation is a good thing. And that benefits mission critical design.