zlacker

It’s not that cut and dry. For a lot of reasons, I don’t do side projects. But I do choose jobs that are using technologies that will keep me marketable. So if I want to learn a new to me technology, I’ll often work some crazy hours to both learn the technology and get the work done.

Yes my company benefits from it, but so do I. For instance, given a choice of trying to come up with an idea to learn about a feature of AWS and pay money for the resources I use, and take advantage of my work AWS (Dev) account where I am an admin, I would rather do a work related project where I have the resources and I don’t have to come up with an idea and I don’t have to pay for it.

What I don’t do is “signal”. I don’t stay at work late, I don’t send emails out after hours, and I pushback if they give me unreasonable deadlines.

>>scarfa+(OP)
You’re not working.

>>Spooky+Sr
Let’s say my team had a feature to get out and the React expert said he could do it in 30 hours and he could have it done by Monday morning without working extra during the week or on the weekend.

On the other hand, say it would take me 50 hours and I knew I would have to work on the weekend because I’m not as experienced, but I thought I could still have it done by Monday.

I might be willing to volunteer, knowing it would take me longer but it would also be done on time. That extra 20 hours, I’m still working, committing code but zeal do trying to figure out the framework. I wouldn’t have a problem doing that because I am learning a new skill.

But, I wouldn’t work weekends to finish a project because I was given an unrealistic deadline.

The first scenario, the extra 20 hours benefits me and the company. The second, it just benefits the company.