Comment by jstummbillig
2 days ago
> 35 kLOC is quite a bit. I wonder how straightforward and maintainable this app ended up to be. This would require taking a look at the sources. While good Rails code tends to be very terse, frontend may be quite voluminous.
I think people will have to recalibrate on this. The LOCs do things that you otherwise would not do. Features and details that simply would not happen — because they are too code/time intensive for most projects. It just won't matter anymore.
> But why would non-technical people would even think in terms of log tailing and version control
They won't! They won't have to. The obvious good stuff that everyone thinks the AI tool should be able do, will just work, because the people building the tools, will mostly obviously focus on making them work.
That or we're completely ignoring principles like DRY and producing a head spinning amount of tech debt.
I can't really imagine producing that much code in that short amount of time and holding any amount of it in my head. I'd bet money there's code in there that does the same thing but different, leading to all kinds of little inconsistencies that make this code worthless in any serious context.
I’m an old school coder. I haven’t vibed. I’m guessing the “who is going to maintain this” could only be another tool similar to what built it. I can’t imagine trying to get my head around that much code in a timeframe acceptable to someone demanding product. So are we headed to a place where everything is written and maintained this way or a lucrative future of having to get these things to work properly.
Given amount of duplication and variation there is no way to guarantee any level of security in such codebase. The bright future ahead!