Live data from Hacker News

The recurring dream of replacing developers

caimito.net

501–510 of 535 posts

Re: The recurring dream of replacing developers

#501

Earlier quoted context omitted.

> If there is “a lot of evidence of the opposite,” the minimum requirement is to name one metric, one study, or one observable trend. You didn’t. You just asserted it and moved on, which is not how serious disagreement works. I treated it with the amount of seriousness it deserves, and provided exactly as much evidence as you did lol. It's on you to prove your statement, not on me to disprove you. Also, you still hav…

What you’re doing here is interesting: you’re flattening everything into “we already had tools” because admitting this is different forces you to ask which parts of your own day are actually irreplaceable. So instead of engaging the claim about leverage, you retreat to credential checks and nostalgia for scaffolding scripts from 2012. Also, saying “this has been automated for decades” is only persuasive if those auto…

Was that statement wrong? It sounds like I accurately clocked your level of expertise lol

And sure it did. We don't have test engineers or QA nearly as much as we used to, and a lot of IT work is automated, too.

Do you think we sit around, artisinally crafting code the slow way, or something?

Re: The recurring dream of replacing developers

#502

Earlier quoted context omitted.

> What is happening now. What the trendlines look like. What follows if those trendlines continue. Output per developer is rising. Time from idea to implementation is collapsing. Junior and mid level work is disappearing first. Teams are shipping with fewer people. These are not hypotheticals. My dude, I just want to point out that there is no evidence of any of this, and a lot of evidence of the opposite. > If you w…

“There is no evidence” is not skepticism. It’s abdication. It’s what people say when they want the implications to go away without engaging with anything concrete. If there is “a lot of evidence of the opposite,” the minimum requirement is to name one metric, one study, or one observable trend. You didn’t. You just asserted it and moved on, which is not how serious disagreement works. “You first, lol” isn’t a rebutta…

Is it just me or does anyone else get strong LLM vibes from the way this is written?

Re: The recurring dream of replacing developers

#503

Earlier quoted context omitted.

[flagged]

> What a nihilistic perspective and empty life. Equally nihilistic are owners, managers, and leaders who think they will replace developers with LLMs. Why care about, support, defend, or help such people? Why would I do that?

I think you missed my point.

If you "quiet quit" you're still working for someone you hate. They still own you.

Instead, you could ACTUAL QUIT and start a business. Then you work for yourself, who you hopefully don't hate as much, and you have the power to define how things are done. So if you think developers shouldn't be replaced by LLMs or whatever, then you can... not do that. I have zero doubt in my mind that that will be a niche somewhere in the global economy for many years to come.

Also you might make a lot of money. Make enough and you're basically free from all these assholes. It doesn't actually take a ton of money when you own 100%. You pretty quickly get to a point where you can start telling off any wanker you want to, but you don't even feel the need, you are your own boss, so you just walk away from them and deal with whoever you want to deal with instead.

Trust me, speaking from experience, this is 1,000,000% better than "quiet quitting" which is pretty much remaining a corporate serf, just the most useless and pussy one in somebody else's room. Of course it's harder, most people who try it fail, real economics, real laws and real people will call you out pretty fast if you don't do things that people other than you think are valuable!

Re: The recurring dream of replacing developers

#504

Earlier quoted context omitted.

> Experienced developers know what subsets of tests are critical, avoiding much work. And, they do know this for the programs written by other experienced developers, because they know where to expect "linearity" and were to expect steps in the output function. (Testing 0, 1, 127, 128, 255, is important, 89 and 90 likely not, unless that's part of the domain knowledge) This is not necessarily correct for statisticall…

That depends a bit on whether you view and use unit-tests for a) Testing that the spec is implemented correctly, OR b) As the Spec itself, or part of it. I know people have different views on this, but if unit-tests are not the spec, or part of it, then we must formalize the spec in some other way. If the Spec is not written in some formal way then I don't think we can automatically verify whether the implementation…

> then we must formalize the spec in some other way.

For most projects, the spec is formalized in formal natural language (like any other spec in other professions) and that is mostly fine.

If you want your unit tests to be the spec, as I wrote in https://news.ycombinator.com/item?id=46667964, there would be quite A LOT of them needed. I rather learn to write proofs, then try to exhaustively list all possible combinations of a (near) infinite number of input/output combinations. Unit-tests are simply the wrong tool, because they imply taking excerpts from the library of all possible books. I don't think that is what people mean with e.g. TDD.

What the cartoon is about is that any formal(-enough) way to describe program behaviour will just be yet another programming tool/language. If you have some novel way of program specification, someone will write a compiler and then we might use it, but it will still be programming and LLMs ain't that.

