Live data from Hacker News

LLMs are eroding my software engineering career and I don't know what to do

human-in-the-loop.bearblog.dev

851–860 of 1001 posts

Re: LLMs are eroding my software engineering career and I don't know what to do

#851

Wut? I pilot LLMs all day but there's no way in hell I'd agree to be at the helm of a finance product. That first pillar is still there. Maybe the author isn't aware of the impact they have, but I know, with the evidence of reverted PRs, that when I step outside my area of deep knowledge I can no longer call BS on the agents. Our most capable agent, with access to the same kind of distributed systems the author talks…

Posting this under a burner so I don't dox myself: I work in FinTech on a regulated product. We have access to Mythos. Mythos identified part of our codebase that it confidently asserted was not complaint with a particular regulation and we were at grave risk by allowing it to operate the way it was. Except this was not the case, it had of course hallucinated what the regulation actually required (I know this because…

[flagged]

Re: LLMs are eroding my software engineering career and I don't know what to do

#852

My career path is suprisingly similar to the author's. Weirdly enough, what he takes as the first pillar to fall is the one I see most undamaged currently. LLMs routinely fail at our business specifics: Local tax regulations, particularities of the accounting process, specifics of our ledger implementations. They're great at refactoring, translating between languages, tracing bugs on existing code even, but there is…

> LLMs routinely fail at our business specifics: Local tax regulations, particularities of the accounting process, specifics of our ledger implementations. So there is a spectrum here, and i dont know what i dont know - meaning i can just be wrong. But we're both on that spectrum and are you sure its not a skill issue? All of the specifics you list seems so fundamental that in similar projects I've inserted them stra…

>If you boil it down to it, you're quite literally saying the problem is the LLMs dont have access to a bunch of facts.

Well yeah, And our problem with mortality is not having access to a bunch of medical facts :)

Kidding aside, it's a fair question. We have several problems with that approach:

One, today they miss X tomorrow Y. You can iteratively add information and get better, but everyone who's had to keep a large company's documentation updated and consistent knows how absolutely hard of a problem that is. Still, this is not the main issue.

Two, knowledge extraction is not clean. We face this daily. "There was no incident on may 12" could mean any of:

- "There was no incident on may 12"

- "There was an incident I was not aware of"

- "There was an incident, but I'm a contractor who has to pay if there's an incident so I'm not admitting shit"

- "There may have been an incident, who knows, I secretly told chatgpt to handle this task for me"

- "Something went wrong but I don't consider it an incident because that particular error has been popping up every wednesday since I joined the company and I was told to ignore it"

- "there was an incident when I touched something you told me not to touch so I will firmly deny there was an incident"

You won't get the LLM to navigate that human problem. You might think that's tech debt and dysfunctionality, but it is real life. It's the same problem as with self driving cars, it's semi easy until you introduce toddlers running after a ball in the middle of a road, drunk drivers and unfixed potholes.

Three, and this is the main issue, surfacing. Skills, agents, etc work for obvious connections like "I'm writing a test => we test with framework x in a style y". they do not work as well for indirect connections like: "If I correct the amount of these past payments' insterests, for a minority of them it might raise the total amount above a certain threshold where we were supposed to have required extra information due to money laundering regulations, and I need to contact legal to see what we do since it's not possible to request the extra info after the fact"

The problem is that the set of things to potentially surface is giant and LLM's fail miserably at connecting what to surface where. It's what we usually refer to as the "spidey sense"/"shitdar" of senior engs. LLMs might get better with time, but so far the ability isn't there.

Re: LLMs are eroding my software engineering career and I don't know what to do

#853
post #831
post #590

Earlier quoted context omitted.

Ha. I've worked in a fairly strongly regulated sector (energy, in the Netherlands), where I collaborated closely with our head of compliance, and she heavily over-interpreted the regulations while I often tried to find more pragmatic solutions. I think adherence to regulation and compliance is nothing to do with whether you're a SWE, a risk officer, or C-level, and everything to do with your own principles, ethics, p…

