1,855 karma · joined February 19, 2008
What changed since then is that the new Liebherr excavator has more than 4000 pieces.
-- https://nl.wikipedia.org/wiki/Dijkstra (through Google translate)
What is weirder (but not the first time I have seen it) is that the list of languages is sorted by country name. German comes before Danish and Dutch after Maltese.
Yet it's entirely plausible that they were consciously making that trade off. I see a lot of similarities to cases like these:
> Ford (..) Pinto became a subject of controversy after Mother Jones magazine exposed that it was prone to deadly fires in rear-end collisions; Ford’s internal documents showed the company knew of the potential problem but chose not to fix it, calculating that it would be cheaper to pay out possible injury claims.
> The Japanese manufacturer of airbags has recalled airbags in some 19.2 million vehicles in the U.S. due to a tendency of the device to deploy with too much force, sending metal scraps flying into the passenger cabin. Eight deaths and about 100 injuries in the U.S. have been attributed to the defect. According to a New York Times report, Honda, one of the companies using the bags, and Takata knew about the dangerous airbags for years before disclosing it to the public and issuing recalls.
I have encountered these at Decathlon and Carrefour (in Europe). It feels fairer, but standing in longer line feels worse, even when that doesn’t make any sense.
Users should make the choice to allow that, and they can by buying an Android phone.
The Netherlands: 36,500 Belgium: 35,000 Germany: 37,500 Sweden: 31,000
These may not be exactly comparable feature-wise, but those extra taxes don't seem to have a big impact.
The number of home births is at 13% according to https://www.volkskrant.nl/wetenschap/typisch-hollands-fenome...
It feels like the primary focus of Windows is no longer to do what the user wants, but to do what Microsoft wants.
When you limit screen time to x minutes per day, that should include screen time outside the house.
- Educate your CTO.
- Just start writing tests. Consider whether you can pull this off.
- Wait for something to go wrong where tests would have caught the problem earlier. That would be a good time to bring testing up again.
- Find another job.
So it has to be something else.
That still works, though.