Why Your Passion for Work Could Ruin Your Career
blogs.hbr.org
blogs.hbr.org
As a side note, it is probably fairly difficult if not impossible to objectively measure passion, so I guess it is pretty pointless to debate any of this in the first place.
But going with the article, startup founders definitely need at least a little bit of what he calls "obsessive" passion.
Cutting your losses, getting sleep, exercise, visiting other (physical) humans ... these things are important for mental health. Be passionate, just know your limits, brush your teeth, and take a break every other weekend. You'll be fine.
That being said, passion is what drives people to hustle, do what's necessary to accomplish something. It's that laser-guided focus that leaves distractions aside. It's the curiosity that promotes hacking and figuring out what to do.
Lastly, it's the basis of the hunch. What Eric Ries mentions as the precursor of data-driven decisions. Passion enables entrepreneurs and hackers to go the extra mile and end up with disruptive innovation and new ideas. This often results in improper consumption of sleep, resources, time, and money.
The goal is not to satisfy society and temporary obligations but rather to create something that cannot be done in any other way, or at least not by those who lack passion.
I believe that people as individuals just need to do careful thinking about their activities. I know people who work for long periods of time, totally focussed, and seem to really be happy. I know other people who don't seem to like what they do for their careers, and I don't think that they find much contentment from work except for appreciating their pay.
One thing that I think is very toxic in work environments is if people feel inadequate in their jobs and work too hard to compensate. Double bad on managers who try to use this.
Useful article.
in my case, i think i have become "better", and what helped was a combination of understanding that i could burn out (when you're young you think that you are indestructible!) and decoupling my "own" projects from my "work" projects.
the decoupling is a difficult balancing act. an employer wants you to care, but wants to avoid conflict of interest. luckily in software development you can develop a personal project that is overtly about a completely different subject area (software for model trains say, rather than payroll systems) but which still improves the skills you use at work (via shared technology, concepts, etc). so while i tend to spend spare cycles on work that doesn't directly help my employer, i am also the person suggesting new approaches and solutions to problems at work - imho it can be win-win.
incidentally, i think the decoupling helps because it provides you with more control (see article). so that suggests that employers who want employees to be as involved as possible, but to avoid burnout, really need to relinquish control - to the extent that some kind of "dual ownership" exists (whatever that means - i am just exploring the idea here).
This article will be a great aid to porcine ablutions.
Btw which passion do you think steve jobs has? Seems like it worked out for him. Hmmmm.