Today VaultPress announced the Code Garage migration details. We really wanted to make sure that we had the details and options on this right. I know that migrations like this can often be annoying, so we went out of our way to make the process smooth and inviting.
Code Garage users that migrate to VaultPress will get their first two months on VaultPress free. For those who don’t want to migrate, we’ll refund your last payment.
Even if you aren’t a Code Garage customer, you should go read Peter’s CodeGarage Locker is Migrating to VaultPress post. He gives a personal history of how Code Garage came to be, how it grew, and how it ultimately was sold to Automattic.
Last week I started spending time on the VaultPress team at Automattic. VaultPress was something I hadn’t worked on previously and had only loosely followed, so the code base was something I wasn’t familiar with.
With my relatively fresh eyes (as far as not having worked on VaultPress before) I spent the first day or so just making observational notes about the service. Developers often suffer from having an intimate knowledge of a system, which can make it hard to picture how a regular user (who isn’t familiar with all the ins and outs) views things. This was my chance to avoid that before diving into the code base.
The next day, after assembling my notes, I started diving into VaultPress. Support, bug tickets, documentation, feature requests, code, the whole thing. I picked one of the very minor items from my notes and found the piece of code that needed to be updated. After running a few tests to make sure the change worked as expected, I committed and deployed the new code.
There is something magical about deploying code on a system that just a day or two ago you had never touched before. The joy of watching that first deploy (even for something simple) go live really gets you over that first hurdle of becoming comfortable with a new project.