Comment

Comment on AI slows down some experienced software developers, study finds

AA5B@lemmy.world ⁨12⁩ ⁨hours⁩ ago

I’m seeing exactly the opposite. It used to be the junior engineers understood they had a lot to learn. However with AI they confidently try entirely wrong changes. They don’t understand how to tell when the ai goes down the wrong path, don’t know how to fix it, and it takes me longer to fix.

So far ai overall creates more mess faster.

Don’t get me wrong, it can be a useful tool you have to think of it like autocomplete or internet search. Just like those tools it provides results but the human needs judgement and needs to figure out how to apply the appropriate results.

My company wants metrics on how much time we’re saving with ai, but

I have to spend more time helping the junior guys out of the holes dug by ai
it’s just another tool. There’s not really a defined task or set time. If you had to answer how much time autocomplete saved you, could you provide any sort of meaningful answer?

source

Sort:hotnew top

MangoCats@feddit.it ⁨10⁩ ⁨hours⁩ ago
I’ve always had problems with junior engineers going down bad paths, since before there was Google search - let alone AI.

So far ai overall creates more mess faster.

Maybe it is moving faster, maybe they do bother the senior engineers less often than they used to, but for throw-away proof of concept and similar stuff, the juniors+AI are getting better than the juniors without senior support used to be… Is that a good direction? No. When the seniors are over-tasked with “Priority 1” deadlines (nothing new) does this mean the juniors can get a littler further on their own and some of them learn from their own mistakes? I think so.

Where I started, it was actually the case that the PhD senior engineers needed help from me fresh out of school - maybe that was a rare circumstance, but the shop was trying to use cutting edge stuff that I knew more about than the seniors. Basically, everything in 1991 was cutting edge and it made the difference between getting something that worked or having nothing if you didn’t use it. My mentor was expert in another field, so we were complimentary that way.

My company (now) wants metrics on a lot of things, but they also understand how meaningless those metrics can be.

I have to spend more time helping the junior guys out of the holes dug by ai, making it net negative

Shame. There was a time that people dug out of their own messes, I think you learn more, faster that way. Still, I agree - since 2005 I have spend a lot of time taking piles of Matlab, Fortran, Python that have been developed over years to reach critical mass - add anything else to them and they’ll go BOOM - and translating those into commercially salable / maintainable / extensible Qt/C++ apps, and I don’t think I ever had one “mentee” through that process who was learning how to follow in my footsteps, the organizations were always just interested in having one thing they could sell, not really a team that could build more like it in the future.

it’s just another tool.

Yep.

If you had to answer how much time autocomplete saved you, could you provide any sort of meaningful answer?

Speaking of meaningless metrics, how many people ask you for Lines Of Code counts, even today?

source
- AA5B@lemmy.world ⁨7⁩ ⁨hours⁩ ago
  
  Shame. There was a time that people dug out of their own messes, I think you learn more, faster
  
  Yes, that’s how we became senior guys. But when you have deadlines that you’re both on the hook for and they’re just floundering, you can only give them so much opportunity. I’ve had too many arguments with management about letting them merge and I’m not letting that ruin my code base
  
  Speaking of meaningless metrics, how many people ask you for Lines Of Code counts, even today?
  
  We have a new VP collecting metrics on everyone, including lines of code, number of merge requests, times per day using ai, days per week in the office vs at home
  
  source
  - MangoCats@feddit.it ⁨5⁩ ⁨hours⁩ ago
    
    I’ve had too many arguments with management about letting them merge and I’m not letting that ruin my code base
    
    I guess I’m lucky, before here I always had 100% control of the code I was responsible for. Here (last 12 years) we have a big team, but nobody merges to master/main without a review and screwups in the section of the repository I am primarily responsible for have been rare.
    
    We have a new VP collecting metrics on everyone, including lines of code, number of merge requests, times per day using ai, days per week in the office vs at home
    
    I have been getting actively recruited - six figures+ - for multiple openings right here in town (not a huge market here, either…) this may be the time…
    
    source
    AA5B@lemmy.world ⁨4⁩ ⁨hours⁩ ago
    Interesting idea… we actually have a plan to go public in a couple years and I’m holding a few options, but the economy is hitting us like everyone else. I’m no longer optimistic we can reach the numbers for those options to activate
    
    source