#Nice clock html software

#Nice clock html software

More time passes, the irritating вЂchief software architectвЂ™ has been sacked and our little application is now core to our organisation. If weвЂ™re not so good we might have shoe-horned repeated and multi-dimensional values into some strange tilda and pipe separated strings. If weвЂ™re good, by now we will have moved our configuration into a dedicated XML schema that gets de-serialized into a configuration model. Now appsettings are no longer sufficient, we have groups of values and hierarchies of values. The business continues to evolve and as it does, more values are moved to our configuration file.

Time passes and our application is now somewhat entrenched in our organisation. The solution is simple, weвЂ™ll move those values out into a configuration file, maybe some appsettings in our App.config.

Months pass, the application becomes widely used, but thereвЂ™s a problem, some of the business values change, so we find ourselves rebuilding and re-deploying it just to change a few numbers. ItвЂ™s not expected to last very long, just a stop-gap in some larger strategic scheme, so weвЂ™ve hard-coded all the applicationвЂ™s values. We start at midnight, 12 oвЂ™clock, with a simple new requirement which we quickly code up as a little application. Let me introduce you to my вЂConfiguration Complexity ClockвЂ™. I still think itвЂ™s good advice, but be warned, like most things in software, itвЂ™s good advice up to a point. вЂњThey will have to change at some point, and you donвЂ™t want to recompile and redeploy your application just to change the VAT tax rate.вЂќ I took this advice to heart and soon every value that my application needed was loaded from a huge. When I was a young coder, just starting out in the big scary world of enterprise software, an older, far more experienced chap gave me a stern warning about hard coding values in my software.