alt Hacker News> I have a friend that just picked up a new consulting job resurrecting an ancient Windows desktop application. No source control, no tests. And it's spread out over a dozen different folders with names like "_old", "_new" and "dates".
That doesn't sound very impressive. Not being tracked with a version control system is fixed instantly with a git init, git add ., git commit .no AI required.
Covering the app with tests is also something that requires no AI. At most, coding agents can generate characterization tests in broad sweeps, but we are talking about a delta between hand rolling and vibe-coding of a couple of days.
Where LLM shines is helping developers build up an understanding of what is in place. Running /explain on a codebase can quickly provide you with a high level summary of what's in place.
Replies
That's what the comment is saying. In normal repositories, version control acts as a record of the momentum of the direction the product was taking. If it's just "_old" and "_new," the developer has to read and understand both, which I think is going to be far more time consuming than your estimation.
The relevancy here is that he's denied the git history, versioning, branches, implicit documentation that even bad source control practices would have given him.