One of my coworkers is really good at churning out code in a short amount of time that will do the job. He's not so good at abstracting his code to make it more reusable, even when he has time.
Another coworker is a hard-working cleanup guy, he doesn't mind getting his hands dirty and spend several long days cleaning up a decade of cruft. But he doesn't always appreciate subtle differences in code, so sometimes introduces regressions.
Third guy we have has excellent domain knowledge which is invaluable, yet is an otherwise average programmer.
I've got my set of things that I'm really good at, and the things I'm not particularly great at.
We don't have a rock star dev, but we have people who are good at different things and we take that into account when planning and executing projects.
One of my coworkers is really good at churning out code in a short amount of time that will do the job. He's not so good at abstracting his code to make it more reusable, even when he has time.
Another coworker is a hard-working cleanup guy, he doesn't mind getting his hands dirty and spend several long days cleaning up a decade of cruft. But he doesn't always appreciate subtle differences in code, so sometimes introduces regressions.
Third guy we have has excellent domain knowledge which is invaluable, yet is an otherwise average programmer.
I've got my set of things that I'm really good at, and the things I'm not particularly great at.
We don't have a rock star dev, but we have people who are good at different things and we take that into account when planning and executing projects.