It has this to do with this thread: programmers who say they don't need to unionize because "their needs are being met" in return for "40 hours a week" don't understand the basic economics of their craft of what being compensated fairly means, and that's something a union could help them with. I've heard more than one case of a big company saying "thanks for that optimization that will save us >$15M/yr for at least a decade, here's a ~$10k bonus!".

The few engineers who care to engage in the negotiations which yield their true market value end up making several times that of the average. Yes, some of them are exceptional engineers, but some are not, and the only real distinction is being able to find and negotiate optimal market rates for their work.

I am a consultant that writes software, does that mean I am not a programmer.

If wasn't supporting a whole raft of people who aren't my kids I could get by on 10 hours a week. Most of these people will be self sufficient in the fall. Then we will see I can get fewer hours.

Charge hourly, produce good work(actually work those hours you charge) and spend enough time learning to stay proficient in your niche of the craft. This recipe won't make you a millionaire quickly, and it won't get you a house in the bay area, but it has given me great financial freedom in the Midwest.