Thinking Too Big vs. Not Big Enough - Application Design
Musings , Project Management , design 123 Comments »I wrestle with this almost daily. I work in a place where we have years of legacy applications just lingering about, in need of service. These gnarled old dwellers of the servers don't know how to play nicely with each other, and they weren't made to talk to some API somewhere. They simply "are" and that's how they need to be repaired.
Or...
We can remake them in the image of ThePerfectApp(tm) born from an ultimate UML diagram and a sacred requirements document! It will be stronger, and faster than its predacessor and will last several years in its powerful domain of extensibility! (cue scary lightning sounds)
Or yet again...
We find a balance and be realistic about our resources and our needs and seek a balance where the old and the new can co-exist in harmony.οΎ Yeah, I'm not so sure of that - or at least how to achieve it. All I see in this solution is a wild inconsistency across the enterprise that is sure to confuse developers for years to come. Can't we just "pause" life and go fix everything for about, say, twelve months or so?
Recent Comments