4 ms·

I believe pretty strongly in having a side project, and working on it at work, but only when I think the side project is something that directly (20% Google mod

I believe pretty strongly in having a side project, and working on it at work, but only when I think the side project is something that directly (20% Google model) or indirectly (skills) benefits the company. Seriously - we aren't digital coolies. We are highly paid surgeons. You wouldn't for a second fire the brain surgeon for reading about a new type of surgery that he can't put to immediate use between operations. Hell no. Its the same with node.js or ember.js or whatever you think the new hotness is that you want to experiment with. You are trying to see around corners and skate to where the puck will be. Sometimes its not obvious how node.js (or whatever) is going to help. You need to balance this against your current role, but 20% sounds about right to me. This is good for the employer. If the employer doesn't get that then you should get a new employer.

ErikAugust 14y ago
"I believe pretty strongly in having a side project, and working on it at work, but only when I think the side project is something that directly (20% Google model) or indirectly (skills) benefits the company" Right. As long as it directly or indirectly benefits the company. In software development, it can be really beneficial to the employer. But I also agree with the example of a PR guy working on his stand-up routine. That probably isn't something you want your employee doing during prime time for an hour a day.
k3n 14y ago
I totally agree that we need continuing education, such as your analogy of the surgeon, but the article specifically mentions scenarios where the side-jobs are completely unrelated to the primary job. I've witnessed this myself, had a guy working on side-projects while on our dime. He was lucky not to get fired on the spot, because pretty much every employment agreement strictly prohibits working a 2nd paid job while you're using company resources whether that's time during the working day, or the company copier/internet, etc. If you're such a bigshot that you can negotiate the ability to work a 2nd job while on-the-clock for your day job, then more power to you, but I'm sure that's extremely rare. If you want to experiment with some new tech -- and you've been allocated the time for it by your superior(s) -- then by all means play around. But in my experience, there's typically at most only a few in each department whose formal role includes these types of projects, and they're always skunkworks-like projects that rapid prototyping or POC-like, and never a full implementation (unless you choose to go forward with it of course). This is the essence of R&D, which is there solely to make sure the business survives -- not you.

ErikAugust 14y ago

"I believe pretty strongly in having a side project, and working on it at work, but only when I think the side project is something that directly (20% Google model) or indirectly (skills) benefits the company" Right. As long as it directly or indirectly benefits the company. In software development, it can be really beneficial to the employer. But I also agree with the example of a PR guy working on his stand-up routine. That probably isn't something you want your employee doing during prime time for an hour a day.

k3n 14y ago

I totally agree that we need continuing education, such as your analogy of the surgeon, but the article specifically mentions scenarios where the side-jobs are completely unrelated to the primary job. I've witnessed this myself, had a guy working on side-projects while on our dime. He was lucky not to get fired on the spot, because pretty much every employment agreement strictly prohibits working a 2nd paid job while you're using company resources whether that's time during the working day, or the company copier/internet, etc. If you're such a bigshot that you can negotiate the ability to work a 2nd job while on-the-clock for your day job, then more power to you, but I'm sure that's extremely rare. If you want to experiment with some new tech -- and you've been allocated the time for it by your superior(s) -- then by all means play around. But in my experience, there's typically at most only a few in each department whose formal role includes these types of projects, and they're always skunkworks-like projects that rapid prototyping or POC-like, and never a full implementation (unless you choose to go forward with it of course). This is the essence of R&D, which is there solely to make sure the business survives -- not you.