so I got an email yesterday that just floored me: netWindows has an offshoot project
I'm in Wisconsin now. I'm still trying to find a place to live here in Madison that's not going to hurt me too badly financially but won't endanger my health, etc...
Work is neat, I have a really fast box, a nice monitor, and good input devices. My new work-related email address is email@example.com. You can still reach me at alex@netWindows.org, but durring business hours the other is more likely to get to me quickly.
Woohoo! I've just accepted a position with SecurePipe and I'll be moving within a week and a half to Madison. Color me elated =)
Paul has put up a list of his likes/dislikes in email. Over time I've seen various articles of this sort from people who read gobs and gobs of mail, and the similarities between them are striking. Almost makes me want to write a utility for a mail client that would put a little bar next to each email in your box outlining it's friendlieness (netiquite quotient?) or some such measure.
The netWindows team is going to be releasing 0.2.4 in a couple of days. My roomate convinced me of the need for another point release in the 0.2.x line and at this point I have to say I agree with him 100%. Sometimes I find that "release early, release often" is easier said than done. In the "real" world there are distinct pressures that drive the release cycle but when it comes to my side-projects, it's kinda whenever I think it's ready. While that helps to ensure that I'm indeed happy with the product, it doesn't necessarialy help the end users.
To help combat that, I'm going to try to keep the project on a 6 week sub-point release schedule. The hope is that by enforcing a timeline on releases we'll better constrain our goals for each one and make sure we get changes into developers hands in digestable chunks.