• FlorianSimon@sh.itjust.works
    link
    fedilink
    arrow-up
    11
    ·
    2 months ago

    I’ve been working as a professional programmer for many years and have never ever seen this kind of evaluation, not even once. I’m pretty convinced it’s an exception rather than a rule. And I’d add that it’s probably a very rare exception.

    • iAvicenna@lemmy.world
      link
      fedilink
      arrow-up
      8
      ·
      edit-2
      2 months ago

      NGL I am also a second hand witness to it. This particular example may be a few but there are a lot of others to the same effect: evaluating performance based on number of lines of code, trying to combine multiple dev responsibilities into a single position, unrealistic deadlines which can usually be met very superficially, managers looking for opportunities to replace coders with AI and further tasking other devs with AI code checking responsibilities, replacing experienced coders with newly graduates because they are willing to work more for less. All of these are some form of quantity over quality and usually end up with some sort of crisis.

      • Ephera@lemmy.ml
        link
        fedilink
        arrow-up
        7
        ·
        2 months ago

        Yeah, and at the end of the day, it is just as much a very rare exception that a dev actually gets enough time to complete their work at a level of quality they would take responsibility for.
        Hell, it is standard industry practice to ship things and then start fixing the issues that crop up.