Going the extra mile or just "do what you were paid for" ?
I think this should be a calculation of an ROI and is definitely situational (case by case).
Do you have the bandwidth to put in the extra time?
Are you in a healthy state mentally and physically to do so?
Should you go the extra mile when it's a sinking ship?
Are you up for a promotion?
Do you need to help pull the weight of a peer/teammate who is having a tough time?
Generally... everyone is different and unique-- they each have something to offer and definitely brings something to the table. And "doing what they're paid for" sounds like they're contributing in some capacity, so that's a good thing 😃and imo I don't think there's anything wrong with that.
Here's a hypothetical/thought experiment:
You're working on a React app and this is your expertise and your crushing it with commits. Fellow teammate is coming from angular or is just new to frontend development or maybe switching careers from a more sysadmin position or maybe they're going through some family troubles at home you're unaware of 🤷🏽♂️; regardless your peer is moving a lot slower or missing somethings, or isn't adhering to "best practices" or doesn't seem to be putting in maximum effort. However, one day you run into a heisenbug you get stuck, you can't track down where or what the problem is, your peer in their unknown infinite wisdom and knowledge of networking knows and tracks down what it is thus solving the problem in a matter of seconds.
tldr; people will always surprise you, and everyone has something to bring to the table. The irony is it's usually the unsuspecting.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think this should be a calculation of an
ROIand is definitely situational (case by case).Generally... everyone is different and unique-- they each have something to offer and definitely brings something to the table. And "doing what they're paid for" sounds like they're contributing in some capacity, so that's a good thing 😃and
imoI don't think there's anything wrong with that.Here's a hypothetical/thought experiment:
You're working on a React app and this is your expertise and your crushing it with commits. Fellow teammate is coming from
angularor is just new to frontend development or maybe switching careers from a more sysadmin position or maybe they're going through some family troubles at home you're unaware of 🤷🏽♂️; regardless your peer is moving a lot slower or missing somethings, or isn't adhering to"best practices"or doesn't seem to be putting inmaximum effort. However, one day you run into aheisenbugyou get stuck, you can't track down where or what the problem is, your peer in their unknown infinite wisdom and knowledge of networking knows and tracks down what it is thus solving the problem in a matter of seconds.