Re: The recurring dream of replacing developers

#505
post #53

I've watched this pattern play out in systems administration over two decades. The pitch is always the same: higher abstractions will democratise specialist work. SREs are "fundamentally different" from sysadmins, Kubernetes "abstracts away complexity." In practice, I see expensive reinvention. Developers debug database corruption after pod restarts without understanding filesystem semantics. They recreate monitoring…

Where have you worked? I have seen this mentality among the smartest most accomplished people I've come across who do things like debug kernel issues at Google Cloud. Yes, those people need to really know fundamentals. 90% of people building whatever junk their company needs does not. I learned this lesson the hard way after working at both large and tiny companies. Its the people that remain in the bubble of places…

Excel is the largest development platform because it's installed on (pretty much) every corporate PC by default, without having to ask Legal, Security, Finance or IT for approval. If we count Google Sheets as "Excel", the people who don't have access to it are a rounding error, if that.

BUT

With the arrival of Agentic AI, I've literally seen complete non-coders (copywriter, marketing artist, and a Designer) whip up tooling for themselves that saves them literal days of work every week.

Things that would've been a Big Project in the company, requiring the aforementioned holy quadruple's approval along with tying up precious dev + project management hours.

In the end they're "just" simple tools, simulating or simplifying different processes, but in a way they specifically need it done. All built from scratch in the time it would've taken us to have the requisite meetings for writing the spec for the application and allocating the resources needed - "We have time for this on our team backlock in about 6 months..."

None of them are perfect code, some of them are downright horrible if you look under the hood. But on the other hand they run fully locally, don't touch any external APIs, they just work with the data already on their laptops, but more efficiently than the commercial tools (or Excel).

Zapier, N8N and the like _kinda_ gave people this power, by combining different APIs into workflows. But I personally haven't seen this kind of results from them.

Re: The recurring dream of replacing developers

#506
post #92

Earlier quoted context omitted.

> The reality is that costs are being reduced by replacing US teams with offshore teams. Hailing from an outsourcing destination I need to ask: to where specifically? We've been laid off all the same. Me and my team spent the second half of 2025 working half time because that's the proposition we were given. What is this fabled place with an apparent abundance of highly skilled developers? India? They don't make on a…

One of my consulting customers has been half India, half not for a decade. There is a real push over the last year to wind down the not India half and shift to mostly India. India based folks cost 50-75% less. I realize that quality India hires would be closer to US rates, but management is ignoring that aspect.

Ah, the circle of outsourcing.

If they're lucky they'll find one solid worker who's going to watch everyone else's hands. I've had one criminally underpaid unofficial[0] tech lead like that. He was herding a team of 11, where like four people at most really cared about the outcome of this project.

[0] Because otherwise a raise would be in order. Can't have that.

Re: The recurring dream of replacing developers

#507

Earlier quoted context omitted.

What you’re doing here is interesting: you’re flattening everything into “we already had tools” because admitting this is different forces you to ask which parts of your own day are actually irreplaceable. So instead of engaging the claim about leverage, you retreat to credential checks and nostalgia for scaffolding scripts from 2012. Also, saying “this has been automated for decades” is only persuasive if those auto…

Was that statement wrong? It sounds like I accurately clocked your level of expertise lol And sure it did. We don't have test engineers or QA nearly as much as we used to, and a lot of IT work is automated, too. Do you think we sit around, artisinally crafting code the slow way, or something?

lol. It was not only wrong. It was wildly wrong. Your tone reeks with pride and entitlement. You’re one of those engineers who thinks he’s so great and a step above everyone else who is a non-swe engineer.

Personally I think being a swe is easy. It’s one of the easiest “engineering” skills you can learn hence why you have tons of people learning by themselves or from boot camps while other engineering fields require much more rigor and training to be successful. There’s no bootcamp to be a rocket engineer and that’s literally the difference.

The confidence you have here and how completely off base you are with your intuition on who is just evidence for how wrong you are everywhere else. You should take that to heart. Everything we are talking about is speculation, but your idiotic statements about me is on the ground evidence for how wrong you can be. Why would anyone trust your speculation about AI by how wildly wrong you are “clocking” me in.

> Do you think we sit around, artisinally crafting code the slow way, or something?

This statement is just dripping with raw arrogance. It’s insane, it just shows you think you’re better than everyone because you’re a swe. Let me get one thing straight, I’m a swe with tons of experience (likely more than you) and I’m proud of my technical knowledge and depth, but do I think that other “non swes” just look at us as if we are artisans? That’s some next level narcissism. It’s a fucking job role bro, we’re not “artisans” and nobody thinks of us that way, get off your high horse.

