r/SoftwareEngineerJobs • • 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-4
714 Upvotes

115 comments sorted by

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.

21

u/davidbasil 10d ago

Sometimes 2-3 days passed along and I added or modified only one line of code. The rest went into research, experimenting, planning, testing, communication, etc

4

u/FlounderLow6725 9d ago

I used to have to do a pr a week for a few lines not to get fired. Now I submit 1000s of lines of slop daily for other people to review and my manager thinks I'm really productive

1

u/davidbasil 9d ago

Haha, I left my last job because of it. And year later their laid off the whole team of devs, managers, testers, etc.

2

u/Left-Attention-1544 10d ago

Except maybe communication, those others can be sped up considerably by AI too.

4

u/davidbasil 10d ago

Sure, but you'll hit the roadblocks sooner as well. Plus security, precision and data integrity are at risk. Anyone car can go 180 miles per hour but nobody does it on regular basis because human can't control it at such speeds.

1

u/BehindTrenches 9d ago

There is a version of AI-assisted engineering where you don't meaningfully compromise precision or production data integrity.

Somewhere in-between 180 mph agent swarming and the 60 mph human speed limit.

1

u/kerrizor 6d ago

Perhaps.. but until business can attach a dollar value to quality, there’s only one speed.

1

u/blueechoes 9d ago

If you are using AI in communication towards me I WILL disregard it. If I want to know claude's opinion I will ask it myself.

2

u/5show 9d ago

The amount of copy-pasted claude slop I’ve had to sift through just this last week. I’m gonna break

1

u/coworker 9d ago

Claude doesn't speak unprompted. What it says on my behalf, is my opinion

1

u/Forward_Problem_8982 9d ago

People used to speak themselves.

1

u/coworker 9d ago

People used to have their secretaries draft memos

1

u/maresayshi 9d ago

another human, at least

0

u/freebytes 8d ago

That may be the case, but AI is often too verbose. You can use fewer words, and the nuance allows people to get their thoughts across without wasting time.

In addition, there was previously a social contract that writing took longer than reading, so if someone was using the energy to write a sentence, then it is reasonable to spend a fraction of that time reading it. Now, generating books worth of nonsense involves no thought whatsoever. We can easily converse with an LLM if we choose to do so.

1

u/Automated_Spite 3d ago

I find communication is now harder. There's a friction point or an edge case or something in the requirements and I go ask the supposed stakeholder how they want it to work, and they can't even begin to explain the intent because they didn't actually read it, they just copy pasted the spec and the followup emails from the client into an agent to generate the requirements doc.

1

u/Left-Attention-1544 3d ago

Just today at work I had an example where AI helped me save like at least an hour. I got a question to an obscure service that I maintain like a few times per year. I know the gist what I wanted to tell the asker but would've had to look up the small details to give them a guide they can work with. So I explained the AI what I wanted to do roughly, let it also doublecheck that my thinking is right in the code and had it compile a guide with executable scripts for the asker to play with so they get the flow they need to implement.

Worked like a charm.

0

u/FFCProductions 10d ago

If you want it to be good, no AI/LLMs can't do that with the frontier models. It takes a knowledgeable user for there to be any benefit. People choosing to use these tools on average didn't have the skill in the first place, hence using a shortcut.

0

u/nahmannotreally 10d ago

My research is done overnight by a fleet of agents. Planning is a 5 minute back and forth interview where we discuss the goal, the shape, and concerns etc. Emailing is now unformatted speech at my computer then proofreading the email before it goes out. Testing is near autonomousb (outside of the most complex shit I do) with agents sending screenshots/videos of them testing software when necessary.

5x productivity may be underselling it.

2

u/davidbasil 10d ago

What is the line of your work? How much security, precision and legal compliance is involved?

0

u/nahmannotreally 10d ago

I work for a software development company that has a variety of projects with a variety of compliance requirements. HIPAA compliance is one example.

0

u/Left-Attention-1544 10d ago

I mean you can always find excuses why it's bad, why it actually slows you down or whatever.

I have written (by accident) insecure code and seen my colleagues write insecure code when AI wasn't a thing. Errors like this would never happen nowadays. Review agents catch this kinda stuff immediately, even more so when you use the best available cyber models like GLM 5.2.

1

u/Adventurous_Lake8611 9d ago

Yeah, sure dude.  Go play in your corner and let the grown ups who live in reality talk.

1

u/Left-Attention-1544 9d ago

any arguments?

1

u/nahmannotreally 9d ago

Don't even try, lol.

It's okay if people don't like AI for whatever reason they decide, but it's nuts that people who clearly have no exposure over ChatGPT free just call people working in the space liars.

I got called an Anthropic bot in this same thread when I described my workflow. They want to stick their head in the sand. Let em.

2

