I feel like you may be suffering from the grass is greener on the other side.
First, work schedule. Keep in mind that, as another commenter pointed out, tradespeople often go through booms and busts, just like any other profession. The difference is that with tradespeople its a lot more obvious, since they still on a job for a few weeks, rather than a few years. On the boom, the tradespeople get a better deal out of it, because they get more work, whereas office workers of course only have the one job. In the busts, the office workers come out better, as the tradespeople have less work, whereas the office workers remain the same as they were in the boom.
Next, hours and vacation. I may be an outliner here, but my hours are the standard 9-5 and I get a fixed 30 days vacation a year, and flexible working (including working from home). As for unlimited vacation = no vacation, and 60+ hours is required, that seems more like a bad office culture/employer, no different than a tradesman would get a bad client. Again, its only more noticeable in office jobs because your there for a long time, whereas a bad client will only be a problem for a number of weeks (though potentially more if they hold off on paying). While we're at it, the same could be said of "their experience is respected". That's based on your employer, not your job.
Finally, standups, agile and office politics (assuming thats what you meant by BS). Its true, tradespeople don't need to suffer with that, but they do need to suffer through a hell of a lot of health and safety precautions and government red tape. Of course you can get some cowboys who don't bother with that, but that seems no different than the programming teams that don't do standups, agile or office politics (apart from the fact that one team is less likely to kill people). I would also mention the physical health issues that it can cause, but programmers get a similar thing through sitting for so long and you graciously didn't mention that.
I don't think being a tradey is a bad job, not at all. Its just not perfect, and like any job has its pros and cons. I too have fantasised about going into that line of work, but I imagine if I did, I'd end up fantasizing sitting in a comfy chair all day building software. As I said, the grass is always greener on the other side.
First, work schedule. Keep in mind that, as another commenter pointed out, tradespeople often go through booms and busts, just like any other profession. The difference is that with tradespeople its a lot more obvious, since they still on a job for a few weeks, rather than a few years. On the boom, the tradespeople get a better deal out of it, because they get more work, whereas office workers of course only have the one job. In the busts, the office workers come out better, as the tradespeople have less work, whereas the office workers remain the same as they were in the boom.
Next, hours and vacation. I may be an outliner here, but my hours are the standard 9-5 and I get a fixed 30 days vacation a year, and flexible working (including working from home). As for unlimited vacation = no vacation, and 60+ hours is required, that seems more like a bad office culture/employer, no different than a tradesman would get a bad client. Again, its only more noticeable in office jobs because your there for a long time, whereas a bad client will only be a problem for a number of weeks (though potentially more if they hold off on paying). While we're at it, the same could be said of "their experience is respected". That's based on your employer, not your job.
Finally, standups, agile and office politics (assuming thats what you meant by BS). Its true, tradespeople don't need to suffer with that, but they do need to suffer through a hell of a lot of health and safety precautions and government red tape. Of course you can get some cowboys who don't bother with that, but that seems no different than the programming teams that don't do standups, agile or office politics (apart from the fact that one team is less likely to kill people). I would also mention the physical health issues that it can cause, but programmers get a similar thing through sitting for so long and you graciously didn't mention that.
I don't think being a tradey is a bad job, not at all. Its just not perfect, and like any job has its pros and cons. I too have fantasised about going into that line of work, but I imagine if I did, I'd end up fantasizing sitting in a comfy chair all day building software. As I said, the grass is always greener on the other side.