4 ms·
There is just a nice magical moment though when you grok what an application does and how it is organized, especially when you didn't write it, which is likely
by matt_s 11y ago
There is just a nice magical moment though when you grok what an application does and how it is organized, especially when you didn't write it, which is likely the most often case.
I think a large issue is when an application has new people working on it or entirely new teams that maintain it. That is when the original authors methodology and organization of the application falls to the immediate need of the day.
The functionality of the software should speak for itself. Commenting your code with why you are doing something is important to help other maintainers later on, including yourself, understand what you were thinking when it was written.
- donatj 11y agoThis. Organization is in the eye of the beholder. I've seen my code bases taken over and completely reversed, and frankly I have done the same. If only there was a better way to communicate exactly what you were trying to do.
- matt_s 11y agoI don't know if this is solvable, it could just be human nature. Some folks like the analogy of software and building construction. I like the comparison to cooking... in this case the closest thing would be how a chef sets up their work space and how it is organized for what they are cooking. Some like it one way, some like it another - is one way better or worse?