Table-Oriented-Programming (TOP) philosophy is that while it's good to apply categories to snippets of code, one shouldn't be forced to have one and only one ca

Table-Oriented-Programming (TOP) philosophy is that while it's good to apply categories to snippets of code, one shouldn't be forced to have one and only one category per snippet. The hierarchical and file-based view of grouping or categorizing code is seen as obsolete under TOP's way of looking at things. We use RDBMS to manage large quantities of physical objects, so why not also use them to manage large quantities of code snippets, such as event handlers. Early databases were hierarchical also, but over time hierarchies ran out of steam. TOP believes eventually the same lesson will be learned about code management. Take MVC for example. Some code maintenance tasks are by entity and not just M or V or C. For instance, adding a new column to a given table. So if one could run a little query to list links to all modules/files/snippets for a given entity, then entity-based tasks are easier.