reesesWeb

The author of Zoe wrote me today to address some of the dull points in my last post. I think that makes him the third person to read this blog. ;>

I was pretty critical, but I'm going to explain it by the late hour. (1 AM, since I'm on the beast coast) He offered some good reality checks on my assumptions.

I was able to get Zoe to snarf messages by dumping my mbox tree in ~/Library and using the file import, as I was still unable to do the network-based import. After importing the last six weeks of personal messages (around 6k messages) the Zoe server became...very...sluggish. It took about twenty seconds to pull up an email message. This was on a pretty constrained box, though -- K6(3d)/333 with about half a gig of RAM and IDE disks. I tarred everything up and moved it to my laptop, and it was considerably faster, but I had issues with message rendering that I haven't eliminated yet. As it is, it's cool, but I think I'll keep waiting.

That aside, we hit alpha on Monday morning, and I think we're actually in good shape. Lots of long days and weekends, but I think my annoying policy of formal code reviews for all code hitting the mainline is going to pay off in reduced effort during QA. Cross fingers, knock on wood, etc. Other people feel the same way, so I'm not just deluding myself.

I fired off the first full catalog import when I was on my way out of the office tonight, and it just occurred to me that I should have had my server monitor do some data validation and let me know at the apartment. Now I'll have to live with the suspense instead of having a silly message pop up in Jabber saying,"Dude, it worked!" I have this nasty habit of capitalising the first word in quotes, so it would probably come across as "Dude, it Didn't worked!" I'm not too hung up on this whole grammar thing for personal stuff, as if one couldn't tell from reading this log.

Bookmark/Search this post with:

delicious | digg | reddit | technorati