Disqus - Latest Comments for jsorensen

Re: Fix a bug in Ruby’s configure.in and get a ~30% performance boost.

jsorensen — Tue, 05 May 2009 05:04:26 -0000

Good stuff, keep it coming!

With the risk of being "that guy", are you submitting this upstream?

Does it ever make sense to use the old behaviour of --enable-pthread (eg. why the extra flag)?

Re: The Exciter - Why You Should Deploy Your Next Application on Ruby 1.9 and a Rant in General

jsorensen — Fri, 27 Feb 2009 09:37:06 -0000

Oh yeah, repository sharing sites, as well as git it self is just the enabling medium here.

The real problem in all this is of course the fact that maintainers sometimes stop maintaining, for various reasons (and that's fine). Maybe something is needed that takes advantages of the social distributed aspect, but isn't geared towards who has the longest HEAD (no pun), but rather how many are actually using a gem. And not decided by vote, but actual usage and gem downloads.

Re: The Exciter - Getting Webby With It

jsorensen — Mon, 29 Dec 2008 11:53:49 -0000

I did originally :) Except it confuses webby when it's in a post (thinks its part of the yaml header)

Re: Verbose logging will disturb your sleep

jsorensen — Tue, 28 Oct 2008 18:13:45 -0000

:)

And my point is that actually sitting there watching those logs feels like an anti-pattern in the first place (information overload is just the symptom/consequence of that), when you really should be collecting and filtering that data from a bigger perspective in order to find correlations and causes, just like you would with any other system related data (performance graphs over time being a good example).

Re: Verbose logging will disturb your sleep

jsorensen — Tue, 28 Oct 2008 17:50:37 -0000

Doesn't matter if it's rails, postgres, tomcat or apache, it's the idea of actually doing the mundane task of sitting there, watching all those little things scroll by, while possibly missing the bigger picture; the overall system components interacting.

But sure, it all depends on what exactly you're looking for in those logs...

Re: Verbose logging will disturb your sleep

jsorensen — Tue, 28 Oct 2008 16:38:45 -0000

The other side of the issue may very well be that your actual approach to viewing the log is flawed. I definitely see your point, but I want to raise it with a "don't tail -f logfiles".

The problem with tailing logfiles is that your context is wrong, you're spend braintime trying to find that particular logging statement (at least if you're trying to figure out the symptoms of an issue), instead of trying to figure out what actually is wrong when all the cogs run together.
Logging to a system that allows you to filter and match timestamps against other systems' logs seems like a much nicer way of spending "braintime". I keep hearing splunk.com is good, and there's a few other solutions whose names escape me right now.

Granted, I haven't used such an approach too much, but frankly I'm just tired of shifting and grepping through all those log files. I'd much rather be in a situation where I could log more and filter more afterwards/meanwhile, than sacrificing (useful) log output in order to ease my what-feels-like-stone-age approach to logging (tail + grep/sed).