31–40 of 56 posts
If an employee's productivity at their day job is not acceptable, then hopefully the employee no longer has a job there.
I can't agree with any of this article. >> It’s a problem because side projects create a talent bubble of people who aren’t fully engaged and are just doing enough at their "real" or full-time job to get by until their startup is up and running. This means their productivity suffers at their full-time job, an expense the employer ends up paying. The side project owners justify it by assuming it will only be for a sho…
"This means their productivity suffers at their full-time job, an expense the employer ends up paying." Incorrect. My side projects have made me a better developer in every way, which actually saves my employers money over the long-term. I learn new techniques, skills, and tools off-the-clock. The kind of training that used to be the responsibility of the employer is now on the employee.
I can't agree with any of this article. >> It’s a problem because side projects create a talent bubble of people who aren’t fully engaged and are just doing enough at their "real" or full-time job to get by until their startup is up and running. This means their productivity suffers at their full-time job, an expense the employer ends up paying. The side project owners justify it by assuming it will only be for a sho…
Take a look at when Chargify was started and if the market was crowded then
Well, because Chargify is miles better than Paypal and banks. Maybe that guy next to me has a face-tweet-o-base idea that's miles better, too.
For a lot of my friends, side projects are the only thing keeping their passion for programming alive. You say below "If you're not happy with your job, just quit," as if it's easy for people to up and leave the position they're in. Not everyone lives in a tech hotspot and not everyone actually wants to or can just up and leave their roles. A lot of these side projects are explicitly being worked on so that they can get more up-to-speed with certain technologies with the intent to apply for something more satisfying to begin with. And if there wasn't value in side projects, companies wouldn't have any reason to "own" what you work on outside of your 9-5.
If you're not getting value from your employee because they're distracted or they don't have the faith or enthusiasm they used to, that's on you to sit them down and talk to them about it and maybe figure out a way to compromise; telling someone they can't spend time on their hobbies anymore is a petty response that doesn't look at the real issue at hand. Perhaps the problem really lies in your camp, not theirs. If you're so concerned your developers are going to up and leave to work on their own dream, you need to incentivize them more. Or, you know, get over it and realize that's business and people have other ambitions outside of your own and there's no reason that they should have to stick around to fulfill them, especially if this is the attitude you have towards the types of things that keep them motivated. If you're really concerned about not being able to create your product because your devs are going to bail to do what they ultimately want to do in their life, perhaps you should become one yourself instead of telling them how they can and cannot live their lives outside of your payroll.
It’s a problem because side projects create a talent bubble of people who aren’t fully engaged and are just doing enough at their “real” or full-time job to get by until their startup is up and running.
Let's be more careful about using the word "bubble." Its intent is to imply large size—thousands, tens of thousands of otherwise capable engineers are all expending their thought and energy on side projects instead of making their corporations richer!
Even if this assertion was actually true (it's obviously not), I'm not convinced that there is any large-scale harm to society, or even to the companies where these would-be entrepreneurs are employed.
First, it lets you experiment with new technologies and frameworks outside of your regular duties. (This can pay dividends to the employer)
Second, it can keep you from code burn out by giving you a creative release. (Also a benefit to the employer)
Third, it gives you freedom to experiment with smaller projects that might not be enough to support a person but create value for someone none-the-less.
Finally, one of those side projects might get traction and create a sustainable business.
Not everyone has the freedom to throw caution into the wind. And oftentimes, even if they do, it is not the best move.
I can't agree with any of this article. >> It’s a problem because side projects create a talent bubble of people who aren’t fully engaged and are just doing enough at their "real" or full-time job to get by until their startup is up and running. This means their productivity suffers at their full-time job, an expense the employer ends up paying. The side project owners justify it by assuming it will only be for a sho…