The best QA isn’t just about finding bugs. It’s about bringing quality to the codebase: typing, better static analysis, linters, and useful libraries. In the other direction, it’s also about integrating into the release process by using integrating the what-goes-on / what-stays-in-beta decisions into quality’s approach to giving signal over any other part of the codebase.
Anything that involves gating bits of code, basically, and deciding whether to gate bits of code or not.
The best QA is linting, CI and language features? Sure and automated testing at different levels too but this sounds like basic things the engineering org does
The sports in which I’ve competed — cross country cycling and cross country running — also have handicaps for age. I always liked that type of system because it also gives both the open results and results by category, and there are lots of categories. W20 can thrash an M30, and plenty of M20s too, even if the overall winner is likely to be an M20.
It was simplistic for sure but gender identity was only a proxy for the handicap that impacted performance: the genetic disadvantage of not having been through a natural male puberty. If we can no longer rely on gender identity as the proxy then it makes sense to either drop the handicap system altogether, or refine it to look at the performance enhancing impact of genetics rather than what your pronouns are.
Good thing that’s nothing like HRT then, is it? Height is (well, mostly) immutable. Sex is not, though many people will fight tooth and nail to pretend otherwise.
No not all women get pregnant, but they generally have the plumbing to do so. My wife and I have tried for years without luck, yet no doctor has ever asked if we tried getting me pregnant instead. Smh
Regarding dropping support for a LUKS encrypted /boot, one of the comments chimes in with “[but] full disk encryption is mandatory in many environments in Europe for security conformity”.
Surely some user editable data has to be stored in plaintext to be able to boot a system? Does grub.cfg need to be signed by the trust chain to be able to boot?
When I hear full disk encryption, I think of what I'm using: Using the encryption feature of the disk with a password / keyphrase prompt built into the system firmware (UEFI). It is 100% transparent to any software.
The only major downside is that you need to trust the hardware manufacturer (and their FIPS certification), which is fine for my purposes, but might not be fine for state secrets or extremely valuable trade secrets.
I don't know if FIPS standards have improved, but combining my priors about products boasting FIPS and manufacturer code quality in general, I would actively not trust it with any data, full expecting it either leaks them, corrupts them, or somehow both.
Unless your UEFI supports reading from an encrypted drive you will at minimum have part of GRUB unencrypted up until the point where you enter a decryption key. so at least initialization, cryptography and filesystem drivers (or module loading) are unencrypted. I hope they are at least secure boot signed else the entire thing is security theater.
But at that point why even encrypt boot and not use something like a signed UKI for decrypting the rest of the disk? That way at least you only have the kernel, its modules and userspace (the initrd usually being a subset of the actual system) as bug/exploit surface instead of also including GRUB and all its modules ontop of that.
I think one has to go clear eyed into freely licensing one’s software. It’s hard to declare you’re giving up all rights and that the IP can be used in any way, only to later say “no not like that!”
If you want a cut of your licensee’s revenue then it’s ok to say so in your licensing terms.
”[The twins] realized they possessed the ultimate scientific tool: a perfect control subject and a perfect variable. Ross wore modern kit while Hugo wore historic replicas. Any difference in performance could be attributed solely to the gear, not genetics.”
It’s a great idea and these men are undoubtedly incredible athletes, but I’m not sure “ultimate” and “perfect” are the right words here.
A killjoy would bring up double-blinding or n>1 and I don’t want to sap the fun out of this being about an interesting people-centric piece.
There’s no mention though of a more basic trick: having them alternate clothes every expedition or season! Pfizer it ain’t, but it would still take it up a notch on the scale of interesting/fun to “ultimate/perfect”.
Meanwhile Google.com shows all manner of depravity if you click “safe search: off”.
I realize there’s a carve out in the legislation for search engines but if the goal is to stop little Timmy finding pictures of an X being Yd up the Z then it is a resolute failure.
The only thing that works with children is transparency and accountability, be that the school firewall or a ban on screen use in secret.
Hosting DNS on the same machine as your application opens up all sorts of nice hacks. For example, you can add domain names to nf_conntrack by noticing the client resolving example.com to 10.0.0.1, then making a connection to 10.0.0.1 tcp/443. This was how I made my own “little snitch” like tool.
Anything that involves gating bits of code, basically, and deciding whether to gate bits of code or not.
reply