code complexity and debugging

I don't use redundant logic because it will make code maintenance more difficult and costs much time. It will be harmful for maintenance. But reusable module has complexity because it has variety features to some levels. So, in some respects, as you are developing, code complexity is inevitable. How can we manage this complexity. Especially when debugging, you can takes much time because of this code complexity. You may say that efficient debugging tools like eclipse will be helpful. Yes, I agree. But nevertheless it will take much costs.

 

Nowadays, inserting debugging messages are very important when developing. As you develope, the program becomes complex more and more. And when you do debugging for some error or issues, that consumes much time. Sometimes, execution and launching itself take much cost and time. For example, you may or have to wait for much time. So, in just one execution, you should solve that problem. But in many case, you can't do so. and debugging itself takes much time even days. But if you inserted useful debugging messages, it could be very helpful to you. You can think easier with those messages and sometimes, without execution, you guess where the problem occurred.

 

But in fact, inserting such messages is boring and takes much time initially. And you should think many things and more things for these message. For example, you could not implement just developing code but also think how to check whether the logic works fine or not.

 

Too many debugging message may be a burden mixed with other message. So, you should design well for this debugging message architecture.