So a guy that married 2 times and divorced 2 times, has 3 children, recommends that the sweet spot for productivity is 60 hours per week, which would mean about 12h/day if you work 5 days or 10h/day if you work 6 days. This means, if you start your work at 8, you finish either at 20:00 or 18:00 + 30-60min lunch break. With such a packed day I can only imagine what a stellar childhood will his kids get assuming he wants to be involved in rising them...
I'm sure most people wouldn't outright say that, but I have no doubt that many corporate leadership types think that way. After all, the C-suite has higher incidences of NPD and ASPD so it shouldn't be surprising. Along with being out of touch, some of them probably think their peons should have the means to do the same.
The other part of the recommendation is "at the office 5 days a week". Working more than 40 hours and spending meaningful time with your kids is very possible, if you aren't wasting 2 hours a day commuting and you have a flexible schedule and you have a partner who can also spend time with the kids.
But he's also not recommending 40 hours, he's recommending 150% of that. Even then, I'd assume that when he says "sweet spot" he's also talking about a median, meaning you'll have to put in additional hours sometimes.
It's not the hardware's fault. It's the software that I don't like. This was the case before and after Apple silicon.From the window management to how I need to setup my computer, everything is slow in MacOS. The UI interactions, how the apps needs to be managed. Everything. I am trying to make it faster. It's not customisable the way Linux is. Maybe I need to be a bit more clear, it is slow FOR ME. Not to mention, after the glass update, I find it very hard to use with respect to UI.
Framework has it's value for ppl that are afraid dropping their laptops/ breaking the screen. Personally i still prefer macs, but I have friends that do value such "features". For the same reason they are willing to buy the Fairphone despite inferior specs/higher per spec price
Maintenance ain't free and letting one of the core elements of OS to be developed by community could lead to undesirable outcomes (ranging from battery/perf impact to introduction of some new bugs or esoteric workarounds). Consistency in codebase and software is important, especially for bigger companies.
Far too many companies aren't willing to embrace newer paradigms/toolchains/software on the principle - if it works don't touch it or inventing some wild workarounds. I think in the end it's for good
our company doesnt do compile on push on the server. It only does it when approved by a subset of ppl. The reason is we have a limited amount of servers and compile takes about 40min/variation. It's very annoying considering at prev job compile took about 10 min in total (project was organized better+ better servers) and there wasn't a limit at all-> compile at each push to gerrit.
I'm now trying to migrate from msbuild to cmake+sscache+PCH for std libraries while also trimming unnecessary includes to reduce suffering in the future - if not for me then at least for future developers. So I would say compile time is important for development. It causes other limitations too (like bugfixing becomes a huge commit with several squished fixes together to avoid recompiles, messing up git history or slower context switching when developing several features in parallel)
"uranium is imported into the EU from Russia" - here you prove again you have zero idea about the topic. Russia is ore importer itself. It exports enriched fuel (which can and IS easily done in EU too, by Orano and Urenco, even in Germany). Out of 22bn energy imports from RU last year, only 0.8bn were nuclear related, most of them spent by countries still running VVER units like Hungary because of their specific fuel elements but that will gradually be gone too with Westinghouse/Framatome help
reply