5 ms·
I was reading some of your other comments, and what a pleasant surprise to another Portland psychiatrist on HN. Small world.
by phren0logy 11y ago
I was reading some of your other comments, and what a pleasant surprise to another Portland psychiatrist on HN. Small world.
- MichaelCrawford 11y agoI live in Salmon Creek but often come to Portland. mdcrawford@gmail.com http://www.warplif.com/mdc/books/schizoaffective-disorder/ http://www.warplif.com/mdc/books/schizoaffective-disorder/
- MichaelCrawford 11y agohttp://www.warplife.com/mdc/books/schizoaffective-disorder/ http://www.warplife.com/mdc/books/schizoaffective-disorder/ s/warplif/warplife/ I Should Not Drink And Post.
- jrapdx3 11y ago> ... what a pleasant surprise to another Portland psychiatrist on HN. Small world. Pleasant surprise indeed, what are the odds? Obviously writing here is motivated by interests in computing as well as brains. Your comment a few weeks ago about SICP strongly resonates. Scheme has been a productive language for me, I've done useful things with it. Curiously along the way it's taught me subtle lessons applicable in my other work. That's not every doc's taste to be sure, no doubt an angled view among a quirky subset. Maybe not so strange finding unusual souls in a place known for its weirdness.
- deleted 11y ago[deleted]
- phren0logy 11y agoIt seems like too good a coincidence to waste it. If you'd like to grab a coffee some time, send a DM to @phren0logy.
- dang 11y agoWhat a wonderful subthread. Care to describe any of those "subtle lessons applicable in [your] other work"?
- jrapdx3 11y agoOK. Being subtle it's hard to put into words, but I'll try. Scheme has a certain beauty, and symmetry when well-expressed. Paradoxically, a seemingly simple application can be perplexing on first glance, its meaning not immediately clear. Sure, the formal elegance is there, but how does it work? The Lispy recursion vital to Scheme won't easily yield to cognitive brute force, when it's obscure to me, it has to sink in over some time. It's not pure thought, one has to see it or feel it. More than just understanding, it has to make sense to me, that is, achieve a higher level of integration among my internal processes than the term "understanding" implies. But once I "got it", it seems simple, a mystery whatever made it hard in the first place. Creating a useful program it's necessary to make sense of the tasks in order to translate into compilable expressions. It really is a kind of conversation in a peculiar language. As I see it, there's a parallel in approaching human illness as a set of algorithmic processes, albeit extremely complex. Here we can apply a lesson, avoiding the temptation to force fit signs and symptoms into some preconceived template vs. what is learned during interaction, a more accurate, nuanced picture of the problems can emerge. The work of healing is recursive, similar elements occur again and again. But as in a Scheme loop, recursion can end by trapping the right conditions. Wait, there's a clue. What is the condition that ends, at least damps, the troublesome recurring behaviors? Most of the time a "handle" can be found, an opening for intervention. Programming teaches there's no universal solution to problems, solutions have to vary according to the situation. Each person with an illness has a unique disease, no two diseases are alike. Each person speaks a different language, we have to develop fluency in that language to be able to help. Skilled healers learn to build "macros" that shape the tools to the problem, sort of like evolving a DSL in Lisp/Scheme. Not exactly the same, but an element of the "mental models" that support effective treatment decisions. Wow, that's pretty long. I don't know how good an answer it is, though a worthy question.
- marincounty 11y ago