Since we introduced claude enterprise, number of unexpected bugs skyrocketed tremendously
this post was submitted on 15 Jul 2026
130 points (97.8% liked)
Programming
27704 readers
393 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
I, for one, am glad they are volunteering as guinea pigs in an experiment to see how long a popular project can survive LLM slop.
And if they harm javascript's popularity in the process and projects start to look elsewhere... that's an added benefit ;-)
The market can remain irrational longer then you can remain liquid as they say
There's no way a million lines of code were reviewed in 11 days. Not by a human at least.
It took the llm 11 days to generate the code
It doesn't seem to say anywhere anyone reviewed it in any time
Ew. Reviewing code is so 2024
What a waste of resources for an unreviewed and unmaintainable pile of junk.
I'll never update Bun again. And maybe I'll just revert back to Npm.
What a shit show.
Please save yourself from lunacy by using pnpm. You can always use shamefullyHoist to get the npm compatibility
Kelley is artisan, Sumner is a factory manager. Indeed they cannot be using same tools or work on the same floor or within the same building. Blind trust in AI (even with guardrails) is a recipe for disaster. They have jumped to Rust to add more guardrails to their AI lunacy but it won't hold for long. At this point there's no single human who actually knows or understands the code and AI code is proven to have durability issues at scale. So direct rewrite gives a quick boost as code is ported from somewhat reviewed base onto new platform, but as new code gets added this will dissipate. It sounds like Bun issue is systemic Zig Rust or Pixie dust won't fix it.
How much is one million lines of code?
If a senior engineer works in a well-defined, well-architected greenfield project, and does extensive tests, 10,000 lines of code written in one year are very productive. The amount of new code per person-year will be much less in larger projects - a good indicator is the line count and the estimated value of the Linux kernel (40 million lines in 2025, redeveloping it in 2011 would have already cost 2200 million Euros, which would pay e.g. 36000 person-years for mid-level German software developers, that would mean 1111 lines per person-year{actually about half of that because of the interim growth of line count in the meantime }- and most software projects can only dream about so much actual value.)
So, you can say 1,000,000 lines of code generated in 11 days are probably 100 person-years of technical debt.
One caveat: It is relatively simple to auto-translate code in restricted languages like Java, Python, or Rust to unrestricted languages like C or C++. In that case, enforced invariants (like "no use of freed memory" or "sharing data across threads xor mutation") become implicit, but verbatim translation is often possible.
The other direction will require a re-design..
you can't compare the tech debt because it's essentially a line by line translation from an existing codebase, not 1M brand new lines of code
that would mean 1111 lines per person-year
not sure if I understand correctly, but this sounds off
You can do the math yourself:
-
how many lines of code does the linux kernel have?
-
what is the estimated value of the kernel, which is the hypothetical cost to re-create it?
-
what do you think the seniority of a linux kernel developer is?
-
what annual salary do they make in the country which uses Linux most - the US?
-
now divide kernel value by annual salary to get man-years, and lines of code by man-years to get average lines of code per year
Result: Typing in code that somehow compiles was never the bottleneck