In Down and Out in Paris and London he is very clear that he comes from some privilege and also that he actually lived the experiences he wrote about. He can't write it from the pov of somebody doing it for decades with no other option but he is explicit that he can't do that.
Kind of is. The point of fiction is to speculate. Judging the characters is fine but the commenter above almost seems to take it personally that the characters are morally ambiguous people - but that's what fiction is meant to explore.
Sort of - if it's determined that somebody bypassed a safety control they can just make the control firmer and fire that person and move onto other things. If it's some fundamental flaw in the engine design that could set them back months/years.
There's another comment that it wasn't the weld but even if it was the welders would build to spec and "better" (if it's known what better is) only if it's straightforward. There are certainly scenarios where a fabricator could design a better jig or use a more precise process but if the spec doesn't call for it then it's probably not going to happen because there are also the dimensions of time and money that matter as well.
Rockets are hard for sure but also almost nobody notices if there's a minor bug in your delivery app that causes it to crash every once in a while - but it can matter alot if there's a microscopic crack in a rocket engine that makes it blow up. Defect rate might be the same but the (literal) blast radius is much higher.
minified is fewer tokens than the human-readable version that we would write. It only really makes sense to write in minified js - it's also where alot of code in the wild is since every production site minifies their js which is then consumed by training.
It's worth noting that if each developer is 20% more productive with AI (let's take that as a premise and not dispute it), then it makes sense to go even further and reduce human headcount by more since the communication overhead of having 25% fewer developers is in and of itself a force multiplier.
tldr; 10 developers with 20% more 'productivity' can be replaced by 7.5 ideal developers and more like 6 or 7 developers due to the benefits of simply requiring less organizational communication.
I still think the ideal team size is unchanged however and that's 7-10 people. Note that teams aren't necessarily the same as direct reports. A CEO for instance has a certain number of reports and a leadership 'team' but they're not a team in the traditional sense since they are more about making good decisions and collaborating on specific things but mostly about leading their own orgs that have vastly different skillsets from eachother.
reply