r/SoftwareEngineerJobs • u/Suspicious_Orchid770 • 10d ago
Coding is only 10–16% of a developer’s week, which is why one team’s AI speedup barely moved delivery
https://leaddev.com/velocity/your-engineers-got-twice-as-fast-your-lead-time-only-moved-411
u/Ok-Investigator3257 10d ago edited 9d ago
I’d say 20 percent of my day as a senior (8 YOE) is writing fresh code. Even then it’s hard to estimate because it tends to come all at once and then none at all.
The rest is:
reviewing code
maintaining test infrastructure or debugging failures
in meetings with my manager about architecture stuff or figuring out who I need to talk to about how to architect things so our product/my work will fit with another teams product/work
mentoring folks/rubber ducking for a teammate
doing research on potential better ways to do things to propose new work for myself
All of that generally involves code but it’s not literally writing new code
Edit since the guy below me deleted his response: yes AI can help with these tasks but it’s really bad at new feature development from a blank file. Yes it will make something that works, which for startups is fine because their business model is make a pile of tech debt that works and exit, but for everyone else it’s impossible to maintain. It’s decent at filling in pseudocode scaffolding but if you don’t architect it first it builds spaghetti
2
u/ActuatorOutside5256 10d ago
Yup. The juniors and mid-level are the ones on the grind, but they need seniors and management to reel them in. When seniors and management don’t do their job right, companies get results like from the post.
1
u/ThomasToIndia 6d ago
This is mostly because you haven't written governance rules. Most of the lack coders are finding in AI is stuff they never wrote down.
Maintenance is the new cope, AI can absolutely build new features that can be maintained.
Also claude 5.5 was a pretty big leap and none of this stuff is getting worse, I am not talking about models, I am talking about the tooling as well.
10
u/Drahkir9 10d ago
And now thanks to everyone vibe coding everything no one knows wtf is going on. You used to be able to have conversations but now everyone’s gotta check everything with their agents.
4
u/AkatsukiPineapple 9d ago
Companies relying on OpenAI or Anthropic for their whole operations seems a crazy move for me.
0
9d ago
[deleted]
1
u/Forward_Problem_8982 9d ago
That's one little detail going wrong and everything else working, versus things going wrong every time you touch AI.
4
3
u/hammonjj 9d ago
Dude, if you’re only coding 10-16% of the week, then there is something seriously wrong with your company’s process (assuming you’re not in some sort of highly regulated industry). I’ve worked at big corporations and startups and never had that sort of split.
1
u/Due_Cap_7720 9d ago
I feel like I do something similar and I feel like because of all the process that time is very efficient. Also with AI, programming is very fast.
1
5
u/Toren6969 10d ago
If you are really only developer, that is pretty low.
If you do not have a dedicated analyst/architect who gives you detailed specifications and actually goes through the business/technical process and all that is on you, then it can be pretty close to reality, especially on more business wise complex products.
4
u/Ok-Investigator3257 10d ago
Yeah that’s most real stuff imo. I’ve never had someone spoon feed me specs and just say “implement this” except when I was a junior
3
u/Dargooon 10d ago
Yes, this always surprises me. Are people simply handed complete specs? Most of my experience starts with: So we've been thinking...
Then you go from there, refine whatever is there, map to tech, insert into arch, test and iterate with customer or internal, build/review test spec with tester, test and iterate, all the time fighting with other projects and priorities like support, product care, sunsetting, release management, customer/supplier meetings etc...
I estimate about 30% of a normal week is code, of about 2/3 is writing/reviewing tests and docs. And I know many in my team code far less than me, I code a lot. We manage to be the top of our specific field, so we're doing something right(?). YMMV, I guess.
3
u/Ok-Investigator3257 10d ago
Also let’s not forget trying to build around existing tech debt vs nuking it and rewriting it all
2
u/Spudly42 10d ago
I'd say a typical split in industry is that an analyst/business side person will grather details on the overall problem, including the business case/types of failures, then use this mostly the prioritize. Then they will likely understand the use cases from the different users, write up requirements for what the software needs to achieve and potentially acceptance criteria. What they won't do is prescribe solutions at all. Sometimes UI/UX is provided, but in that case they would probably work with the developer to understand what is possible and how complicated different approaches are. So specs provided to you, kind of, but never in the form of technical solutions, just business requirements.
1
1
u/DarkLordCZ 10d ago
"Architect" started using Claude and now I have to decode (and fix...) whatever the fuck am I even supposed to do.
I'm thinking of becoming an electrician, I'm starting to hate the field...
2
u/gochisox2005 8d ago
Management should be fired if they aren’t building an environment where devs are coding 6+ hours per day. I can’t even imagine.
2
u/dillanthumous 7d ago
That's why I am enjoying LLMs now. They have gotten good enough that I can get some real work done while also dealing with my mountain of meetings, emails and messages.
4
u/TashLai 10d ago
What a piece of bullcrap.
Idk which workplaces have coding take only 10-16% of developers work, but let's assume this is true at least for some. That doesn't account for all the thinking you do while watching Netflix with your gf and then realizing you didn't actually watch a second of it.
3
1
u/rmullig2 10d ago
I don't think companies care as much about moving faster than they do about getting the work done with fewer developers.
1
1
u/hibikir_40k 10d ago
What I find confusing isn't claiming that little time is spent coding, but assuming that this is the only part of engineering that AI is doing very well. Examining logs and metrics, for instance, is something that the machine does really well nowadays. Writing documentation (when the model is one of the strong ones: the weaker ones write drivel). Right-sizing infrastructure, looking at said data. Looking at whether a high level idea will be expensive to implement, or breaks core invariants. All of that is LLM-fodder nowadays.
3
u/ContraryConman 10d ago
I think this is a cope in its own sort of way. People will copy-paste an entire feature of debug ticket into Claude Code and it will autonomously plan, design, debug, unit test, integration test, CI pipeline, write documentation, and open the PR while the "human in the loop" scrolls TikTok. And then people will have the gall to look at you and go "well AI is only replacing typing code, and typing code was such a small part of the job"
2
u/West_Till_2493 10d ago
Copy paste? What is this the Stone Age? Just tell Claude to do all of my open tickets
1
u/ContraryConman 10d ago
True, my Claude uses the Atlassian Jira + Microsoft MCPs so it knows all my open tickets and Teams messages without copy/pasting
1
u/Dry_Hotel1100 10d ago
and it solves this user stories without any UI since nowhere are humans anymore.
1
u/Big_Arrival_626 10d ago
U also need to take care of state issues and services breaking cuz they're used somewhere else. This is the one thing Claude is bad at. It's still really easy but average dev is too lazy to even consider this so it gives you an edge
1
u/OutsideMenu6973 9d ago
Always works perfectly at work, yet I’m always swearing at it first thing in the morning for failing to stay the course on building the next billion dollar fart app
2
u/Healthy_Coconut1636 10d ago
All of this will still need a human in the loop though who understands how the systems work.
1
u/Spunge14 10d ago
The problem is that orgs are now trying to have 9 women give birth to one baby in a month.
Once they realize coding goes faster with just one engineering lead, their agents, and the codebase, things will get real.
1
u/numerical_panda 10d ago
You mean, when the understanding of the code base is entrusted to the only person who has ever remotely touched or read the code?
1
1
u/abrandis 10d ago
Why does understanding a codebase matter so much, this is a false assumption, when you get assigned to a large project you don't understand the codebase and often just a small piece of it... AI is no different...if fact it's better you can ask it about the codebase and it will explain it to you....19x better than having some developer with an attitude not want to be bothered as to why his shit loop structure has odd logic and variable names are cryptic
1
u/numerical_panda 10d ago
When the AI bigwigs suddenly hike prices or turn the intelligence knob to zero, good luck with your cryptic variable names.
1
1
u/TheReservedList 10d ago
This is insane, where are you guys working?
Coding is only 16% or a lead engineer's week? Sure.
But if you're an IC and you only sit to program LESS THAN A DAY per week, you're just being mismanaged. Period.
No wonder AI is going to replace us all if we're that inefficient at communicating.
1
u/ThomasToIndia 6d ago
Then the awkard part where no one wants to talk about how badly coders would lie on the regular. I feel like AI may be a collective karma on coders.
Heaven forbid you had a no coder manager, they qould be taken advantage. Most coding was redundant, CRUD stuff, and most of the good coders built themselves internal tools.
Man customers were so exploited. Government contracts? Jesus.
1
1
1
u/Junglebook3 10d ago
10-16% is really low. On the low end, of a given 40 hours work week, they only code for 4 hours? That's less than half a day. They spend 4.5 days doing other stuff? That seems like a massive organizational issue.
1
u/ILikeCutePuppies 10d ago
Why do people keep thinking that llms only help with the coding part of the job. They help in many other areas as well. They do not do the entire job and they do create new problems even as they speed some processes up.
1
u/Kyy7 9d ago
When novelist or journalist is writing a story they are doing a lot more than just inputting words. They are thinking what to include, what not to include, how things should be presented, how the story should be structured etc. They may also discover things while writing that can make them go back and alter much of ehat they have written.
Much of the same goes for programming. Often one has to write code to get feel for the problem, discover new things that may affect what and how something gets build in the first place.
Perhaps agentic development provides some ways to achieve similar things but I feel it is missing something fundamental related to this.
1
u/iliasd15 9d ago
People are so against Ai I don’t get it. It will still make that 10 / 16 % faster. It will still help you with other tasks too.
1
u/crispAndTender 9d ago
Da fuck, 80 to 90% easy, 15 to 30 min standups daily otherwise no meeting for devs
1
u/vibr8ing-cockr1ng 9d ago edited 6d ago
The original post content no longer exists here. The author used Redact to remove it, exercising their right to control their data & privacy.
Encouraging repeat tub makeshift sharp hunt
1
u/Southern_Orange3744 9d ago
This makes me think
You only need.a fraction of the team
The team as a whole is under leveraged
Product team sucks at deciding what they want , see 2
1
1
1
u/aidealy 9d ago
u/FlounderLow6725's manager is counting the part of the week the article says AI sped up.
Thousands of lines a day look like speed, and the cost lands on whoever reviews them and whoever fixes them a few weeks later.
The author wants lead time and where the work waited reported next to adoption and PRs merged.
I'd add one more number, how much of what merged needed a fix after it merged.
Next to that, the slop shows up as work coming back, and the reviewers finally get credit for the time it eats.
I started Aidealy to rank engineers this way from Git history, so merged work and reviews earn points and a fix after the merge takes them back.
1
u/Puggravy 6d ago
WTF were can I get one of these jobs? I spend at least a good 20-25% of my Time coding.
-2
u/Positive-Task-9248 10d ago
Skill issue
And I want to know the full break down of what those developers been doing the whole week. AI does not only speed up coding, it also speeds up documentation, testing and reviewing.
1
1
u/werpu 10d ago
I have been in jobs where literally 30% of the week were planning meetings and other meetings and discussions about the code reviews... the line can be as high as 50% depending on the reviews for instance. Coding is not only hammering something in, but reviews take a ton of time as well planning also!
2
u/ithilain 10d ago
This is a big one for me, i regularly have days where I'm in 3-4 meetings spread just far enough apart to ruin productivity. For example today i have a 10-10:30, an 11:00, lunch, a 1:30-2:30, and a 3-3:30. Realistically I'm not getting jack shit done in the 30 minutes in between those meetings so thats a solid 5.5 hours out of my day that I'm not coding just from meetings.
0
u/Hour_Interest_5488 10d ago
I doubt the metrics.
But the amount of issues in the internal company processes I have seen throught out my career astonishes me.
1
u/MatkaGracz 10d ago
Tell it to my boss, he can hook up "anything" with AI in few hours, so it should take us few minutes.
55
u/Nearby-Echo-1102 10d ago
If my former development team only spent 10-16% coding I would have been out of a job - that’s just insane. I can see why these teams are not seeing much improvement, they are so bogged down in process that they’re not actually delivering.
If teams are only using them for coding, well, you’re already hindering yourself.