Also - I'm done distro-hopping. The problem is KDE/Gnome- KDE is aping Windows (badly), Gnome is aping macOS (also badly). I'd list all of the problems but it would take an essay.
Also - I'm done distro-hopping. The problem is KDE/Gnome- KDE is aping Windows (badly), Gnome is aping macOS (also badly). I'd list all of the problems but it would take an essay.
Shit. Works.
This is critical. I can focus on my actual task at hand, rather than fiddling with the system.
Some perspective: I've been on Debian for 15 years, and I still hold it in very high regard for servers. I'm also an occasional Alpine & OpenBSD user; and Windows for games. I've tried Ubuntu, couldn't stop it from getting in my way. Before you suggest Fedora, Arch, NixOS, whatever: I'm done distro-hopping. The experience is about equal everywhere. No amount of "choice" beats thoughtful design, accessibility, and vertical integration.
I wonder if there are EU clouds doing that properly, namely with its own internal "security" cleanup crew and getting rid of those hackers and scanners.
Engineering is the practice of using natural science, mathematics, and the engineering design process to solve technical problems, increase efficiency and productivity, and improve systems.
In short engineering is the ability to follow processes and measure things. Most developers I have worked with are incapable or unwilling to measure things (on any level), therefore they are incapable or unwilling to be engineers.
If you want better software set minimal, measurable, objective standards. That becomes your foundation, your law. It is as much a soft skill as a technical skill, which is explained just before halfway through the video. Software is very very bad at this and is almost entirely reliant upon compile checks to just magically set some implicit success criteria. Most developers will balk at the idea of a disciplined planned approach and just expect some abstraction to do it for them.
Once you have achieved the process you test for compliance and you measure the result. Testing for compliance isn't a manual QA effort or tiny test units. Its a total process, a certification that you are willing to bet your job and credibility upon. For software such discipline is often foreign. In other jobs like medicine, law, law enforcement, soldiering, and even truck driving getting this horribly wrong will terminate your career forever and can land you in jail or result in devastating civil suits.
Until software is willing to become an adult like those other professions this will remain a distant challenge and its a monumental drain on the resilience of those developers who try their best to achieve that disciplined intent.
That statement may be a bit much, but working in organizations unable to, well, organize around ideas leads to the state we’re in today, where most developers has to run around like headless chickens and put out fires. There’s exceptions, but from my point of view they are pretty rare.
Here's a nice example: https://github.com/WordPress/WordPress/blob/92d9e70f849c337c...
Side-rant: It's nuts how hard it is to find a good laptop that has 64G RAM, let alone "more than 64G" as you cite. I finally thought I found one in a Thinkpad X1 2-in-1, but then it just had terrible build quality, broken speakers (low rumbling sound, unfixable even after a repair and a replacement), badly working components (eg fingerprint reader) etc. I ended up returning it. The HP is a full 1000 euros cheaper (!), and it's better in every way (incl processor speed) except the smaller RAM. Oh how the mighty have fallen.
I've personally always solved this problem by enabling "Hibernate" (not sure if that's a Windows-specific term) which writes the entire RAM contents to a file and then shuts down completely. The downside is that it takes a few seconds to boot (impressively few seconds on a modern machine, actually), but still, the laptop doesn't come on instantly. But I like knowing that there's no chance the laptop somehow turns on and overheats/drains in the backpack, because it's completely off.
This doesn't take away from the author's rant at all, the idea that a sleep mode would need to support notifications or updates (!) is absurd. A good sleep mode would need to only support "minimum power usage" and "fast wake-up" and nothing else. But with MS's usual mix of excellence and absurd stupidity, that appears to not exist, and "hibernate" is to me an acceptable compromise. My understanding is that Macbooks have gotten this right for decades already, pretty nuts that PCs lag behind so much.
It's no substitute for backups (I use Borg), and syncing is good (I use Syncthing, I guess iCloud also counts). But snapshots should be ubiquitous at this point, just like having a "trash bin" was mainstream in 1995.