Skip to main content
37 events
when toggle format what by license comment
S Feb 12, 2014 at 15:51 history notice added maple_shaft Historical significance
S Feb 12, 2014 at 15:51 history locked maple_shaft
S Jan 22, 2014 at 14:16 answer added Shailendra Madda timeline score: 0
S Jan 22, 2014 at 14:16 history made wiki Post Made Community Wiki by Shailendra Madda
Feb 16, 2012 at 23:35 comment added Warren P Debugging != PAPER EXERCISE. Your question is full of contradictions and makes NO SENSE.
Feb 16, 2012 at 22:58 answer added user39741 timeline score: 1
Feb 16, 2012 at 22:55 comment added Mike Dunlavey Finding bugs by just eyeballing code is not much use. The more useful skill is stepping it under an IDE and finding bugs that way.
Feb 16, 2012 at 22:36 answer added HLGEM timeline score: 1
Jan 3, 2011 at 10:29 vote accept Manoj R
Jan 2, 2011 at 23:08 comment added Winston Ewert Depending on the amount of information given about the bug it sounds like it may have been to hard. Off-by-one errors are common and showing someone code and expecting them to find them is hard. (Which is why its often recommended to write test cases which hit the edge cases, the computer will do a better job of following the code then you will) Even if you gave particular indication of what the code did wrong (i.e. which inputs fail), I suspect many good coders would have trouble without a debugger to use.
Dec 24, 2010 at 5:06 history edited Manoj R CC BY-SA 2.5
edited body
Dec 24, 2010 at 2:08 comment added Job @Manoj R, are you sure that you could find the same problem given the same amount of time? Are you sure that just because the applicant does not find a problem on paper in 20 minutes, that she would not be able to get good at it with Google (Yes, fucking Google) on her side and a couple of weeks of practice?
Dec 24, 2010 at 1:54 answer added JB King timeline score: 1
Dec 23, 2010 at 21:33 answer added Omega Centauri timeline score: 2
Dec 23, 2010 at 21:32 answer added ern0 timeline score: 0
Dec 23, 2010 at 20:32 answer added mctylr timeline score: 3
Dec 23, 2010 at 18:25 comment added Manoj R Edited the question.
Dec 23, 2010 at 18:24 history edited Manoj R CC BY-SA 2.5
added 24 characters in body
Dec 23, 2010 at 18:22 comment added user1249 Did you say "find the bug?" or "here is the stack trace. what is the bug?"
Dec 23, 2010 at 18:16 history edited Manoj R CC BY-SA 2.5
added 238 characters in body
Dec 23, 2010 at 17:30 answer added JohnFx timeline score: 5
Dec 23, 2010 at 17:27 history edited JohnFx CC BY-SA 2.5
edited title
Dec 23, 2010 at 17:23 comment added user1249 COuld you please elaborate on the difference between the skills shown by the puzzles, and what the program was the application could not find a bug in?
Dec 23, 2010 at 17:23 comment added Mason Wheeler @Fanatic: Only if you're only working with your own code. Most of the debugging I do at work is digging up other people's errors.
Dec 23, 2010 at 17:21 answer added Macneil timeline score: 5
Dec 23, 2010 at 17:10 comment added leed25d some people are better at it than others. it is often difficult to spot an error in a piece of foreign code --especially during a stressful interview.
Dec 23, 2010 at 17:04 answer added TMN timeline score: 7
Dec 23, 2010 at 16:02 comment added Fanatic23 Debugging is retrospecting your own errors, kind of. Nobody's perfect.
Dec 23, 2010 at 15:58 answer added Srikanth Remani timeline score: 1
Dec 23, 2010 at 15:45 comment added Demian Kasier You can only code as good as you can debug. the two go hand in hand in my book.
Dec 23, 2010 at 15:37 answer added BarsMonster timeline score: 11
Dec 23, 2010 at 15:36 answer added Mark Freedman timeline score: 10
Dec 23, 2010 at 15:36 answer added spong timeline score: 3
Dec 23, 2010 at 15:36 answer added Jon Hopkins timeline score: 24
Dec 23, 2010 at 15:33 comment added Michael K Was he allowed to run the program, or did he have to find the error looking at the code?
Dec 23, 2010 at 15:32 answer added Darknight timeline score: 37
Dec 23, 2010 at 15:28 history asked Manoj R CC BY-SA 2.5