跳到正文
Hacker News (official RSS)(reddit.com)·· 13 天前品質評分43

Reddit 討論 AI 全面寫程式一年後,團隊逐漸失去理解程式碼的能力

A year after the 100% AI mandate nobody understands our code

重點導讀

Reddit 的 r/ClaudeCode 有使用者分享,公司推行「所有工作都透過 AI 助理」一年後,程式碼庫膨脹、團隊難以理解程式運作,管理層開始要求工程師重新多自行撰寫程式。

AI 伴隨問答

自備 Key 深度分析

針對這篇報導有疑問?可直接點選快捷問題或向 AI 追問背景脈絡與技術細節:

正文

# Reddit - The heart of the internet
Skip to main content

Open menu Open navigation[](https://www.reddit.com/)Go to Reddit Home

r/ClaudeCode

Sign UpSign up for RedditLog InLog in to Reddit

Expand user menu Open settings menu

Image 1 Go to ClaudeCode

r/ClaudeCode•3d ago

u/gato5fication

A year after the 100% AI mandate nobody understands our code

Help/Question

A year ago leadership told us everything goes through agents now. Hand written code needed a reason. It felt great for about 6 months, we shipped more than we ever had.

Now the codebase is around 3x the size it was and nobody can explain how most of it works. The agents struggle too, they keep re-implementing helpers that already exist somewhere else because there are 4 versions of everything.

The part that actually hurts is who is left. The two people who used to read every PR and push back left in the spring, one quit, one was "restructured".

coderabbit still comments on every PR, but there's nobody left who can tell if a comment matters or not, so people just resolve them all.

This month management started quietly asking us to "write more of it ourselves" again. Except half of us haven't written anything non trivial in a year and it shows. I spent 2 days on something I would have done in an afternoon in 2024.

Not sure what I want from posting this.

Is anyone else at the point where the mandate is being walked back, and how did you get the understanding back?

Read more

Share

Image 2: u/MetaforDevelopers avatarMetaforDevelopers•Ad

Long agent runs going off the rails? Muse Spark holds context through each step.

Learn More

dev.meta.ai

Image 3: Thumbnail image: Long agent runs going off the rails? Muse Spark holds context through each step.

Image 4: u/sapient_artifice avataru/sapient_artifice•Ad

You're paying $20/month to Claude. $20 to ChatGPT. Both log everything. Both forget context. Both own your data. One free app. Every model. Your machine. Nothing logged. You've been doing this wrong the whole time.

  • Image 5: Claude + GPT + local. Free.
  • Image 6: Your data stays. So does your money.
  • Image 7: Switch models mid-sentence. Free.
  • Image 8: Every model. One app. Free.
  • Image 9: Mage Lab. Local. Free. Your data stays with you.

magelab.ai

Download

Image 10: u/franciska-fyi avataru/franciska-fyi•Ad

Your agent wrote 4,000 lines before lunch. You're still reviewing yesterday's. In Delta, review the reasoning behind every change, with the agent there to answer for it.

Download

delta.dev

Image 11: Clickable image which will reveal the video player: Your agent wrote 4,000 lines before lunch. You're still reviewing yesterday's. In Delta, review the reasoning behind every change, with the agent there to answer for it.

Collapse video player

Sort by:

Best

Open comment sort options

  • Best
  • Top
  • New
  • Controversial
  • Old
  • Q&A

Comments Section

Image 12: u/AutoModerator avatar

AutoModerator

•3d ago

Moderator Announcement Read More »

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

_I am a bot, and this action was performed automatically. Please__contact the moderators of this subreddit__if you have any questions or concerns._

Reply Share

Image 13: u/EugenPenguin avatar

EugenPenguin

•3d ago

Refactor using agents

Reply Share

Image 14: u/orbital_trace avatar

orbital_trace

•3d ago

Image 15: Profile Badge for the Achievement Top 1% CommenterTop 1% Commenter

we'll never get paid to write code again unfortunately. But we will get paid to understand it, make the agents evolve it, and keep it secure.

Reply Share

more replies

more replies

more replies

more replies

more replies

more replies

Image 16: u/s0ftware-dev avatar

s0ftware-dev

•3d ago

You’re not gonna get any sympathy here as this sub is fully of people who have bet their life on LLMs writing everything. But I do resonate with your experience. It gets to a point where there is so much slop that it’s better to just treat the project as a black box and continue dumping slop into it.

The project will continue to get more and more bloated until the token cost per change is extortionate and the understanding of the codebase is so diluted that you won’t even be able the guide the agent. You will get bugs in edge case that you didn’t even know existed and relatively small changes before such as dependency upgrades become major tasks.

Reply Share

more replies

more replies

more replies

[](https://www.reddit.com/user/nesh34/)

nesh34

•3d ago

There is one solution to this problem, and that's to slow down.

To accept that productivity can increase but it can't be 3x or higher, it can maybe be +50% productivity sustainably.

Most businesses can afford to go slower to be sustainable.

Do that, retain expertise and then it'll be great. Push everyone really hard and it'll be a disaster.

Reply Share

[](https://www.reddit.com/user/This-City-7536/)

This-City-7536

•2d ago

Can you tell my boss that thanks

Reply Share

more reply

more reply

more reply

more replies

more replies

more replies

[](https://www.reddit.com/user/raichulolz/)

raichulolz

•2d ago

That’s kind of what I’d expect happen. Leadership only cares about the NOW, nobody seems to be worrying about a few months from now or what’s gonna happen when shit hits the fan a year from now and an agent can’t fix it...

Don’t get me wrong I use Claude a lot but at the end of the day we have a responsibility to understand and have ownership of the code for this very reason. I’ve pushed back massively against a lot of the AI reviews to make sure people still understand our codebase and to limit recklessness.

Comparing my team to a separate team that’s completely AI pilled, we deliver more sustainable and stable software.

Before anyone comments and disagrees with that I said, this is my own experience delivering large scale systems. I don’t really understand how anyone can just completely detach themselves from their work and let an agent deliver everything.

It’s just unsustainable to me. Just like this post suggests. At the end of the day, if you don’t understand what you’ve added to the codebase, you are adding technical debt and you will eventually not understand how to fix an issue.

Reply Share

more replies

more replies

more replies

Image 17: u/snoopy_bg avatar

snoopy_bg

•2d ago

There will be many bankruptcies in the IT sector due to reckless integration of AI and honestly this is what they deserve.

Reply Share

more replies

more replies

more replies

Image 18: u/Prestigious_Luck1062 avatar

Prestigious_Luck1062

•3d ago• Edited 2d ago

A concern I have is, what if, AI companies are running at a loss?

What if they need to increase the pricing so they are profitable? (or at least lose less)

What if that means plans increase 500%, and api costs 25%?

Alot of companies have made, and are actively making decisions based on the pricing we have now as being long term stable and viable. Core and key staff have been let go, you can just go back.

EDIT: I meant to say "you can't just go back".

Reply Share

more replies

more replies

more replies

Image 19: u/orbital_trace avatar

BorysBe

•3d ago

Pre-AI era we had the same problems, no accountability just like now with the agents.

This is either a very small piece of software or everyone here seems to work on NASA projects. 95% of software is poorly written, not documented or difficult to maintain if John who wrote most of the code is on Holiday.

Also, what is the "wider context" mentioned here and where is this documented? Or still in people heads?

Reply Share

more replies

more replies

more replies

Image 20: u/EugenPenguin avatar

KellysTribe

•3d ago

yeah, I don't entirely get this. Sure it's easy for shit to fall apart but that was true with humans too - now it can just happen much faster. You say it is reimplementing helpers again bc they are in 4 different places...then give it the instruction to "search for existing functionality before implementing a new function" and "find duplicate code and refactor" (it takes about an additional 4 or 5 lines to tell it to orchestrate the changes and so on but you get the idea). I feel like this is either generated bait, or just a lack of problem solving.

Reply Share

more replies

more replies

more replies

Image 21: u/betaphreak avatar

betaphreak

•3d ago

You don't maintain any specifications/business requirements in the repo itself? That's the only way I found you can manage repos at ~500k lines of code

Reply Share

more replies

more replies

more replies

[](https://www.reddit.com/user/No-Afternoon-4057/)

No-Afternoon-4057

•2d ago

Not sure what you want either, but agents rewriting multiple helpers is definately bad AI architecture, lack of documentation, RAG, DRY directives ...so on and so forth.

My codebase has about 600.000 lines of code, with about 40 - 50% of them being documentation...not even a single function is duplicated anymore (and yes, i had plenty of number formatters and such duplicated before).

Reply Share

more replies

more replies

more replies

[](https://www.reddit.com/user/4ngryMo/)

4ngryMo

•3d ago

Most systems need a rewrite after a decade of constant development, especially, if the teams working on it rotate. If AI can do it 5x - 10x faster, you need a rewrite that much more often.

If we concede writing code to an LLM, maybe it’s time to look at new language or paradigms.

Reply Share

more replies

more replies

more replies

Image 22: u/EugenPenguin avatar

CranberryStock7148

•2d ago

I don't understand this at all. This literally makes no sense to me.

A major part of using AI is to better organize and document the code base. The idea is that all of the knowledge of the code base now lives in the documentation. And everything is cleanly, structured in a kind of hierarchical format. CLAUDE.md points to the documentation index, and this way Claude is able to pretty much instantly understand how anything and everything works.

I hate to use this phrase, but it sounds like you guys have been "doing it wrong". It's fine to use AI for working on individual features in isolation, especially at first when you're just starting to adopt it.

But the solution now isn't to drop AI. It's to use Claude to audit the entire code base and start to write up hierarchical documentation on all of it that is perfectly up-to-date and correct.

And then to have Claude start refactoring. Have a conversation with it about how the architecture can be improved and how redundant parts can be removed so that it follows modern coding and architecture standards. Including creating all of the unit tests necessary to ensure that refactoring doesn't break anything.

This is all extremely easy. I find it unfortunate and baffling that there are companies that are not doing this. Your entire repository or repository is need to be architected and documented in a way that Claude always knows exactly where everything lives at all times. Then, basically all of the problems you are describing simply go away.

Remember that Claude isn't just for writing code. It's also for understanding codebases.

Reply Share

Image 23: u/EugenPenguin avatar

belowaverageint

•2d ago• Edited 2d ago

It actually makes perfect sense. OP's company determined its priority was to ship as fast as possible and to not worry about code quality. The outcome was as expected. Now this has caught up with them and they've realized that code quality matters. However it seems like the management is detached and has unrealistic expectations.

This has happened at many companies that think AI is magic. Why wouldn't you use magic if it's available for $50/month?

Reply Share

more replies

more replies

more replies

more replies

more replies

more replies

[](https://www.reddit.com/user/shoogliestpeg/)

shoogliestpeg

•22h ago

This was expected. The people who can't code mandated that the technical specialists work against their own best practice in the hopes of replacing you with LLMs

Union up if you can.

Reply Share

more reply

more reply

more reply

[](https://www.reddit.com/user/hellocppdotdev/)

hellocppdotdev

•3d ago

They just vibe coding at scale. That's 100% not the way to build real world software.

Reply Share

more replies

more replies

more replies

[](https://www.reddit.com/user/Comprehensive_Heat25/)

Comprehensive_Heat25

•1d ago

I 100% thought this was satire when I first started reading. Anyway it sounds like the people who make decisions don’t understand how these processes work. Color me shocked. Use a capability registry and architecture decision records log.

Reply Share

Image 24: u/orbital_trace avatar

Sorry-Programmer9826

•3d ago

Strongly agree with this. Agents create code really really fast and produce 90% good code with 10% madness. If you're not weeding out the madness as you go the next tasks starts with slightly mad code and makes it a little madder. So the first agent PR feels like magic, as does the 30th. But by the time you get to the 100th you've lost control and it's madness built on top of madness.

I hand write very little of my code, but it's really important to remain in control and understand (at a high level) what it's doing

Reply Share

more replies

more replies

more replies

Image 25: u/Crazy_Ruin_4383 avatar

Crazy_Ruin_4383

•2d ago

The code mess is by design, now it can only be supported by ai

Reply Share

more reply

more reply

more reply

[](https://www.reddit.com/user/Technical-Athlete-9/)

Technical-Athlete-9

•2d ago

Agentic development is a new dogma. It reminds me of agile. You can document how some of the practices are hurting projects all you want, but execs want to believe in the free money they were sold ever so badly.

Fighting it isn’t how I’m going to spend my time. I’m going to work on improving processes with the dogma. And this time I think it’s really pointless to fight it, because (a) the agents are rapidly improving and (b) I figure over 50% of software engineering jobs will be cut within 5 years. Won’t matter how good you are, it will be damn hard to find work that won’t churn you out every couple of years.

At any rate, the code will be shite and there will be days where nobody knows how to fix problems by hand. So you’ll likely be piling agentic fixes on agentic messes.

Reply Share

more replies

more replies

more replies

[](https://www.reddit.com/user/TattooedBrogrammer/)

TattooedBrogrammer

•2d ago

We’re 100% AI shop, I do some studying on system design, and now what I do is ask Claude to investigate a sub system or path and build out a document explanation with flow diagrams of just that section and I can often point out arrows to areas that don’t make sense or multiple paths made for the same flow through that and high level tell it how I want it to be structured and if does a good job of fixing it. Also I often ship logs and a shadow in v1, where it runs beside the current system and logs what happened and what the new system would have done, then have Claude review the logs after a week and workflow the new system vs old and I can often see if there were any edge cases I would have missed. It’s not the same as coding but in finding this method is improving our code that’s been ravaged from a year of fast prs only AI reviewed.

Reply Share

more replies

more replies

more replies

Image 26: u/orbital_trace avatar

EvenGodsForget

•2d ago• Edited 2d ago

I’m honestly not shocked that this is happening, but I’m amazed to see it getting so much traction on the ‘coding is solved’ subreddit. Well done on presenting this in a reasonable and pragmatic way.

We need more skilled developers speaking from experience about the long term consequences of throwing away oversight and expertise. These tools can be great assistants but they sacrifice sustainability for speed, as do so many other technologies we use.

Reply Share

more replies

more replies

more replies

[](https://www.reddit.com/user/Barbanks/)

Barbanks

•2d ago

You need to set up plugins, agents, skills and reference files to put guidelines and guardrails up for the A.I. I.E. context engineering and use of context primitives. Use the PROSE methodology.

The problem you’re seeing is that likely no one is using the same agents or there’s too much flexibility in what an agent can/can’t do. You can only blame so much on hallucinations.

If you all agree on a programming standard, architecture, patterns etc… then you should be setting up agents to hook into that.

I did all of this and while I haven’t read the code in over 1 year it takes me less than 10 minutes to wrap my head around entire systems. It’s because the patterns are being adhered to. And when they’re not you just point it back to the source context architecture and it fixes it.

What you’re seeing is akin to bringing on a team of junior engineers who have never worked on a team together. They will introduce 4 different architectures and varying styles. The difference now is it’s all automated and at hyper speed. So something you may catch 6 months down the road before it’s a problem is introduced in 30 minutes.

Reply Share

more reply

more reply

more reply

People also ask about section

People also ask about

Discussion on AI code mandates in ClaudeCode

Companies implementing AI code mandates, especially with tools like Claude Code, often face challenges like code bloat and maintainability issues, leading to debates about productivity versus code quality.

Challenges of AI Code Mandates

  • Codebase Bloat and Lack of Understanding: Mandating AI for all code can triple codebase size and make it difficult for human developers to understand how most of it works. "Now the codebase is around 3x the size it was and nobody can explain how most of it works."
  • Difficulty in Maintaining Quality: AI agents struggle with consistency, often re-implementing existing helpers and leading to "slop" that makes the codebase harder to maintain and debug. "It gets to a point where there is so much slop that it’s better to just treat the project as a black box and continue dumping slop into it."
  • AI Ignoring Rules and Instructions: Even with explicit rules in CLAUDE.md, Claude Code has been observed to ignore instructions, skip steps, and provide incorrect summaries of its actions. "It ignores EVERY. SINGLE. RULE."

Strategies for Effective AI Integration

  • Implement Strict Configuration Files: Utilize configuration files to deny unwanted actions, such as docker run or docker-compose up, to prevent AI from making critical errors. "PSA this is why we have config files"
  • Maintain Human Oversight: Developers should remain in control and critically review AI-generated code, as agents can be "confidently incorrect" and require significant human intervention to avoid compounding errors. "Agents create code really really fast and produce 90% good code with 10% madness. If you're not weeding out the madness as you go the next tasks starts with slightly mad code and makes it a little madder."
  • Use AI for Specific Tasks: AI tools are highly effective for documentation generation, recalling syntax, and simple SQL queries, which can significantly boost productivity in these areas. "Things that the tool is really good at, though, help me out a lot, even to the point that I would dread not having access to this tool going forward: \\- documentation: oh, my god, this is so good."

Corporate and Ethical Concerns

  • Executive Pressure and FOMO: Companies often push AI mandates due to fear of missing out (FOMO) on perceived productivity gains, sometimes leading to unrealistic expectations and increased incidents. "But when AI turned into a FOMO thing, now executives forcing us using AI to increase productivity."
  • Policy Ambiguity and TOS Violations: Anthropic's policies regarding Claude Code usage, particularly with SDKs and automated processes, can be unclear, leading to confusion among developers about what constitutes a terms of service violation. "Anthropic really needs to explain this. I’ve created a study app for myself that uses claude -p in the backend to help generate study guides for me to review. Am I technically violating TOS by doing this now?"

Are you considering implementing an AI code mandate in your organization?

  • * *

Show More

Recommendations for model routing platforms

Sandboxing techniques for Claude code

Grok bot usage limits and resets

Claude AI open source options

Image 27

Image 28

you are out of usage credits.

Public

Anyone can view, post, and comment to this community

0 0

Image 29
Join the most real place on the internet

Continue with Phone Number

Continue with Email

By continuing, you agree to our User Agreement and acknowledge that you understand the Privacy Policy.

Image 30

讀者討論

理性交流 · 即時討論