940 karma · joined April 3, 2017
When I was talking about skilled trades I was mainly referring to your union/licensed/Journeyman types. We had continued training programs to keep up with latest NEC/NFPA/ASHRAE/ASME changes. We also had the option of teaching at the union hall (all apprentices work normal days and go to training at the hall on Tues/Thurs) to earn a little bit extra money.
I've met good craftsman as well as lazy ones, but like you said, now that I'm a full-time developer, the same still holds in our industry as I'm sure it does in most industries.
I have been in a union before (nearly a decade of industrial electrician/power plant operator work before I obtained my CS degree). You bet there is corruption in some unions, but perhaps it is different in the "skilled trades" though, at least it seems that way from my personal experience.
Avoiding blue collar work is a primary motivation for my transition to full time software dev...we'll see how it turns out though because the office culture/work environment is very foreign to me in many ways.
In the trades, after the job was over or I had turned over to the oncoming shift operator, I didn't think about work at all until my next shift, it was great, my off-time was mine. It was much better mentally compared to now where I have to have my phone on me at all times and respond to emails from our customers (granted, my customers or Transmission System and Distribution System operators controlling the electrical grid, so it is pretty critical when the applications experience issues). There are pros and cons of each, with pay being roughly equal (outside of the major tech hubs). Am I glad I switched? Sometimes, but the skilled trades (electrician, pipe-fitter, plumber, HVAC tech, welder, etc.) are definitely a good way to go if you want to learn a useful skill and have a relatively stable middle class life.
I don't get this attitude at all, but perhaps that is because I transitioned into software dev from the trades. In the trades you want your apprentices to ask questions, I don't see why Senior Devs would be assholes. In my experience, when I asked my Senior Devs questions, and this was after initial research efforts on my part, they were all receptive and helpful. It is much better to ask the question as a Junior than commit to prod and create even more work for the Seniors.
> "...pout over not getting enough money"
You're trying to make striking sound childish but there are plenty of legitimate reasons why unions go on strike.
I don't think a U.S. union would try to loosen immigration restrictions...they'd care about protecting the rights of U.S. workers...also, why would a union representing U.S. workers want to increase the labor supply?
I was a journeyman electrician for nearly a decade before obtaining my CS degree. The company that hired me, in order to pay me what I was making as a topped-out journeyman, brought me in as a Senior Developer (and its corresponding pay "bucket"). This was my first job actually developing software and I was, in title, a "Senior Developer," even though I knew next to nothing other than what was covered in my college curriculum.
TLDR: Titles don't mean much...
Improved compensation, benefits, bonuses, stock options, paid conferences, training, etc...
That's not currently working too well for us...
Trades like plumbing, electrician, lineman, P&C technician, mechanic, power plant operator, transmission/distribution operator, welder, etc...
My original comment still stands though. FB's timeline changes might damage those business that rely solely on FB, sure. That's to be expected if you're built around someone else's platform that you have zero control over. It still doesn't mean the "death of small businesses."