> I know several top 1% engineers in the Valley who disengage from recruiting processes when 996 or something similar is mentioned.
A few years back, on this board, 996 was something people made fun of when it was reported that some Chinese companies did it [1].
And now, the strongest claim this blog can make is that some engineers in the US would disengage from recruiting? That the issue with working on saturdays is daily standup? What happened in these years for such a change to happen?!
Until recently American engineers made a lot of money at comparatively cushy jobs. A decent engineer in the US could make 5x their equivalent in most European nations. Staff+ engineers at FAANG could make 5x that. People in a good position tend to not like rocking the boat.
Not just that, but the union would likely end up capping their salary much lower so the wealth can be spread around. How hard is the 10x engineer on the team going to work when the compensation is the same regardless? This is where people end up working multiple jobs, if they can keep up with their peers only working one day per week.
Again see Steve. Something can look like a good position and still rapidly deteriorate.
This one wasn’t that rapid either, you had plenty of warning. I remember discussing inequality with friends in 2014, and probably knew about it since Occupy Wall Street (2011). Or earlier.
i disagree. i also disagree that most people developing tech solutions for startups are engineers or are applying an engineering discipline. but i would agree that the majority of people in valley tech firms are closer to the rentier class than they are to working engineers.
I would tell a recruiter directly that 996 is a red flag.
Prior to that it was cracked (née 10x (née ninja)) engineers or sigma grindset or whatever.
It's performative. If you bring people together to build something that they actually give a shit about, you'll out-perform a group of people who are grinding out of fear. And you'll _definitely_ out-perform the kinds of people who are buzzword heavy.
What happened? Started with Musk purging half his staff ...
I've been around long enough in this industry to see the pendulum swing back and forth a few times. The peak of 2020/2021 was the epitome of "spoiled tech worker" but now we're well on our way the other side, I'd say.
> How likely is it that those "protestors" are US and Israel propped
It's almost sure that both US and Israel are meddling with the current situation. That doesn't mean the situation isn't also started by and wanted by the population.
For a comparison point in the past, the civil rights and antiwar movements in the US were grass-roots movements started by local people with legitimate claims. At the same time, opponents of the US like USSR were involved in stirring these movements, because of course they would.
There isn't much you can infer about the legitimacy of a movement by learning that the movement is helped by foreign intelligence agencies.
The best way you can avoid this kind of confusion is 1) make a society in which malicious actors don't have many latent issues to stir, and 2) make it so your country's intelligence agencies aren't malicious actors. There isn't much else to do.
Iran has a water crisis, and allegedly the economic situation is so bad that people are starting to wonder if it will soon affect their ability to buy food.
Even the Romans knew that if you wanted to stay in power you had to provide bread and circuses.
Regulation is made to protect customers. Consumer trust is favorable to business in the long run.
It's really sad that US technologists confuse business and grift these days. Maybe it's related to their main customers being VCs, and the people using service just being props needed to have the line go up.
My point is not the types/monadic constructs, etc (I love to do functional jerk off as a guy next to me, though), but that there are ways to keep code readable and straightforward without neither invocation chains
> You don't need to repeat anything for software. Software can be copied arbitrarily for no practical cost.
...Or so think devs.
People responsible for operating software, as well as people responsible for maintaining it, may have different opinions.
Bugs must be fixed, underlying software/hardware changes and vulnerabilities get discovered, and so versions must be bumped. The surrounding ecosystem changes, and so, even if your particular stack doesn't require new features, it must be adapted (a simple example: your react front breaks because the nginx proxy changed is subdirectory).
The article kind of misses that cost has two axes : development cost and maintenance cost.
low cost/low value software tagged as disposable usually means development cost was low, but maintenance cost is high ; and that's why you get rid of it.
On the other hand, the difference between good and bad traditional software is that, while cost is always going to be high, you want maintenance cost to be low. This is what industrialization is about.
You don't need to push yourself into burnout as an employee in order to participate in an early stage startup.
> earning €80k
80k€ gross is not a lot for a decent SWE in western europe. The reason people complain in Amsterdam is not the hours, it's that your comp is shit.
reply