6 ms·
I’m a fully remote worker. To my managers the work I do is a lot. To me it’s about 4 hours a day. There’s no deceit in this. What I tell them I’m working on i
by dvtrn 5y ago
I’m a fully remote worker.
To my managers the work I do is a lot.
To me it’s about 4 hours a day. There’s no deceit in this. What I tell them I’m working on is what I’m working on, what I’ve declared as ‘finished’ is factually ‘finished’.
To the company, I’m still contributing the things I agreed to, responsive to the people who come to me for help (as a senior) and on track with the projects assigned to me.
When the wall comes and I just cannot will myself to stare at the same problem anymore, that’s it for the day. Sometimes that takes longer than others, sometimes it’s 5 hours instead of four. Sometimes it’s a whole 8 hour day.
So..matter of perspective, I guess. The agency and autonomy are nice, though. Some people want a shorter work day given. I’ve just decided to take it.
- Seattle3503 5y ago> To me it’s about 4 hours a day. There’s no deceit in this. What I tell them I’m working on is what I’m working on, what I’ve declared as ‘finished’ is factually ‘finished’. I've come to realize this isn't always a mistake on management's part. I work at a company where developers use the full day to get tasks done because there is so much on our road map. There is absolutely no slack, when something new comes up, something else needs to drop. We are hiring, but now I spend some of my time training them. I've seen friends work for companies that keep some % of their experienced developers time idle so those devs tackle issues that might pop up.