this post was submitted on 22 Jul 2024
253 points (95.0% liked)

Programming

17354 readers
535 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] iAvicenna@lemmy.world 50 points 3 months ago (1 children)

sure it is the dev who is to blame and not the clueless managers who evaluate devs based on number of commits/reviews per day and CEOs who think such managers are on top of their game.

[–] Kissaki@programming.dev 7 points 3 months ago (1 children)

Is that the case at CrowdStrike?

[–] iAvicenna@lemmy.world 12 points 3 months ago (1 children)

I don't have any information on that, this was more like a criticism of where the world seems to be leading to

[–] FlorianSimon@sh.itjust.works 11 points 3 months ago (1 children)

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 8 points 3 months ago* (last edited 3 months ago) (1 children)

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 7 points 3 months ago (1 children)

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.

[–] nitefox@sh.itjust.works 2 points 3 months ago

Nono listen to me, it’s agile