And actually it was even simpler than that. No coding involved - I did this with nothing more than a handful of IFTTT recipes. Hook it up to Google, listen for "Home" commands, and send them to a Google Spreadsheet. I have one for each type of entry I wanted to log - meals, symptoms, medications. Planning to add activities and some general exercise capturing when I have another 20 minutes (ha).
And I'll add some biometric logging, although my ultimate goal would be to actually script that to get data directly in from my BP monitor and a scale automatically. Same with sleep data from the app I use to track that. Both would be easier if I were using one of the devices or apps for tracking those that IFTTT supports.
The idea is to set up and collect as much as I can with as little manual entry (i.e., typing) as possible, with as little coding as possible.
Exacly. Pipes and grep functionality are great abstractions that have saved people countless hours.
The fact that there are a lot more easy to use tools today means things are easier to do today, and are going to keep getting easier.
There's no such thing as "real" tools; there are only different models of risk. If you're building a system that needs speech recognition, what you should care about is the risk that the next recognition won't be correctly interpreted, and the odds of that are probably greater for a local installation of PocketSphinx than for a Google service, even including the possibility of it "going away".
Sounds like someone scripted an Ajax-Json-API-Call to Google Servers.. today's equivalent of writing a small shell script.. "wow, I piped grep, had I done this by hand in C this would have taken me days" would have been the tweet in the 80s.. what did they call it back then, Gopher?