4 ms·

Lot of BS excuses in there. The ones about nitpicking in reviews too, if the comment is a tiny nitpick then surely it's trivial to fix? I regularly fix a whole

by sfn42 3y ago

Lot of BS excuses in there. The ones about nitpicking in reviews too, if the comment is a tiny nitpick then surely it's trivial to fix? I regularly fix a whole bunch of minor things people comment on in minutes, it only takes long if it's a big change. You can also work on other stuff while waiting for reviews. Similarly one guy complained about pipeline runs, like what? Does it take hours? Are you just waiting for it to finish? Are you not running tests locally first?

hahahafevs 3y ago
Most of these complaints are from people that are essentially causing the problems they complain About. They just can’t see past “must write garbage code as fast as possible” Writing docs? Waste of time Reviews? Waste of time. Usability to other engineers? waste of time. Waiting for CI because they can’t be bothered to test thing locally first? Waste of time. Stakeholder approval? lol waste of time, we don’t care if people want the software we write. Having any idea how anything works outside of whatever tiny thing being worked on? Waste of time.
- RetroTechie 3y ago
  > Most of these complaints are from people that are essentially causing the problems they complain About. They just can’t see past “must write garbage code as fast as possible” +1. The article summarizes well as: reasons not to ship code asap. Do it right the 1st time. Failing that: make sure any fixes absolutely, 100% fix the problem, are well tested & don't cause regressions. Isn't [determine requirements], running builds, QA etc supposed to take time? Is development velocity even a goal worth striving for? Whatever you kick out the door, could be on others' systems for ages.
dilyevsky 3y ago
At one former gig we pulled telemetry from devs machines and lo and behold - the biggest complainers ran the pipeline twice a week or something. At this point i am convinced surveys is the worst way to go about “measuring” productivity. People are just going to tell you what they think you want to hear mixed with some self-serving bs and you will end up pouring resources into fixing the wrong things

by sfn42 3y ago

hahahafevs 3y ago

Most of these complaints are from people that are essentially causing the problems they complain About. They just can’t see past “must write garbage code as fast as possible” Writing docs? Waste of time Reviews? Waste of time. Usability to other engineers? waste of time. Waiting for CI because they can’t be bothered to test thing locally first? Waste of time. Stakeholder approval? lol waste of time, we don’t care if people want the software we write. Having any idea how anything works outside of whatever tiny thing being worked on? Waste of time.

RetroTechie 3y ago
> Most of these complaints are from people that are essentially causing the problems they complain About. They just can’t see past “must write garbage code as fast as possible” +1. The article summarizes well as: reasons not to ship code asap. Do it right the 1st time. Failing that: make sure any fixes absolutely, 100% fix the problem, are well tested & don't cause regressions. Isn't [determine requirements], running builds, QA etc supposed to take time? Is development velocity even a goal worth striving for? Whatever you kick out the door, could be on others' systems for ages.

dilyevsky 3y ago

At one former gig we pulled telemetry from devs machines and lo and behold - the biggest complainers ran the pipeline twice a week or something. At this point i am convinced surveys is the worst way to go about “measuring” productivity. People are just going to tell you what they think you want to hear mixed with some self-serving bs and you will end up pouring resources into fixing the wrong things