I've found two things to matter: 1. experience, i.e. knowing why and how a rule matters (in general, but also to auditors) 2. willingness to think If these aren't present, you get overly restrictive compliance that at the same time accomplishes nothing.

scruples are also often a surface of friction that get in the way of business objectives.

Re: LLMs are eroding my software engineering career and I don't know what to do

#854

Earlier quoted context omitted.

I do this several times per week. You can ask Claude to hunt down duplication, brittle scripty code, overly defensive fallbacks, and footguns.

It's kind of dumb that we have to do this as a separate process, which introduces even more churn and review burden, rather than having this out of the box in the code generation process.

But think of the profits for the AI companies!

Re: LLMs are eroding my software engineering career and I don't know what to do

#855

I’ve been using Claude Code with Opus 4.7; it’s not that the code it produces is wrong, it simply tends to write too much of it. In my opinion it’s still worth thinking about a particular feature and finding the best way to fit it into your code because Claude will often just pick a layer of the stack (maybe presentation), and jam it in there. A couple weeks later you need this data somewhere else and Claude can’t re…

I have also noticed the too much code issue. The open question for me is whether too much code is actually a problem. These tools are a fact of life now. If we can solve problems or debug faster, and the software is less buggy, than it's not too much lines of code, it's just right.

Meanwhile most of the software I use seems to become less reliable every month.

Re: LLMs are eroding my software engineering career and I don't know what to do

#856

I see many comments saying, "AI can't do X with 80-100% accuracy; therefore our professions are in good hands." While I don't want to sound overly pessimistic, the models are improving at a rapid rate. If asked ~3 years ago where the state of the models are today, it would sound like sci-fi if answered, "the models are creating full MVP apps in ~30 minutes with one prompt". The hurdles the models are facing now, like…

[flagged]

Naive bordering on the juvenile take on complex issues? Check.

Polarizing and unable to process nuance? Check.

Biased, arrogant and hypocritical? Check.

My god, you’re the perfect developer. You’ll fit right in. Have a seat.

Re: LLMs are eroding my software engineering career and I don't know what to do

#857

I've posted this before but worth posting again: I work in DevOps at a firm that has been very enthusiastic about using LLMs (in the good sense). The phases were basically: - try out having the LLM do "a lot" - now even more - now run multiple agents - back to single agents but have the agents build tools - tools that are deterministic AND usable by both the humans (EDIT: and the LLMs) The reasons: 1. Deterministic t…

LLMs, Jenkins for the entire software universe :-D

For those unaware, Jenkins (Hudson), is a CI server that supports all sorts of pipelines. Those pipelines can very easily be turned into huge balls of mud by putting logic in them. The proper way to do it is to put that logic into simple scripts and tools and have Jenkins just do high level orchestration.

Re: LLMs are eroding my software engineering career and I don't know what to do

#858
I don't care as much about LLMs deprecating my accumulated knowledge. After a quarter of a century in the industry I have plenty of stuff in my head of purely sentimental value.

But for me, the real catastrophe is that they took away all my motivation to learn which was the main work driver for me. Anything I can learn now, the models probably already know or will learn soon enough. Steering LLMs isn't anywhere near being a "deep" skill I'm used to having and it too is being eaten by the agentic tools faster than we learn it. The "make it good" button is coming. And I hate it.

Re: LLMs are eroding my software engineering career and I don't know what to do

#859

I see many comments saying, "AI can't do X with 80-100% accuracy; therefore our professions are in good hands." While I don't want to sound overly pessimistic, the models are improving at a rapid rate. If asked ~3 years ago where the state of the models are today, it would sound like sci-fi if answered, "the models are creating full MVP apps in ~30 minutes with one prompt". The hurdles the models are facing now, like…

[flagged]

Ad hominem arguments in every one of your comments.
Post reply on HN