Infrequently Noted

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.

Tim has finished our discussion of the merits of innerHTML. My hat goes off to him for all the hard work he put into the article.

My resume is now available in HTML format. The not-so-subtle inferrence here is that I'm looking for a job. If you are in need of a security engineer or web application developer with a penchant for making seemingly crazy things work (and work well), I'm your man.

My roomate mentioned to me the other day that my only problem with the hiring process is that I don't look great on paper. That may be true, so to combat that, I'm going to list a couple of reasons why you (or someone you know) should hire me:

1. The phrase "hard working" isn't even a good start.
   
2. A good way to motivate me is to tell me that it can't be done or that "it'll never work". Stand back and watch.
   
3. What I don't know I'm not afraid to learn.
   
4. I'm smart.
   
5. I'm a geek to the core, but I understand that just because something appeals to my geek side, that doesn't make it a good idea.
   
6. I listen to good music.
   
7. I try not to have opinions about things I know nothing about.
   
8. When I do have an opinion, it's for a good reason.
   
9. If you don't plan on reimbursing me for books, don't even bother calling. Educating myself isn't something I do in a classroom, it's something I do on my time because I like to do it.
   
10. Above all, I understand that technology is a means to an end. I'm passionate about what I do, and because I am I try to understand how and why people will use what I build.
    
11. I do this because I love doing it. If you're doing it for other reasons, please refrain from calling.
    
12. I am comitted to building quality software
    
13. The most important thing about a workplace to me is the people I work with. Second to that are the projects I get to work on. Everything else flows from those 2 things.
    
14. I'm available right now. Right this minute.