Does anyone know a google-able term for split keyboards that have doubled keys down the middle column (B/N, G/H, T/Y, 6/7)?
I see one instance on this page of a keyboard with double "B" key ("Alice layout"), but not the others.
I've been interested in trying a split keyboard, but I like to type those middle keys with either left or right hand depending on the moment, so all the split keyboards I've tried have ended up somewhat annoying, for that reason.
I don't think there is an actual name for that. I actually don't think I have ever seen a keyboard with a layout like the one you describe. I'm not really sure if it was really intentional on the Alice layout. The extra B might just be for extra symmetry between the two halves.
I didn't see it on the feature list, but it might be nice to allow it to run as a cron job and send email for reminders. These days, most mobile phones have an associated email like your-phone-number@vztext.com (depending on carrier), so you can send yourself text messages about chores and whatnot.
Or, perhaps just as good, have a way for it to dump out data as json, and could be consumed by some other send-the-email tool. There is the "-json" sqlite option, of course, but I'm not sure if your schema is meant to be stable.
I have a perl script for reminders like this that has been super handy over the 10+ years I've been using it. Never bit the bullet to put it in a nice UI or have a backing DB like this project, though.
There's definitely some scope and appetite for some notifications/reminders here. I haven't thought about the UX here, but the ingest pipeline + automatic reminders seems like a killer combo!
I went down this rabbit hole a while back — there's a fascinating history of various scientists' investigations into the blue sky, across many decades, with some back-and-forth between Russia and Europe. Einstein eventually made a connection between it and the seemingly-unrelated issue of "critical opalescence," by showing that the fluctuations of densities is responsible for the scattering, not just a simple "individual molecules floating in space" analysis that Rayleigh originally performed. But funnily, for an ideal gas (such as our atmosphere), the formula works out to be the same.
So, "Rayleigh scattering" is the common term still used today, but there is a deeper reason for the formula being correct — it remains correct even when molecules are relatively close together, such as in the lower layers of our atmosphere.
Django aside, I think this is a really important point:
Being able to abandon a project for months or years and then come back
to it is really important to me (that’s how all my projects work!) ...
It's perhaps especially true for a hobbyist situation, but even in a bigger environment, there is a cost to keeping people on hand who understand how XYZ works, getting new people up to speed, etc.
I, too, have found found that my interactions with past versions of myself across decades has been a nice way to learn good habits that also benefit me professionally.
This is the main reason I'm extremely disciplined about making sure all of my personal projects have automated tests (configure to run in CI) and decent documentation.
It makes it so much easier to pick them up again in the future when enough time has passed that I've forgotten almost everything about them.
I'm finding that in this build fast and break things culture, it is hard to revisit a project that is more than 3 years old.
I have a couple of android projects that are four years old. I have the architecture documented, my notes (to self) about some important details that I thought I was liable to forget, a raft of tests. Now I can't even get it to load inside the new version of Android Studio or to build it. There's a ton of indirection between different components spread over properties, xml, kotlin but what makes it worse is that any attempt to upgrade is a delicate dance between different versions and working one's ways around deprecated APIs. It isn't just the mobile ecosystem.
I have relatively good experience with both Rust and Go here. It still works and maybe you need update 2-3 dependencies that released an incompatible version, but it's not all completely falling apart just because you went on a vacation (looking at you npm)
Build fast and break things works great if you're the consumer, not the dev polishing the dark side of the monolith (helps if you're getting paid well though)
As a consumer, I can not remember any feature that I was so enamored about having a week earlier than I otherwise would have, at the expense of breaking things.
Totally relate. My main project lately is for my wife, and it’s absolutely rock solid from a testing/automation standpoint. The last thing I want to do is accidentally break something and give her a headache when i’m just trying to build her a nice thing that brings her joy.
I have a rule that any commit which changes the implementation has to include the documentation update at the same time.
Most of these documentation updates are a sentence or two, or maybe a paragraph. The overhead of incremental documentation updates like that is tiny enough that I don't really think about assigning extra time for them.
If you know what you are doing, you can hibernate other kinds of tortoises by placing them in a fridge (as opposed to a freezer). One of my
friends does this with their Russian tortoise.
If you need to travel, make sure you have someone reliable who can check on them, in case of a power outage.
This is also why I write a formal requirements document for all but the smallest throw-away projects. Much easier to know wtf you were thinking 18 months ago if you write down wtf you were thinking at the time.
According to the constitution, impeachment is literally for treason, bribery, high crimes or other serious misdemeanours. But the SC basically said it fundamentally can not be treason, bribery, a high crime or any misdemeanour if he did something in his role as president. So the whole process has become stale.
Ultimately, the Senate decides on whether to convict/remove for impeachment. The SC does not decide it. Sure, I imagine the Senate would generally want to broadly stay in agreement with the SC, but they don't have any obligation to do so.
At least that is my understanding; I'm not a lawyer or constitutional scholar :)
That's not how it works - in the case of impeachment the Senate holds a trial, and they are allowed to use their own definitions of treason, bribery, etc. The Supreme Court is in charge of what the regular courts do and can make rulings that bind them, but they can't bind Congress in the same way. After all, the justices of the supreme court are also subject to the impeachment process like the President is and it'd be weird if they could make rules about how that works.
You added the adjective "serious" to misdemeanors, which is not in the Constitution. The "high" in "high crimes and misdemeanors" means crimes and misdemeanors committed by high officials, not crimes and misdemeanors that are extreme.
The constitution actually doesn't really say anything about what misdemeanours are applicable in this case. This part has been shaped over time in congress, similar to how common law is shaped by courts.
If I understand you correctly, then if a President's cabinet (high officials) break the law the President can be impeached. Which makes sense to me. It places accountability on the President to pick trust worthy people and to immediately get rid of them if they break the law (to lessen the chances they'd be impeached for not doing something about it and insuring they are prosecuted).
But I think you're missing their "like bank robberies" point. Punishing the avenue of transport for illegal activity that's unrelated to the transport itself is problematic. I.e. people that are driving safely, but using the roads to carry out bad non-driving-related activities.
It's a stretched metaphor at this point, but I hope that makes sense (:
It is definitely getting stretchy at this point, but there is the point to be made that a lot of roads are built in a way which not only enables but encourages driving much faster than may be desired in the area where they're located. This, among other things, makes these roads more interesting as getaway routes for bank robbers.
If these roads had been designed differently, to naturally enforce the desired speeds, it would be a safer road in general and as a side effect be a less desirable getaway route.
Again I agree we're really stretching here, but there is a real common problem where badly designed roads don't just enable but encourage illegal and potentially unsafe driving. Wide, straight, flat roads are fast roads, no matter what the posted speed limit is. If you want low traffic speeds you need roads to be designed to be hostile to high speeds.
I think you are imagining a high-speed chase, and I agree with you in that case.
But what I was trying to describe is a "mild mannered" getaway driver. Not fleeing from cops, not speeding. Just calmly driving to and from crimes. Should we punish the road makers for enabling such nefarious activity?
(it's a rhetorical question; I'm just trying to clarify the point)
Hear hear. I'm also a daily LMS/squeezebox user, across many years.
In fact, given the full-throated open source nature of that platform (you can even build your own player with a raspberry pi[1]), I doubt I'll ever need to use anything else for the rest of my life for playing music in my home, even as my devices die and need replacement over time.
... which does make me wonder: that's great for me, but I can definitely see it as a deterrent for companies to do similar. If they want to make a competing future product, they'll be competing against an open-sourced version of their past selves, too.
FreeBSD and OpenBSD explicitly mention the prefaulting behavior in the mlock(2) manpage. The Linux manpage alludes to it in that you have to explicitly pass the MLOCK_ONFAULT flag to the mlock2() variant of the syscall in order to disable the prefaulting behavior.
How I miss my script kiddie days of being 15, downloading "nulled" versions of vBulletin off of Limewire and throwing them up on pocket money paid cPanel web hosting account waiting for it to upload on my parents 56K.
Also, beware of taking generalities (such as the claims of this study) and applying that directly that to your specific life, or anyone else's.
I mean, I like your comment and am glad you got thinking about this, but it's just a line of reasoning that I see a lot and I wish I saw less, so that's why I bring it up (:
"True for most people" does not imply "true for me" or "true for that person over there".
And the reverse is not valid either, of course - "true for me" does not imply "true for most people."
There's always some tension between people's individual anecdotes and experiences (which are fascinating, and I like), and the claims of broader studies like this one.
Sometimes I try to remind myself of this with the "on average, people have 2.3 children" factoid. Obviously, nobody actually has 2.3 children; the general truth does not necessarily apply to specific individuals; potentially not even a single one.
I see one instance on this page of a keyboard with double "B" key ("Alice layout"), but not the others.
I've been interested in trying a split keyboard, but I like to type those middle keys with either left or right hand depending on the moment, so all the split keyboards I've tried have ended up somewhat annoying, for that reason.
reply