I couldn't find anything other than their first responders page but IMO any robo taxi operating in a metropolitan area should be publishing their disaster response & recovery plans publicly.
Hard to tell if this is auto generated but I'd guess so. There's a somewhat egregious error. In the Helmholtz–Kohlrausch effect section the site states"
"The illusion where increased saturation (or chroma) of a color is perceived as an increase in the color's lightness."
But that is notably wrong. Lightness is a tonal metric (closer to white, more lightness) and is defined as such on that site as well.
In the H-K effect, emitted light of greater saturation (less lightness) is perceived as higher luminance (brighter) than emitted light of greater lightness.
A more accurate statement would be "The effect whereby colors of greater saturation than, but equal luminance to, a less saturated reference color are perceived to be of greater luminance that the reference color." (I'm sure that could be tightened up.)
I spoke to Cal for this article though I don't think he used much of our interview. I developed GTD software back in the first as Kinkless when became OmniFocus after I joined Omni for a year.
Today I don't use any "super specialized" tooling for task management. Intentionally. I don't like being wedded to any given app. My tools are Apple Reminders (universal for my family since we're all on Apple devices) and Obsidian (or really just plain text / markdown, accessed currently through obsidian).
Lots of thoughts about all this but in short there were some good ideas I took from GTD (universal capture being the biggest, but that's not really a GTD unique idea) but most of it I've jettisoned.
(my obsidian / markdown usage is basically "take notes, sometimes notes become projects, those projects automatically show up in a dashboard" and mixing notes, content, and tasks organically)
This leak feels like a trial balloon (sanctioned or not). I suspect there is enough "hmm is this a good idea" and pushback within wotc that this is a way to gauge how terrible of an idea this really is (it is terrible and would burn the brand down).
I didn't run Solarized through WCAG when designing it (I don't believe that was around when I was designing it, though I could be wrong) but I did design it to enable high contrast use (this is mentioned on the site but sometimes overlooked in implementations). The highest contrast base tones as background / foreground colors (base03+base3) do pass with a 13.91:1 ratio. In "low contrast" mode, Solarized passes all but WCAG AAA with a value of 4.74:1.
As my eyes age I often use Solarized in higher contrast configuration, so I'm sensitive to this issue.
Two things I want to add (better as a comment than edit):
1) I don't use Solarized everywhere religiously. I use it a LOT, no surprise. Still my preferred color scheme in most editing, terminal, code situations. But I am happy to use other well designed colorschemes in various contexts (writing, task management apps, etc.). Even when Solarized is available, sometimes variety is what's called for.
2) Solarized was designed to enable the colors to be used in high contrast modes as well. As my eyes age I sometimes will apply the colorscheme in a higher contrast mode. This adaptability is sometimes overlooked but it is inherent and intentional to the design.
Developer of Solarized here. Glad that it continues to be a popular design. I've let the github languish and regret that. Luckily since it's just a color scheme the website and info on github has been enough for it to continue to propagate.
There have been plenty of other color schemes that I think it's safe to say have been inspired by Solarized and this is very satisfying to see. Many of them have done a better job at thinking through the git structure of their projects :)
For those interested in further reading on this and many, many other nuclear weapon safety incidents, I recommend the excellent book "Command and Control" (also a documentary but the book is significantly more comprehensive).
As someone that helped create a relatively popular task management app, I've scaled things wayyyy back personally and now mostly use Apple Reminders and Streaks (Apple ecosystem only so far).
Streaks has a great "don't do this" function for tracking habits. Recommended as a habit/recurrence tracker in general.
I ran Linux on a P50 for years and that unit, which is sitting in front of me right now, is the reason that I won't buy another ThinkPad, ever.
It was the biggest lemon I've ever owned. I've been through multiple mainboards, dozens of repair center calls for battery and power issues (which persist even now).
(Having owned somewhere around a half dozen different ThinkPads, all of them well loved up till the P50, this was a sad end to my support of that platform.)
I deployed Fleetsmith a couple years ago after evaluating the field. Fewer features than the competition but well designed and clearly improving over time.
Zach Blum (CEO/co-founder) would regularly follow up on issues and tickets himself, always friendly and helpful.
I know transitions like this can be rough but I'm glad to see them achieve this success.
I spent a WEEK out of my computational basics curriculum teaching middle school students just about paths. Just about FILES and paths. Did this with a VPS and chromebooks SSHd in. Also, later, Raspberry Pi units.
They simply don't understand computers when they walk in my classroom door. They understand mobile app user interfaces.
Readers of this thread may be interested in lower cost options. I built a middle school robotics curriculum around Dexter GoPiGo robots: https://www.dexterindustries.com/gopigo3/
While you can do visual/block based coding on these, it also has built in Python support and the whole curriculum I ran was Python based.
My criteria for selection of this platform included:
- support for Grove sensors
- flexibility in machining own parts if desired
- Python support
- rPi based
(no affiliation with this company, just a positive real world end-user/educator experience)
This past year I taught Python to 7th and 8th graders.
But to 6th graders I taught CLI basics and Inform7 (all on the command line).
It was one of the most successful "programming and computer basics" courses I've ever run. A fair amount of custom tooling to make it run smoothly, but a shared VPS for the students and some deploy scripts made it possible to not only make individual games but also collaborate on a larger scale game written collaboratively (each user writing their own set of rooms which was compiled automatically into a full game).
in so far as ssh is just one of dozens of commands that the girls learn on the command line, it's perhaps not.
in so far as it makes them realize that computers are discrete entities that are networked and that this is what the internet actually IS... it's priceless.
The first time we connected to a remote machine in a different state it BLEW THEIR MINDS. One of them asked if it was EVEN LEGAL :)
It's a single command, yes, but it's also the pivot point for a whole unit on remote access, networking, IP addresses, etc.