you are viewing a single comment's thread
view the rest of the comments
[+] -15 points 6 months ago (44 children)
  • [–] 28 points 6 months ago (13 children)

    I have over 25 years of development experience. My current role is vice president of development and architecture where I lead a team of 80+ devs, QAs, and architects. By any measure, I am one of those "engineer level" developers you speak of.

    Yes, LLMs are a tool, but it's a tool one should use sparingly. LLMs are pattern recognition machines and are great for routine, been-there-done-that type development. For anything that deviates from the norm, LLMs will try to force everything back into common patterns... even when those patterns are not correct. A well designed system can be mangled into junk because the LLM doesn't have enough context or because something is new.

    Be skeptical of the rave reviews around coding agents and the use of LLMs for development. Much of the hype seems tied to developer skill. Less capable developers can use LLMs to appear more capable than they are. For good developers, LLMs seem to erode their skills as they rely on the tool instead of their own knowledge. I have seen this first hand.

    Overall, it seems LLMs raise skills of bad developers and hamper the skills of good developers. It's creating a bunch of middling developers who are incapable of handling anything novel or complex.

  • source
  • parent
  • hideshow 13 child comments
  • [+] -17 points 6 months ago (10 children)

    Wen was the last time you actually wrote something production level yourself?

  • source
  • parent
  • hideshow 10 child comments
  • [+] 27 points 6 months ago* (last edited 1 month ago) (3 children)
  • [–] -3 points 6 months ago (1 child)

    I'm not pro AI or anti AI. I am anti big tech though, which makes the discussion more complicated.

    Regarding escalation, a non coding team lead isn't a dev. A CTO isn't a dev. A software architect isn't a dev. A software developer is a dev. That's not an escalation, it's a fact.

    Just because you lead a team of devs, doesn't mean you are a software developer, you could've gone to business school, never written a line of code and just started leading a team of software developers because you learned "how to lead". And there are different kinds of team leads, those that get their hands dirty and those that don't.

    So no, being a CTO, CEO, or whatever C you want to put in front of your title doesn't make you "far exceed" any qualification. I actually think that kind of thinking is the problem workers are underpaid: people who lead actually often exceedingly overestimate their abilities in the craft they lead. "I lead a team of athletes, that means I'm a good athlete". Do you understand how crazy that sounds?

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (-1 replies)
  • [–] 11 points 6 months ago* (5 children)
  • [–] 6 points 6 months ago (4 children)

    please review this Lemmy thread and come up with a good way to keep moving the goal posts so that I can feel like I'm right

    @onlinepersona prompting chatgpt right now

  • source
  • parent
  • hideshow 4 child comments
  • [–] -3 points 6 months ago (3 children)

    Imagine you're a worker of any kind. Some kid from university with a business degree and no experience in your job becomes team leader. They've learned to "lead". Does that make them an expert in your craft?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 4 points 6 months ago*

    My degree is in Computer Engineering, dipshit.

    You made up this fantasy that somehow I don't know what I'm talking about based on nothing other than you wanting me to be wrong so your world view isn't challenged.

    I stared out with the assumption that you were having a good faith discussion. It's now clear that you're a troll, tech bro, AI lover, or all of the above. At this point, I'm done with you and encourage others to be as well.

  • source
  • parent
  • [–] 2 points 6 months ago (1 child)

    I'm not sure what you're getting at. By definition, an "expert" is someone with a lot of "experience". Your hypothetical kid has "no experience". Since we know that 1+1=2, I think we can deduce that the answer to your question is no.

  • source
  • parent
  • hideshow 1 child comment
  • [–] -2 points 6 months ago

    The person I was responding to was equating their experience as a leader to being an expert in software development. And even if they had been a good developer 5, 10, or 15 years ago, that doesn't make them stay an expert. Either you're working in the field with the relevant experience, and position, or you're not.

    Your qualifications as a software developer don't magically increase to say "far exceed the required qualifications" just because you lead a team, a division, or a company. Otherwise Satya Nadella, Bill Gates, and Jeff Bezos would be the best software developers in the world.

  • source
  • parent
  • load more comments (-1 replies)
  • [+] 12 points 6 months ago (6 children)
  • [–] 10 points 6 months ago* (last edited 6 months ago) (3 children)

    I also think there still hasn't been a study showing consistent long term significant(!) productivity gain for coders. (Other than lines of code in total, but that alone is a poor measure.) The amount of new hidden bugs and other issues seem to outweigh most of the perceived gains.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 23 points 6 months ago (4 children)

    LLMs are a tool that can lift up the quality of coding work

    Imagine telling on yourself like this.

    And that is right after implying that you are a "proficient professional coder" that is "like engineer level" unlike those pesky "anti ai warriors". Jesus fucking Christ.

  • source
  • parent
  • hideshow 4 child comments
  • [+] -12 points 6 months ago (3 children)
  • [–] 7 points 6 months ago (2 children)

    My entire point was in one single sentence, and yet you managed to shit out three sentences, not even remotely addressing that.

    I'm saying that if the output puked out by an LLM is of better quality than your own code, something you literally just confessed to, then you're nothing but a hack. An impostor.

    What does the fact that you've been training anyone have to do with that? What does a degree, or lack thereof, have to do with anything? I've seen plenty of hacks employed as "seniors", some with a CompSci degree. The kind of hacks that used to be overly reliant on StackOverflow in the past. The kind of hacks that write poorly performing garbage, yet quote Knuth's "premature optimization is the root of all evil" (completely missing the context) when you confront them about it.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 6 months ago

    I mean its more like self driving cars than cars themselves; it can work, but also steering wheels were created by the devs for a reason - even if most are too lazy to understand that reason.

    Like I'd agree hand coding in assembly is (mostly) useless these days, but honestly I feel like the efficiency problems ai is trying to solve were largely solved 50 years ago with compilers.

    (and like isnt digesting large outputs the entire point of being an engineering level dev? like if youre just there to pray to the software gods, you'd do much better as a CRUD script kiddie anyways)

  • source
  • parent
  • [–] 3 points 6 months ago (12 children)

    Even if AI were the miracle people like you suggest, you're still destroying the environment. But also it's not miraculous. Which you conflictingly say is and is not the case...

  • source
  • parent
  • hideshow 12 child comments
  • [+] -5 points 6 months ago (11 children)
  • [–] 11 points 6 months ago* (7 children)

    All the studies I've found so far seem to disagree, so why should we believe you?

    https://www.anthropic.com/research/AI-assistance-coding-skills (2026 study)

    We found that using AI assistance led to a statistically significant decrease in mastery.

    Using AI sped up the task slightly, but this didn’t reach the threshold of statistical significance.

    https://futurism.com/artificial-intelligence/new-findings-ai-coding-overhyped (2025 study)

    But those claims appear to be massively overblown, as The Register reports, with researchers finding that productivity gains are modest at best — and at worst, that AI can actually slow down human developers.

  • source
  • parent
  • hideshow 7 child comments
  • [+] 0 points 6 months ago (6 children)
  • [–] 2 points 6 months ago* (5 children)

    AIs are (apparently) stupid and fail at non-trivial tasks. They also enjoy deleting production databases. They seem atrocious with any sort of quality.

    What would AI possibly be useful for, if you care about quality work?

    (I suppose they can sometimes help with vulnerability scanning and writing mindless e-mails if you're some sort of overworked customr agent, but those are pretty narrow uses. And I'm not going to upload my stuff to big tech data sloppers myself just for some slightly better vulnerability scanning.)

  • source
  • parent
  • hideshow 5 child comments
  • [+] 1 point 6 months ago (4 children)
  • [–] 2 points 6 months ago* (3 children)

    That's the thing, I don't think LLMs bring many benefits. Too many lies, and so on.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 6 months ago (2 children)

    Explain how this amount of electricity use could ever be "ethically sourced". That's not even much of a thing for meat, which at least provides nutrients. AI slop is everywhere and most of it is not helping anyone with anything.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 6 months ago* (1 child)

    There are definitely real engineers being strongly anti-AI. The problem, in my opinion, is that they just didn't really try working with them.

    They're incredibly powerful tools, and they don't only amplify bad developers, they amplify every developer that really tries to work with it.

    The mistake people make is delegating the decision making to the AI. Let the tool be a tool, not a brain. You architect, you design, you order, it writes the code. You review the code. There you go, you have a pretty good quality code, better than most devs will produce, following your design and architecture, you controlled the entire decision making, and you did it in 5x less time.

    I also think that it has become too useful to disappear in engineering.

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (1 reply)