Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> almost universally when I see people use print debugging they seem to take quite a bit longer than just break pointing at the problem area.

Could it be... because they don't know where the problem area is yet? Which is what the original article and most comments in favor of print debugging say.



How can they not know? If you see unexpected behavior in some subsystem, it should be easy to pinpoint.

e.g. in a UI context, timeline shows wrong data. Start there and work backwards.

I can only imagine it's hard to pinpoint if the code is not factored well.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: