>Google spent decades selecting for these "moralizers" and is now reaping what it sowed; "don't be evil" was a cultural slogan that carries consequences if it attracts a particular kind of mindset.
And apparently that mindset drove an enormous amount of profit and, at least in the beginning, gave the company some sort of social conscience.
It's amazing that you can be so against these things
To be fair Google did downgrade their "do not evil" value to "it is possible to conduct business without being evil" but it's fair to be reminded of all the evil they do do that led them to downgrade themselves in their own estimation.
A lot of people on hacker news get threatened by collective action. This is understandable, given the number of employers, wannabe employers and people with large portfolios who frequent this site.
This is kind of why I expected some people to make a big deal out of how this isn't a big deal. Tech unionisation is genuinely threatening to many here and this Google walkout stuff is a potential sign of things to come in this industry.
Yes, I remember it was a problem with Django. It wasn't just the application server, you might need to run some scripts, after the database is up, before kicking off the webserver. Any workflow like this is explicitly unaccommodated.
100% of the solutions ive seen to address this problem have been hacky - either polling bash scripts or explicit waits.
>The problem of waiting for a database (for example) to be ready is really just a subset of a much larger problem of distributed systems. In production, your database could become unavailable or move hosts at any time. Your application needs to be resilient to these types of failures.
absolute bullshit. docker compose thinks that it can excuse its bugs by dint of the fact that we're supposed to build "more resilient" applications to accommodate them.
and, their proposed workaround with "wait for" is disgusting. their tool should be able to handle readiness detection. it's so fucking basic.
it's not only this but this is an example of the bullshit in this shitty tool excused with shitty reasons.
The point, however, is that the customer/regulator dictates quality standards, not the person assembling the burger.
Whereas apparently many software engineers do not take their cue from customers since they strive for some impossible "no bug policy" (or some other such rubbish).
China's approach with its 737MAX competitor, has, ironically been the exact opposite of this. Their fear wasn't getting the price low enough to satisfy shareholders but not getting the airline approved by US and European regulators.
I was dubious before the crashes but after Boeing's reaction to the crashes I'm fairly sure I'd feel safer on their planes than Boeing's.
It's also a business endeavour that's done a lot of bragging about the number of people it will render jobless. It's not going to be an easy political sell to erect lots of additional road furniture unless it's cheap and unobtrusive.
And apparently that mindset drove an enormous amount of profit and, at least in the beginning, gave the company some sort of social conscience.
It's amazing that you can be so against these things