There is more value to programming than what it puts in your bank account though. If you wish to build and be part of a truly engaging product, you have to engage for the long haul with a codebase, on the order of years. That means either (A) you make your own product (and are responsible for your own business strategy, accounting and sales), or (B) you get into a fixed contract with some employer (where due to the long term relationship they will be careful to restrict what they pay).

In scenario (A) you will not spend all your day programming. You will have to care about the business parts. If you're not cut out for those parts, even if you end up making lots of money, you will probably not be happy.

In scenario (B) you are more likely to be able to spend more time programming, with less overhead to worry about, but this depends heavily on the employer, so you may end up performing several false starts or walking away from an employer/employee relationship. If an employer accepts you, you will most likely not be paid what your time is worth, but this is a willing exchange for not having to care about the non-technical parts of the story.

Is there a scenario C? If there is I've not yet discovered it.