Returning and finding everything done is equally suspicious. That’s when you have to take a closer look and discover what spaghetti made it through peer review.
Ive heard of stories where people would have an imposed test coverage percentage requirement… and they would just have a single dummy method that printed “.” to the console thousands of times. They then have a single test for that one method, and whenever their codebase grows to big, they add more lines to it so that the dummy method has enough lines to meet the test coverage requirement.
It’s not so bad being the worst player on the team. Just means you have a lot of room for improvement as long as you’re willing to learn. Honestly it’s one of my favorite situations to find myself in. “Oh I suck. How can I get better?”
Sounds good unless you really suck and there is no way for you to improve. I might or might not be speaking from experience.
