4 ms·
My guess would be that for non-technical people it's much easier to schedule visible work (frontend) vs invisible work (backend). Are the people that are managi
by overgard 2y ago
My guess would be that for non-technical people it's much easier to schedule visible work (frontend) vs invisible work (backend). Are the people that are managing you less technical possibly? If you have a good technical lead they should probably understand the work to give you, but PM's and scrum masters frequently don't understand.
I guess the other thing I'd ask is, why the strong resistance to frontend work? I get not seeking jobs for it or not preferring it, I don't seek those either, but for my own personal productivity I like to have a decent idea how to build a frontend in case I'm waiting on someone that's overloaded in order to deliver my feature etc. It can be helpful for a career if you don't have to frequently tell people "I can't do that", vs, "it's not my strong suit but I can pitch in"
- throwawaybcknd 2y ago> why the strong resistance to frontend work? I am bad at it. So they get an under-performing employee with low morale and I get complaints about my work. > It can be helpful for a career if you don't have to frequently tell people "I can't do that", vs, "it's not my strong suit but I can pitch in" I usually do the latter, but then in December I thought I'd better make sure, reasoning that things go better the clearer I am ahead of time. That was the first time I tried saying, "Seriously, I can't do that kind of work." This time I got nothing but that kind of work.