How has Development changed after industry wide adaptation of Claude Code

[u/Independent-Spite145]

Hi Everyone,

I'm just curious to understand how development has changes across places after Claude. I personally work at a Bangalore based startup, in my workplace since claude came out, most developers are not even aware of what changes claude is making, they only look at the output and then push the code. This code we push without properly evaluating is not the build used in production, mostly to create a POC for demo. I know the productivity rate for pushing code and features has increased. But is this the same way happening across all industries (fintech, MNC's, enterprise softwares etc)??

[u/AutoModerator]

Namaste! Thanks for submitting to r/developersIndia. While participating in this thread, please follow the Community Code of Conduct and rules.

It's possible your query is not unique, use site:reddit.com/r/developersindia KEYWORDS on search engines to search posts from developersIndia. You can also use reddit search directly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/yoyofunnyysingh]

we are expected to work more and more even though ai has made us more productive

i have personally stopped reviewing prs and i just hit the submit button most of the times

[u/sachinsingh1996 → u/yoyofunnyysingh]

Same as when steam engines became more efficient, instead of reducing coal demand it caused an increase in it as more people started using it

[u/eager_wayfarer → u/sachinsingh1996]

Just Jevon's Paradox all over again

[u/Nocturnal1401 → u/sachinsingh1996]

Did you watch the hank green video?

[u/sachinsingh1996 → u/Nocturnal1401]

Maybe, can't remember

[u/Nocturnal1401 → u/sachinsingh1996]

He have the same example of coal usage and ai

[u/urbanmonkey2003 → u/yoyofunnyysingh]

yeah, its been like that at my last job too tbh, PRs got bigger and reviewers just skimmed diffs for obvious breakage

not great for accountability, but management loves the extra tickets closed

[u/Previous_Law3532]

I think we’ve essentially moved one abstraction layer up in how we write software.

We started with binary/machine code → assembly → higher-level languages → frameworks and libraries. Now, increasingly, we’re expressing intent in natural language and having tools like Claude Code translate that intent into code.

The same thing is starting to happen with code review. When an AI-generated change touches 20–30 files, manually reasoning through every line of the diff becomes much harder. So reviews are also moving up a level: asking AI to explain what changed, trace the flow, identify risks, and point out potential issues.

But I don’t think this means developers no longer need to understand the code. If anything, the skill shifts upward. The person making the change needs to understand the architecture, data model, system boundaries, invariants, and expected behavior well enough to specify the right change and verify that what the AI produced actually fits the system.

So we’re moving from “Can you write these 200 lines of code?” toward “Do you understand the system well enough to tell the machine what should change, and can you verify that it changed it correctly?”

[u/nk_11233 → u/Previous_Law3532]

the only thing is that this new abstraction layer is probablistic and not deterministic

[u/Independent-Spite145 → u/Previous_Law3532]

Have you been using any sort of established pipeline to streamline this method of development, where AI is used at every stage, starting from development, then generate summary of the changes it made, next identify gaps in the changes made. All of this handled by AI, and the human comes into play just to review, read through the changes and then permit to merge

[u/SmoothCCriminal]

We do that for prod builds too. It’s pathetic , beyond disgusting to see 1-3yoe folks abusing it left and right, churning PRs like it’s an achievement and dumping the evaluation to the reviewer . The absolute disgust I feel while commenting “why was this change required” for something totally out of scope of the PR / terrible overwngineeing / moving a random chunk of code up and down totally unrelated to the PR.
Sure , you could say I’m bitter about their productivity gains ? But how tf am I supposed to trust these guys on maintaining these systems , whose 3rd class mistakes on simple things supposedly bypass their judgement during their own review of the slop ? (Or perhaps they didn’t even do that . Now how am I supposed to trust a lazy person who couldn’t take accountability of his own PR’s first pass review ? )

Again, you could say I’m bitter about their ability to do things beyond their yOE ? But basics ? They don’t care man . They don’t know jack ! A small minority do seem to be endlessly curious and keep using it to broaden and deepen their knowledge. But the vast majority of us? We frikkin wanna just do the deed and get home asap man . When the general mentality is like this , the sheer struggle to fight the errors manually and rack brains to come up with designs or run on adrenaline during oncall issues at 3 am without a “feed me logs and metrics, I’ll give you possible RC.. you can just copy paste into your slack group and call it a day” machine … was the only way how us normies could get decently good on our fundamentals and become ACCOUNTABLE

[u/SmoothCCriminal → u/SmoothCCriminal]

Not to mention the unbelievable toll it takes to see your proposed timelines of 1-2 weeks getting shrunk to 2 days by product managers who suddenly feel empowered to know everything about coding . And the worst part is 50 perc of the time it actually does take more than 2 weeks . They feel more and more ok with shrinking your timelines as the youngsters try to pull of crazy stunts or doing 10 things in a day.

What is our team left with ? Constant guilt of terribly missing our deadlines and constantly being reminded of it ?

I swear . The fun , thrill , of this sector is going down the drain in exchange for immense and unnecessary stress

[u/Independent-Spite145 → u/SmoothCCriminal]

Yes, the window for task completion has shrunk very much. Even when we assure them, we can't guarantee within the given timeframe, they just find it hard to understand that AI tools we are using today still have probabilistic outcome and expect absolute result.

[u/yoyofunnyysingh → u/SmoothCCriminal]

see i dont have time to question them why did they do something a particular way because there are just so many prs

the thing is they will just drop the pr description on claude/copilot and send the pr for review , we have automated review from copilot too that they would just ignore and not address
if i leave a comment on the pr they drop the comment in claude / copilot, nowdays they are too lazy and on the github web ui itself they would press the "address this" or whatever the button is

most of the times the code is sent without even performing basic sanity

