2 ms·
Seems to be a frequently occurring issue, most (good) software engineers know that LOC basically means nothing, if anything, less LOC is a better goal over more
by embedding-shape 4mo ago
Seems to be a frequently occurring issue, most (good) software engineers know that LOC basically means nothing, if anything, less LOC is a better goal over more LOC, if you absolutely have to have a goal. As soon as people/companies starts bragging about how many LOC they can ship, you need to start being very suspicious, mostly because they just admitted to not actually understand software engineering at all.
Cursor did something similar months ago, bragging about producing millions of LOC while what they actually made barely worked and could have been built with an order of magnitude less LOC: https://emsh.cat/en/one-human-one-agent-one-browser/ https://emsh.cat/en/one-human-one-agent-one-browser/ (https://news.ycombinator.com/item?id=46779522 https://news.ycombinator.com/item?id=46779522 | 324 points | 5 months ago | 156 comments)
What I don't understand, isn't there a single engineer working with these people who ask them what the fuck they're doing, before they hit that publish button? Or is there just such a constant pressure to publish anything that quality just simply doesn't matter at all to these people?
- ChrisMarshallNY 4mo ago> 169 server requests for various assets totaling 6.42 megabytes in size. Ahh … remember the good ol’ days, when we were forced to cap our Web pages at 32K? I have found similar issues with LLM-generated code. Lots of code … lots of issues. Just yesterday, I went through a whole bunch of LLM-generated code, and switched the threading model. It sped up my code significantly, and the jetsam crashes stopped immediately. Until I used LLM code, my apps had never jetsam-crashed before. First time for everything, I guess.
- cindyllm 4mo ago[dead]
- filmax777 4mo ago[flagged]