953 karma · joined December 27, 2008
Secondly, I make use of this highly customized neural network-esque technology I use which gets a finely-grained history of everything I do and uses it to build a model of importance by which it can filter out irrelevant content. It's a bit processing intensive--it can only filter through 30-50 items per minute--but it's not a big deal since my RSS feeds only produce less than 500 items a day, so that's only 10 to 20 minutes of processing per day. It produces (on average) only a couple of false positives (items I don't actually care about) per day, and (although of course it's hard to empirically confirm) it seems to produce similarly few false negatives. This is a huge gain over every other system I've tried (especially populist voting-based systems).
(I'm using wmii on Ubuntu).
I replied because the quote was taken out of context, and I don't think that the idea applies in the general case.
Of course, in the context of the article, somebody interviewing with investors probably should have thought out in advance about the sorts of things the investors would want to know and ask about, so they shouldn't be fumbling too much.
Personally, I can generate concise statements (and I'm good at it when I try), but the first couple of times I verbalize an idea I'm usually somewhat verbose. I make an explicit effort to figure out a concise way to say things once I've noticed that I'll probably be expressing the same idea again (and when I write). Perhaps other people become significantly more concise over time without effort, but I'd estimate my baseline compression rate is only something like 10% (whereas when I explicitly compress I can often get 30% or better).
I think the difference is that some people think very verbally and linearly, whereas I tend to think more visually and abstractly. A lot of the time, I have to translate the ideas in my head from these somewhat amorphous concepts or visual ideas into English (or German, or code, or whatever).
import sys
def debug(*s, sep=" ", nl="\n"):
print >>sys.stderr, sep.join(map(str, s)), nl,
pass
debug("There was an error on line", 10, ":", nl="")
debug(1,2,3,4,5, sep="-")
And then comment out the line with "print" to disable it.Of course, by that point you may as well use the logging module.
Obviously, YMMV.
I'd happily switch away from AIM (by that, I mean the protocol/servers, I use Bitlbee/irssi and Pidgin), except that a lot of the people I know use AIM exclusively.
And make sure you can change the waiting period, in case you go on vacation or something.