←back to thread

418 points floverfelt | 7 comments | | HN request time: 0.217s | source | bottom
Show context
jeppester ◴[] No.45057505[source]
In my company I feel that we getting totally overrun with code that's 90% good, 10% broken and almost exactly what was needed.

We are producing more code, but quality is definitely taking a hit now that no-one is able to keep up.

So instead of slowly inching towards the result we are getting 90% there in no time, and then spending lots and lots of time on getting to know the code and fixing and fine-tuning everything.

Maybe we ARE faster than before, but it wouldn't surprise me if the two approaches are closer than what one might think.

What bothers me the most is that I much prefer to build stuff rather than fixing code I'm not intimately familiar with.

replies(8): >>45057537 #>>45058508 #>>45061118 #>>45061272 #>>45061732 #>>45062347 #>>45065856 #>>45070745 #
1. whstl ◴[] No.45061272[source]
LLMs are amazing at producing boilerplate, which removes the incentive to get rid of it.

Boilerplate sucks to review. You just see a big mass of code and can't fully make sense of it when reviewing. Also, Github sucks for reviewing PRs with too many lines.

So junior/mid devs are just churning boilerplate-rich code and don't really learn.

The only outcome here is code quality is gonna go down very very fast.

replies(1): >>45061959 #
2. jstummbillig ◴[] No.45061959[source]
I envy the people working at mystical places where humans were on average writing code of high quality prior LLMs. I'll never know you now.
replies(3): >>45062509 #>>45062835 #>>45065358 #
3. actionfromafar ◴[] No.45062509[source]
Some of them will get hired to fix the oceans of boilerplate code.
4. jeltz ◴[] No.45062835[source]
I am working at one right now and I have worked at such in the past. One of the main tricks is to treat code reviews very seriously so people are not incentived to write lazy code. You need to build a cultire which cares about quality of both product and code. You also need decent developers, but not necessarily great developers.
replies(2): >>45062923 #>>45067203 #
5. raziel2p ◴[] No.45062923{3}[source]
It's very easy to go from what you're describing to a place hamstrung by nitpicking, though. The code review becomes more important than the code itself and appearances start mattering more than results.
6. jimbokun ◴[] No.45065358[source]
Did you make an effort to find those places and get them to hire you?
7. jstummbillig ◴[] No.45067203{3}[source]
Oh, I understand what you need to do. It's like losing weight. It's fairly simple.

And at the same time it's borderline impossible proven by the fact that people can't do it, even though everyone understands and roughly everyone agrees on how it works.

So the actual "trick" turns out to be understanding what keeps people from doing the necessary things that they all agree on are important – like treating code reviews very seriously. And getting that part right turns out to be fairly hard.