Reply to Beck on (almost) zero-defect:
I totally agree, since I have at least one example. I boast on the fact that, my code virtually never has had a bug; in my last job, it was literally zero. Unfortunately, I have to mention it to my managers and bring it up explicitly, since “bug-free code” will receive less attention; a better job appears less of a job. I have to mention this, because managers sometimes don’t see that being possible, so they fail to measure the efficiency of inefficient people vs efficient ones; they can only compare. Hence, the truly efficient people, even 10X ones, will ironically appear as the “inefficient ones”! What they do may take a bit longer than others, but will work clockwork quietly without making noise and cause meetings and follow-up tasks. It is impossible to prove that, a delivered task could have taken 5 sprints, if done by others. When a better code is delivered, say 10x productivity comoared to others, it will look like as if it was a smaller task: 1/10th size. The only measure of complexity seems to be how long humans will struggle doing it. … Maybe the only solution is to be careful to only work in a team with people of similar code maturity; that your peers’s outputs have “comparable” levels of “defect density”.
PS. I don’t mean absolutely zero defect, but rare.
Original discussion: https://www.linkedin.com/posts/kentbeck_i-saw-a-lovely-logical-argument-for-why-activity-7277435725162102785-geG-?utm_source=share&utm_medium=member_ios
They invite you to humbleness . They deem arrogant. etc. So, as a solution: don’t join that company.
But unfortunately, unshit companies are rare, and are getting rarer (in terms of percentage).
هیچ نظری موجود نیست:
ارسال یک نظر