>it might be fun to represent lisp code in a treemap Wow, yeah, that's a really interesting idea. Is there just one (good) way to map a codebase? Many? It see

>it might be fun to represent lisp code in a treemap Wow, yeah, that's a really interesting idea. Is there just one (good) way to map a codebase? Many? It seems like a bad idea at first glance, since the map shows, at any level, more things with less context-per-thing when compared to straight text. It seems totally natural to use it for profiling. Refactoring would be a lot more grokable if it could all be visualized at once. But how would it work for scanning/editing & digging through documentation?