[dreadnip]

I guess the main takeaway is that you don’t care about the quality of the generated code. The end result is all that matters.

If I ask it to “add drag & drop”, I already know in my mind what the correct code should look like, because I’ve implemented it many times in the past. LLMs just never deliver the -code- that I want. The end result might look ok and the drag & drop will work, but the code will be atrocious and on first glance I can pick out 10-20 mistakes that I’ll have to ask it to fix. And even if I ask for a fix, I’ll never get the same code quality as hand written code. And how can I push this kind of sub-par code to an employer’s repo when I know that I can (and should) write better quality code myself. This is what I’m being paid for right?

[thunky]

> This is what I’m being paid for right?

That's a good question. Because developers can sometimes have a bit of an unhealthy love affair with their own code.

Does your employee actually care as much about code quality as much as you do?

They would probably ask what is the downside of accepting this lower quality code, given the upside you presented:

> The end result might look ok and the drag & drop will work

Which you did quickly, saving them money (in theory).

[jama211]

Well said.

[jama211]

No, you’re being paid to deliver the product to the _company’s_ chosen standards, not yours. And in my experience, fast and cheap and cheerful is often exactly what they want. They’ll have changed their minds next week and want it all ripped out for something else anyway.

[martinald]

Exactly. _So much_ software dev is "throwaway" in my experience. Of course some isn't. Landing pages, A/B tests, even a lot of feature work is very speculative and gets put in the trash.

I do wonder if this is why there is such a gulf in LLM experience. If you're doing hardcore huge scale distributed systems then I can (maybe?) see why you'd think it is useless. However, that is very niche imo and most software dev work is some level (unfortunately) of virtually throwaway code. Of course, not all is - of all the ideas and experiments, some percentage is hopefully very successful and can be polished.

[jama211]

Indeed. And you get some engineers who only want to code perfect bespoke code all the time and sometimes that’s useful and sometimes it’s not. It depends on the requirements of the client, just as it would in any other trade. We need to be flexible to both the clients time and money budget, and also make code that suits the criticality of the task at hand. If you can’t lower your standards to fit a use case, I think it’s actually a bad thing.