Anyway, the reason why these two render the fonts the way they do has already been discussed to death so I won’t go into that.  Ultimately though, it helped me to understand something about myself when it comes to Web Design that I always thought was kind of odd…

For some reason, I’ve always had an easier time doing graphic design on my Mac but writing code has always been easier on a PC.  Even though Photoshop is almost exactly the same on Microsoft’s Windows and Apple’s OSX operating systems, I’m more inspired and can knock out graphics quicker on the Mac.  Even though Dreamweaver is pretty much the same on both, I can knock out code quicker on the PC.  I’ve always suspected it was the way the fonts displayed on the different operating systems, but after reading up on why they two render fonts the way they do, now I’m certain that is definitely the reason.

Now that Macs can run Windows as well as OSX, I’m planning to go back to just using Macs, although my G4 won’t do it since it has to be an Intel-based Mac so I have to buy a new one.  This is mostly because I’m just tired of having to reinstall Windows on my computers every couple of years and all the other problems I’ve had with Windows and PC hardware.  I’ve never felt like I needed to reinstall OSX on my Macs ever and I’ve hardly had any hardware issues.

Anyway, does anyone know if Boot Camp or Parallels render screen fonts the Mac way when you’re running Windows or does it keep it the Windows way?  I’m going to have to find that out before I go back to the Macs.  I use Visual Studio 2005 these days but I guess if Boot Camp or Parallels render the fonts in Windows apps the Apple way, then I may have to rethink that plan.

My Windows Problems

In the past year, I’ve had to re-install XP on my brother’s computer twice. Once, his hard-drive died (not XP’s fault) and another time because a virus messed his computer up. I just re-installed XP on a friend’s computer because a virus and spyware made it completely unusable. I had to re-install XP on one of my computers because it had gotten slow, bloated and was crashing too much.

Luckily, I was able to save most of the important data from each computer each time so it wasn’t as bad as it could’ve been, but it’s more than I’ve ever had to do with any Mac I’ve owned ever! I’ve never had to re-install the OS. Not once. Plus, the only time a Mac ever felt slow and bloated was when it had finally lived past it lifetime.

My Mac History

The first Apple computer I ever used was in elementary school (maybe 5th grade) and it was an Apple IIe, I think. All through the rest of school and even early college, Mac was the only option.

I bought my first Mac in ‘96 or maybe ‘97 and it was a Beige G3 233mhz. Then around ‘02, I was doing more print design (huge files) and Photoshop seemed slow so I talked myself into getting a G4 867mhz. I also wanted OSX. Anyway, I still use my G4 to this day and it works great.

My Move To PC

In 2000, I got a job as an ASP developer and a Windows PC was the only option there, unless you were a graphics person in the marketing department. So, I became a PC user during the day and a Mac user at night. For some odd reason, I’ve always found graphic design easier on a Mac and programming easier on a PC. Eventually, though, with ASP.NET I wanted to be able to program locally so I bought a Desktop PC. Later, as I starting taking classes again, I got a Laptop PC. My PCs have been ok, but I’ve definitely had more problems with them than my Macs.

What About Now?

From now on I’m going to go back to buying Macs. I’ve briefly touched on why but there are many more reasons going into that decision. Of course, I’ll still need to run Windows while programming but with move to Intel, I can do that now on a Mac. That’s actually one of the bigger reasons why I’m going back. Now I just have to resist buying a new computer now because I don’t really need another right now. My G4 and two PCs should still be ok for a while longer. It’s very tempting though!

Making the Wedding Ours

Angi and I spent a lot of time and effort into planning this wedding. We wanted it to be very much “ours” and to reflect our personalities well. I know there are a lot of guys out there that leave much of the wedding planning to the bride, often because many brides have planned their dream wedding from an early age it seems, but my Angi wasn’t like that. I tried to stay involved with every aspect of the wedding (finding/choosing the church, reception hall, caterer, florist, rehearsal dinner, etc.). I think the only part I wasn’t involved with was the dress part; I wasn’t allowed.