Also wtf do you mean by the “slow” way? Do you have communication issues? Not only will a non swe not understand you but even a swe doesn’t have a clue what the “slow” way means.

>We don't have test engineers or QA nearly as much as we used to, and a lot of IT work is automated, too.

Oh like automated testing or infra as code?? Ooooh such a great engineer you are for knowing these unknowable things that any idiot can learn. Thanks for letting me know a lot of IT work is “automated.” This area is one of the most mundane areas of software engineering, a bunch of rote procedures and best practices.

Also your “my dude” comments everywhere make you look not as smart as you probably think you look. Just some advice for you.

Good day to you sir.

Re: The recurring dream of replacing developers

#508

Earlier quoted context omitted.

Which is why I fire the quiet quitters on the spot

I am so appreciative of the employment protection laws we have in Europe so I don't have to deal with managers like you.

Yeah but you are paid less than half for a reason

Re: The recurring dream of replacing developers

#509
post #332

Earlier quoted context omitted.

>Wait, so we can infer the future from “trendlines”, but not from past events? Either past events are part of a macro trend, and are valuable data points, or the micro data points you choose to focus on are unreliable as well. Talk about selection bias… If past events can be dismissed as “noise,” then so can selectively chosen counterexamples. Either historical outcomes are legitimate inputs into a broader signal, or…

Respectfully, you seem to love the sound of your writing so much you forget what you are arguing about. The topic (at least for the rest of the people in this thread) seems to be whether AI assistance can truly eliminate programmers. There is one painfully obvious, undeniable historical trend: making programmer work easier increases the number of programmers. I would argue a modern developer is 1000x more effective t…

There is no respectful way of telling someone they like the sound of their own voice. Let’s be real, you were objectively and deliberately disrespectful. Own it if you are going to break the rules of conduct. I hate this sneaky shit. Also I’m not off topic, you’re just missing the point.

I responded to another person in this thread and it’s the same response I would throw at you. You can read that as well.

Your “historical trend” is just applying an analogy and thinking that an analogy can take the place of reasoning. There are about a thousand examples of careers where automation technology increased the need of human operators and thousands of examples where automation eliminated human operators. Take pilots for example. Automation didn’t lower the need for pilots. Take intellisense and autocomplete… That didn’t lower the demand for programmers.

But then take a look at Waymo. You have to be next level stupid to think that ok, cruise control in cars raised automation but didn’t lower the demand for drivers… Therefore all car related businesses including Waymo will always need physical drivers.

As anyone is aware… this idea of using analogy as reasoning fails here. Waymo needs zero physical drivers thanks to automation. There is zero demand here and your methodology of reasoning fails.

Analogies are a form of manipulation. They only help allow you to elucidate and understand things via some thread of connection. You understand A therefore understanding A can help you understand B. But you can’t use analogies as the basis for forecasting or reasoning because although A can be similar to B, A is not in actuality B.

For AI coders it’s the same thing. You just need to use your common sense rather than rely on some inaccurate crutch of analogies and hoping everything will play out in the same way.

If AI becomes as good and as intelligent as a human swe than your job is going out the fucking window and replaced by a single Prompter. That’s common sense.

Look at the actual trendline of the actual topic: AI taking over our jobs and not automation in other sectors of engineering or other types of automation in software. What happened with AI in the last decade? We went from zero to movies, music and coding. What does your common sense tell you the next decade will bring?

If the improvement of AI from the last decade keeps going or keeps accelerating, the conclusion is obvious.

Sometimes the delusion a lot of swes have is jarring. Like literally if AGI existed thousands of jobs will be displaced. That’s common sense, but you still see tons of people clinging to some irrelevant analogy as if that exact analogy will play out against common sense.

Re: The recurring dream of replacing developers

#510

Earlier quoted context omitted.

>Wait, so we can infer the future from “trendlines”, but not from past events? Either past events are part of a macro trend, and are valuable data points, or the micro data points you choose to focus on are unreliable as well. Talk about selection bias… If past events can be dismissed as “noise,” then so can selectively chosen counterexamples. Either historical outcomes are legitimate inputs into a broader signal, or…

> The trendline is clear. Just as early aviation was dangerous but steadily improved, this technology is getting better month by month. I'm yet to be convinced of this. I keep hearing it, but every time I look at the results they're basically garbage. I think LLMs are useful tools, but I haven't seen anything convincing that they will be able to replace even junior developers any time soon.

Look at the past decade. Zero AI to AI that codes and makes movies in an inferior way when matched with humans.

What does common sense tell you the next decade will bring? Does the trendline predict flat lining that LLMs or AI in general won’t improve? Or will the trendline continue like most trendlines typically trend on doing? What is the most logical conclusion?

Post reply on HN