> is about a year old now, so it should be in prime shape

A 1yo project may be in good shape if written by just one dev, maybe a few. But if you have many devs, I can guarantee it will be messy and buggy. If anything, at 1yo it is probably still full of bugs because not enough time has elapsed for people to run into them.

▲

mattmanser 7 hours ago | parent [-]

It's only 510k LoC, at ~100 lines of code a day for a year, this code base would take 23 engineers a year to write. That's for 220 working days in somewhere civilized.

And I'm sure we all know that when working on a greenfield project you can produce a lot more LoC per day than maintaining a legacy one.

Given that vibe code is significantly more verbose, you're probably talking about ~15 engineers worth of code?

I know that's all silly numbers, but this is just attempting to give people some context here, this isn't a massive code base. I've not read a lot of it, so maybe it's better than the verbose code I see Claude put out sometimes.

▲

lelanthran an hour ago | parent | next [-]

> It's only 510k LoC, at ~100 lines of code a day for a year, this code base would take 23 engineers a year to write.

Correction: a code base of 500kLoC would take 23 engineers a year to write. There is no indication that the functionality needed in a TUI app that does what this app does needs 500kLoC.

▲

cududa 6 hours ago | parent | prev [-]

When you say it’s not a massive codebase, I’m curious, what are you comparing it to?

	▲	kordlessagain 36 minutes ago \| parent \| next [-]
		Splunk.
	▲	mattmanser 5 hours ago \| parent \| prev [-]
		The previous poster was making out that in a year the code base would be a mess if people had done it. This is a two-pizza team sized project, so it's not a project that the code quality would inevitably spiral out of control due to communication problems. A single senior architect COULD have kept the code quality under control.