4 ms·

I like all your points, but option 2 is very intriguing. I've never had the time for that, given I use all my mental and physical capacities for my day job. S

I like all your points, but option 2 is very intriguing. I've never had the time for that, given I use all my mental and physical capacities for my day job. So I'm conflicted; I just don't think I'd have enough time to do a side project to the standards I'd expect of myself. I think that's also why many posters here are saying 'use some new language feature X to make your work project more exciting' - basically adding a side project into your day job. [I think that road can lead to ruin, if you're making it harder on the next person to work on the code. Be careful and considerate.]

ebbv 12y ago
I know a lot of people work that way (using new technologies in their day jobs) but personally I take my day job too seriously to do that. I learn new technologies by doing side projects. Then once I feel comfortable with them I can start using them in my day job. I don't want to look my boss or coworkers in the face and say "Yeah that fuck up was because I was using this project to learn a new thing." I think you're over estimating how much time you need for a side project. You can even just spend a couple hours on a couple weekends a month on something. Or even every other month. You don't have to work on it every day or anything. That's the great thing about it being a side project. There's no rush. No timetable other than whatever you choose for yourself.