dnr

It's emphasizing writeability over understandability, which is totally backwards from the point of view of engineering robust systems.

Except it's barely even writeability, it's some bizarre notion that code should read like English where possible. And of course, since it's not actually English, it's only possible in limited ways and trying to generalize past those limits will break. So you have to learn exactly where the limits are anyway, which is as much effort as learning to use a proper library, except harder because a proper library will have the decency to stay in its own namespace.

(If you meant your comment to be "I found this works for me: ..." or "Have you tried ...?", then write it that way. The imperative mood is off-putting.)

FWIW: On my laptop, which I use most of the time these days, I adjust the brightness continually, probably 20+ times a day, and keep it pretty low. (I buy Thinkpads partly because their minimum brightness is so low.) On my desktop monitor, which is more annoying to adjust, I actually keep it at 0 most of the time, and bump it to 35 when the sun is out.

The only time I can even consider using light mode is mid-day with plenty of natural light around. At night when all the lights are dim, even the lowest brightness on my laptop (which is quite low), plus redshift, plus blue-blocking glasses, isn't enough to be comfortable in light mode. I use the "Deluminate" extension for Chrome to make all sites dark, all the time.

Perhaps I'm unusually sensitive to light (I think I am), but based on the comments here I think I'm far from alone.

I got a bunch of warnings about missing firmware so I manually downloaded some i915 firmware files from the linux-firmware repo. I assume that's just an Ubuntu packaging quirk. I'm not sure if they were actually needed or not.

This is on Ubuntu 19.10, kernel 5.3.0, and it started happening after a minor update, so I figured it would probably get fixed in another minor update. That didn't happen, so then I thought I'd better update to a newer kernel before reporting anything. Then 20.04 was almost here, so I decided to wait for that. Hopefully I'll get around to that soon and discover my particular bug has been fixed, otherwise I'll try to report it.

https://chrome.google.com/webstore/detail/deluminate/iebboop...

I tried most of the "dark mode" chrome extensions out there and found this was the best (compatibility, performance, etc.). Not affiliated, just a happy user.

https://squares.io/

The issue in that link is weird because it seems like part of the problem is that he credited Cage on his own album, admitting that he was copying it.

https://github.com/teleshoes/tpacpi-bat

I set mine to stop charging at 85% and not start again until it drops below 75%. If I know I'm going to be away from power for a while (e.g. traveling) I manually tell it to charge up to 95%.

Anyone know if there's something like that for Android?

http://dnr.im/tech/articles/mvdir/

https://bitbucket.org/davidn/mvdir/src/default/mvdir

Similar to vidir, but predates it by a few years. I still use it regularly!

I run it nightly from my home server. It has a few limitations (due to limitations of the Google Photos API) but overall it does what you want.

Also, part of my ideal requirements is an app built by an entity that I trust as much as Google. Open source is great, and this app is simple enough that I can skim the code once, but I'm not going to do it for every update, and I might miss something. There's still something to be said for that kind of accumulated trust. (I might not trust Google as much as I used to, but I still keep my life on gmail, so I have to trust them pretty far.)

I did use Go professionally for about five years, and read lots of criticisms of it (and still do out of curiosity). Most of them struck me as just not a big deal in practice. When I had to write some list-processing code that could be greatly simplified with generics (a few times per year), I just sighed and typed it out and moved on to a more interesting thing. When I had some repetitive error-handling code, I refactored it or wrote some helper functions. The dependency stuff was annoying when starting a new project, but once you pick a dependency manager/vendoring tool it's fairly straightforward (and of course now this is included).

Certainly, the language and ecosystem has warts and frustrating things. Maybe Elixir has fewer warts, I don't know. But overall the experience of using Go is fairly smooth and boring and productive. The things that people like to complain about don't really register in day-to-day usage. That's not BS, that's my personal experience.

Without backups, having a phone die or get lost is a very frustrating experience. If you use backup codes, you have to go re-register 2FA on every account with backup codes. And of course some don't offer backup codes.

You could screenshot and print out the QR code at registration time (I've done this for a few accounts), but shared printers apparently retain history of everything they've printed, so you'd need to own a personal printer, which seems absurd.

You could write down the TOTP secret on paper instead. Ideally with multiple copies and then move them to different physical locations. That's a big hassle to do for each new account registration, which seems to happen every few months.

Encrypted backups solve this easily: you get one key, which you write down once and distribute to different locations if you want. After that there's nothing new to do for new accounts at registration time. And restoring onto a new phone after one dies is also easy.

(This is a personal pet peeve since I have a short email address that tons of people sometimes think belongs to them, and get a huge amount of mail intended for other people.)

I know they're trying to be nice, but it ends up slowing everyone down: suppose a car and a bike are approaching a four-way-stop intersection with the car clearly going to arrive a couple seconds before the bike. As the cyclist, I would assume the car will come to a stop or almost-stop, wait about a half or one second, then start moving. With that assumption in mind, I'll adjust my speed so that I slow down for the stop sign (prepared to stop in an emergency) and roll through right behind the predicted position of the car, without losing too much momentum.

If the car takes their right of way, this is great. But suppose they decide to stop completely and wait for the bike to go through first (against the right of way). Now as the cyclist, I also have to stop completely, since I don't know when they're going to start moving again. If we make eye contact, I'd feel safe to go, but I feel like that's reinforcing bad behavior. Instead I refuse to make eye contact and force them to go first, as they should have initially.