In another world, where the interdisciplinary cards fell a little differently, and the history of clinical psychiatry sustained talking therapy in lieu of pharm

In another world, where the interdisciplinary cards fell a little differently, and the history of clinical psychiatry sustained talking therapy in lieu of pharmaceutical hegemony, I think programmers of all types would read Lacan a lot more. Not for any one of his clinical findings, but as so many lessons in system design. As so many lessons in the determining nature of syntax. As inspiration for they way infrastructure determines superstructure. The clinical stuff was obviously the most important thing to him, but it doesn't even touch on his thoughts about language, which turns out to be thoughts on cybernetics, and the spontaneous effects of making some variables static and others dynamic, so to speak, that's really all it is. That, IMO, is where the good stuff is, if your not an analyst.