3 ms·

>>> I was probably the only non-hostile one, even friendly, to him at work by that point If you did not help him, this is highly subjective

by fasteo 4y ago

karamanolev 4y ago
Not to me. If they wanted to be a frontend dev, billed themselves as such and didn't want to take on backend duties, then they did their fair share by speccing the API and providing that. They have no direct obligation to work on the backend.
franciscop 4y ago
I did try to help him in any way I could, but didn't know the language he was using so I was not able to actually code for him. Couple of examples: I made a Node.js program to help him debug why a 3rd-party endpoint he had to call wasn't working, documented the endpoints he was doing (learned Swagger for that), and acted as intermediary between him and our manager to try to reduce the scope of the work or to at least ship in two parts.
clnq 4y ago
It sounds fair to me that a developer hired to do front-end work does not want to do back-end. I can't blame him for setting boundaries, especially in a dysfunctional management workplace. I've been in the back-end developer's situation and I still didn't think it is fair for others to re-specialize and help me in a large company. It's neither mine nor their fault the management is incompetent. If this was a small company with a close-knit team covering for each other's blind spots, then it could be different. But what was described was at least a medium-sized company where in all likelihood the manager was paid a good amount of money to be competent at their job. And instead the manager played games, saw the results of their actions, tried to slide the blame onto the person they made fail, and lost good engineers. The situation was completely in the manager's hands and so are the results. If we start expecting people to manage themselves under the managers, then what is the manager doing? Are they just a liability to the company with no upside? The role doesn't make sense then.

>>> I was probably the only non-hostile one, even friendly, to him at work by that point If you did not help him, this is highly subjective

by fasteo 4y ago

>>> I was probably the only non-hostile one, even friendly, to him at work by that point If you did not help him, this is highly subjective

karamanolev 4y ago

Not to me. If they wanted to be a frontend dev, billed themselves as such and didn't want to take on backend duties, then they did their fair share by speccing the API and providing that. They have no direct obligation to work on the backend.

franciscop 4y ago

I did try to help him in any way I could, but didn't know the language he was using so I was not able to actually code for him. Couple of examples: I made a Node.js program to help him debug why a 3rd-party endpoint he had to call wasn't working, documented the endpoints he was doing (learned Swagger for that), and acted as intermediary between him and our manager to try to reduce the scope of the work or to at least ship in two parts.

clnq 4y ago

It sounds fair to me that a developer hired to do front-end work does not want to do back-end. I can't blame him for setting boundaries, especially in a dysfunctional management workplace. I've been in the back-end developer's situation and I still didn't think it is fair for others to re-specialize and help me in a large company. It's neither mine nor their fault the management is incompetent. If this was a small company with a close-knit team covering for each other's blind spots, then it could be different. But what was described was at least a medium-sized company where in all likelihood the manager was paid a good amount of money to be competent at their job. And instead the manager played games, saw the results of their actions, tried to slide the blame onto the person they made fail, and lost good engineers. The situation was completely in the manager's hands and so are the results. If we start expecting people to manage themselves under the managers, then what is the manager doing? Are they just a liability to the company with no upside? The role doesn't make sense then.