Did delivering quality really get easier? I'm certainly not seeing it in the software I use. Delivering scale doesn't mean the mission was executed well.

▲

axegon_ 6 hours ago | parent | next [-]

Judging from everyone I know, it will take people a lot of time to learn and accept a lesson from decades ago(one from before some of us were even born and I'm in my mid 30's): lines of code is a shit metric. Sloppers tend to believe that something seemingly working = production ready = good execution. And the metric, of course, is lines of code or "tokens". Until then, the list on this website will keep growing exponentially.

▲

gavmor 6 hours ago | parent [-]

Does it seem like even senior developers are forgetting this axiom? Or do we feel as though it's been obviated by LLM grokking swaths of text for us?

TBH I'm so arrogant, I always suspect there's redundant nonsense in any code module I haven't myself inspected. LLM code is no different.

▲

ambicapter 4 hours ago | parent | next [-]

> I always suspect there's redundant nonsense in any code module I haven't myself inspected.

I don't think this is arrogance in the sense that it's probably correct. It is however pretty easy to take that line of thinking into an arrogant attitude though, which is the real issue.

▲

axegon_ 5 hours ago | parent | prev [-]

Seniors are no different and that infuriates me even more. The few times I felt lazy and let an AI do a simple function for me, all hell broke loose. I'm starting to think that many people were never that senior to begin with: Writing the code accounts for very little of what development requires and is often the easy part. Understanding the problem and finding the sweet spot/optimal compromise, edge cases and how you can break it is what has always been difficult. Seeing github explode with slop and github(microsoft/openai) themselves push even harder should be a wake up call for anyone that understands what development is: not writing the code but having someone else go through it, analyze it, understand the problem you are trying to solve and why you made the decisions that you made - that pretty much always takes a lot more time than writing the actual code. And then I see someone push 20 commits in a day, each being 5000 lines, jam packed with emojis and other slop and tell me that they carefully reviewed all of them? Yeah, that's bullshit, mate.

	▲	gavmor 4 hours ago \| parent \| next [-]
		I'm easily pushing 20 commits a day, but I won't pretend to have reviewed it all, let alone carefully. What I did was design it all carefully. But, for some projects, yes—I still do line-by-line code review with a colleague. Then again, a lot of my efforts are explicit refactor aimed at reducing LOC and tidying the codebase with, eg DRY. > The few times I felt lazy and let an AI do a simple function for me, all hell broke loose. This is confusing, because LLMs are more than capable of implementing "a simple function." How did you spec it out?
	▲	ambicapter 4 hours ago \| parent \| prev [-]
		I once worked at a fairly large corp that considered itself tech-forward (it was a retail ecommerce company), and at one point they just decided to demote all engineers one level because they somehow finally realized that everyone they had been calling "Senior" were definitely not at that level.

▲

5 hours ago | parent | prev [-]

[deleted]