More details: they were running a traditional labor-limited small business and they automated some of the work. This automation was a huge improvement and they realized it could be useful to other companies. In early 2019 they had a web app ready and started taking external customers. In late 2020 they started to see serious growth, which has continued. They let me share some numbers:
This is a run rate of ~$340k/y, up from ~$100k/y a quarter ago, ~$52k a quarter before that, ~$12k/y a quarter before that, and ~$7k a year ago. That's growth of ~50x in a year, or 7.8% a week, which is extremely good. Expenses are servers ($40/m), plus the time they have been putting into it (~20hr/wk).
We went out and practiced: she walked the route with me staying well behind. When she got to the second crossing I pretended to be the crossing guard. She seemed ready to do it on her own.
We thought together of how this could work, and the standard approach of glancing over at the clock every so often to see how much time you have left didn't seem like something she would be able to do yet. We decided to use alarms. I set up three on her tablet: start getting ready (7:15), leaving in five minutes (7:55), and time to leave (8:00). I don't give her any additional timing reminders; everything is up to her now.
(Short version: go try my new program, in your browser!)
In my original version, I counted zero crossings the estimate the current pitch (detailed explanation). Then I fed this into simple additive synthesis code. It worked, but it had a few issues:
Sometimes it would detect whistling when there wasn't any, and make clicks (or beeps in a later version).
If you whistled too quietly or not clearly enough, it would failed to detect the whistling and you get silence, or drop outs.
It was very sensitive to a "gate" parameter: set it too high and you get the first problem above, too low and you you get the second. In noisy environments that was often no good setting.
It was not steady enough to feed into an existing synthesizer, because those expect the precise input you get for my keyboard.
My simple custom synthesizer didn't sound very musical.
My new version is much better on all of these dimensions. The key idea is that because the input signal is very close to a sine wave, we can directly use it for synthesis. Here is a short snapshot of whistling:
So far, the only things that have helped have been minimizing use and icing (flexible wrist packs are nice!). I've tried two nonsteroidal anti-inflammatory drugs (NSAIDs), Ibuprofen and Naproxen Sodium, without effect. I'm about to start on the immunosuppressant methotrexate, which I have mixed feelings about, but positive on balance.
I'm still doing lots of dictation, but I haven't needed to continue with voice control. When using the computer/phone, as long as I dictate words, I've been able to still use my hands for navigation. The biggest problem is when I have substantial tasks that aren't just reading and writing, such as spreadsheet work or green-field coding. Luckily this is only a very small portion of my regular work, and I've been doing fine there, though I'm not sure what dictation will look like once I'm back in the office. I'm back to playing music, which I'm really happy about, but no jammer or fast melody.
<link rel=prefetch href=url>The browser will take a note, and then when it doesn't have anything more important to do it might request
url. Later on, if it does turn out to need
url, it will already have it.
|Code||Apartment Price Map|