Developer’s Toolkit: Mark Dunphy

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.

Hello it's Mark!1. Who are you, and what do you do at Behance?

By now you’ve probably already learned my name, so I suppose I won’t go into that. However, I will tell you that I’m a backend software engineer at Behance.  I have the interesting position of floating between teams and products quite frequently, so I get to leave a little Mark (hah, get it?) on everything.  Beyond the sprinkling of love and code I put into other team members’ projects, I’m primarily responsible for Behance emails (notifications, automated digests, switching service providers, you name it) and fighting spam.

Read more →

Developer’s Toolkit: Andrew Crerar

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.

andrew 1. Who are you, and what do you do at Behance?
I’m Andrew and I’m responsible for the development and day-to-day operation of our Custom Creative Networks. What is a Custom Creative Network (CCN)? I’m glad you asked! CCN’s are essentially streamlined, thinner versions of Behance but differ in that they have the ability to be customized; really cool stuff. On a normal day you can catch me working the full stack: anything from writing SQL, PHP, or JS, to making CSS changes and going to production (Wooo)!
Read more →

Developer’s Toolkit: Nina Berg

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.

ninaberg1. Who are you and what do you do at Behance?

Hey there, I’m Nina Berg, a Quality Engineer here at Behance. Our team’s job is to ensure Behance is as stable and bug-free as possible. To that end, we work on developing whatever tools, infrastructure, and processes are needed to test our website. My recent projects include working on a Selenium testing library called Paige, and designing a continuous integration workflow for the cookbooks our devops team works on.
Read more →

And an amazing week it was!

Events for our fifth Portfolio Review Week are just about wrapping up, and with over 300 events and 3,234 uses of the hashtag #BehanceReviews, we are blown away by how well our online community can come together and collaborate offline. Thank you to all of our hosts and attendees for a truly amazing week and stay tuned for some additional stats! Here are some highlights:

Pinterest Page
#BehanceReviews on Twitter
PRW Flickr 

PRW # 5

 

Developer’s Toolkit: Krasimir Georgiev

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.

krasWho are you and what do you do at Behance?

Hi there! My name is Krasimir, software engineer here at Behance. I’m part of the backend team and my main responsibility is to break the site and fix it after that (on my first day here Bryan said I could, so I do it from time to time).

My job is to implement new features and improve the old ones. I work on a better way of storing and retrieving the images on Behance. I was also involved in improving the way invites and requests on the site work. The rest of what I do is still under wraps.

I moved to NYC almost 4 years ago and joined Behance about 1 year ago. It’s great to be a part of something that I’ve known and followed for a long time even when I was back in Bulgaria.
Read more →

Full Swing: Portfolio Review Week 5 Update

Portfolio Review Week 5 is currently underway and we’ve been seeing tons of Tweets, Instagrams, Blog posts, and other social media blips all week. We’re continually amazed by the excitement around all of the events. Keep posting pictures and recaps of everything you’re doing and keep an eye out for our updates on Pinterest!

Here are some shots from various events around the world!

 

Auckland from anjanaiyer

Screen Shot 2014-05-14 at 10.48.20 AM

Read more →

Moving Data Centers with Chef

Moving data centers is scary, make it less scary with Chef, U-Haul not included.

@mtldo + @cfortier at #chefconf2014

At ChefConf 2014 this year, Chris Fortier and I had the privilege of presenting on the challenges of moving from a physical data center to the cloud. Beyond the move, we had to move towards more automation and a hands off approach to managing servers. This meant learning Amazon Web Services in depth and getting Chef onto every one of our machines. The result of our work was a library of cookbooks that could reliably work in three distinct locations: physical servers in Rackspace, laptops in our SoHo office, and cloud instances in AWS. As we developed these cookbooks we gradually improved our process and testing techniques. We reached a flow that kept cookbooks tested and trustworthy no matter where we launched. This also gave the whole team visibility into system changes that would have been easily missed otherwise.

Read more →