4 ms·
There's several types of "carrying". You have the type where one person is the visionary, is capable, but doesn't have the patience to do the grunt work and on
by chii 3y ago
There's several types of "carrying".
You have the type where one person is the visionary, is capable, but doesn't have the patience to do the grunt work and only wants to do the most prestigous or "important" shit. They do it well, but expect the rest of the team to do the thankless stuff.
This is the type i hate, and i rather not have them.
The other type is someone who is self-less, and just does the work regardless of self-interest or agenda. They will do both prestigious work, and will also do thankless work, as long as it contributes to the success of the project. They will stay late, fix up other's mistakes, etc, without complaints or expectation that others do the same.
This is the type i admire and want to work with.
- gthink 3y agoThat's a very succint description of the arrogant person and the one whom everyone mislabels as arrogant.
- rightbyte 3y agoYe. "Super stars" are often just people that stampede the other devs. Like, working together is so inefficient in bigger teams that someone let loose will appear very productive, but he is slowing down everyone else.
- icedchai 3y agoI know several who are in the second category. The problem with constantly fixing other's mistakes is the other people never learn to take responsibility. They know the people carrying the project are not going to let it fail. No matter what, whatever they did is going to get fixed.
- wiseowise 3y ago> The other type is someone who is self-less, and just does the work regardless of self-interest or agenda. They will do both prestigious work, and will also do thankless work, as long as it contributes to the success of the project. They will stay late, fix up other's mistakes, etc, without complaints or expectation that others do the same. Been there, done that, it's a career dead-end.
- oceanplexian 3y agoI used to be that person, but the problem is that you’re creating an incentive structure that doesn’t enable the management chain to identify and correct problems. A company should not be standing on the shoulders of a single engineer doing thankless work to prevent catastrophe.