Why do spam filters suck?
I have a pretty decent spam filter in Outlook at work, but I'm still surprised by the crap that gets through occassionally. It seems to me that a few simple filters would catch a lot of the spam I get.
For instance, if the subject line or return address contain profanity or graphic descriptions of bodily functions, I probably don't want to read it. Likewise, if a grammar or spell check flags more than -- oh, I dunno -- 30% of the body of the message, I don't want to read it even if it's not spam.
A big group from work went down to the apple retailer in Fayetteville on Tuesday to ooo and ahh at the Mac Mini. It really is pretty mini. Grab a stack of 5 CD cases. That's about how big it is. Pretty cool. Not nearly as cool as the 30" widescreen monitor they had on display, but not bad.
I'm planning to get one, but I'd like to hold off until Tiger comes out. Plus our CIO said he'd buy one for everybody on our dev team if we make our beta and final release dates, so I'll probably wait at least long enough to tell if we're staying on schedule. He might've just been kidding, but we're planning to hold him to it. ;-)
After working through the excellent intro tutorial last week on OnLAMP covering Ruby on Rails, I'm now evaluating that as a possible web dev alternative to PHP. I like Ruby a whole lot better than PHP, so I'm pretty stoked about possibly getting to use it. Hopefully it'll work out.
For instance, if the subject line or return address contain profanity or graphic descriptions of bodily functions, I probably don't want to read it. Likewise, if a grammar or spell check flags more than -- oh, I dunno -- 30% of the body of the message, I don't want to read it even if it's not spam.
A big group from work went down to the apple retailer in Fayetteville on Tuesday to ooo and ahh at the Mac Mini. It really is pretty mini. Grab a stack of 5 CD cases. That's about how big it is. Pretty cool. Not nearly as cool as the 30" widescreen monitor they had on display, but not bad.
I'm planning to get one, but I'd like to hold off until Tiger comes out. Plus our CIO said he'd buy one for everybody on our dev team if we make our beta and final release dates, so I'll probably wait at least long enough to tell if we're staying on schedule. He might've just been kidding, but we're planning to hold him to it. ;-)
After working through the excellent intro tutorial last week on OnLAMP covering Ruby on Rails, I'm now evaluating that as a possible web dev alternative to PHP. I like Ruby a whole lot better than PHP, so I'm pretty stoked about possibly getting to use it. Hopefully it'll work out.