Build for Necessity, not Architecture
(source: Pixabay.com ) Build for Necessity, not Architecture, ... does not describe the current Codavore code base. In fact, I'm about to throw out my last 6 weeks of work, not because its broken, but because this beautifully crafted solution turns out to add a great deal of pain it was designed to avoid. And when coming to terms with this, the same solution kept popping up in my notes: "Build for necessity, not architecture." This is about what I did wrong, and how I plan not do it again. If a class doesn't talk to any other class, then it can be written any way it feels like. Its bugs will be isolated, and so can be fixed without risk in the future. When multiple points in code need to talk to the same resource, or understand multiple classes, then an architecture needs to be applied to standardize their connection. Always question if a new architecture could/should be solved by an existing one. Sometimes you need to shift the problem. Thos