| Unpopular opinion: As a recent graduate (last 5 years), I can't agree with most works desire to unionize for one reason: demand for your skills. When I was looking for my second tech job, I turned on that switch in my LinkedIn that lets recruiters contact me. I was immediately inundated with 10-20 messages a day from recruiters asking if I could speak with them about <Role with my expertice>. For me this was the most insane luxury in the workplace, instead of having to go out and look for jobs, those jobs were coming to me and knocking on my door. What I took from that is tech workers have an incredible choice in where they can go work because their skills are highly in-demand. So why unionize? Don't like where you work? Flip a switch and suddenly you have 10-20 offers a day from other companies looking to hire someone with your skillset. Yes, you have to spend time combing through the messages, on the phone with recruiters and going to interviews but at the end of the day with that level of attention to your skillset, you can basically decide where you want to work. Company A seems great but the culture is toxic, ok great let's see what company B has to offer. Company B has a good culture but their data collection practices you don't agree with, ok let's see what company C has to offer. Company C has a great culture and doesn't do the things you consider unethical with data collection, bam we have a winner. Also on the topic of general democracy in the workplace regarding decisions. As an engineer you don't make those decisions, you just implement them. Don't like the decisions, go somewhere else. Want more/total control over decision making? Start your own company. |
But more importantly, these are the "halcyon" days of finding tech work, and they are fleeting. There is absolutely no guarantee the job market will look this promising in a few years. Things seemed to be on an endless upward trajectory in the 90s and then it all came crashing down.
If you're gambling on the fact that tech work will always be in extremely high demand, then you have a combination of risk appetite and optimism that makes for a founder.
As someone who worked through the period of the tech industry during the dotcom fallout, lots of stuff people take for granted today was non-existent: You had much less autonomy over the technical aspects of the objectives you were trying to achieve. Mandated tools, crappy underpowered computers, bureaucracy, over project dependencies, process-heavy SDLCs weren't just the norm, but widely viewed as the proper way to build software. It was all a reaction to what was seen as the "inmates running the asylum" during the dotcom boom. It basically took a bunch of promising startups in the mid-aughts to start cleaning people's clocks and become juggernauts to get the broader industry to reverse course. It also became a lot cheaper to do a tech startup.
Basically, understand that a lot of what is enjoyable today about working in tech is a side-effect of supply-and-demand; they HAVE to avoid developer-hostile actions because we're difficult to hire and expensive to employ. Once that's no longer the case, the screws are going to tighten. Just look at China's 9-9-6 work policies and companies using chat tools to spy on their employees to keep them working as a point of reference.
> As an engineer you don't make those decisions, you just implement them.
I'd like to think we have enough integrity as a profession to fall back on an Eichmann-adjacent justification.