Win a copy of Mesos in Action this week in the Cloud/Virtualizaton forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

how much time it takes to fresher to learn debugging and solve the issues without facing any problem

 
ishikaji Agarwal
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
how much time it takes to fresher to learn debugging and solve the issues without facing any problem in eclipse...
actually i am very new to this nd am facing a lot of problem so i want to know how much time it vl take?
 
Seetharaman Venkatasamy
Ranch Hand
Posts: 5575
Eclipse IDE Java Windows XP
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Welcome to JavaRanch! also please go through UseRealWords

the answer to your question is it depends on your interest
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 34401
346
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Welcome to CodeRanch!

It also depends on what you mean by "without any problem". There are also problems solving issues. That is why they are issues. I think you mean that you feel comfortable with the debugger. And not that long. Less than a week if you are focusing on it.
 
ishikaji Agarwal
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I mean i do debugging bt i m nt able to undrstnd where the actual error is?
For example-- on a page you add some data and on screen it shows successful bt data is not present in database
and you have to check why it happens?
 
Kunal Lakhani
Ranch Hand
Posts: 622
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
ishikaji Agarwal, you have been said earlier
Welcome to JavaRanch! also please go through UseRealWords

Use 'but' instead of 'bt', 'am' instead of 'm', 'not' in place of 'nt'
 
Anayonkar Shivalkar
Bartender
Posts: 1557
5
Eclipse IDE Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
ishikaji Agarwal wrote:I mean i do debugging bt i m nt able to undrstnd where the actual error is?
For example-- on a page you add some data and on screen it shows successful bt data is not present in database
and you have to check why it happens?

Well, those kind of problems are not at all related to eclipse (after reading your original post, I thought you are facing difficulties during debugging 'with eclipse' )

So, first thing first - in multilayer application like this (which involves GUI and business logic and DB), logging is one of the best friend of developer. Do extensive logging (even if at debug level - I mean 'debug' level of logger).

Secondly, try to figure out who is giving success message to GUI. What exactly happens so that GUI feels that there is a success? Chances are that GUI or business layer is reading some 'result' value to decide this.

Lastly, track down who is writing to that 'result' stuff? Somewhere, it must be happening that even without putting the value in DB (or even after a failed insert query), somebody is shouting 'success!' and modifying that result object accordingly.

I hope this helps.
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 34401
346
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The actual skill of debugging takes time and practice. And it is never easy.
 
ishikaji Agarwal
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
ok thank you Anayonkar.
 
Anayonkar Shivalkar
Bartender
Posts: 1557
5
Eclipse IDE Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You are welcome.

However, as Jeanne Boyarsky said, it takes time and most importantly - patience.
 
ishikaji Agarwal
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
yes i come to know that.
 
Kiaama Liames
Ranch Hand
Posts: 52
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The skill of debugging is related to your programming skill and experience
 
arulk pillai
Author
Ranch Hand
Posts: 3387
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It depends on 4 things

1. Your domain knowledge -- how well you know your application
2. Your IDE related debugging skills like adding break points, stepping through, adding watch list, etc.
3. Your problem solving skills to isolate, apply reasoning, etc.
4. Technical know how -- for example incorrect implementation of equals() and hashCode() can cause tricky issues that are harder to debug.
 
fred rosenberger
lowercase baba
Bartender
Posts: 12124
30
Chrome Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
"without facing any problems" is an AWFUL high bar to set. If you are always learning new technologies (and why wouldn't you), you should expect to always encounter new problems. There is nothing wrong with asking for help when you need it. The important thing is a) to make an effort to learn/figure it out yourself first, and b) to learn from what someone told you, so you don't get stuck on the SAME problem over and over.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic