mubou
Joined 1 year ago
Joined 1 year ago
1. Win+R
2. control /name Microsoft.BitLockerDriveEncryption
3. "Back up your recovery key"
The funny part is, Wikipedia is the #1 data set used for all sorts of machine learning training (not just LLMs). I hope they at least mark articles that were translated/edited by AI, because otherwise the AI machine is gonna start feeding back into itself sooner or later.
Look up some python computer vision tutorials and train a model to detect you wearing glasses vs. not wearing glasses. Run that on a Pi and hook up a smart plug or displayport switch between your monitor and pc so that it only turns the monitor on once it detects you're wearing the glasses :)
This is already a worrisome possibility with security keys -- if you have Windows Hello enabled, the dialog you get when adding a security key to an account might sometimes be to add it to your TPM, but it's not clear that's what Windows is asking so you might put your creds on your CPU while thinking that they're going on the Yubikey; imagine what happens then when you upgrade your computer?
Users need to know where their logins are stored. Making these things "transparent to the user" in the name of ease of use (treating users like toddlers) is the wrong approach. I realize the average user doesn't understand the technical side here, but that just means we need to do better as devs and designers, not throw in the towel and make decisions for the user.
Unfortunately there's no way to set this per-site, at least in Chrome. Similarly, if you disable animations in Windows, you also disable all animations and transitions in websites that support prefers-reduced-motion, causing some sites to feel janky as a result.
They really need to add a per-site toggle for that, and a browser-level option to ignore the OS' setting. Turning off animations in Word shouldn't turn them off in Google Calendar.
See if there's a subreddit for your country. Even if it's not very active, you could ask what other social networks they're using.
foreach (Node node in EnumerateNodes(root, x => x != null, x => [x.Left, x.Right]))
where EnumerateNodes uses `yield return` (i.e. is a generator) and calls itself recursively. Though it'd probably be easier / better performance to write an implementation specific to each node type.
1. Does this add additional complexity? How much more time/effort would it take to implement the feature? And most importantly, how much added effort would it take to maintain the feature? (Would adding this feature become a burden later?)
2. Can we be sure that the feature, as we would implement it now with our limited information, will meet future requirements, or would we perhaps be implementing something one way only for it to turn out that it would have been better implemented another way once there's an actual, defined usecase for it? (Remember that once you add something to an API, it can be hard to change or remove it later.)