Before I dive into this review, you should probably have some background information. First of all, as the title suggests, I am a graphic designer for a web design company. I spend 90% of my time on Adobe Creative Suite programs (most of that time is dedicated to Photoshop). Second of all, I am a female. This piece of information applies to this review because as a woman, I am genetically predisposed to have smaller hands than (most) men. Lastly, I have run through the gambit of Apple mouses since 2004. That being said, lets get started, shall we?

The good:

1. The size. I love the way this thing conforms to my hand. So much so, I feel like all other mouses feel too large and clumsy. I have read reviews where people have claimed this mouse is too small and light. I have not had this problem – however as stated previously, I have normal sized hands for a 5′8″ female which means they’re relatively small.

2. The scrolling. The predecessor to my Magic Mouse was of course the Mighty Mouse. One of the main problems I would have with the 360 scroll ball on the Mighty Mouse was it would become gritty and would stop being functional. This could always be cured by holding it upside-down and puffing can o’ air into the recesses of the 360 ball. Obviously this problem is cured by Magic Mouse. Please note – being a control freak while using Photoshop, I turned off the momentum scroll. I have been told this is a nice feature, but I can’t say that from personal experience.

3. The right-click. Although the right click is functional with the Mighty Mouse (as long as that is specified in the system preferences), I feel like the Magic Mouse’s right-click is more responsive and intuitive.

The bad:

1. The sensitivity. This is a double-edged sword. Sure, it’s nice when you WANT to scroll, but when you don’t it’s a pain. This rears it’s ugly head often when I am using Photoshop. An example of this is when I have the color picker window open. Notice on the screen shot the field next to the “R” (meaning red) is highlighted; this happens by default when one opens this color picker window. What happens when this field is highlighted is the scroll functionality on your mouse can easily add and subtract the color red. Many times I have barely brushed the top of the mouse and it will change my selected color without my consent. There is no clear area on your mouse where the scroll sensitivity begins, so just laying your hand on the top of the mouse can create a scroll with any slight movement.

2. The two finger swipe. This also goes back to the sensitivity problem. I had to turn this option off after I was working on code in our CMS and my fingers brushed the top of the mouse. The mouse somehow gleaned from this that I wanted to go back to the previous page in my browser, and thus losing all of the work I had just completed.

The conclusion:

After turning off the two finger swipe functionality, life has been easier along with learning how to deal with the problems in Photoshop. I haven’t yet ditched this mouse for the older Mighty Mouse (which is still in my possession), but that’s only after adapting to its downfalls. Basically my conclusion to this review is I would NOT recommend this product to a Graphic Designer, but I would recommend it to people who don’t use Adobe Creative Suite.

As a long time user of OS X I’ve tacked on application after application to handle small, but essential, tasks.

Fluid for running my calendar and Stacks, JustNotes for syncing with simplenote, The Hist List for personal tasks, Quicksilver for application launching, and xScope for Web Development quickies.

Each of these applications has the option, and generally encourages, the use of global shortcuts. For those of you that don’t know, a global shortcut is a keyboard shortcut that can be can be used system wide.

The main advantage of this is the ability to access common features or tools without having to switch apps (i.e. switching songs in iTunes). However, many applications have default shortcuts that get overwritten by the global alternative. For instance, a common shortcut in Photoshop is cmd-option-d which is used to feather a selection. Yet, in OS X, trying to use this results in the dock getting hidden.

The best way around this issue is to create custom shortcuts for things that have conflicts or need quick access. However, before diving in and going crazy — “uh.. what did I set that shortcut to? *Click*click*click*, oh, right, cmd-option-shif-ctrl-F3″ — follow a simple framework to avoid headaches . Here’s what I recommend.

1. If possible leave the standard program shortcuts in place. This makes for less hassle down the road if you ever have to reinstall the OS or use multiple machines for task (i.e. a school computer lab).
2. Make all program based shortcuts cmd-ctrl-LETTER. To date I have not found any program in OS X that by default uses cmd-ctrl-LETTER shortcut’s. The first advantage to this is that you don’t have to worry about overwriting already-in-place shortcuts. Second, and most importantly, the cmd-ctrl keys are super easy to reach and use.
3. For custom global shortcuts use a standard. Preferably cmd-option-ctrl-LETTER. Similar to the last bullet, I have never found a pre-set shortcut that used cmd-option-ctrl-LETTER. Yes, it sound like a lot of keys, but it’s three right in a row and they’re easy to reach.

The point is, if you standardize pre-set, local, and global shortcuts you’ll never have to worry about the key combo, all you’ll have to do is remember the letter or number you used. Further, it’ll keep conflicts at a minimum and give you a lot of options for growth down the road.

I’d love to hear other tips on what people are using so don’t hesitate to comment with your suggestions.

Recently here at Imulus we had a production server go down, meaning all of our clients’ websites on that box were unreachable.  Thankfully, we had the proper precautions taken and backups were restored in hours.  Yet it was a very stressful time for all of us and it led me to wonder what else was out there and how much better we could have responded in an emergency.

After a bit of research I found Microsoft’s Web Deployment Tool, also sometimes referred to as MSDeploy.  Of course it only applies to Windows Servers with IIS, so if you are looking for another OS/web server solution this article is not for you.

