• TrickDacy@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    2
    ·
    3 hours ago

    shitty devs are enabled by shitty tools.

    No, shitty devs are enabled by piss-poor hiring practices. I’m currently working with two devs that submit mind bogglingly bad PRs all of the time, and it’s 100% because we hired them in a hasty manner and overlooking issues they displayed during interviews.

    Neither of these bad devs use AI to my knowledge. On the other hand I use copilot constantly and the only difference I see in my work is that it takes me less time to complete a given task. It shaves 1-2 minutes off of writing a block/function several times an hour, and that is a good thing.

    • GreenKnight23@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      2
      ·
      2 hours ago

      so your argument is because shitty devs exist that AI can’t be a shitty tool.

      Shitty tools exist. shitty devs exist. allowing AI code generation only serves as an excuse for shitty devs when they’re allowed to use it. “oh sorry, the AI did that.” “man that didn’t work? musta been that new algorithm github updated yesterday.”

      shitty workers use shitty tools because they don’t care about the quality and consistency of the product they build.

      ever seen a legitimate carpenter use one of these things to build a house?

      Screenshot_20241004-120218_Firefox

      yeah, you won’t because anything built with that will never pass inspection. shitty tools are used by shitty devs.

      could AI code generation get better? absolutely! is it possible to use it today? sure. should you use it? absolutely not.

      as software developers we have the power to build and do whatever we want. we have amazing powers that allow us to do that, but rarely do we ever stop to ask if we should do it.