(no title)
have-a-break | 8 months ago
We as engineers have let the recruiters and VC funding brainwash us into lower salaries. Kind of looking forward to a rebound.
have-a-break | 8 months ago
We as engineers have let the recruiters and VC funding brainwash us into lower salaries. Kind of looking forward to a rebound.
rednafi|8 months ago
That said, once the project goes beyond a certain threshold, LLMs offer little more than a highly capable autocomplete. In larger codebases, the current context window is too small for the tools to even answer questions properly, let alone make any non-trivial changes.
Productivity starts going down once you try to use LLMs in a large codebase and expect them to be as helpful as they were in a smaller one. Often, these authoritative little shits will whirl you around in a doom loop and still won’t find any useful solution. And suddenly you find yourself having to clean up the mess.
I’d still say the productivity benefit is positive, but at the same time, the hype around these is bonkers. Employers are holding onto the hype cycle to bring down wages through FUD.
roncesvalles|8 months ago
Exactly this. I've really tried to find use for LLMs in my big tech company SWE job and I just can't. The context is just too large, and not just the code context. In the time that I can "explain" everything to the LLM, keep iterating until it spits out something semi-useful and massage that into something I can merge, I'd rather just do the whole thing myself.
But it's amazing for greenfield personal projects.
bluefirebrand|8 months ago
I find LLM autocomplete extremely annoying compared to traditional intellisense
It is wrong way more and I don't want multi-line autocomplete, it's too intrusive
casualscience|8 months ago
Llms are still a big speed boost there
JonChesterfield|8 months ago
9rx|8 months ago
Significantly so! But the thrill of the gamble keeps me coming back, sadly.