We’ve had a few comments from clients and prospects as we’ve grown over the last year that they’d like us to be more easily reachable.

Well, we’ve listened.

You can now reach a real human being 24 hours a day, every day of the year, by simply calling 866-WORKHABIT (866-967-5422). If you want to talk to someone specific, all you have to do is ask, and they’ll try them.

If you have feedback, I’d love to hear it. Just dial the number and ask for Jonathan Lambert (I’m the CEO), and I’d be happy to talk with you. Or email me directly at j@workhabit.com.

Finally, someone has written one of the most useful tools I've seen for IE debugging for CSS. In the author's words, IETester, "... is a free WebBrowser that allows you to have the rendering and javascript engines of IE8 beta 1, IE7 IE 6 and IE5.5 on Vista and XP, as well as the installed IE in the same process."  read more »

A client asked me today about how to most effectively merge his changes from trunk to a production tag (in his case, tags/prod within his subversion repository).

The problem with merging two non-working copies in this case is that each one is about 54 megs of data. All in all, with the roundtrip to the server (twice!), the merge was taking about 45 minutes to complete.

The alternative is to do a “working copy” merge, where you merge between two working copies, back to the first one, like so:  read more »

• trunk - source working copy
• tags/prod - destination working copy

So say you’re plugging along, developing like a madman (or woman), and, as can happen, your system needs a hard reboot.

It can happen. It’s rare. Months will go by for most people without a crash. But when it does, well, MAMP doesn’t like to play nice anymore.

The specific case that can happen:

• You boot your system.
• You open komodo and resume your project
• You make a couple changes, open a browser, and realize you forgot to start MAMP.
 read more »

One of our clients asked us how to structure their SVN repository, and it occurred to me that I haven't read anything about this online for Drupal-based projects, so I thought I'd blog it and see if we can get a dialogue going on best practices for larger projects.

This is by no means complete, but it shows the general structure we start with on projects. The larger he project, the more teams you have working simultaneously, and the more parallel development efforts you have, the more complex your svn administration can get.  read more »