Seems generally worse for the world if we want to force everyone to work 24/7 with no joy or interests outside of work. Ah well. Do you think they can recognize it? I don't think any of these companies will have anything interesting to say, last ten years, or improve lives.
It mostly looks like an act to me, a cargo cult where if they offer up enough "work" they'll be rewarded, disregarding any usefulness.
As far as I could tell, the article seems to be specifically about founders, not "everyone".
Personally I don't agree even for founders since I've seen too many that end up just grinding the gears without producing value - when that leads to meetings etc reducing the productivity of the entire team it's a problem. But committing to a stressful life as a founder in itself doesn't seem that bad as long as it's not propagated poorly to the team.
I imagine one'd have much more time to create things that matter to them as well, or at least the option to pursue such things. Kind of an odd potshot on op's part.
I've seen this opinion before but disagree with it. There are maybe five names to learn. They relate to the actual concepts, allowing you to expand your knowledge.
The part I've been trying to explain to coworkers is that the union isn't just for software engineers at the company, but for the support staff as well. We have it good but I have seen support and sales staff get bullied pretty hard.
Sure you might not even get a raise with a union, but perhaps those same benefits of remote work when needed, unlimited vacation, and an hour lunch can be extended to every worker at the company.
The most expensive workers teaming up with the least expensive to give them more power is a good thing, I think.
Funny enough, that's probably the worst way to convince engineers due to the belief that is rooted in this field which is both rockstar qualities and a false sense of security due to companies (so far) overpaying to reduce talent pools. So bringing up support staff and sales usually results in the mindset that they should just switch fields.
Instead talk about sports unions, like the NFL Player Association, and that usually gets them re-evaluating all they've been previously understanding about unions.
Funny how proponents have to talk about sports or actors' unions to sell developer unionization because we aren't sports players or screen actors. Try talking about what actual engineering unions do instead, like the SPEEA.
(Frankly, I can't think of any unions of engineering professions aside from the SPEEA in the US and I couldn't find any in a casual Google search. Anyone know of any? And if there aren't any, well, people might want to think really hard about why.)
And I've seen support and sales staff bully software engineers, often for being too white or male for their liking. So they should unionize on our behalf, for fairness and justice?
This is entirely my thesis on why they'll win. Of course google wishes they could ignore all attribution.
They are slighting the law just like airbnb and uber did. They offer a better form of consumption. This is disruption at it's finest, and it will be in the courts forever.
The new issues will be interesting. Now that I've seen the quality of the output and played with it a bit I'm already squinting at comments here and there. We're in for an even stranger internet.
A modern tech stack won't help that much, there are other issues.
> Most subway services cannot significantly increase their frequencies during rush hours, except for the 1, G, J/Z, L, and M trains (the L service already is automated with CBTC).
> However, even without CBTC, the system is currently retrofitted to operate at frequencies of up to 60 trains per hour (tph) on the IND Queens Boulevard Line (30 tph on each of the local and express pairs of tracks made possible by the Jamaica–179th Street terminal, which has four sidings past the terminal for each set of tracks) and 33 tph on the IRT Flushing Line.
Any time I want to get a side project actually done, I'll use Phoenix + Live View. It's effective and efficient (from both a dev perspective, a server resources perspective, and a client load speed perspective). You don't have to worry about an API or setting up react etc but have enough interactivity to get your idea across.
I don't think it's any fanatical following, it looks like a lot of other people are in the same boat as me with it. It's just good and effective.
It mostly looks like an act to me, a cargo cult where if they offer up enough "work" they'll be rewarded, disregarding any usefulness.
reply