Branding Our Wedding

On top of all that, I wanted to brand our wedding by designing the invitations, programs and website myself. This was something that was inspired a little bit by Jason Santa Maria (Branding Your Wedding).

My goal was to have invitations that were unique and like no one else’s wedding. I looked at a lot of samples of invitations and was unimpressed with the bulk of them. Far too often, the invitations would use one font and often only one text size throughout, which made nothing stand out.

When I took this project on, I knew my work project was supposed to be complete almost three months before the wedding. Unfortunately, my work project started a little later than planned and took longer to complete so the two overlapped. There were days that I spent a long day working on that project and then a long night working on the wedding stuff. That was an extremely stressful time!

How Did It Turn Out?

Overall, it turned out well! I didn’t spend as much time on the website as I would’ve liked, but it still turned out ok. I’m little happier with how the invitations and programs turned out design-wise. Unfortunately, while I’ve been doing some graphic design (completely self-taught) for almost 10 years now, most of my designs have been for the web; print is not exactly my area of expertise. They both printed out fairly well though, but they could’ve been better.

Of course, I’m kind of a perfectionist so I always think things could’ve been better. We did get a lot of compliments on them though and they were unique.

One semi-major problem with the invitations turned out to be the dimensions when we tried to mail them. It turns out that the USPS started charging $0.13 more for mail that isn’t the standard elongated rectangle shape so a large stack of invitations were returned to us. Even worse though, was that for some of the invitations they didn’t return, they made the person we sent them to pay $0.13 to get their invitation. I’m only aware of that happening to a few people, but it probably happened to more and they just never had heart to tell us about it. That was super embarrassing!

So How About The Rest?

The rest of the wedding turned out great! I think it was very much us. For the ceremony, we used a lot of really cool music done instrumentally on the piano. We used some Journey (“Open Arms”), Lionel Ritchie, Kenny Rogers (“Through The Years”, a favorite of my mom’s), The Beatles (“Here, There and Everywhere”), Billy Joel (“She’s Got a Way”, for the bride, which was incredible!), John Lennon (“Grow Old With Me”) and finally, we left on Queen (“My Best Friend”), which was fun! We were very happy with how all the music worked out.

The reception was cool. The place we had it had a very cool feel to it, the food was good (what little we actually got to eat), the cake was good, the dancing was good (the DJ was a friend of Angi’s and a great DJ), etc. With the exception of us being pulled in a million different directions all night, we had a great time.

The Details

The idea behind this redesign was to start over from scratch and rebuild everything. Our old database that was originally setup about five years ago was getting to be pretty messy. It had been through two redesigns and with each set of improvements, it became more and more cluttered. With this redesign, I decided it was going to be better to start over from scratch and for us to convert and migrate as much data as possible.

So, for this redesign, I not only created a new database, but also built a complete administration site so others in the company could manage the content. After that was started, I build the entire front-end site. Needless to say, it was a huge undertaking. Of course, I didn’t build the entire thing by myself or anything, but I did the vast majority of it, database, back-end and front-end. The one part I didn’t create was the visual aspects. Marketing oversaw that part; I just put it over my code.

The Focus

The focus on this redesign was to make the site much easier for user to find what they are looking for. In the past, we always focused on our product lines, but realized that the average user has no idea what the differences are between the product lines. This time around, we focused on more generic terms like Home Audio that breaks down to Home Theater Systems, Speakers, etc. At the bottom level is where you finally see the product lines. We also used to have a focus on News-type items, but realized that over 80% of our traffic was directly to the product sections and most visitors didn’t care about the News items. So, we made products the main focus with News and other things as secondary options.

Another focus was to make the site more search-engine friendly. We used url-rewriting to make the urls easier to read for humans and to hopefully get the search engines to rank our pages a little higher. The urls match the page titles and the titles on the page which they supposedly like.

