This weird trend reached an apex in a Feb 2026 OpenAI blog post [1], recently on the front page [2], which describes the process for building... something... written 100% by agents.<p>There is no description of what the thing is, no indication of what value it provides its users. The closest it gets is "the product has been used by hundreds of users internally, including daily internal power users".<p>But the fact that the thing has a million lines of code is repeated twice in the first few hundred words.<p>[1] <a href="https://openai.com/index/harness-engineering/" rel="nofollow">https://openai.com/index/harness-engineering/</a><p>[2] <a href="https://news.ycombinator.com/item?id=48416264">https://news.ycombinator.com/item?id=48416264</a>
> <i>"the product has been used by hundreds of users internally, including daily internal power users".</i><p>My guess is it’s an email filter.<p>> <i>million lines of code</i><p>> <i>written 100% by agents</i><p>Yeah, probably an email filter. Or maybe a JS menu for a departmental wiki that basically recreates jquery using MS JScript and transpiles it into JS 5.
> My guess is it’s an email filter.<p>It may also be an email generator.<p>The email filter team is trying to match the pace of innovation of the email generation team. At stakes is the ability for the employees to process the billions of mission-critical generated emails each of them receives each day.
Your hilariously specific hypotheses remind me of how little I know about technology.
The entire Linux kernel is about 40 million LoC, and only something like 16 million LoC after you remove drivers. I have a hard time imagining whatever OpenAI was talking about there having anywhere close to 6% as much utility as the Linux kernel, despite having 6% as many lines of code. And I have a hard time imagining it's anywhere close to maintainable, regardless of how powerful their LLMs might be.
To be fair, few things of any number of LOC have as much utility as the Linux kernel, and it's also a particularly dense example of code. There's plenty of other examples that have higher LOC / utility ratio without being vibe coded. For example, Google's monorepo famously has 2 billion LOC, which is a statistic I've heard long before LLM coding took over.
Clarification: Google claimed to have 2 billion lines of code in their repo ten years ago, and a commit rate of 50,000 changelists per day, both on exponential growth trends.
The Linux kernel is not in any way at top of big projects. A kernel, as the name suggests, deals with specific issues and tries to remain small.<p>The world’s biggest software is usually built over endless adapters of different data and a need to reconcile endless edge cases with laws, regulations and real world complexities.
Chrome has 50 mil LoC<p><a href="https://openhub.net/p/chrome/analyses/latest/languages_summary" rel="nofollow">https://openhub.net/p/chrome/analyses/latest/languages_summa...</a>
Sorry, was it not this?<p><a href="https://github.com/openai/symphony" rel="nofollow">https://github.com/openai/symphony</a>
The reality distortion field is strong around anthropic. Anthropic posts tons of equally bullshit blog posts, written entirely by AI, saying absolutely nothing, to the front page and they consistently average many hundreds of upvotes.
Oh god why did you make me read that.<p>>We intentionally chose this constraint so we would build what was necessary to increase engineering velocity by orders of magnitude<p>What kind of wanky bs is "engineering velocity". Maybe the post was written by AI?
I'm constantly thinking about that Microsoft guy who posted something like "we want 1 million LoC per engineer per month", which basically read as satire to most engineers I talked to, except apparently it was not satire at all, and indeed seemed to reflect the position of many CEOs etc when it comes to LLM code generation.<p>I do think that over the past few months, it <i>feels</i> like the hype around producing unmaintainable amounts of LoC has started dying down. More pragmatic and realistic takes are seemingly shared more openly, and are maybe even getting through to top leadership at some tech companies. Maybe not all is lost yet.
I once worked in a company where there was an 80% code coverage requirement. Some enterprising contractor had a script that generated a single file with its own covering test suite the size of which could be tuned to achieve 80% over the whole codebase. Mostly the code was untested.
It has been incredibly hilarious to watch the C-suites sudden realization that tokens COST MONEY and immediately revise their guidelines for how employees should use AI.<p>Like maybe having every engineer generate 1 million lines of code per month every month…with no thought to how those lines of code would make the company money…or how many tokens would be burned to accomplish this at what cost…wasn’t fully thought through.
1000000/25/8/60 = 83+ lines of code per minute.<p>100000 LOC per month /25 days per month /8 hours per day / 60 minutes per hour<p>That seems...problematic for anyone doing code reviews.
The word “slop” was a good choice to talk about the mass of code generated by AI. I think it resonates with non-tech people and it conveys disgust. It’s clear that we should avoid slop.<p>“Technical debt” never hooked management in the same way and we have found it hard to convince them that it needs to be addressed. Debt in general is something that can be a problem, but doesn’t need to be avoided or addressed until it is a problem so the can is kicked down the road.
Just fix technical debt over time as you work on other things and budget for it as you give estimates.<p>This approach has always worked for me. Non technical management will never understand technical debt and really shouldn’t need to.
To be fair, they are also different things, though there is certainly overlap...<p>To me, tech debt, captures the idea that we cut corners now to move faster, with the understanding that it will need to be "re-paid" and cleaned up later, otherwise we take on too much tech debt, and everyone knows too much debt is bad...<p>AI slop code means people feed their tasks to a model, trust it to drive the changes, they might do some cosmetic clean ups, then generate a 3 pager PR description they didn't even read themselves, then toss it over to the code reviewer, <i>let that chump figure out what the hell I was doing while I ship 3-4 more PRs</i>...
Technical debt is a indefinable quantity which makes it very prone to be abused to mean "I wish I could rewrite this in [insert some fashionable language, framework or coding style]".<p>AI slop is an easier concept to quantify. It's basically the code for which insufficient people in the organisation have a meaningful understanding of how it works or what it does.
> which basically read as satire to most engineers I talked to<p>Seemingly engineers get this wrong too. I'm reminded of when Cursor bragged about how many lines of code a group of agents could produce, with the underwhelming results of a barely working browser, when the same could be built with much less code.<p>But they highlighted the amount of code as they were proud over how much slop their constellation of agents had shit out, and these were supposedly engineers, really strange to see.
“Less is better” is sort of… the position of the engineer who enjoys the craft of programming, right? I don’t think this is universally believed.<p>And anyway, I’m pretty sure what people really mean by this “less is better” mantra is: the lowest amount of code that still accomplishes the goal and is still readable is preferred. Linux apparently has 40M lines of code, and I bet most of it is better than mine. Some things just take lots of code.<p>Which seems to leave room for these agent salesmen to pitch SLoC as a plus. We just have to believe those lines are all good ones. I that case, it would be impressive. I don’t believe it, but they are probably pitching to people who do.
> “Less is better” is sort of… the position of the engineer who enjoys the craft of programming, right?<p>No, it's the perspective of a programmer who wants the project to not be bogged down too much in technical debt so every change gets slower and slower to implement, as everything gets more intermingled. A clean design helps you move faster for a long time, compared to a design that is fast to implement but makes it hard to move forward properly in the future, without resorting to shortcuts and/or hacks.<p>> Some things just take lots of code.<p>True. Rich Hickey does a good job differentiating between what's complicated because the domain is complicated, VS what's complicated because the implementation just ended up that way, even though with some more thought and design, could have been made a lot simpler.
Less is better is the position of the engineer who has seen some shit and whose career lived to tell about it.
> <i>“Less is better” is sort of… the position of the engineer who enjoys the craft of programming, right? I don’t think this is universally believed.</i><p>I think it is (or should be) a goal & business-oriented concern as well, not just an engineer's who enjoys their craft.<p>More complex systems are worse than simpler systems (that accomplish the same), in cost, maintenance, fragility, ease of understanding, etc. Fewer moving parts usually result in higher reliability, fewer things that can break down or fail to interact properly, etc. That's a business concern too, not just engineering craftmanship or whatever. Business people <i>should care about this too</i>.<p>I don't think this is the same as bikeshedding over irrelevant details, something we software engineers are often prone to. Monstrous complexity does impact the business!
It's like we've all forgotten what <i>technical debt</i> means. We just say the phrase, but we have forgotten that it is analogous to actual debt. Every line of code produced should be treated as a liability to the company, like a bond they issued that they have to pay interest on in the future. You only take on the liability if it produces more business value than it costs to maintain. The goal is not to issue as many bonds as you possibly can.
> I do think that over the past few months, it feels like the hype around producing unmaintainable amounts of LoC has started dying down.<p>I wonder if a small part of this is more and more business and product people actually trying to incorporate AI into their daily workflows. I have seen this in both small companies I work for. People were very excited about getting Claude Cowork a couple of months ago, and while they use it daily, I would say they are rather underwhelmed compared to the magic they were expecting.
Complaints include the output being mediocre and verbose, it getting the most basic things wrong, hitting token limits all the time, and people going back to doing things themselves because it is faster.<p>Sure, there is some degree of holding it wrong in the beginning, but people are realizing that maybe, just maybe, there is still somewhat of a gap between what AI CEOs, LinkedIn grifters, and YouTube AI supplement peddlers claim and reality.
I suspect this is it. I'm 40, and the only tech person in my social circle. Many of my friends were all excited about using it for things like basic webdev and home networking. One shotting that type of stuff is very viable even if you don't know anything about the topic. Now that they are trying to use it for something they actually know about, suddenly it's unusable. It's a modification of Gell-Mann Amnesia.
I had an MoM at Stripe who pushed back on perf designations based on number of PRs.<p>I wish I were joking.<p>(The had never been an engineer.)
It's a signal. It's not a strong signal, and you certainly should not base your entire perf on it, but if the number is unusually high or low, it's a signal that could warrant further investigation.<p>(I once worked with an engineer that had two PRs, both fairly small bug fixes, in a given calendar year, and when I looked more carefully, they did not have any other obvious output or impact.)
Trying to parse your sentence, which is ambiguous...<p>You're saying that the manager-of-managers would argue that the number of PRs <i>should</i> affect perf ratings? Or the MoM would push back <i>against</i> the line managers who were giving ratings based on # of PRs?
I think the reliability struggles of Github may have helped with this
It's not unmaintainable if you have 1000 agents maintain it.
It is unmaintainable even if you spend 100k per month on tokens to have LLMs pretend they are maintaining it, if they slow down and make little ACTUAL progress. Sadly real progress is impossible to measure, if all you have is an overexcited """engineer""", a credit card, and so much cash spent you could hire all the best engineers you know and still have money for a porsche.
Well, software presumably has a goal of accomplishing something for some end-user, so the progress should be trivial to measure: are features/changes being completed?<p>The marketing ploys of OpenAI/Anthropic where agents build something that nobody uses might be hard to track given that there are zero users. But what about everyone using agents for real software? It's trivial to prove that agents make progress.
Yes that is the entire point. Measure features deployed in production and their value in gaining and retaining customers or users, cost reductions, reduced incidents and outages, etc.<p>Lines of code is completely irrelevant as a metric.
It's not unmaintainable if most of it is tests. Just have it write tests until it becomes safe for AI.
…and then the CEO sees the token bill…
All else being equal, and assuming you are building the right thing, being able to deliver more correct lines of code is a good thing. The question is how to do it reliably, given that a human cannot possibly read all of it. The answer seems to me to involve spot checks with proofs of correctness and statistical quality control, the latter being things that can be automated. One issue I see is that the models are constantly changing and are therefore not well understood statistically.
If you are generating that many lines of code it’s also almost impossible to tell if you’re building the right thing. You need to deploy each functional change and measure if it’s giving you the expected outcome, before moving onto the next thing.
>All else being equal, and assuming you are building the right thing, being able to deliver more correct lines of code is a good thing.<p>Why? If you can deliver the same thing in fewer correct lines of code wouldn't that be preferable? At a bare minimum if you're still insisting on using AI to slop out your project, having it do things in fewer lines of code means you can fit more into your LLM's context window.
> If you can deliver the same thing in fewer correct lines of code<p>it really depends on what you're doing. If your goal is "become interoperable with the N different and incompatible network protocols that people have devised for doing task X" I'd really like to know a solution that doesn't have at least some part of the amount of code that scales with N.<p>Example: consider <a href="https://bitfocus.io/connections" rel="nofollow">https://bitfocus.io/connections</a> which connects to 700 different things. Right now it's written with Node.JS, with one repo per connection (example: <a href="https://github.com/bitfocus/companion-module-meyersound-galaxy" rel="nofollow">https://github.com/bitfocus/companion-module-meyersound-gala...</a>). Let's say you want to make a similar product but that runs on ESP32 where performance is paramount so you need C++ or Rust. How do you do that without at least as many lines of code as the existing JS implementations for every system supported by Companion?
Without looking at the details, I expect that each network protocol has a checksum of some form, and there are likely a lot less than N different checksum algorithms. Similarly I expect several will have encryption - using one of a few standard algorithms (if any doesn't use a standard algorithm you have a strong case to say not supported). I also expect that there is a lot of protocol parsing - this can be done as custom hand coded for each, or using a parsing framework (and likely there are some places of generic code in between).
This is still not an argument for more lines of code. It demonstrates that lines of code are positively correlated with number of features, yes. But that's like saying the number of nails scales with the size of a house. More nails does not <i>create</i> more house.
Then you simply produce those fewer lines of code even faster. The question is, how fast are you delivering correct code?<p>Moreover, writing too terse code harms readability and maintainability. There is such a thing as irreducible complexity.
> I'm constantly thinking about that Microsoft guy who posted something like "we want 1 million LoC per engineer per month", which basically read as satire to most engineers I talked to<p>Did those engineers not actually read the complete tweet? Because it wasn't about "engineers should write 1M LOC per month of product code" it was "we want to scale automated porting of code to safe languages so that 1 engineer managing 1M LOC of automated conversion can work". Which doesn't seem like satire at all..? It just means "develop mostly reliable AI-driven refactoring tools with good guard rails". Which seems quite sensible, actually?
I don't care - porting the current architecture - with all the known I wish I had done this differently's - doesn't gain much. See some developers I've worked with who love Rust for "safety", even though they just put everything in unsafe at the first sign of trouble instead of thinking about how this should work safely.<p>Porting to a new language is easy, but does nothing useful. What we need is to fix the mistakes of the past so we can get to the future. We need to make acceptable performance.
> Because it wasn't about "engineers should write 1M LOC per month of product code" it was "we want to scale automated porting of code to safe languages so that 1 engineer managing 1M LOC of automated conversion can work".<p>Making a grand claim of a goal and not really having an explanation on how to achieve it isn't really much better. I could say "we want to scale food production so that one farmer could manage a million acres of corn a month", but that wouldn't really be sensible. A line of code is less work than an acre of corn of course, but I don't think it's at all apparent what upper bound for how much code is actually plausible for a single engineer to generate in a month and have any degree of confidence in. Given the absurd levels of hype around AI from non-engineering management in the past couple of years, it's not clear why the benefit of the doubt is earned here when there legitimate are managers and executives claiming pretty much exactly what you're claiming this guy wasn't.
Minor correction: LinkedIn, not twitter. <a href="https://www.linkedin.com/posts/galenh_principal-software-engineer-coreai-microsoft-activity-7407863239289729024-WTzf/" rel="nofollow">https://www.linkedin.com/posts/galenh_principal-software-eng...</a><p>> Because it wasn't about "engineers should write 1M LOC per month of product code" it was "we want to scale automated porting of code to safe languages so that 1 engineer managing 1M LOC of automated conversion can work"<p>These are one and the same. Whether it's ported code or not doesn't change that. The framing device also doesn't matter, because it's the exact "Oh it's our <i>goal</i>" shtick that executives use in the former's case.<p>"It's just a measure" doesn't cut it in a world where every single AI measure immediately gets turned into a target by executives greedy for efficiencies that don't exist.<p>EDIT:<p>Right, I forgot. This is HN where everyone is a galaxybrain and "Port a million lines of code per month" is a totally reasonable goal for a single individual.
I can easily game writing 1M LOC per month by having the LLM write code in more verbose ways, with useless indirections and abstractions thrown in for good measure. I could even ask claude to write code that does nothing but just takes up line.<p>In contrast, converting 1M LOC of code per month is a much more solid measure, as long as you measure LOC of the source, not the new code. Sure, in the short term you can pick the easy/verbose things to port, but it's hard to do sustainably. A 5M LOC code base would still be expected to be ported in 5 engineer months.<p>Granted, you can still rush the work, not test properly, neglect good planning and engineering. Ported lines of code should not be the only measure (just like with any other measure). But it's a much less problematic measure than <i>coding</i> 1M LOC
> Granted, you can still rush the work, not test properly, neglect good planning and engineering.<p>Which is the core point of my reply and not something to just be casually handwaved, thank you very much.
If everything in the initial code is 300% covered with excellently documented tests that should be minimally changed during transition (if transition don’t reveal any corner case tests were missing, maybe the transition is not such a bright move after all), that seems a possible thing to consider.<p>Otherwise it really sounds like a recipe for unnecessary huge risk with dubious expected positive outcome.<p>Not saying don’t have fun, but on the other side maybe not with the core product of you cash cow already?
> "we want to scale automated porting of code to safe languages so that 1 engineer managing 1M LOC of automated conversion can work". Which doesn't seem like satire at all..?<p>Because many programmers don't believe that'd work. See the reaction to Bun's porting to rust. (I bet Bun will work and prove those programmers wrong, but that's another story.)
> When a company says “AI made everyone more productive, so we need fewer people”, I want to see the evidence - and I don’t believe it exists today.<p>Because they're bullshitting and using AI as an excuse to correct from their covid era over-hiring while simultaneously making themselves look good to investors by showing they're embracing the hip new technologies to become a more streamlined and cost-efficient operation than ever.
It is endlessly... amusing (?) to me, that we as a community spent decades trying to make it clear that our productivity is not easily measured because what we're doing is complicated and long running, only for AI to come along and suddenly LoC, Nx multipliers, tickets / week etc are held up as useful if not objective measurements.<p>The reasons we rejected LoC and other measurements have not changed (broadly: code output isn't important, quality output is). AI has all the same problems people do. But for whatever reason we are throwing what we've learnt away. It's kind of embarrassing.
The non-technical people are in charge and they're not tethered to reality in the same way that engineers are. Objective reality will win in the end, but that doesn't prevent damage being done in the short term.
IDK, I do think a lot of it is LLMs enable people who were not in our community to come into it (in an eternal september kind of way) and they are going through all this from first principals and ignoring their elders, but I've also seen technical people suddenly measuring themselves this way. The most optimistic read of this is that they _feel_ productive, and that feels nice, and they want to share how that feels, and so they are reaching for these garbage metrics because they have nothing else.
> The most optimistic read of this is that they _feel_ productive<p>In addition to "feel productive", two other feels I think are flying under the radar:<p>1. You get a parasocial relationship with a "friend" (or at least conversation partner) who seems to "understand" you.<p>2. You get some form of gambling entertainment when you pull the lever and the output keeps landing on different sides of the jackpot you want.<p>While #2 has some overlap with classic creative struggle, I think it can at least be seen as a kind of junk-food verson, where the frequency is different and the health-promoting parts aren't present.
[dead]
Maybe a particular group of software engineer cultivated the need for careful measures. But the programming field never escaped the idea of simple metrics.<p>That's because you would always have loosely involved but aggressive and demanding bosses (there is unfortunately an economic value to the boss whose primary task is forcing more effort out of the employee and who doesn't help coordination or anything else). So at best you had two intersecting clouds of approaches with actual accomplishment intersecting with LoC and related measurements.<p>The thing AI is that it provides all the tools to satisfy that loosely involved but demanding boss. So suddenly you are going to have a larger demographic of people who like LoC and feature-additions as metrics 'cause now they are easy.
All that to shill slop machines so the billionaire class can throw people out on the street.
If your A+ senior developer spends 8 months working on a feature that ultimately doesn’t get shipped or a MVP that gets killed, then you wasted that A+ senior developer and their productivity was the same as the other two B+ engineers that also worked on the project. This is actually a very common issue and usually ignored when it comes to things like hiring or assigning resources to a project. AI won’t change that in a meaningful way, your team may just finish their tasks a lot faster but the bureaucratic layer above will likely remain the same, which will make any AI coding gains negligible. Companies would have to be rebuilt from the top down for AI and that’s very unlikely to happen.
I think engineers tend to over index on this kind of thing being "waste". You didn't waste that investment, you paid for the option to ship that feature or MVP and the research into the question of whether it made sense to ship it.
That's cool but don't get heart broken when engineers leave after repeatedly being told the thing they worked on for months wont ship because someone at the top said so.
Not really? If those are people I'm close with, I try to express this perspective to them in 1:1s that things that don't end up shipping are not a waste for the reasons I expressed here. And most of those people (because they are simpatico with me, which is why we're close) tend to see it the same way I do, and not leave because of this. And if they do leave for this reason, I conclude, well, they just weren't really aligned with me on this particular perspective. And that's a bummer, but not everyone is gonna see things the way I do.
put simpler, you learned what not to build.
It's definitely that, which is very valuable, but it's also the optionality value additionally. You had the <i>option</i> to launch the thing, which you wouldn't have had if you had never worked on it at all. It's notoriously difficult to properly value optionality, but it definitely has value, and often a lot of value.
Shouldn't companies figure this out before wasting tens of millions in budget + working hours? All I'm reading is that corporations are not taxed enough if they are okay with such opulent waste.
Story time. small business. less than 30 people.<p>ceo had invested £1 million to build a data analytics platform. "democratising data analytics" in a very specific domain. essentially, competing with someone like databricks in a niche. although they had never heard of databricks before i showed up. For that million pounds they got a job scheduler written in pure django with a halfway finished react frontend. the whole thing was constantly broken. there were multiple race conditions throughout the product.<p>the million pounds and then some was all spent before i even joined. <i>three years after i joined</i> i had fixed the worst of the problems.<p>i finally convinced the ceo they'd been doing the wrong thing all this time -- they should focus on analytics + specific domain consultancy services instead of software products.<p>the major failure was no-one ever moved on from idea V1. they never moved to idea V2. which meant they never got to idea V3. instead, everyone spent a hell of a lot of time talking about how great V1 was going to be, and how they planned to build V1 and what V1 would look like, check out this status update about our progress on V1, check out this mock up on what V1 is going to look like etc.<p>3 months after joining was the first time i mentioned apache airflow. they literally could have just stuck a nice frontend on top of it and written a backend data transfer library. job done. very cheap idea V1. the previous team of django developers could only see their trusty django hammer.<p>multiply the budget by 10x or more. exact same thing at some big corpo. it's just a bigger budget and more bullshit.
No. This is like saying "shouldn't scientists figure this out before wasting tons of money running experiments?".
Nobody can perfectly predict the future.
Knowing what to build (and that it hasn't already been built or bought elsewhere in the company) requires bits of information / person-to-person networking / visibility into the state of the company that not all managers or VPs have.<p>In fact, most people don't have that knowledge, because they're busy with existing or "local" problems , or because they didn't know to ask Davis the DBA or Kris the Kafka Cluster Manger or Alex from accounting if we have <resource> our team can plug into and use. "Oh, yeah, El has one under their desk they kick occasionally, ask them to hook you up!"<p>If you solve this problem in a turnkey way Fortune 500 companies will write you very large checks to help them prevent such duplicate waste, and will in turn become the 15th system they need to integrate....<p>That XKCD joke about "how 14 standards becomes 15 standards" also applies to the class of "one system to integrate with and report from all other systems"
> spends 8 months working on a feature<p>Are you sure those 8 months is not being spent on just “coding”? There’s design, product team input and iteration, etc. Where did you see that an A+ engineer goes into a cubicle and come X months after with an MVP in isolation?
Weird baseless push for AI on the end, with no reasoning, no goal, no claim of gain. "Just go and use AI, people, developers must adopt new things."<p>It's not the first article I've read recently that is an ad for AI after a short context pretending to criticize it, with nothing connecting them.
Oh come on, the value of AI > 0. That’s not a controversial take.
AI is the new cloud. There's no market for people or companies who aren't committed to it. If you're a dev who refuses to use AI, no company will hire you; and should a company decide not to use AI they will have a hard time retaining devs (and they will need more devs). Their investors and big-ticket customers will also think twice before signing off on major commitments.<p>So yes, use AI. Don't nitpick the costs and benefits. The world is headed this way; if you want to develop software for a living and afford to eat, you need to be too.
> and should a company decide not to use AI they will have a hard time retaining devs (and they will need more devs)<p>Need more devs? Why? If a company was being profitable just fine prio AI era, they will still be profitable if they decide not to use AI. Shipping crap faster is not a formula for success. Shipping quality faster? I prefer shipping quality at a good pace
It's much more than that. There's plenty of market for people and companies who don't specialise in cloud software. The market for programmers who don't use AI is going to be more like the market for programmers who don't use compilers.
> So yes, use AI. Don't nitpick the costs and benefits. The world is headed this way; if you want to develop software for a living and afford to eat, you need to be too.<p>It's really saddening to see software engineers throw out all critical thinking and innovation out the window to behave like sheep and follow the trend line. The industry was trailblazed by people that refused to do just that and the same is going to be true in the future.
Or, don’t. Do what you want, don’t listen to random people on the internet telling you what to do.
>The difference this time is pace: you could delay adopting “the cloud” for a couple of years and survive. With AI you might get a few months.<p>It is weird that the author seems to understand that the pro-AI claims made by AI companies about the product’s necessity are not falsifiable, but then backtracks with “woah woah woah but don’t think I’m anti-AI.”<p>How is the assertion above any more rigorous than the productivity claims the author is criticizing throughout the rest of the article? That you won’t “survive” if you don’t adopt AI within a few months?<p>It is not true when the AI CEO says it, and it is not true when the person calling BS on the AI CEO… for some reason also says it…
When the AI CEO says it, its because stock go brrr. I never believed that AI CEOs because they're making unverifiable claims that they never backed up, claiming you're firing people because of AI is so open for interpretation, and it shifts blame from you to the AI, reality is we should not blame AI for something a CEO did, you could have re-trained employees for AI, but you didn't why not? Maybe because it's not about AI is it?
He is talking about the cultural considerations of being hire-able. Not about productivity.
> It is not true when the AI CEO says it, and it is not true when the person calling BS on the AI CEO… for some reason also says it…<p>People do take into account the motivations behind what someone says and to me the motivations here seem different enough to make some difference here. The AI CEO has an obvious motivation to lie, but the person calling BS doesn't have such a clear motive...
><i>When a company says “AI made everyone more productive, so we need fewer people”,</i><p>They are implicitly saying that as a company, they don't want to be more productive. They want the same productivity by paying fewer more productive people.<p>Why is there an imbalance between what an employer gets paid for a unit of production and what an employee gets paid for a unit of production?
> Why is there an imbalance between what an employer gets paid for a unit of production and what an employee gets paid for a unit of production?<p>Because labor gets exploited to make the owners richer. That's the basic fact, even though the owners (as a class) have financed a lot of propaganda to justify and obscure it.
> They want the same productivity by paying fewer more productive people.<p>I believe you mean same output but fewer people? But by definition that would be higher company productivity, as the definition of productivity at the company and/or national level is the ratio of outputs to inputs. If you have fewer people but are getting the same output, then the productivity of the company (or nation) has improved.<p><i>If</i> you had fewer people but <i>the same productivity</i> then there would be no benefit to the company as the outputs would correspondingly be reduced (and it may actually be worse for the company if the company has any fixed costs).<p><a href="https://www.mckinsey.com/featured-insights/mckinsey-explainers/what-is-productivity" rel="nofollow">https://www.mckinsey.com/featured-insights/mckinsey-explaine...</a>
I don't see LOC as that different from number of hours in the office. They'd always say pre-pandemic "If they're not in the office, how will I know they're working?" Simple, use the output metrics that you use to evaluate all of your workers to see what they contribute to the business.
I kinda feel as if this was the money quote:<p><i>> If you got a free headcount increase essentially overnight, why wouldn’t you use it to deliver more value to your customers, faster?</i><p>That shows that, in reality, it's short-sighted profit-taking. Boss just wants another lambo in the garage, and doesn't really plan to be around, when it's time to pay the piper.
I largely think that we engineers are to blame for LoC being still perceived as an asset rather than a liability. We are proud of stuff we create, but it turns out that you can't describe how "big" something is without some metric, and so we fall back on the metric that is easiest to compute.<p>Suggestion: we should all shift our terminology, and in particular make heavy use of phrase "...and it cost N lines of code". And say what we spent those LoC on.<p>"I implemented new feature X, and it only cost 200 lines!"<p>"That bug was brutal to figure out, but in the end it only cost 6 lines of code."<p>"It was doing something in case X that it didn't do in case Y, and it turns out that the distinction wasn't even needed. So I fixed the problem and saved 20 lines of code at the same time!"<p>Lines of code <i>are</i> a price you pay. We don't go around bragging about how we spent $200 without any mention of what we purchased with that money. Why do we do that with LoC? "I had to pay an extra $200 because I signed up late" and "I only paid $200 for my hand-painted artisanal pottery lamp hanger. Factory-made ones cost upward of $1200 on Amazon!" are two very different statements, and map to exactly the same distinction in code.
More that LoC is a simple metric that has always been a problem.<p>Non-Functional requirements is a vestigial term from ‘function point analysis’ which is from the late 70s, and which also ended up being a proxy for LoC.<p>The entire industry is so focused on measuring now, and incentives are so skewed to short term that lagging indicators like maintainability are a non starter in many organizations that it will be challenging to fix this time.
This is already changing again now that CEOs have wised up to the fact that they're paying for code by the line but these lines don't translate to profit.
Not enough people read The Goal.<p>Ugh. Just imagine the following on a normal curve:<p>Pre-AI: The goal is to make more money.<p>With-AI: The goal is to ship more code.<p>Post-AI: The goal is to make more money.<p>Can't wait to see how we get there...
I think a better metric these days is what percentage of code is not reviewed / understood by humans. That is the real bottleneck. Until we can stop looking at the code, AI barely matters - you are just trading quality for quantity.<p>Thats why it is so amazing for speed runs and prototypes. Here it is legitimately > 10X faster.
You need to retrain managers from seeing a prototype and thinking "yep, ship it" and over to "okay, how do we build this properly?" And I don't think that's gonna happen.
It seems to naturally follow that a company that sells lines of code would want to measure success in lines of code.
The paradigm used to be create good enough abstractions you can express what you need in a few dozen lines or whatever. Those lines will be clearer and more precise than English for describing what it does.<p>I wonder if we'll ever get back to that? If it's still relevant?
We're still in the FA phase of FAFO when it comes to LLM code generation, aren't we?
If developers burn through thousands in AI tokens a day, does it really matter, and is it a good spend? Are the outputs actually checked for sanity, fitness, qa/qc, security etc. How much rework is coming out because of lack of validation, or too much automation in the soup.<p>The more I read, the more I feel that 1 dev, 1 ai agent with the dev as a gatekeeper is probably the most appropriate workflow. Where you now treat the single dev + ai as a team in terms of planning and cost analysis and you get about 1.2-1.3x the throughput compared to a traditional team of 3-5 devs with partial PM and partial QA where the Dev now needs to take on those roles too.<p>The output should include more/better testing, examples, demos etc... since the bus factor is now 1, but AI is expected to be able to do the heavy lift.
> Measuring programming progress by lines of code is like measuring aircraft building progress by weight.<p><a href="https://www.goodreads.com/quotes/536587-measuring-programming-progress-by-lines-of-code-is-like-measuring" rel="nofollow">https://www.goodreads.com/quotes/536587-measuring-programmin...</a>
Large enterprises class systems are notoriously difficult to work Ai. It’s the context window limitation. Assuming 10 tokens per LoC. The best models today cannot wrangle 100k distributed LOC across multiple repos. It’s great for building new and maintaining smallish codebases. All this code being written is fantastic, but maintaining them efficiently over the code lifecycle is tricky.
Not a better publicist, but:<p>A) a newly-receptive audience - engineers who have discovered that they very much enjoy and appreciate the tradeoff of proximity to the code for amplified velocity and impact, now that it's possible to achieve without being a manager of messy human teams.<p>B) an ecosystem in which it's grown nearly impossible to connect a functional description of something to how much bespoke construction and effort was involved, partially because of marketing and partially because of how much software already exists to be built on top of. It's impossible to tell from a few paragraphs of functional description whether something was built in a weekend or took a team 4 years to ship, so volume of code is the natural fallback for describing complexity.
It's dying down now because unlike before, companies are paying out the ass for those tokens, where many companies now have token budgets enforced rather than the previous tokenmaxxing.
LoC by itself is useless and so is AI LoC, it doesn't really show anything by itself.<p>But if you pair AI LoC in a range and also task completed in the same range and then compare that with historical data over a similar range without AI, then you have something tangible.<p>You also need to look at defect reports to understand the full picture of is AI being helpful.<p>So, we do need to measure AI LoC and AI PR counts, but we also need to make sure we are using other metrics to help paint the full picture.
It is pretty funny how this whole industry in a very short amount of time, with tons of experience and knowledge to lean on, reverted back to dubious measurements of productivity. If you track LoC and tokens used as productivity measurements, developers are going to max their LoC and token usage! Its so predictable that we have a Law named after this phenomenon! The fallout was so predictable I feel like I should have been positioning myself for all of the potential consulting work that's about to be needed.
When I read recent news on HN, I feel it is a fable about Goodhart's Law. The law says: 'When a measure becomes a target, it ceases to be a good measure.' The dog should wag its tail. But the tail is wagging the dog.
Reporting on percentage of AI generated lines of code is very different from total lines of code. Yes I know both of them are missing what's the value delivered, but the later assumes the value is the number of lines, while the former assumes value is at least the same but delivered faster.
My old CTO has a spiritual metric that always resonated with me: Revenue / Lines of Code. The higher the number the better.
>The difference this time is pace: you could delay adopting “the cloud” for a couple of years and survive. With AI you might get a few months.<p>I don't think so. Take a good company A (with a good product and a good pace of good features) of today. Take the extreme case they decide not to use AI at all. Well, they will still be shipping good features at their current pace.<p>No amount of AI will make a bad company ship a better product than A's. If any, bad/mediocre companies will be pushing crap faster than they did before, but that's it.<p>AI can make good companies better, but cannot make bad companies good. Why does company A need to worry about shitty companies using AI? Sure, other good competitors could be using AI, but all in all, shipping "faster" is not the "mark" of good quality
Yeah, that closing message was a little weird to me. I understand framing the article as "not anti-AI", especially if the author uses and enjoys the tools. But the end sounds like a call to blindly adopt the tools and figure out the justification later.
Yeah I think it also really depends on what your business is. Many or most of us here (and likely also the author) work in the kinds of tech-forward businesses where competition is fierce and velocity is essentially. But there are many many businesses, and also tons of public sector organizations, where this is not the case. Leadership in those organizations should probably be going a lot more slowly, waiting and seeing, letting all the fast movers fight it out through all this churn, and adopting only whatever eventually rises to the top.
Converting the production database to Prolog to ship LOC.
So what has actually shipped? I'm already using much many more AI-coded projects in my daily life than I was a few months ago.
I agree with the main point but this misses something crucial:<p>> why wouldn’t you use it to deliver more value to your customers, faster? That should show up as MAU, conversion, revenue<p>Most roadmaps are full of garbage and would be better off being deleted. You get very few truly useful new features in a year.<p>To paraphrase ESR: the value to your customers is in them being able to know that can rely on your product still operating next year, not in those 20 new features.<p>Or to think about it another way, maybe block will be better off with fewer developers, but only if they produce sufficiently FEWER features so that they’re forced to prioritize.
Confusing skeptic and sceptic will never not be funny to me (edit: I now live in shame)
Then I think you are the confused one, as they mean the same thing but one is US and one is UK+NZ+etc.: <a href="https://en.wiktionary.org/wiki/sceptic#English" rel="nofollow">https://en.wiktionary.org/wiki/sceptic#English</a>
I think you’re reading “sceptic” as “septic”. They are not the same word.
Damn it - well, I'll never live this one down, I'll learn to shut up next time
Nah, as long as you're good a sport about it, it's all good. In fact, it's refreshing to have someone make a mistake like that so confidently, and then own up to it immediately.
It shows good character to own your mistakes.
About as funny as “confusing” color and colour. Which is to say: not very.<p>Skeptic and sceptic are pronounced identically, because they are just different spelling of the same word.
Sure, live in shame, but don't let go of the humor in it all :)
Sceptic is the UK spelling of skeptic.<p>Maybe you've confused it with septic?
How do you mean? Guy was born and raised in New Zealand and is using British spelling. There is nothing confused or confusing about this.
beautifully put, AI is changing the way we make software but the way we measure productivity is still in our hands. L'chaim!
When will performance or lacks of bugs become a metric again?
Many mid size to large companies are hilariously inefficient and the executives have no idea how work actually gets done. This means you can (in theory) fire a decent percentage of your workforce without affecting your output. You can then claim they’ve been replaced by AI without anyone ever challenging that assertion. I’m not making a pro or anti AI claim here, just saying that you won’t know whether you were wrong about it until/unless things start to go really badly.
It’s worth looking at sectors where LLM code generation hasn’t been very visible, such as certification-accredited flight-control, braking, train-control, medical, or nuclear-control source code involving real-time embedded operating systems. This sector relies on assurance: deterministic scheduling requirements, detailed commit traceability, tool qualification, configuration management, independent verification, etc.<p>Since this is an area where failure can lead not to Instagram accounts getting hacked, but planes falling out of the sky and nuclear reactors spewing radioactive elements, it’s worth a close look. Some of the most visible companies in this sector include: QNX, Wind River, SYSGO, Lynx, Green Hills, Siemens Embedded, etc. None of them seem to have much if any adoption of LLMs for source code generation based on public statements.<p>Research in this area agrees with this view:<p>“In this paper, I have conducted a comparative analysis of the C++ code generated by popular LLMs including: OpenAI ChatGPT, Google Gemini, DeepSeek, Meta AI, and Microsoft Copilot for compliance with MISRA C++. The study revealed that none of the evaluated LLMs generated MISRA-compliant code despite clear prompts, with DeepSeek showing the fewest violations and Meta AI the most.”<p><a href="https://arxiv.org/abs/2506.23535" rel="nofollow">https://arxiv.org/abs/2506.23535</a>
This study showed that people writing computer games had little interest in productivity tools (because they are producing something that is really used). But people who produce things that not really used are obsessed with productivity:<p>> the perennially unprofitable venture-backed startup, for which faux productivity is connected to the generally immaterial nature of its high valuations, versus the game studio that lives and dies by the profitability of its products.<p>> In a sector of the economy where "it's not about how much you earn, but about how much you're worth," the labors of the companies whose workflows are built on the kinds of productivity apps that today comprise nearly 40 percent of Product Hunt's output are not actually directed at the creation of a thing, but at the appearance of the creation of a thing.<p>Maybe this is why Silicon Valley seems to have become obsessed with productivity and AI whereas the people in the industries you mention don't seem as excited. It's because they are actually making real things so they don't have to 'look busy' in order to justify themselves.<p><a href="https://components.news/the-gamer-and-the-nihilist/" rel="nofollow">https://components.news/the-gamer-and-the-nihilist/</a><p><a href="https://news.ycombinator.com/item?id=47235774">https://news.ycombinator.com/item?id=47235774</a>
I don't get how if productivity is barely moving, how a decrease in comprehension will improve anything.
The kloc fallacy never actually disappeared. Project and engineering managers got wise to the fact that it was only loosely correlated with shipping features, and stopped emphasizing it. Most everyone else has carried on silently believing it without really thinking about it. And of course engineers themselves have always believed it. How many times have you heard some guy talk about how he wrote 10kloc over the weekend as a brag?
So, how the comapny will be evaluating the students on what basis?
> But! Hold my beer… in February 2026 METR effectively walked it back : their follow-up estimates flipped to a speedup (with error bars wide enough to ride a Moto Guzzi, with panniers, through!), and they abandoned the study design entirely - because developers now refuse to work without AI, and can’t reliably self-report time on agentic work. Their latest position: AI probably speeds developers up in 2026, and we can no longer cleanly measure by how much.<p>This may be true, but they followed in May with this [0]:<p>> Importantly, survey results are not necessarily grounded in reality. There are reasons to be skeptical of people’s responses to counterfactual questions such as about AI’s effect on productivity — for instance, our study in early 2025 found that people overestimated AI’s effect on their time spent on tasks by 40 percentage points on average.<p>[0] <a href="https://metr.org/blog/2026-05-11-ai-usage-survey/#productivity-gains-over-time" rel="nofollow">https://metr.org/blog/2026-05-11-ai-usage-survey/#productivi...</a>
> But adoption is the starting line, not the scoreboard.<p>Yes yes, shout it from the rooftops! Over the next few years I think we're going to see that companies that get this point will keep doing meaningful things, and stand a chance of weathering this transition period.<p>I think we're going to see a bunch of companies that went all in on AI for AI's sake go under because they've lost their mission, lost their implementation, and won't have a way to get those back in a reasonable timeframe and at a reasonable cost.
I think this is important:<p>> <i>When a company says “AI made everyone more productive, so we need fewer people”, I want to see the evidence - and I don’t believe it exists today. Show me that x% of your workforce is genuinely idle (or even just underutilised) because the work can now be done by fewer people. Even then: I’ve never seen a product/SaaS company that didn’t have an endless roadmap. If you got a free headcount increase essentially overnight, why wouldn’t you use it to deliver more value to your customers, faster? That should show up as MAU, conversion, revenue.</i><p>I see some people calling for calm instead of AI panic by invoking Jevons Paradox. But at least within these companies there's no good evidence of Jevons in action, is there? The roadmap is endless, but when employees are perceived to be idle they get fired instead of being assigned more (or more ambitious) tasks.<p>To be fair, one could claim Jevons applies to "the market" at large, but at least we can say the evidence from tech companies is <i>not encouraging</i>. So maybe it is, indeed, time to panic a bit?<p>> <i>Choosing the layoff instead tells me the productivity claim is doing PR work for a decision that was already made for other reasons (over-hiring, investor pressure, take your pick).</i><p>Yup, I think we all suspect this. Though it's probably a mix of the two factors.
> So maybe it is, indeed, time to panic a bit?<p>Anyone relying on a steady paycheck from an employer should panic a bit all the time, because nothing can save them from bad management. The reference to Jevons Paradox doesn't say anything about individual managers responding correctly. If 30% of managers screw up, that's a lot of collateral damage.<p>Now to respond to your actual point, I don't think software developers should panic. Even if pure software engineering gets hit hard, I'm having trouble imagining a scenario where years of software development skills plus knowledge in a specific domain isn't a good thing for current software developers. This is unlike what happened with international trade, where you had 60-year old textile workers losing their jobs, no alternative jobs, and no policy being offered to compensate them for the effects of trade.
Yes, it's the "market" argument that I find compelling. That is, not jevons within firms, but rather across them.<p>Is it true that the evidence in tech so far is not encouraging? I was pretty worried about the job market a year or so ago, but it seems pretty good for experienced people at the moment, no? (I do have big concerns about the entry level pipeline though!)
Writing. Code. Is. No. Longer. The. Bottleneck.<p>Deciding what to build. Reviewing Code. And testing code. Are the new bottleneck.<p>So of course we don't see massive productivity gains. Because these parts of the SCLC were always bottlenecked but their capacity matched the throughout. We fired all the dedicated QAs years ago. Sr+ engineers that do all the code review are limited.<p>Teams have not re-organized to match the new code-input velocity.<p>Engineers don't want to do QA because it's "beneath them".. and most engineers don't like performing or are not Sr enough to do extensive or high quality code review.
Was writing code ever the bottleneck for anyone other than raw juniors and non-programmers?
There is some truth to this, but in practice I'm finding that yes, removing the writing code bottleneck has improved throughput quite a bit.<p>My day (excluding the huge amounts of communication overhead) used to progress as a serial operation of: 1. Write some code for one thing, 2. Self review of that thing, 3. Review other peoples' work, 4. Respond to review comments, 5. Get things merged, 6. Back to 1.<p>Now I have more of a tendency to queue up work on a few things at once, and then the serial steps are the self reviews and reviews of other peoples' work, and some of the review commentary back and forth (though I can automate some of this in parallel as well).<p>The upshot is that I'm more working in batches now than in serial, which I really do find to be more efficient.<p>It's not that it has removed <i>all</i> the bottlenecks at all, but no longer being required to focus all my attention for periods of time on physically typing code has removed <i>one</i> important bottleneck, and has changed, and I would say, improved, my workflow significantly.
One thing the AI tools have taught me is that it hasn't been my personal bottleneck for at least a very long time. It's made that part faster for me, and that allows me to take bigger bites at the apple each iteration, but it's not meaningfully speeding me up in the way people claim.
I disagree that it's not meaningfully speeding <i>me</i> up. I'm definitely doing a lot more, and more quickly. But the benefit is definitely smaller at the team and organization level, because we still have all the same serialization points - review, validation, decision making - downstream of my work.
I realized after I posted that it didn't quite capture what I meant. For instance if I'm able to do a more complex piece of work all at once in about the same amount of time as it'd previously take me to do a simpler piece of work, than that is a speedup. And that's what I am able to realize.<p>But what's not as much the case is that if I did an A/B test on the same task that I'd be massively sped up because so much of my day to day work are the things you mentioned as being serialization points. The time I take to figure out what needs doing, what the best approach would be, making sure it was actually the right thing to have done in the first place once I'm done, all that stuff. I use AI assistance for those tasks too but it's not the same effect as when I just hand off the pure implementation phases. So it winds up being "faster" and you'll have to pry my AI assist tools out of my cold, dead fingers - but if I'm being honest with myself by *that* metric it's not a huge gain.
Depends on your company. I'd say very rarely, and never for long.
This. Isn't. News.<p>People. Already. Know. This.<p>It hasn't been the bottleneck for decades for the majority of products.
Code has never been the bottleneck, and it was always an illusion that it was. I mean, programmers on the whole are a group that jerks around probably 95% of their time (this isn't an attack as I've spent my career as a software developer, and this included countless hours on Reddit, HN, Slashdot, and so on).
> Engineers don't want to do QA because it's "beneath them"..<p>I’m fine with doing QA. But the fact is that it’s not how management measure my productivity. Spending hours doing QA looks like wasting time to them because it’s not an activity they track. They track my tickets so any hours not spent on them is literally harmful.<p>Also there’s the fact that you can’t QA your own output. It’s easy to overlook mistakes and defects.<p>> and most engineers don't like performing or are not Sr enough to do extensive or high quality code review.<p>Just like QA, code review takes time. It’s easy to justify that time when the submitter has put in the effort to ensure that the contribution is worthwhile. Or can explain the design clearly. Not so much when it’s slop thrown over the wall.<p>> Deciding what to build. Reviewing Code. And testing code. Are the new bottleneck.<p>None of those are truly bottleneck. Deciding what to build is obvious: Something that solve a user problem. Reviewing code is easy when the intent of the code is clear (with additional prose if needs be). Testing code is equally easy and should already be automated.<p>The one slow activity has always been about designing the solution. And it has no relation to code. It’s mostly deep thinking and research. I do it on the sofa or in front of a whiteboard. If I’m typing, I already have a solution in mind.
'something that solves enough users problems it's worth it to implement it' rather, and I think it is often difficult to judge how much engineering time to spend on user issues.<p>I'm currently working in an internal team, so I value cost savings estimation, but even before prioritising was also a bottleneck (although a small one compared to architecture and design)
How do you get to discuss without going to the article directly
I don't know about anyone else, but for me, even though the AI writes a lot of code, the vast majority of that code tends to be... tests. Same with my coworkers.<p>This morning I reviewed a 1,200 LoC PR. Pretty large by pre-AI standards. But most of it was tests. Before AI, it would be a lot smaller, but only because the PR author wouldn't be nearly as diligent with test coverage as AI tends to be.<p>And to preempt some common rebuttals:<p>1. I always read the tests to make sure they are meaningful, and rules and subagent review routines in place to make sure stuff like "assert 1 == 1" or "Process.sleep(5000)" never make it in.<p>2. Tests do add a maintenance burden as well, but I find that it's pretty easy to refactor and condense tests.
> "Augment surveyed 219 engineering leaders and asked them to define “AI-native engineering” . They got 219 different answers."<p>I mean, if you give 219 people a free text box and ask them to explain anything, you're extremely unlikely to get the exact same answer twice...
> I think every engineer should be using AI daily.<p>Why?
Please read the full paragraph for the answer instead of cherry picking a quote for a knee-jerk reaction:<p>> Be curious, try the new tools, test the latest models. To not do so is silly.
> [...]
> you could delay adopting “the cloud” for a couple of years and survive. With AI you might get a few months. The way we work has already changed, and it’s not changing back as far as I can tell.
> you could delay adopting “the cloud” for a couple of years and survive. With AI you might get a few months.<p>I really dislike these claims that act like they know the future of engineering, that they’ve been let in on some enlightenment that we haven’t been. What’s going to happen in a few months? Is Sam Altman going to nuke my house from orbit? Or is it because my CTO is going to fire me for not using AI? If it’s the latter, that’s not a curiosity problem, that’s a “there’s a gun to my head” problem.
It seems to be based on some idea that there's no way you can be productive enough without AI. But I've yet to see any companies really shipping meaningful software at some unprecedented speed that was not possible pre-AI. Instead, I see a lot of half baked features and buggy apps. I am not convinced that those that choose to either NOT use AI or use it more sparingly / judiciously (my preference), are somehow going to be "left in the dust".
I read the entire paragraph, and the entire article. Nothing in there explained to me why every engineer should be using AI every day.
Because I don't think that's the point of the article, which is just a commentary about how AI labs are marketing the effectiveness of their services by using terms like "8x more code per quarter" like that's an obvious good thing (which it isn't).<p>If you want a more in depth explanation, go look for interviews with devs who were already super-productive before LLMs and now came around to using them everyday.
If you read the paragraph, then why did you just ask "why?" instead of expressing your opinion about the explanation given in that paragraph?
Because it's fun. And why shouldn't we be into incremental automation?<p>I still write code manually to keep my trad-coding skills from withering away, but using AI without a doubt has allowed me to better test my existing apps. Create playwright automations I would've never had the time for. Allowed me to search through docs many times faster. And it just making programming more fun when I do use it for more challenging problems, and I actually get something working at the end of the day.
We need a Slop Audit methodology.<p>That is why I have created one (Open Honest Slop Audit).
I guess nobody cares anymore that AI is built on one of the largest thefts in history.
Another writer, back in February[1], noted "Every major tech CEO is now competing on what percentage of their code is written by AI"<p>1 <a href="https://www.thepragmaticcto.com/p/lines-of-code-are-back-and-its-worse" rel="nofollow">https://www.thepragmaticcto.com/p/lines-of-code-are-back-and...</a>
I'm reminded of my first tech job about 25 years that had some not very technical manager who had a technical toady write up a script to check lines of code added as a productivity measure. I was in big trouble because it didn't account for lines removed or modified, only new lines added. The copy paste guy was praised of course for how productive he was for.<p>Funny how AI is continuing the same story of non/semi technical busy bodies with their dumb bullshit.
To play devil's advocate for a moment (although I hate it): LoC often actually means NIH... but NIH suddenly has a pretty big proponent in the form of resistance to supply-chain attacks.<p>Basically the choices are:<p>1. Roll your own<p>2. Lockfile your deps for too long<p>3. Chase the bleeding edge for every dependency<p>The first is security-through-obscurity because DIY libs will have bugs and vulns but they won't be well-known. The second means missing known vulnerabilities. The third means supply-chain risk.<p>The rash of attacks and the ease of LLM-powered roll-your-own has shifted the risk-reward calculus towards 1.<p>But I hate it. This is the further Peter Pan never-gonna-grow-up of our industry that we cannot develop solid best-practice tools and must churn endlessly.
Amateurs. Using LLMs merelly to generate code. pfft... so 2026....<p>A few of my workflows now are: Use an LLM to generate code that generates code.<p>"Second Order AI Software Engineering(TM)"
Another AI slop article urging me to use AI on the orange AI fanboy site which has guidelines against AI slop comments, but AI slop submissions, that's just fine I reckon... Screenshot since the share button demands I have some social media login.<p><a href="https://imgur.com/a/UW15xVE" rel="nofollow">https://imgur.com/a/UW15xVE</a>
"As someone who spends a lot of time writing x86_64 Assembly and optimizing pure-JAX code for TPU clusters, this recent obsession with LLM-generated 'Lines of Code' metrics feels like a massive step backwards.
In High-Performance Computing (and especially things like quantum simulation, which I work on), the entire goal is reducing complexity and overhead. The magic of frameworks like JAX/XLA isn't how many lines of code you write, but how elegantly a few purely functional lines can compile down to highly parallelized hardware instructions.
If an LLM writes 100,000 lines of boilerplate for a project, someone eventually has to maintain, debug, and pay for the compute to execute that bloat. The real value of AI in engineering shouldn't be churning out a million lines of CRUD per month; it should be helping us build better differentiable systems, grokking complex mathematical landscapes, or spotting inefficiencies in low-level execution.
We spent decades learning that Goodhart's Law applies heavily to software engineering (more code != better software). It’s strange seeing leadership forget that just because the code is now generated by an agent."
[flagged]
[flagged]
The thing LOC measures best is how much code someone now has to read, understand, and keep alive. That number going up is a cost, not an output.<p>I spend a lot of my time taking over codebases other people left behind, and the AI-heavy ones have a recognizable shape: lots of plausible-looking code, thin tests, and nobody who can tell you why a given abstraction exists. Writing was never the hard part. Deciding what not to build, and being able to delete it confidently later, is the part that does not get faster with a model.<p>What did get faster for me is reading and reverse-engineering unfamiliar code - which is a little ironic, since the same tools are now producing more of the unfamiliar code that needs reverse-engineering in the first place.
[dead]
[dead]
Bragging about an AI agent generating a million lines of code is exactly like bragging about an automated factory generating a million tons of airplane weight. It completely misses the point of engineering. The bottleneck in software development hasn't been "typing speed" for a very long time; it's domain understanding, system design, and long-term maintenance.<p>Every line of code an LLM instantly spits out is a line a human engineer will eventually have to read, understand, debug, and migrate when the underlying business logic changes. The "better publicist" might be successfully selling these generation metrics to executives, but it's the actual engineering teams who are going to be paying the maintenance tax on all this auto-generated sprawl for the next decade.
[dead]