u/PineappleLemur 9d ago

It's nice not needing to talk to any people, waiting DAYS for their answer.. only to change their mind after you're halfway through an update.

I agree that this is the flow if you're working on a project by yourself.. I have a few of those and it's super fun not needing to wait for anyone.

But in most work you kinda need to work with people which takes those productivity numbers back to where it was before LLMs were a thing.

1

u/nahmannotreally 9d ago

At my organization all meetings are turned into transcripts that are captured, all emails are captured, and tasks are generated automatically throughout. Our task lists are coordinated, our agents keep us briefed on everything that's happening in the company in near real time, and if you're blocked by someone else they're aware of it before you are actually blocked by them in most cases.

The organization is small enough that even if I somehow end up waiting for something I can ask them in person within the hour and they can usually toss an agent at the issue to unblock me. We're not rawdogging models either. There's a set of strict guardrails, guidelines, and what have you to keep things on track, verified, and within company standards.

The bottleneck can sometimes indeed be the need for human communication, but we are nowhere near back to pre AI levels of productivity. I'm in a room with quite literally 15 monitors, 3 people, with God know how many terminals open at any given time with status reports and audio queues keeping everything moving at a pace that was absolutely impossible before this technology arrived.

1

u/CapitanJenkins 9d ago

Anthropic bots out in the wild before the IPO

1

u/nahmannotreally 9d ago

Ok dude lol

1

u/DenserPotato 9d ago

don’t you have to code for research, experimenting and testing?

4

u/pengs151 10d ago

Coding is the easiest part of the job and the fastest always has been its just the majority has always sucked at it.

1

u/Wonderful-Habit-139 9d ago

Wrong, coding is not the easiest part. It’s so difficult you need to have meetings and design docs and plan ahead just so that you don’t end up writing code that you regret writing for not being extensive enough and not handling edge cases properly.

2

u/doubleohbond 9d ago

Agreed that you’re both making the same point. Writing lines of code is easy. Figuring out what you should and shouldn’t write is where the engineering comes into play.

AI does not help with this

0

u/PineappleLemur 9d ago

The actions of writing the code is the easy part.. the decisions making, design, architecture, meetings, collecting requirements, etc is the bulk of the process needed before writing anything.

AI can help organize it.. but people need to know and understand what their wants/needs means, this takes time to get through and for everyone to agree on including setting up timelines.

0

u/Wonderful-Habit-139 9d ago

> The actions of writing the code

Pressing keys on the keyboard is easy yes. That's not coding though. Do you not realize how ridiculous it sounds trying to reduce what part of coding is easy, and then to try to imply that coding in general is easy?

"Typing the letters `def` to define a function while coding is easy, therefore coding is easy" this is what it sounds like.

> the decisions making, design, architecture

Those are things that you do because getting things right while coding is hard. So you plan for it beforehand, and then once you're prepared enough, you go and write the code and solve many more problems that you could never anticipate during the design phase. But you at least are more prepared than if you went in to code blindly. But the code is the most important part, and if you had a perfect being that wrote perfect, correct, scalable and maintainable code, you wouldn't need prior design and architecture. You'd just write the correct codebase from the start.

2

u/PineappleLemur 9d ago

Oh come on you know what I mean...

By the time you can start coding anything the decision are mostly made, during that time you don't need to talk to anyone (unless they change their mind.. which happens a lot) or figure out anything.

It's just you typing it out, looking at reference and example for things you've never done before.

I agree with what you say but if I had to list down things I need to do in the role... Talking and convincing others that X way to do Y is the right path forward or chasing people to extract what they actually want while explaining them the cost of it..

The actual time I spend sitting down coding is a small fraction compared to dealing with BS meetings, emails, documentation, testing, debugging, purchasing, etc..

Yes coding is hard because it needs a lot of planning to be good and readable. But to me it's still easier than dealing with people.

0

u/Wonderful-Habit-139 9d ago

No I don't want to know what you mean, because this kind of rhetoric trivializes the very important work that software engineers do, and gives ammunition to non-technical dumbasses that think their contributions are all that matter and that devs just do routine work and not actually solving problems.

Besides that... yes I know what you mean but I encourage you to not repeat that kinda stuff like I said, it's a harmful notion. Especially when you say it to someone that doesn't understand coding.

> By the time you can start coding anything the decision are mostly made, during that time you don't need to talk to anyone (unless they change their mind.. which happens a lot) or figure out anything.

I just said in my previous comment that this is not true. There are so many additional things that come up during implementation that you cannot plan ahead for during design, and they are NOT trivial at all.

> The actual time I spend sitting down coding is a small fraction compared to dealing with BS meetings, emails, documentation, testing, debugging, purchasing, etc..

