HN user

vova4kin

2 karma

Founder-engineer at VeViDi. 17+ years on Ruby on Rails. I ship V1s with founders and take over live Rails apps that lost their team. React / React Native on the front, AI-amplified delivery by default. https://vevidi.com

Posts0
Comments1
View on HN
No posts found.

The thing LOC measures best is how much code someone now has to read, understand, and keep alive. That number going up is a cost, not an output.

I spend a lot of my time taking over codebases other people left behind, and the AI-heavy ones have a recognizable shape: lots of plausible-looking code, thin tests, and nobody who can tell you why a given abstraction exists. Writing was never the hard part. Deciding what not to build, and being able to delete it confidently later, is the part that does not get faster with a model.

What did get faster for me is reading and reverse-engineering unfamiliar code - which is a little ironic, since the same tools are now producing more of the unfamiliar code that needs reverse-engineering in the first place.