I think that comparing the trades to software is a bit too coarse; there's a huge range of skill/experience/compensation variation in each.
Last week, I hired a gasfitter to do something that was straightforward, but needs to leave a paper trail. The job he did roughly equates to setting up a static website or similar - basically "turning the crank" for half a day; no fancy skills or tools. His billable rate is about twice what I made at my last local tech job; I was doing fairly fancy DSP firmware, he's got more work available than time to do it. And his rate is substantially lower than another quote I got to do the same job.
I think you're right that this is largely a "grass is greener" situation, but it's also important to look at the externalities of the options. It seems possible to have a successful trades career that rarely involves going over 40 hours/week, but it's hard to do the same in skilled software development. There's also the physical cost; working at a computer all day is super unhealthy.
Last week, I hired a gasfitter to do something that was straightforward, but needs to leave a paper trail. The job he did roughly equates to setting up a static website or similar - basically "turning the crank" for half a day; no fancy skills or tools. His billable rate is about twice what I made at my last local tech job; I was doing fairly fancy DSP firmware, he's got more work available than time to do it. And his rate is substantially lower than another quote I got to do the same job.
I think you're right that this is largely a "grass is greener" situation, but it's also important to look at the externalities of the options. It seems possible to have a successful trades career that rarely involves going over 40 hours/week, but it's hard to do the same in skilled software development. There's also the physical cost; working at a computer all day is super unhealthy.