I was somewhat skeptical at first because, well, I’m skeptical of everything.  They even call me the skeptic here at work.  It also seemed a lot of people that were writing about it were fanboys and it was a very new product (I started testing when this product was still a release candidate).  After reading about it thought I should give it a shot since it sounded very powerful.  Here is a short version of what we were looking for:

• Able to take all manual steps out of recovery
• Backup all files and code that made up the website
• Include all settings, SSL Certificates, Bindings etc.

After playing with it and doing some tests I was very impressed.  The tool does deployment/backups per site, so if you host multiple sites on a server and want to customize depending on site you are able to do that.  You can view code dependencies, backup databases – do almost anything you want.  You can choose to use the GUI from IIS Manager or go command line.  You can choose to export the package to another server immediately or create a folder with an archive of all necessary files for restoration later.

If you are interested in using it for deploying, go get it,  check out this overview page or visit their forums.

If you are interested in seeing how we created a fully automated solution, read on.

Since we wanted something that had little or no human interaction, and therefore not error prone with a high degree of reliability, I came up with a solution that took all human involvement out of the backup and recovery process.  The solution we came up with is broken into 3 parts.

1) Backups of all sites in IIS needs to occur in case of a server failure.

2) Replicate backups to other available live servers as well as offsite automatically.

3) The ability to recover our site(s) needs to be easily and quickly available with fewest manual steps as possible.

To address all these I wrote a small, simple program to help the Web Deployment Tool with this process.  The program has two purposes and can easily be scheduled through the task manager in order to create a repetitive and up-to-date solution.  The program writes two files.  The first .bat file should be run nightly, or however often you want, and contains commands for msdeploy that create an archive backup for each site in IIS.  The second bat file contains all commands for msdeploy to install/restore each website that has been archived.  This second file should only be run if a server goes down and you need to restore sites on your standby server.

To take care of our first step we must schedule an execution of our custom application to generate our archival and restore bat files.  We must also schedule an execution of the archival .bat file our program generates to be run afterwards.  The bat file execution results in the creation of an archive for each site.

Now that all sites are backed up with step #1, we need to take care of step #2.  To do this, just use your favorite sync tool to copy all necessary files to other server(s) and offsite.  If you don’t know what I am talking about, check out Super Flexible File Synchronizer or Microsoft’s Sync Toy.  Using a program to move files on an automatic basis allows us to be ready to execute step three if we ever need to.

Step #3 is the only manual step in this whole process and is quite easy.  First, bind the new server you are recovering to with all necessary IPs, or do whatever network voodoo you need to.  Secondly, run the recovery .bat file.  The file will install your site(s), application pool, certs and restore all settings.  One click recovery?  Yes please!

If you think this code could be used in your environment you may grab a generic version here – I hope it helps.  Obviously, I make no warranty about any of this process or code.  If you do use the code, please read the readme as well as the code comments.  The code is a Visual Studio 2008 C# solution licensed under GPL.  Use your heads and do your testing people!

If you come up with anything different feel free to comment and let us know how you have improved upon the process.  If you modify the code please send me what you have done.  Enjoy!

For those responsible with switching sites from one server to another there’s a sure-fire way to quick propagation. It’s done by lowering the TTL (time-to-live) settings from a typical default of either an hour or day, down to 5 minute intervals. I’ll show you how.

First gain entry into you DNS server. In this example I’m using GoDaddy’s Total DNS Control (even though the UI is terrible).

Click on Advanced Mode, change the dropdown for TTL to 1/2 hour. This is the lowest GoDaddy goes but other interfaces, like Probind allow you to drop the intervals by manually entering an number. When finished click OK and you’re done.

I suggest starting the process about 1 week before the site is ready to go live. That gives servers across the web ample time to update their caches in advance of your update. Make the IP change when you are ready to update the server IP and you’ll notice a much quicker transition.

BONUS TIP: Also, we HIGHLY recommend using the free OpenDNS service. This system is a savior for giving us almost instantaneous ability to view DNS changes the moment they happen.

It’s 6:30pm and you’re tired from a long day of work. You’ve just finished writing a four page email to a client. Documenting all of the tasks you completed that day. In fact, you even took time to explain the reason you used nofollow linking to the client’s intranet website. Then, moments later, Mail unexpectedly quits. Your work is gone.

Or… is it. You remember copying the contents of the email to your clipboard minutes before. Quickly you open a new email and anxiously paste:

http://tr.im/OMG_ribbons …

wait, no, surely that can’t be right. You paste again:

http://tr.im/OMG_ribbons …

Then you remember, that co-worker of yours, Taylor, sent you a link on IM (”Haha, d00d this is hilarious”). But for some reason it didn’t format right and you had to copy it.

You think — there must be some solution, assuredly. Yet no, your work is gone. You swear to yourself, “never again.” Fortunately, moments later you find a blog post describing your exact scenario. It suggests downloading the free app Clyppan to record your clipboard history. “Wow, that’s awesome,” you say to yourself, “I’m gonna use this all the time.”

And guess what, you do.

Edit: One note, if you don’t set Clyppan to run on startup via system preferences > accounts, then you’ll have to start it manually every time you login to OS X.

Edit 2: Some might suggest the Quicksilver Clipboard module for this same functionality, however, as of 10.5 that module tends to randomly appear when quitting certain applications. Hence why I moved to Clyppan.