1,401 karma · joined April 8, 2012
"We aim to construct a physically-grounded compositional framework for hybrid system synthesis, particularly targeted at applications in robotics. Compositionality lies at the heart of language in general [WHM12] and its formalization underlies much of computer science in particular [Lee90]. However the behavioral modularization of physical synthesis for digital computing that arguably ushered in the information technology revolution [MC80] has proven much harder to achieve in analog computing technology [Mea89]. There are fundamental reasons for this challenge to become more severe in machines intended to perform mechanical work on their environments [Whi96]."
Since you know enough about this field to cite it, does it appear to you that this stuff could be written in a more comprehensible way, without losing expressive power? Or is this level of ornament necessary to say whatever it's saying?
I'm also very taken with the idea of systems propagating themselves. Formally, this is called "autopoiesis" and is its own fascinating and related rabbit hole.
The coolest thing this morning, prompted by your comment, is the "self-licking ice cream cone" [1]. This paper [2] is particularly intriguing. Thanks again.
[1] https://en.wikipedia.org/wiki/Self-licking_ice_cream_cone
It would be interesting to know if this really changed anything for anyone (competitors, VCs) for that reason. It's like the efficient market hypothesis applied to product roadmaps.
The distinction you're drawing between "guessing" and "being sure of something but being wrong about it" is hazy at best, from a cognitive science point of view, and the fact that it doesn't _feel_ hazy to a person's conscious experience is exactly why this is interesting and maybe even philosophically important.
More briefly, people are just horseshit at knowing themselves, their motivations, their state of knowledge, the origins of their knowledge. We see some of these 'failures' in LLMs, but we (as a general rule, the 'royal we') are abysmal at seeing it in ourselves.
This strikes me as the essence of expertise, the difference between talking to someone who's read a book or a review paper, vs someone who is a real expert at that thing. You can be quite competent and insightful from having done a modest amount of reading and thinking, but if you're seeing the Matrix, and know how all these forces are interacting with each other, that's just a whole other level. It makes an impression when you brush up against it.
However: it always weighs on me how this is all a matter of framing. Like, I don't know the electronics. There's a level of metal that I don't get. Some of the really high-level stuff is now beyond me, too. I catch myself saying "I should really take x {weeks, months, years} and really grok that." And yet my actual experience suggests this is a mirage.
More briefly: there are always more layers for a fuller understanding. It's hard to see how many of them are really useful. Maybe the kid who is 10x better than me at LLM collaboration will benefit more than from having a deeper stack. It's interesting to ponder how these different consequences will play out.
There's no question about this being the right way to use it for me, but I wonder if this could introduce something bad for someone just starting out, who hadn't first got all the reps with the drudgery over decades? Still mulling on that.
The fact that it usually had errors didn't bother me at all -- it got much of the way there, and it did so by doing the stuff that is slowest and most boring for me: finding the right libraries / functions / API set up, structuring the code within the broader sweep.
Interesting side note: un-popular languages, but ones that have been around for a long time and have a lot of high-quality and well-documented code / discussion / projects around, are surprisingly fecund. Like, it was surprisingly good at elisp, given how fringe that is.
p1: "What do you think of my story? Be honest."
p2: "I'd rather not say."
p1: "Seriously, tell me what you think, it's fine if you hate it. I need the feedback."
When you think about it from that perspective, it's no dumber than people are.
Part of this is surely that I don't know wtf I'm doing, but it seemed like there was not an underlying data structure held in memory that you could conveniently query / manipulate, but rather, most of the existing org functionality built some kind of structure each time you did an operation.
Would appreciate any pointers, code examples, tutorials that show how to effectively navigate / manipulate an org structure and have it reflected in the buffer, if there is such a thing.
Unfortunately, I expect Obsidian to have a serviceable outline mode before I expect Logseq to turn out a polished product. For god's sake, take on that Neovim project, and post about it!
I'm going to ruminate on this.
If you're an average American of today, you're living a life of comfort and abundance that could not have been imagined 100 years ago, and yet you'll have about the same trauma as did your equivalent back then, even though they would have dealt with things that would have killed you, figuratively or even literally.
Kind of related to Durkheim's "Society of Saints" idea [1].
This suggests a therapeutic vector: increase the variance in your own life. It probably won't be technically hard, though it would be psychologically very difficult. If the theory is right, many of your minor traumas should quickly dissolve.
It would take some amount of will to pull this off, of course. Though probably less suffering than the aggregated suffering conferred by the traumas.
[1] https://www.tutor2u.net/sociology/reference/durkheim-on-devi...
https://sleepdiplomat.wordpress.com/2019/12/19/why-we-sleep-...