This post is part of a series where Behance developers talk about the various tools they use to get things done and make ideas happen.
1) Who are you and what do you do at Behance?
Hello, I’m Chris Fortier and I am the Lead Quality Engineer at Behance. My main responsibility is to help guide the Quality Engineering Team so that we can figure out how to test all the various aspects of our websites. I’ve been on the team for a year now (I know, I’ve slacked off on writing this post) and I’ve been involved in quite a few projects. The first major project that I worked on was an automated process to build a replica of our production environments so that we can have a more effective development and testing process. These environments are built on VirtualBox and OpenStack virtual machines. For the past several months I’ve been working very closely with the DevOps team as we adopt Chef and standardize our infrastructure as code. Looking forward to 2014, we are in the process of a complete overhaul of our testing infrastructure and busy trying to figure out how to build a Continuous Deployment process. Stay tuned for details.
I was born in Florida and lived there most of my life. I met my awesome wife about 12 years ago when we worked together at Universal Studios. I had never known a world without Disney or the beach until a few years ago when we moved to Albany, NY and got to learn all about this thing called snow. The best part of Albany was that we had lots of time to learn how to snowboard. As for sports, I went to the University of Florida and mainly watch college football – Go Gators! It’s still a little strange to me that people in the north watch NFL more than college sports, it’s the definitely the opposite of the south.
2) What hardware do you use?
I keep it pretty simple when it comes to my hardware and software choices. I have a 15″ Mac Book Pro with Retina Display, an i7 processor, and 8 GB of RAM. I have a pair of Dell 24 inch monitors on my desk, but I spend a decent amount of time working at the high-top table or helping out other developers so I don’t use them that often.
3) What software do you use?
When working with code (or writing this blog post) I do my work from the terminal and use VIM for my editor. I recently upgraded the experience and started using iTerm 2 along with Square’s Maximum Awesome pack of plugins. Google Drive is my go-to platform for documenting processes and collaborating with my team. I use a combination of Wunderlist and Evernote for keeping track of my tasks and notes.
4) What do you listen to while working?
The random conversations of my co-workers :) Even though we are now a part of a large corporation, we work hard at keeping the startup-vibe. My latest projects have involved lots of impromptu conversations and debates throughout the day which means I don’t get to listen to too much music. However, when I have my headphones on I’m usually listening to Country.
5) Out of all the equipment used, what piece of software/hardware do you feel is the most useful of all?
The high-top table and dry-erase wall. Most of my job is working with multiple teams that are working on multiple projects. There is no better way to discuss the issues and make sure we are on the same page than to sit down and draw it all out.