Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I also spend a lot of time at work trying to get the code into a shape I deem acceptable to open a MR for the team, without looking incompetent.

At home I stopped reviewing the code for my mobile app, and I do not feel this has affected maintainability.

With 150k LOC, the AI still performs changes as easily as it did three months ago, when I started the project.

If anything, the new models made it easier.

When I read all those posts from people advocating a very hands-on, understand each line approach, I speculate many come from a position like me at work or have never seriously tried 'vibecoding' a large project from scratch with SOTA models.

People routinely post that things I work on for 30 hours/week are impossible.



150k sounds like a LOT… what’s your use case for the app?

It seems for any particular problem/comexity there is an estimate of how many LoC is needed (written by humans, good coding practices). And after reaching maturity (and not increasing scope) the LoC converges.

My experience with LLMs so far is it’s a constant battle to not explode the LoC. There’s always pressure away from “maintainability” and a “small elegant cohesive” codebase.


It is in media management. I cannot talk about the features in detail, but I would not be surprised if it can be done with half the line count.

What I was trying to say is that maintainability appears largely unaffected.

Doing manual QA testing and iterating on improvements still works great.

The question then is in which cases "small elegant cohesive" is worth it, when the implementation effort increases tenfold. For the product I am working on at home for 30h/week, I can confidently say it is not worth it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: