Deleted code doesn’t contain bugs, they say. I always felt kind of unsafe with the idea of actually and straightforward removing code while into refactoring smaller or larger parts of the systems – after all, same as it doesn’t contain bugs, deleted code also doesn’t contain business logic anymore which might not be what you want at times. Yet, trying to clean up parts of (the Java / Java EE based) components in our system, I have to some degree changed my mind about that.
I’ve recently been writing about Apache CouchDB and its various features of interest in our environment, and I will continue doing so as, after working with this platform, I came across a bunch of thoughts I quickly felt like pinning down, either in order to remember them, or in order to eventually have some discussion on that topic as I still consider myself learner as far as both CouchDB and architecture on top of CouchDB is concerned.
More than once, the last couple of weeks I repeatedly stumbled across situations in which I had to remember the infamous Law Of The Instrument in order to explain some peoples attitude towards technology and overall technological decisions. I am not sure if this “law” holds completely true all the time, but I am sure there are some valid points to it.
Looking back at yesterdays Dresden Eclipse Indigo demo camp, I ended up with a couple of thoughts in my mind, both related to the technologies demonstrated there, and related to how to make meaningful use of them in a real-world environment. Overally, this demo camp event mainly was dominated by topics related to modeling tools and concepts on top of Eclipse technology – hardly a surprise knowing that itemis, the company behind tools such as XText, also appeared as main sponsor and organizer of this evening. Consequently, XText also appeared on the agenda in its latest EMFText and how to easily build (or, better, “have around”) an Eclipse integrated debugger for EMFText based domain specific languages at no additional costs. Running a DSL interpreter and doing debugging just the way you’d do it in Java code surely is an interesting experience. Not even talking all too much about ProR integrated with XText for the purpose of capturing requirements in a somewhat formal way. In some situations, this is just what you want or need, and problems to eventually be solved by using these tools are obvious almost immediately…