The folder thing is something I’ve noticed too. The problem with folders is that in most interfaces you can’t see their content until they’re opened. In some re

The folder thing is something I’ve noticed too. The problem with folders is that in most interfaces you can’t see their content until they’re opened. In some really bad interfaces you can only see one open folder at a time. Flat lists let you see the entire thing at once. As long as there is some sort of natural sort order, it’s still a “neat” way to organise things. E.g.: SomeApp-PRD-Web SomeApp-PRD-DB OtherApp-PRD-Web OtherApp-PRD-DB OtherApp-PRD-API Is roughly how I organise cloud resources. You can instantly see that there are two apps, and that both are web+db but the second one also has an API. If you had folders you’d just see this: SomeApp OtherApp That just tells you that there are two apps, and nothing else. You have to navigate several times to get to the detail you could see at a glance with the flat structure. Similar concepts apply to code at every level. I avoid overly abstract functions that do their job through seven levels of trivial abstractions for the same reason. A one-page “flat” function can be more readable and maintainable.