Comments on: Stack Traces and Consulting Rates http://myarch.com/stack-traces-and-consulting-rates Builds and bytes Mon, 07 May 2012 05:20:01 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Steve Loughran http://myarch.com/stack-traces-and-consulting-rates/comment-page-1#comment-34829 Steve Loughran Wed, 21 Jan 2009 08:58:14 +0000 http://myarch.com/?p=141#comment-34829 mmm, we produce some pretty big stack traces too. A root cause is the fact that Java interfaces/base classes limit the scope of all exceptions that aren't descended from RuntimeException to a select few. If you subclass other people's code, or wrap other people's code in your framework: nested stacks. The nice thing about OSS code is the recipient gets to handle the trace; paste it in the IDE and see what went wrong. For closed source, all you get to do is paste the text into google and see who else got the same error. Which is why you should never put stack traces, error messages or windows error codes into blog entries, except as screen shots -otherwise you end up fielding the support calls from everyone whose search turns up your blog entry mmm, we produce some pretty big stack traces too. A root cause is the fact that Java interfaces/base classes limit the scope of all exceptions that aren’t descended from RuntimeException to a select few. If you subclass other people’s code, or wrap other people’s code in your framework: nested stacks.

The nice thing about OSS code is the recipient gets to handle the trace; paste it in the IDE and see what went wrong. For closed source, all you get to do is paste the text into google and see who else got the same error. Which is why you should never put stack traces, error messages or windows error codes into blog entries, except as screen shots -otherwise you end up fielding the support calls from everyone whose search turns up your blog entry

]]>