Akram Chotunukki

Greenhorn
+ Follow
since Nov 16, 2009
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Akram Chotunukki

Thank you Burk and Jacquie. You responses help me. You have answered on "why" part and to some extent "how" part of "art of debugging".
14 years ago
I think I am still waiting for better suggestions from JavaRancher's.

Burk Hufnagel wrote:
The system you describe doesn't make a lot of sense
Burk



I agree that if you need to understand the as-is system you need to execute test cases/test data (if they already exists) but believe me, in my experience I have just given source code like as I said without any kind of documentation and even test cases/test data are not given. So whatever it takes to make the next developer life easier, I need to do that starting from scratch taking the initial pain to take to understand the code and deliver the solution with unit test cases, documentation etc. But I want some good debugging tips
14 years ago
Dear Jacquie

I am Java/J2EE developer from past 7 years. I worked on different kinds of java applications and j2ee/soa based enterprise applications and technologies like XML, SOA, WEB SERVICES, INTEGRATION PRODUCTS LIKE BPEL, ESB, WEB APPLICATIONS ETC.

Lot of times in our career we have to work on Maintenance Projects (aka brownfield development) since there are very few Development Projects (aka
greenfield development) opportunties we get. So we need to have good debugging skills and a good temperament to understand the code that already exists.

My experience at least is that I have given just source code and was asked to deliver the solution or fix bugs/code-issues etc. without being given any code documentation, application documentation
, requirements documentation, design documentation etc. and in these scenarios understanding the code can be challenging and daunting task as 80% of your project time you may be running the debugger for understanding the requirements and problem at hand. This approach is not acceptable but we have do not have choices most of the times. So a devloper who has good temperament in reading/debugging the code all day long can have good career in projects or companies. And I am not good at debugging the code which is the area I would like to improve upon.

I request you to give some suggestions on how to improve our debugging skills based on your vast industry experience. For debugging skills, I understand that it depends on individual
skills, his grasping skills, analytical skills etc. however I would like to know how to improve on them ? and any debugging tips from you ?
may be we can run eclipse debugger and understand but would like to hear from you the smart ways of understanding code written by others ? how to debug smartly code written by others ?
any tools, techniques, tips, hacks, strategies etc. we can use that increase our productivity in debugging code ? how to smartly debug web applications etc. ? etc.


Thank you in advance for your time on my thread.


- Akram
14 years ago