At the same time, I do end up using a lot of open source software as part of that work, and when I have issues with it, I do submit fixes back to the project. Sometimes they are accepted (in some form), sometimes they're ignored. This isn't overly time consuming, and if nobody did it, I'd be spending a lot more time fixing bugs myself.
Likewise, I occasionally open-source stuff I build that happens to be reusable. As far as I can tell, none of that code is widely used, but on the off chance that someone is looking for something exactly like it, it might save them some time.
Nah, it's because it's more fun to work on open source code! I don't work on stuff that's not fun or not interesting in some way, so there's definitely always an element of self-interest.
As to giving back, there's nothing stopping you. My latest for-profit venture has spun off two open source projects that "the community" can use in the future. Past projects have done the same.
The key is to do things to benefit yourself, with open source being a side product. That's how big companies do it. Why shouldn't it be the same for us little guys?
You get all the advantages the author talks about, with none of the disadvantages that the commenters here point out. You get income, and you get something concrete you can point to when it comes time to interview for your next job:
"I built and designed somerandomthing.com from scratch. It's built on the mZungu stack and handles peak loads of 14k requests per second. Check it out when you get a chance. It pays my rent."