What resources are available to convince a developer that Java stack traces are worth logging -
i've landed in new code base. while working make application run locally, noticed getting one-liners errors in log , console output - no stack traces. started searching code , thing find logged exception message. ditto "chaining" exceptions: message being retained. mentioned project's sole developer , asked if intentional design decision. reply was, in part, "i don't think we'd gain [logging stack traces]."
from years of java development, know how valuable stack traces are: tell line exception happened on , can track how got there. read stack trace , relevant code , that's enough solve 80% (n.b.: statistic has no statistical backing) of errors encounter.
i'm not looking arguments log or when - that's not question, , it's been covered elsewhere. really, seems such fundamental thing me never thought of how explain other "strack traces show error was." hoping find quote effective java or like, google hasn't turned far.
any suggestions of authoritative, convincing sources descriptions of why should pay attention stack traces?
create intentional error in code base , make him track down :-). seriously, have arguments, if demonstrate how helps , how time saves when tracking down bug.
Comments
Post a Comment