Just some random feedback on the val.town interface. The concept is interesting but I have one gripe. I want to know what the code I'm about to run will do and

Just some random feedback on the val.town interface. The concept is interesting but I have one gripe. I want to know what the code I'm about to run will do and I notice the pretty unique `@stevekrouse.hnLatestPosts` type interface where it looks like you can reference functions. But this leads to a deep chain of reference. Like, that function leads to `@stevekrouse.hnSearch` which leads to `@stevekrouse.fetchJSON` which leads to `@stevekrouse.normalizeURL`, etc. There is some kind of DAG of dependencies that is invisible to me. I'm wondering what could be done from a UI perspective here? Like, maybe a tree view where each node is expandable? Right now it just pops open a new browser tab and I end up with context spread across multiple tabs. The concept of composable references is powerful but I think the UX could be improved.