This attitude is why so many open-source projects are shit. That said, the habit of shipping often is a good one to have. But I think it's important to follow through and deliver something of quality every time you ship.
just because you're trying to improve doesn't mean you have to share your bad code with the world.
there's nothing wrong with writing code and trying to improve, but there's something to be said for being a good editor and not releasing every keystroke you type. why release that which isn't good or useful?
True that he probably wasn't passionate at the beginning. But he must have developed it along the way. You don't continuously work 16-hour days unless you're passionate.
I wonder if the difference is when you look at "one and done" guys vs. serial entrepreneurs. But even then - many seem to change domains in subsequent startups.
Find something about your work that you're passionate about, rather than the work itself (you could call it being indirectly passionate). For me, I'm passionate about creating useful things. So long as I'm creating useful things at work I'm passionate about it.