"After all, it only takes 15 minutes to get the new files and deploy the new version of the application" he continued. "After all, how often will they change?"
I had to resist the urge to say "sooner than you might think"...
At that point I should have realized that perhaps this guy was unreachable. I say that because when I attempted to explain my position he just waved me off and immediately stopped listening and started doodling on his notepad.
Upon reflection, a number of problems were evident:
- I have done a really bad job explaining the value of using reusable components or what a "service" is
- I have done bad job of explaining why decoupling the content of an application from the code is a good thing
- I have forgotten that I was 23 once and already knew everything there was to know about everything and that there was actually a time before I had to get woken up at 2:00am because a server stopped working.
- He didn't realize that spending 15 minutes a day for a year added up to roughly 1.5 weeks of work (BTW his 15 minutes are more like 1 hour)
- I didn't make it evident that every time we redeploy the app, we kick out users and risk screwing up our main corporate web site
I guess my lesson is to realize that some folks don't get the big picture and you need to be careful about delegating important decisions to them. I find it ironic that the very people who complain about the haphazard nature of our legacy applications, are continuing the tradition of not thinking through the solution.