Monday, October 23, 2006

Subversion on Windows

Source control has always been a bit problematic in the Microsoft world. Most of us have used Visual SourceSafe quite extensively and don't have to be convinced that it pretty much sucks rocks. The good news is that the souce control story has gotten better in recent years and months. The most notable event was the launch of Team Foundation Server, which comes with Team Source Control, a huge improvement in the Microsoft offering for source control.

However, TFS is not very ideal for single-man shops like myself (yes, I do some software side projects from time to time). It's ideal for teams (even small ones) where collaboration of source code with the software development process is important (this should be the case with any shop). It's also not very free. I'm a bit of a cheap skate, so all-free was definitely more appealing.

In the past I've played with CVS and liked it. It's been around for a long time and has a decent Windows implementation that installs an easy-to-manage Windows service. However, CVS has its well-known shortcomings. These shortcomings are the primary reason for the creation of Subversion (SVN), which is very CVS-like, but better in many ways.

The only down side to SVN, it seemed, was that it didn't have a very good Windows implementation. Specifically, the server install did not include a Windows service. You had to come up with some other way of keeping your SVN process (or daemon as they call it) running using a 3rd party Windows service wrapper or the like.

Well, digging further, I recently discovered that it's not too difficult to use SVN with Apache, which is an open source web server that has a very nice Windows implementation. Accessing SVN via Apache (i.e. HTTP) is ideal because it allows you to easily browse your repository, and it works great with TortoiseSVN (my preferred SVN client) which uses WebDAV to communicate with SVN via HTTP. In fact I found the best resource for setting all this up was in the TortoiseSVN documentation itself.

Very cool! Now, I'm a die-hard SVN fan.

Lovin' GMail

It's probably safe to say I switch email providers as often as blog engines, perhaps even more often. However, I think I've finally found one I can stick with for a while: Gmail.

My email story goes something like this:
  • Way back in the day, used whatever email address my ISP gave me. I quickly gave this up for a free Yahoo Mail account, which allowed me to check my mail from anywhere and not give up the address if I changed ISP's.
  • Purchased a domain name (twistedstream.com) and thought it would be cool to host my own mail server at home! I think I played with some 3rd party POP3 server at first. Then I switched to what all the cool Microsoft kids were using: Exchange.
  • I finally got tired of my home server either going down (which, in all honesty, didn't happen very often) or my ever-reliable Internet connection dropping and consequently people complaining about not being able to send/receive email to/from me. So I switched back to a hosted solution called Everyone.net that would work with my domain name. I believe was able to access my email via POP3 and IMAP. I liked the IMAP capability because it was more like Exchange.
  • Unfortunately Everyone.net only did email. All my calendar and contact data was still local to one machine. Then I decided to switch back (yes, back) to Yahoo Mail. Yahoo was also able to host my domain name as well as sync calendar and contacts with Outlook (this worked most of the time).
  • Then a coworker turned me onto a hosted Exchange service at 1and1. Man, this had to be the Holy Grail of email (for Outlook users)! And, for the most part, it was. But then I took a new job where the OWA (Outlook Web Access) didn't play well with the corporate firewall; essentially it made checking my personal email next to impossible while at work.

Then enters Gmail.

I've actually had an account for some time (I picked one up back when it first came out and it was the latest rave). However, besides some of its different ways of organizing mail, it just seemed like another web mail client. However, two things peaked my interest and eventually made me switch:

  1. The ability to send email from any email address (not just your @gmail.com account). Yes, via a slick validation email, Gmail will allow you to send email from any account. Couple this with aliases set up in my MX record, and Gmail now becomes the center of my email universe.
  2. The ability to import all of my old email. Granted, this feature isn't provided out of the box by Gmail. You have to do some digging, but a free tool called the Gmail Loader allows you to import all of your old mail. And when I say all, I mean all. I was able to suck in email as far back as 2000 (which is all I had archived). The beauty of this is all of that email (over 1GB) is now labelled and searchable with Gmail's awesome search engine. And since Gmail gives you over 2.5GB of storage, I still have plenty of room.

One more feature that Gmail has that I like, but don't necessary use, is their POP3 access. Like many other hosted email services, you can use a rich email client (Outlook, Outlook Express, Thunderbird, etc) to pull down your email via the POP3 protocol. Gmail makes that experience better with the following added capabilities:

  • More choices on how messages are stored on the server.
  • The ability to send email from any email address that you've validated on the Gmail site.
  • Having a copy of any email sent from your rich email client stored in the Sent Mail folder on the server (as long as you use the Gmail SMTP server in your client-side configuration).

Very cool stuff. I now feel content with my email :).

ps
I have to say a big thanks to my friend Michael who's been using Gmail for some time now and got me re-interested.

Monday, October 09, 2006

My BPTBEC ratio is very low

I have, once again, switched blog engines. I began by using LiveJounral, then I switched to hosting my own. That was cool, but I got tired of having to maintain the server and have friends complain that they couldn't read my blog because my internet connection was down (which is Comcastic!). Not that it really mattered anyway since it was a rare occasion to actually see a new post from my blog.

So, I've made the move back to a hosted blog. For kicks, I decided to go with Blogger. They've been around a long time, have a pretty slick interface that's free, and the Blogger account integrates with my Google ID, which is cool.

Finally, regarding the subject of this post. In all this silliness, I thought it would be fun to make up an acronym to describe my blogging behaviors. BPTBEC stands for Blog Posts To Blog Engine Changes. Right now that ratio for me is at about 3.7. Hehe, I think most average bloggers would have a value in the 100's or 1000's. Well, at least I've got something to shoot for.