Filed under: Code Comprehension

Makeovers

Roughly a month ago i was hard at work, against time time and energies to integrate a whole new set of changes in the services with the UI. It was crazy to put it mildly and it was one huge chunk and it was evolving everyday. The whole transition to the new changes took a new 5 days to come to stable grounds. After i was done, i left for a week long break. I knew that the changes would continue, even from where i left off. When i came back however, change was made in virtually every way the application was conceived to begin with. The changes resulted in a drastic makeover and i was in no state to even comprehend the new dynamics of the business that were introduced in the software. I was truly lost. Makeovers are a part of any developmental process. But the big question is if they should be. At least by definition, they should not. A makeover is something that has to come after the development phase is over, instead of being a part of it. In the world of software, where the work and the daily text is  adorning the guises of programming languages, understanding the changes becomes even more difficult. One might argue that this is a common feature of any profession and is not specific or more so in the software world. But i tend to disagree here. Not because i am a part of this Industry of Logic, but because as a proponent of logic i can not help but notice that this industry is still young and is driven by a truly illogical set of rules and frameworks.

Read the rest of this post »

A Coder's Handwriting

This is a phrase coined by i-don't-know-who. But this is a phrase used my a colleague of mine at office. When ever there is any issue in the code on the TFS, instead of doing a history check and the past check-ins, this guys identifies the author of that code based on its "handwriting". Interestingly enough more often than not, he is correct. And surprisingly enough, when you think about it for a minute, there seems to be some sense in his method.

Read the rest of this post »

My Final Year Project Problem Brief

This is a snippet of my Final year Project's Problem Brief. It was an adventurous project, had loads of fun doing it. BTW, the next tutorial on Silverlight is coming up soon, so stick around. In this project we are trying to address the problems of Comprehension and Reduction of Java Code. While writing programs a programmer looses track of the flow of the code and at times even the logic of the program that he is writing. This is a very common problem for many coders, especially when they are writing lengthy programs.

Read the rest of this post »