[carlinm]

I don’t see this as hiding code complexity or an alternative to writing cleaner code. It seems the argument is that when we come to a file/class/etc., that we should be initially presented with the outline rather than both the outline and details. It’s an approach to orienting oneself to a grouping of functionality, made first class by the IDE. It’s almost like opening a book and starting with the table of contents before diving into any specific chapter’s details. Allowing the reader to get a sense of what’s covered by this grouping of functionality before diving into the details. I haven’t tried this approach myself but it seems like an interesting exercise at the least.