3 ms·
A huge drawback to changing this is all of our computing resources are based on a 100+ year old concept of a file cabinet with folders and files. It has a lot o
by mattbrewsbytes 4y ago
A huge drawback to changing this is all of our computing resources are based on a 100+ year old concept of a file cabinet with folders and files. It has a lot of historical traction which you would be attempting to go up against with a different concept.
As long as the code is easy to find and doesn't have similar naming as other code you should be good to organize however you want. If you work on a team then make some decisions as a team on how to organize files. I work with Rails which has an opinionated view on folder/file structure which is great because I don't have to spend time thinking about it and can focus on getting things done.
- jeddy3 4y ago> all of our computing resources are based on a 100+ year old concept of a file cabinet with folders and files. While they are based on the same concept, putting things inside of things (in hierarchies) is a pretty solid way of sorting stuff. There are other ways as well, such as labels/tags. But regardless of technology I feel like folders (in one way or another) is one of the tools you would reach for.
- perilunar 4y ago> putting things inside of things Were you thinking of this Monty Python skit when you wrote that? https://youtu.be/LFrdqQZ8FFc https://youtu.be/LFrdqQZ8FFc