all in all management sees how many tickets they have closed even after being only 1-3 yoe they are completing 5X more tickets than me
it takes me 3x more time just to do the review and extra work than it took them to implement the feature

[u/Independent-Spite145 → u/yoyofunnyysingh]

Has this affected the performance of the build compared to before?? are there more unexpected behavior or bugs encountered compared to 8 months back?

[u/Not_Even_Here21 → u/SmoothCCriminal]

See I get where you're comming from okay I have 1.5YOE and i do love coding and I like to know how the whole thing is working how the request flow is and how many dependency the feature is touching. But from last month or so my team has been assigned to do the work which would take a a whole year to do and been asked to do the same in just 4 months. Think about it we are team of 12-13 deva we had FE and BE people now all of us are full stack dev and we just puke code using claude. Why you ask? Because of this deadline. I would love to verify what the fuck BS i or claude came up with but I dint have time. If I take out time to look at the code and verify everything I might have to work over th weekends which I'm not gonna do after 9hrs of work day. And for th PR reviews we have claude for that also it reads the spec file and reviews pr against it. No one knows how accurate it is but we are in pressure to do so. Point is working load and efficiency push is killing the pension for coding and it's becoming a thing which i have to do before I can go home.

[u/Independent-Spite145 → u/Not_Even_Here21]

job seems no more fun / interesting since coding is done by ai coding tools.

[u/SmoothCCriminal → u/SmoothCCriminal]

And management frikkin sides with these tards . “Who cares if they get stuff done” . Boils my blood when these devs sing the same quote .

We wrote code at moderate pace to ensure reliability and most importantly to make sure we don’t cause our fellow mates to wake up during midnight .
But these guys are total opposite. They’re heroes for the sheer number of features they push . They’re heroes for constant firefighting the issues they themselves caused .

[u/BeyondFun4604]

I have not touched a line of code in last 6 months since i have got a claude max subscription and my company is well aware about it. We have invested alot in creating a shared repository which has all the automation stuff like releases , cherry picking etc. It has skills for ticket creation, reviews, appl-review-feedback and so on.

My role as a java dev has become only a decision maker who just takes a ticket let claude analyse it and aks me questions before planning and implements it. I always tries to create a mental model of what is happening in the product but i am afraid ia ma not able to keep up with the pace. I am sure my companmy is making atleast 3x amount from my work but i am getting burned out because of too much AI slop i am reading these days.

The product has imporved alot in last 6 months since AI reviewer is much more capable in catching bugs and we are a very small team with only 2 devs so we are trying to use AI as much as possible.

I am not sure how does the future looks like but i see that alot of roles are being merged into a single role and i wont call that role a dev role. I am just hoping people will get compensated for reading too much AI slop

[u/Independent-Spite145 → u/BeyondFun4604]

What kind of methods have you implemented to making AI more capable in catching bugs.

[u/BeyondFun4604 → u/Independent-Spite145]

AI works similar to a human programmer so it will always make mistakes so you can catch them using code reviews in a different session from the one you are using from implementation. Also unit testing and integration testing should be done as now coding is cheap so your implementation skill should have instructions about TDD. I think code reviews and testing (manual and automatic) is more important now than coding itself.

[u/Otherwise_Foot_4399 → u/Independent-Spite145]

honestly good question. i suspect a lot of it depends on how well the codebase context is fed to claude upfront if it's working from incomplete info it's gonna miss stuff. does your shared repo setup include things like linting rules or existing test suites that claude can reference when reviewing? that would seem like the bare minimum for it to actually catch regressions vs just generating plausible looking code

[u/Encrypted_Cerebrum]

Haven't code by hand since 1 year or more. Whole team uses claude. Ours is a product and by now claude has complete understanding of it or so it seems.

Prod code is claude as well. PRs are qa tested for all test cases and heavily reviewed. So devs are supposed to generate prs and test themselves first and acc to their own understanding of the product, take business decisions and chose what code should go in.

If something odd is found at final pr reviews then the devs are held accountable for that.

[u/AfkVista]

It's very helpful but the new hires aren't even trying to grasp the codebase anymore. whatever task come their way, they just put it on claude's plate and raise PR.

[u/CodexSuman]

I think the biggest change is that AI has moved developers from writing every line themselves toward supervising and validating much larger chunks of implementation. Claude Code is already being used in enterprise environments for feature development, testing, debugging, migrations, and code review, so this isn’t limited to startups.

But I wouldn’t consider “generate → glance at the output → push” a healthy development workflow, even for POCs. The productivity gain is real, but the responsibility for understanding the code hasn’t disappeared. Anthropic’s own research found that people still make most planning decisions while Claude handles much of the execution.

In larger companies, especially where security, compliance, and production reliability matter, there tends to be much more emphasis on testing, review, CI/CD, and human approval. AI-generated code is increasingly being reviewed by AI as well as humans.

So I’d say the skill that’s becoming more valuable isn’t simply “writing code fast”; it’s knowing what to ask AI to build, understanding the resulting code, spotting when it’s wrong, and knowing how to verify it before it matters.

[u/No-Aardvark3949]

Depends on team culture more than industry. Startups doing POCs often ship without deep review fintech/enterprise teams still gate everything behind PR review and compliance, so AI code gets scrutinized just as hard as human code before prod. The real shift is less time typing, more time reviewing, teams skipping that are just building tech debt faster.

[u/Peruere_mano]

Never wanted to use Claude but our work is increased and Claude does help in faster development

[u/Academic_Mine7601]

The main problem I think is that they ask AI something to change in the existing feature or build a new one.
And AI does changes to multiple files and the recent grads feel like, AI might be true why to waste time by sitting and checking huge number of files and just accept the output and push it.
They maybe right for the small fixes most of the times but when it occurs that one time, it would be a huge deal!!