The fact that he thinks LOC has anything to do with how effective he's been as an engineer is a huge red flag.
He didn't say exactly that, he said that he takes issue with his manager calling him the "least effective" person on his team. Which sure, there is some possibility that he wrote a lot of code, and it was all useless, but to be the _least_ effective while _presumably_ shipping at least some features...
Either he's incredibly, incredibly bad at what he does, or he just had the misfortune to step into the bear trap that is the Amazon PIP machine.
Knowing Amazon, he probably just got unlucky.
Then, he should have mentioned something that he improved ... Anything.
The fact that he didn't is a huge red flag.
Re:Amazon Pip Horror Story
by EthOptimist on Friday February 04, 2022 @05:18PM
(#30214147)
He mentions this because LOC is an objective metric that Amazon uses to analyze performance..
Amazon has a way to generate a lot of infrastructure with code templates. So I can push out a ton of infrastructure code in a short amount of time by simply running the generator script. So then I just need to plug and play functionality code. He could be factoring that code in with the count.
Re:Amazon Pip Horror Story
by BrokenLButton on Saturday February 05, 2022 @01:05AM
(#30218216)
^It's autogenerated code for sure, especially considering he's from AWS.
> I only have one humble request, if I submited 51k lines of code in January and my whole team submitted 68k, do not call me a "Least Effective"
Let's give him the benefit of the doubt and assume he works 10 hours 6 days a week. Of course he takes no bio breaks, doesn't eat or drink and is not required to attend any standups or status meetings or design reviews.
This nets you 15600 minutes to code. So even under these absurd conditions he has managed over 3 lines of code per minute. What a god.