However I am curious how others feel about learning on your own time. I do a fair bit of that (and the company often benefits as a result) but there is hardly a set line between working and learning in our line of work, its definitely a continuum.
This is much more rewarding than doing unpaid work for your boss on code that will probably never see the light of day anyway.
There is a lot to learn by collaborating with other people on code projects of this nature.
I love programming and working out how to solve a problem, but if it something my employer makes money off then they can give me the time to fix it. In my own time, I work on my own projects and challenges. Be it the automation bot I have running in my house or the games that me and a few friends create.
Doing work stuff in your own time can - and does - lead to the expectation that you'll do it more, so the business accounts for that and will possibly even count it against others that don't do it.
Its also a shane that the former is what most people find themselves in. A means to an end in a world that isnt very kind to everyone.
There are those that spend off-time programming, just not for their employer's tasks.
The quid-pro-quo of employee-employer loyalty is largely gone these days, so it's not unreasonable to only work the hours you're compensated for.
I'm using the term loyalty for lack of a better term. There was a time when employees would often go above and beyond for their employers, because the reverse was also often true. Roughly, the shift away from the "lifetime employment" model.
Things like:
- Somewhere in the 1980's, when layoffs started to happen even in relatively financially healthy companies
- The move from pensions to 401k's
- The shift of a higher percentage of healthcare costs to the employee's portion
- More focus on hiring outsiders into higher level positions, versus training/placing internal candidates
Specifically, I might be incented to occasionally "work for free" if I thought the company would, for example, not lay me off during a particularly rough financial period.
I think that people who work on their employer's projects during their own time are unimaginative - they could be writing their own software for their own benefit but they instead choose to make their employer rich and not see any of that compensation themselves.
This is of course assuming you're drawing a salary from the company and you're not mostly paid in equity, in which case putting in free hours might make more sense if you can make the product profitable.
I think its a bit rude for you to suggest someone who brings some work home has no life. Many developers are passionate about their job, they love learning and most importantly they love a good challenge. You don't stop thinking about a challenge at work as soon as the clock hits 5.