Claude Code is the Inflection Point
11 69About 4% of all public commits on GitHub are now being authored by Anthropic's Claude Code, a terminal-native AI coding agent that has quickly become the centerpiece of a broader argument that software engineering is being fundamentally reshaped by AI.
SemiAnalysis, a semiconductor and AI research firm, published a report on Friday projecting that figure will climb past 20% by the end of 2026. Claude Code is a command-line tool that reads codebases, plans multi-step tasks and executes them autonomously. Anthropic's quarterly revenue additions have overtaken OpenAI's, according to SemiAnalysis's internal economic model, and the firm believes Anthropic's growth is now constrained primarily by available compute.
Accenture has signed on to train 30,000 professionals on Claude, the largest enterprise deployment so far, targeting financial services, life sciences, healthcare and the public sector. On January 12, Anthropic launched Cowork, a desktop-oriented extension of the same agent architecture -- four engineers built it in 10 days, and most of the code was written by Claude Code itself.
11 comments
The things must really be getting desperate (Score: 5, Insightful)
by Mr. Dollar Ton ( 5495648 ) on Saturday February 07, 2026 @07:22AM (#65974366)
in "AI" land if someone's paying for these ridiculous advertisements.
Re:The things must really be getting desperate (Score: 5, Interesting)
by burtosis ( 1124179 ) on Saturday February 07, 2026 @08:51AM (#65974462)
in "AI" land if someone's paying for these ridiculous advertisements.
Yep, it’s like saying all products have been designed by AI for 50 years because humans have been using CAD models, CNC, and database like inventories. Without humans in the loop none of them would useful at all, just like coding with any “AI” agents so far through a single prompt. The bubble surface tension is holding in a critical amount of hot air and the upwards pressure is causing the surface to erode and evaporate even faster which is why news outlets are reporting on the AI stock sell off as fears over AI replacing all coding tasks because someone has a need they can vaguely describe. It’s a multiplier of human productivity, not the dream of end stage capitalists who want to replace and dispose of the working class.
Re: The things must really be getting desperate (Score: 5, Interesting)
by caseih ( 160668 ) on Saturday February 07, 2026 @12:21PM (#65974728)
Possibly, but it definitely means he hasn't spent any significant time with it. Pay $20 and try it for a month and then post about how awful it is.
My initial experience with Claude wasn't great. In fact it completely failed at the task I gave it. But later on I began to use it in more specific ways---here's my code, can you modify it to do foo, and add a feature bar---and it really began to work for me. Was pretty incredible actually. And I began to use it to teach me and explain parts of the API to me, complete with examples based on the code I already had. And it's pretty good at helping you quickly get up to speed with code you've never seen before. Plan mode is also a key to success. I now use Claude regularly as an assistant.
Claude is also a pretty good debugging tool. Over the past couple of months I've run into problems with my code that I banged my head against for hours, knowing it was probably something simple and obvious but I couldn't see it. Finally I told Claude what was happening and had it analyze the code and more often than not it found the problem with my logic, even pointing out something in another part of the program that I hadn't considered that caused the problem.
I do very little vibe coding, but I have used Claude to add features I needed to an OBS plugin. I also used it to modify a flutter app to add complementary features to communicate with my modified OBS plugin. I have no experience in flutter or dart. But I did review the changes Claude made and they were quite reasonable.
Claude isn't perfect or all that creative, but it still is a game changer. 90% of what programmers do isn't novel or ground breaking, but just putting together existing parts in new ways that fill a need. Claude is very good at assisting in this. The only downside is Claude is fairly expensive. I can only use it for about 1 hour before I hit my 5 hour limit. And if I was to use it heavily the Pro account wouldn't last very long in a week. $100 for the max account is pretty expensive.
I'm looking at other models that are improving all the time. OpenCode cli (not too bad) with Kimi 2.5 Thinking, Qwen3. Not quite as good as Claude but still darn useful. I'm tempted to get hardware to run Qwen3 locally. Probably AMD Ryzen AI Max+ 395-based system. Seems a bit ludicrous how expensive they are for what is basically gaming laptop hardware. And I expect the price to jump in the next month, maybe even double by the end of the year.
Re:Short-term Analysis Hype FTL (Score: 5, Funny)
by haruchai ( 17472 ) on Saturday February 07, 2026 @08:11AM (#65974416)
"anything you can do, I can do butter"
i guess we're toast
Will make the experienced developer more effective (Score: 5, Informative)
by simlox ( 6576120 ) on Saturday February 07, 2026 @08:05AM (#65974404)
And make inexperienced ones produce more crap. I tried it a little and it could really speed things up, but it is like outsourcing to junior developer, except it is much faster and cheaper. In general it is good at scrabing examples, produce templates code, fixing some bugs, but it makes quite a few mistakes.
Re: Will make the experienced developer more effec (Score: 5, Informative)
by BlueKitties ( 1541613 ) on Saturday February 07, 2026 @09:26AM (#65974502)
No, but they "gave grunt work to the code monkeys." People have become a bit more hesitant to use language like that these days, so they just say junior developer.
Re:Will make the experienced developer more effect (Score: 5, Insightful)
by Carcass666 ( 539381 ) on Saturday February 07, 2026 @09:25AM (#65974492)
And make inexperienced ones produce more crap. I tried it a little and it could really speed things up, but it is like outsourcing to junior developer, except it is much faster and cheaper. In general it is good at scrabing examples, produce templates code, fixing some bugs, but it makes quite a few mistakes.
Agreed. There are some things that I find pretty annoying about it that you have to tell it explicitly not to do. For example, pulling in really old versions of NPM or Python packages. It has a propensity to not know when it is correct or incorrect, or perhaps, it it is unable to share its level of uncertainty. Most of these things can be mitigated by updating and refining Claude's prompting.
I think there are some things those of us clutching our pearls at the thought of all of the AI slop ought to keep in mind:
Most of the furniture in my home is not hand-made by Amish carpenters, it is machine milled and partially assembled by cheap labor. It is not as good and will not last generations as hand-crafted furniture, and that is okay. For better and for worse, a lot of SMB executives look at software the same way (at least until it doesn't work), they want "good enough" software that works until the next merger or acquisition, so they can cash out and go on to the next thing. They are not intersted in paying for software built using hand-built assembler (SpinRite - we miss ya').
The good news is that there are things we can do, and if we get good at them, AI can do the mundane bits and software engineering will still be a thing. We get better at Specification and Test driven development. We review the hell out of the code AI generates and make sure our linting and bench-marking tools are up to snuff. We get really good at authoring prompts that keeps AI tools within the guardrails. And yes, we keep AI away from the really critical stuff, at least for now...
As a woodworker and software engineer (Score: 5, Interesting)
by Somervillain ( 4719341 ) on Saturday February 07, 2026 @01:25PM (#65974788)
Most of the furniture in my home is not hand-made by Amish carpenters, it is machine milled and partially assembled by cheap labor. It is not as good and will not last generations as hand-crafted furniture, and that is okay.
Carpenters build houses. Woodworkers make furniture. I make heirloom furniture as a hobby. The machine milled stuff is superior. You can make far superior furniture with technology and tools. Your furniture is lower quality for 3 reasons:
1. materials. Your furniture is made with particle board. My pieces are made with hardwood, carefully chosen for grain and lack of defects.
2. assembly: Your furniture has to be shipped long distances. My pieces have only been moved from my basement to the room. Therefore, I use joinery and glue and expert technique...mass market furniture has to be moron-proof.
3. finish: I lovingly applied finish to every portion after it was assembled and corrected mistakes. I add an additional coat or 2 for durability because my children are monsters. Your furniture had minimal finish spray applied before packaging. Commercial furniture has no incentive to give you good finish. It just has to look good for 30 days. If it looks like shit after a year, it just increased the chance you'll buy another one soon
We are not all writing air traffic control systems or medical device firmware. There is an awful lot of "enterprise software" that is not much more than database CRUD and visualization. People are not going to die if that software is not using the most efficient data types, etc.
NO! "Close" is noticeably inferior to good.
1. You like data breaches? No person may die, but your business may if it has enough lawsuits from data theft from your vibe-coded garbage.
2. You like high cloud spend and global warming? Keep writing inefficient vibe-coded slop in Python with 40,000 frameworks that add no value. Just keep spinning up new instances so you don't have to learn Java or Rust. It won't kill anyone as fast as a medical device or air traffic controller mistake...but you're harming the planet with your laziness.
3. You like inefficiency? If you take 100,000 lines to do something you could have done in 500, it is very hard to maintain, increases the likelihood of bugs and is a perpetual cost carried by your employer. It's expensive. That money could be wasted bogging down 2 or 3 engineers or you could hire 6 delivery people...or upgrade tooling....or invest the money in a useful manner that employs more and benefits society.
Look, if you don't take pride in your work, go sell real estate or something like that. You have no business being a programmer. I use Claude daily at work. This week, it actually helped me and only catastrophically fucked up 2x..so maybe it saved me a tiny amount of time after I fixed their mistakes? AI is overhyped, but generally neutral...neither bad nor good. However, shitty work?...that's a fucking cancer and we need some serious chemotherapy to flush it out of the industry. Just because you're doing enterprise development doesn't mean it's OK to suck at your job and suck at life.
Four Percent? (Score: 5, Insightful)
by SlashbotAgent ( 6477336 ) on Saturday February 07, 2026 @08:11AM (#65974414)
Hyping 4% sounds like a scammer hyping shit coins and NFTs.
I fully expect an increase, but this article is pure spam/hype.
Re:Claude Code is good (Score: 5, Insightful)
by twdorris ( 29395 ) on Saturday February 07, 2026 @08:35AM (#65974444)
if you don't know how to code it's a god send.
I contend just the opposite. I'd be terrified to watch someone that doesn't know how to code use claude code for the very reasons you mentioned. It's going to do amazing stuff most of the time and really stupid stuff periodically. To pick up on that stupid stuff, knowing how to code and conscientiously reviewing changes with that background knowledge is the only way to get those impressive results.
Re:Claude Code is good (Score: 5, Insightful)
by dj.delorie ( 3368 ) on Saturday February 07, 2026 @10:13AM (#65974576)
In my experience... if I ask Claude to help with something that's my strong point (like my core coding), it's like training a junior programmer, and I can solve my problems faster myself. But... when I need something outside my core expertise, like helper programs, wrappers, or interfaces to other technologies I'm not familiar with, it's a very fast way to get 95% of the way there without wasting time climbing the learning curve myself for a one-time need.
Like any tool, you have to know when to use it and when not to, and what its strengths and weak points are.