When you zoom out on Google maps, usually the street names and bussiness pins disappear. This code style is like having a fully informationally dense zoomed out map. Being too zoomed in is definitely frustrating, and reminds me of early attempts at "mobile" web pages. But I'm not sure that this condensed code style is a good general solution either, it certainly seems overwhelming, like a where's waldo puzzle.

I prefer having a consistent information density regardless of zoom level. When I would like to see more details, I would like to achieve that by zooming in. When I want the overview, I'd prefer to zoom out and have certain details omitted from the map.

Having a clear and by-convention code organization is one way to achieve this. Then to drill into the details, just navigate the project directory to the right file.

For rabbit Hole style hunting, following references/symbol usage/definition is ideal, which is enabled by modern IDEs.

K and family are made for data analysis. Data analyses are relatively simple software projects that don't have a very wide scope. I think this dense style of programming falls apart when you consider the breadth of requirements of typical modern application software.

I have definitely seen many 'typical modern applications' where the business logic can be summarized into 100 lines of code. The rest is just shoveling things around.