▲ 306 ▼ A devious interview (more images in post) (files.catbox.moe) submitted 1 year ago by felixwhynot@lemmy.world to c/programmerhumor@lemmy.ml 16 comments fedilink hide all child comments cross-posted from: https://lemmy.blahaj.zone/post/29211735 If the images here don't load, try using a different frontend.
[–] someguy3@lemmy.world 15 points 1 year ago* (last edited 1 year ago) (3 children) What was the reason for turning the department over? permalink fedilink source parent hideshow 3 child comments replies: [–] Malix@sopuli.xyz 15 points 1 year ago corporate mandated stupidity? permalink fedilink source parent [–] punkwalrus@lemmy.world 11 points 1 year ago (1 child) You got me. I think it was because our group was under one contract set of hires (I was an employee, but some of these people were still part of a contract), which is why we weren't let go immediately. But sometimes you get some manager who doesn't want the OLD people, but a FRESH NEW set of people. For example, when the entire QA department was let go an outsourcer, all the documentation we made was thrown out the window because "that was the old way!" And the next major software release was a disaster. And we were going from a 16 bit client (Windows 3.1x based) version to the new 32 bit (Windows 95/98-native) version, and the QA/testing was not really part of the process. "Who are these product testers, and why are they so negative about the product? LOSE 'EM! They only see mistakes, there's no room for that kind of attitude, and it slows the whole release cycle down." Corporate stupidity. permalink fedilink source parent hideshow 1 child comment replies: [–] someguy3@lemmy.world 1 point 1 year ago Yeah that was actually what I figured. Though I'd only do it if the group couldn't change ways for whatever reason. That should be the go to, remaking the group is the nuclear option. permalink fedilink source parent
[–] Malix@sopuli.xyz 15 points 1 year ago corporate mandated stupidity? permalink fedilink source parent
[–] punkwalrus@lemmy.world 11 points 1 year ago (1 child) You got me. I think it was because our group was under one contract set of hires (I was an employee, but some of these people were still part of a contract), which is why we weren't let go immediately. But sometimes you get some manager who doesn't want the OLD people, but a FRESH NEW set of people. For example, when the entire QA department was let go an outsourcer, all the documentation we made was thrown out the window because "that was the old way!" And the next major software release was a disaster. And we were going from a 16 bit client (Windows 3.1x based) version to the new 32 bit (Windows 95/98-native) version, and the QA/testing was not really part of the process. "Who are these product testers, and why are they so negative about the product? LOSE 'EM! They only see mistakes, there's no room for that kind of attitude, and it slows the whole release cycle down." Corporate stupidity. permalink fedilink source parent hideshow 1 child comment replies: [–] someguy3@lemmy.world 1 point 1 year ago Yeah that was actually what I figured. Though I'd only do it if the group couldn't change ways for whatever reason. That should be the go to, remaking the group is the nuclear option. permalink fedilink source parent
[–] someguy3@lemmy.world 1 point 1 year ago Yeah that was actually what I figured. Though I'd only do it if the group couldn't change ways for whatever reason. That should be the go to, remaking the group is the nuclear option. permalink fedilink source parent