The details are in The Genericons Icon Font Story announcement post. In additional to being a nice general use icon font, it is licensed under GPLv2 (or later), so no more trying to sort out licensing terms to see if the icon font will jive with your existing open source projects. They are also free, as in no cost. The font is already in use in the new WordPress Twenty Thirteen theme ( demo site is at http://twentythirteendemo.wordpress.com/ ).
Having 48 new people in one year is amazing for me to see. That is four times the total head count of Automattic when I joined in 2007. Last year also saw Velda Christensen join Automattic, which doubled the number of Automatticians in Utah. :-)
Twenty twelve also brought new challenges for me as my focus at work shifted from Akismet (check out the crazy spam numbers in the spam vs. ham chart) to VaultPress. Looking forward to both services (along with the rest of Automattic) having a great 2013.
Scott Berkun has announced the topic for his next book:
The next book is based on the journal I kept while working at WordPress.com. It tells the story of what I learned working for one of the most amazing companies in the world.
This is the first time I’ve seen someone write a book about where I work. Automattic really is a special place and I look forward to reading Scott’s treatment of it.
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.