So, How Did It Turn Out?

Overall, I’m very happy with how the site turned out. It’s faster than I ever thought it would be. The code is clean and very easy to work with now. Plus, I learned so much planning and building this site. I’ll post some of the cooler things I learned soon. Now it’s time for me to take some time off because I am so burnt out right now.

Oh yeah, the url: Klipsch

Eating Your Own Dog Food

Obviously, the purpose of this contest is to show developers some of the cool things you can create using the free Visual Studio Express software, so I’m amazed that Microsoft missed a great opportunity to show that it eats its own dog food. I guess to be fair, ASP is a Microsoft product, but it is more like they are eating their own old and stale dog food. After all, the Express software is all about .NET and should have been created in Visual Web Developer.

I know that Robert Scoble has written a few times about Microsoft “eating the dogfood” (see this post from last week) so I’m sure he would disapprove as well. They do have an RSS feed on the site though, which is almost redeeming, but not quite.

Made In Something Other Than Express

I’ll never use an Express product now because of this hypocrisy! Ok, just kidding. I do actually use Visual Web Developer every day at work and even most nights and weekends when I’m not at work and I love it. I was just a little disappointed the site wasn’t “Made In Express” like it should have been.

It really is a good product (I can only speak for VWD) and this is coming from someone that refused to use Visual Studio in the past for web development. Dreamweaver in edit view was always my editor of choice. Unfortunately, I do still have to use it for FTP because the FTP tool in VWD is terrible! That’s probably my only real complaint about VWD. Intellisense makes up for any of its weaknesses though. That alone makes my life so much easier.

Next Time, Make It In Express!

Anyway, I hope the next time Microsoft does some sort of contest or whatever promoting their Express products that they actually use them to make their site.

The Move from Static to Dynamic

At my day job, I have been through about three major redesigns of our website over six years and am currently working on our fourth. Throughout these various redesigns, our site began as a completely static HTML site and became more and more dynamic over the years. The nice thing about having a dynamic site is that I am no longer responsible for managing the site content; I am only responsible for the code and any bugs that pop up. The major drawback to having a dynamic site is that we’ve amassed a lot of data and it has gotten more and more difficult to redesign the site each time.

Our second redesign was our first primarily dynamic site and its foundation (the SQL back-end) was the basis for every redesign until now because of all the data. We have modified the database pretty heavily over the years, but its basic foundation is still there, mostly because it became too difficult to start over from scratch with the deadlines we had for each redesign. Hell, with the last one, I had two weeks to reprogram the entire front-end of the site by myself by the time the marketing department had finished the redesign plan and I barely got that done in time. There was barely any testing done but it turned out to not be as buggy as I thought it might be. It’s not how I like to do it, but I had no choice.

The New Redesign

As I mentioned before, I am currently working on another site redesign, but this time around it has been decided that the functional changes needed are too great to just modify the current database like we’ve done before. So now, we are starting over from scratch. It is just something that needs to be done, but it’s a huge undertaking. To be honest, it is a bit overwhelming.

With the previous redesigns, I was able to “freeze” the database and start the reprogramming. I just made a copy and the content managers had to keep track of any changes they made after it was frozen so they could make them again on the new version. This time around, however, it’s going to take too long to do the “freeze” option so my plan is to create the new database, get the admin screens working and then migrate the important information from the old database.

The Payoff

Even though it will be a difficult redesign, it will be worth it in the long run. I’ll admin, our current database is a mess with tables and stored procedures that are no longer being used, but the site is too large to keep up with what is and isn’t being used.

Starting over from scratch is going to make it much easier to manage the site and make it easier for future redesigns. It’s also gives me the opportunity to take what I’ve learned since the last redesign to improve and optimize the site.

Final Thoughts

Managing a fairly large site can be difficult and even frustrating at times, but it has given me experience I couldn’t have gotten working only on smaller sites.