Comments on: Lazy java developers (or why I hate stack traces in logs) http://phasorburn.com/index.php/archive/lazy-java-developers-or-why-i-hate-stack-traces-in-logs/ Warning: Do not look into phasor with remaining eye. Mon, 21 May 2012 21:23:56 +0000 http://wordpress.org/?v=2.0.10 by: Michael http://phasorburn.com/index.php/archive/lazy-java-developers-or-why-i-hate-stack-traces-in-logs/#comment-4047 Mon, 19 May 2008 17:54:12 +0000 http://phasorburn.com/index.php/archive/lazy-java-developers-or-why-i-hate-stack-traces-in-logs/#comment-4047 Sweet, a new way to get developers to remove dodgy bits from otherwise good products. Just piss him off enough. Seriously though I use comm edition at home and I've always banged my head at the excessive stack dumps, it makes it really hard for an admin to discover some tiny bugs like disk permissions or wrong passwords. Sweet, a new way to get developers to remove dodgy bits from otherwise good products. Just piss him off enough. Seriously though I use comm edition at home and I’ve always banged my head at the excessive stack dumps, it makes it really hard for an admin to discover some tiny bugs like disk permissions or wrong passwords.

]]> by: Trever http://phasorburn.com/index.php/archive/lazy-java-developers-or-why-i-hate-stack-traces-in-logs/#comment-4046 Mon, 19 May 2008 16:26:33 +0000 http://phasorburn.com/index.php/archive/lazy-java-developers-or-why-i-hate-stack-traces-in-logs/#comment-4046 Glad to be of service! Thank you for fixing this. Much more effective than logging an official bug, methinks. LOL. Glad to be of service! Thank you for fixing this.

Much more effective than logging an official bug, methinks. LOL.

]]> by: Dumb. Ass. Java. Propeller Head. http://phasorburn.com/index.php/archive/lazy-java-developers-or-why-i-hate-stack-traces-in-logs/#comment-4045 Mon, 19 May 2008 03:22:30 +0000 http://phasorburn.com/index.php/archive/lazy-java-developers-or-why-i-hate-stack-traces-in-logs/#comment-4045 I own that code, and I agree that it's completely asinine that we log a stack trace on simple auth failures. I'd always thought that at some point I'd edited it out and the support folks had made me put it back in. But I just checked the source control history... and that line of code has never once budged since the first IMAP checkin. I've been pissed off for years that I wasn't supposed to remove that line, and, uh, yeah. It'll be gone in 5.0.7. So... thanks for the rant. Dickhead. I own that code, and I agree that it’s completely asinine that we log a stack trace on simple auth failures. I’d always thought that at some point I’d edited it out and the support folks had made me put it back in. But I just checked the source control history… and that line of code has never once budged since the first IMAP checkin. I’ve been pissed off for years that I wasn’t supposed to remove that line, and, uh, yeah. It’ll be gone in 5.0.7.

So… thanks for the rant. Dickhead.

]]>