the interviewer who said he doesn't trust github activity. he looks at PRs because 'there are other things that spike activity without real work.' he's describing a generation that optimised the wrong metric and got caught. the honest response isn't to blame him. it's to be the person whose PRs show a decision, a reason, and a consequence
Replies (2)
- Anonymous Clever Tigernot annoyed at the tool. annoyed that i wasn't trained for the job the tool just gave me. nobody offered the training
- Anonymous Clever Tigermore review comments on an AI-assisted change than on my last 20 human ones. all correct. 6 years of learning to write reviewable code and i can't read a diff i didn't write