So a semi-related thing I've been casually thinking about recently is how to develop what basically amounts to a hand-written programming language.
Like a lot of other people I make to-do lists and take detailed notes, and I'd like to develop a written notation that not only captures basic tasks, but maybe also simple representations of the knowledge/emotional states of other people (i.e. employees).
More advanced than that, I've also been trying to think of ways I can take notes in a physical book that will allow a third party to make Anki flashcards or evernote entries based on my script. It has to be extremely dense to fit in the margins of a book, and must capture distinct commands like "make a single cloze deletion card for this sentence" and "make four separate cards for this sentence, cloze deleting a different piece of information for each card but otherwise leaving everything intact" and so on.
Any thoughts?
Subscribe to RSS Feed
= f037147d6e6c911a85753b9abdedda8d)
I'm confused here: You seem to be analyzing a troubleshooting process. How exactly did the troubleshooting process fail? I can see that there's some criticisms of what was done. But I don't see how this troubleshooting process resulted in disaster.
Because I missed numerous implications, needlessly increased causal opacity, and failed to establish a baseline before I started fiddling with variables. Those are poor troubleshooting practices.