@matigo That has generally been my experience. JSON looks so new and wonderful and easy :P
@matigo If I just structure my data in JSON without worrying about _id and _rev, I'm safe for if I ever want to import everything into CouchDB or similar, right? I.e. just keep it all in one folder for now with filename YYYYMMDD-restaurantname, one file per entry?
@matigo CouchDB actually looks pretty good. I was originally wondering how I'd go about managing the documents once I'd written them.
@matigo Then yes, not as strongly typed is the main appeal. What do you mean by full programmatic and what benefits would there be going down that route?
@matigo Not sure what you mean by that.
My notes tend to be one section per course, then one section for ambiance, another for general notes, etc. So the appeal of JSON is I don't have to have 20 columns for the entire table (course01name, course01comments … course10name, course10comments) since such long dinners aren't a habit.
Been thinking about it and it looks like I should be compiling my restaurant notes into something like JSON.
Had lunch and then a nap, with plans to go for a walk before this afternoon's talk about the disconnect between language and smell in English.
But now it's snowing. Heavily. Wet snow, unfortunately. I have about 2 sips of coffee to make a decision.
@matigo That, or something modelled after the Magic is Might statue [harrypotter.wikia.com]?
// @streakmachine @peemee