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.
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?”
I’m having that same imposter syndrome feeling right now. But one of the SMEs at work today randomly complained to me about another agent and his lack of caring/learning and thanked me for how I am. So. Sometimes it works out well as long as you’ll listen and learn. You can always learn more it just takes time.
In most crafts, and I consider software development one, there’s rarely no way to improve. The problem arises if the client or the employer wants you to improve too quick, faster than you could, and sometimes faster than even possible.
But to be fair, sometimes developer doesn’t want to improve either
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.
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.
Or worse, it means you’re not as good as you thought you were.
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.
I’m having that same imposter syndrome feeling right now. But one of the SMEs at work today randomly complained to me about another agent and his lack of caring/learning and thanked me for how I am. So. Sometimes it works out well as long as you’ll listen and learn. You can always learn more it just takes time.
In most crafts, and I consider software development one, there’s rarely no way to improve. The problem arises if the client or the employer wants you to improve too quick, faster than you could, and sometimes faster than even possible.
But to be fair, sometimes developer doesn’t want to improve either
Imposter Syndrome, I choose you!!
Also, all the automated tests were commented out.
Checking the ci logs for the past week, like:
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.
Percentage of lines covered by tests is such a terrible metric.
All metrics are terrible when used for anything other than objective analysis
Yeah, every metric that can be applied automatically ends up becoming useless if people are incentivized to break it
Relevant xkcd
There’s always one. Thanks for finding it ❤️