Same for me. But time does not mean that the coding part is now easy. Just that you get less time to do that work even though it is still very important. If you removed all meetings and still coded, you would get a product. If you removed all coding and kept doing meetings, you'd have nothing.

> But to me it's still easier than dealing with people

I'd say it can be more enjoyable for sure. Because you get to work with systems that are deterministic, and if there are issues it's just a problem with ourselves and we need to learn and overcome that obstacle, and we always manage to do so. People are irrational so no matter how correct you are in your assessment, you're not there to be a therapist. But coding is not easy, and getting things right in a scalable and maintainable way is very difficult.

2

u/Sixstringsickness 10d ago

We have run into this our org as well... Endless discussion no decision.  Culture change is hard.  

2

u/PreparationAdvanced9 10d ago

Sometimes the discussions are valid and need to happen. Sometimes it’s better to time box. This requires experience and expertise to know when to do either

2

u/Sixstringsickness 10d ago

Yes - agreed.

1

u/UnfamiliarPath 10d ago

What did your former development team work on?

1

u/Franc000 10d ago

Sometimes parts of delivering is figuring out what to deliver exactly, how/where in the architecture, and aligning different dev teams on the features (looking at you micro service architectured softwares). All those requires meetings, just looking at the code base (which can now be helped with AI to be fair), and deliberating with other devs.

On complex and mature-ish software, I am not surprised of 15%-20% coding time, that sounds about right. Of course the proportion would be vastly different at the start of a green field project.

1

u/SerLarrold 10d ago

Can only speak for myself in the med tech space but meetings meetings and more meetings about the meetings is a lot of what occupies my time. Hell I could be more productive if we could get more tickets but everything moves slow

1

u/r0pe_tri1ck 9d ago

oh, you would not believe the things I've seen in corporate.

1

u/Perfect-Campaign9551 9d ago

If I could improve features and add things myself without having to discuss it with two layers of people I could move faster too. And actually make a better product imo...

1

u/2hands10fingers 9d ago

The more complex the requirements, the more meetings there tend to be

1

u/Kvsav57 9d ago

Coding was never the big part of the job.

1

u/Due_Cap_7720 9d ago

It sounds like you are wasting a lot of time then. Planning and alignment are very important.

-2

u/MajesticAd3651 10d ago

If you look at a day in software developer on YouTube, you would see they mostly spend time hanging out not doing work.

I also can't believe this 15%, even for tech lead its probably close to 50% imo.

11

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:

  1. reviewing code 

  2. maintaining test infrastructure or debugging failures

  3. 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

  4. mentoring folks/rubber ducking for a teammate 

  5. 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

u/[deleted] 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

u/theschuss 10d ago

Typical coding time is 20-30%. Note this doesn't include QA or design time. 

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

u/NPPraxis 8d ago

Try working at a bank. Meetings all day

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

u/DirtyFrenchBastard 6d ago

Didn’t you hear Claude can do all this, it’s over 🙄

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

u/jmclondon97 10d ago

Yall have girlfriends?

2

u/dzogchenism 10d ago

They’re from Canada. You wouldn’t know them.

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

u/klop2031 10d ago

Cuz you get random ass adhoc requests by seinor management

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/Teiktos 6d ago

Atlassian MCP is fucking trash bro. Try to use it via sth like executor’s CLI for reusable scripts and less context bloat through better filtering. This thing is shitting stuff like user profile image links into your context like there’s no tomorrow. 

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

u/Spunge14 10d ago

They don't have to read it

1

u/numerical_panda 10d ago

Ah, like we do with assembly code now?

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

u/No_Bend9143 10d ago

It's an incredible research tool

1

u/Distind 8d ago

The last 3 times I've had someone try to use AI for log analysis it's been entirely wrong and the answer was found in the logs faster than it took to prompt the AI by the next guy on the email chain.

This almost cost the last guy his job because of how far off it was.

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

u/haolecoder 10d ago

If AI has barely moved delivery, that’s a you problem.

1

u/GameMasterPC 10d ago

This isn’t true.

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

  1. You only need.a fraction of the team

  2. The team as a whole is under leveraged

  3. Product team sucks at deciding what they want , see 2

1

u/rboes1991 9d ago

Thank you!!! I keep saying this, as a dev.

1

u/Neither_Ad_9675 9d ago

Skill issue. Agent should do much much more then writing code

1

u/Bangoga 9d ago

Depends on the level. As a senior yeah my coding work isn't as high as it was when I was younger.

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

u/Impressive_Sleep_470 10d ago

Agreed - im seeing speedups on ny team of like 30-50%

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.

1

u/narium 9d ago

Any place with any sort of legal exposure will be doing this because "the AI wrote it that way" is not a valid defense in the courtroom.

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.

0

u/afops 9d ago

AI speeds up my non-coding tasks more than my coding tasks

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.