Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


Developing for Ackability (and other ways to get along in large, autonomous engineering teams) #88

wants to merge 1 commit into from

2 participants

Brian Morton Keith Pitty
Brian Morton

I'd love to talk about the technical challenges that we deal with at Yammer around putting every one of our codebases in the hands of our 150+ engineers, each with assorted backgrounds and unique skill sets, distributed over 3 continents.

In this pull request, you'll find the full abstract for this talk :)

Brian Morton

Also note that this is my first talk proposal and I am SO EXCITED.

Keith Pitty

Thank you for your proposal. Unfortunately, due to the high number of excellent proposals, our panel has not been able to include this talk at this stage. Should this situation change, we will contact you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Nov 1, 2012
  1. Brian Morton
This page is out of date. Refresh to see the latest.
19 brian_morton-developing_for_ackability/
@@ -0,0 +1,19 @@
+# Developing for Ackability (and other ways to get along in large, autonomous engineering teams)
+Autonomy, transparency, and sustainable velocity are among our core values at Yammer. The trust we have in each other puts all of our codebases in the hands of any of our 150+ engineers with assorted backgrounds and unique skill sets distributed over 3 continents. In addition to that, we're bringing new people on almost weekly. We do this with very few formal processes and a whole lot of success.
+Contributing to a new or unfamiliar codebase can be challenging, especially when they are rapidly changing or not in your language of choice. You look for good examples of how things have been done in the past and then try your hardest not to break things. Some of our codebases are smaller and this comes at a much lesser cost. But others have grown over time or, in the case of our Rails application, were once the single monolithic codebase.
+These larger codebases are in a constant state of surgery as things are pulled out and encapsulated into smaller services and codebases. We're far better off with smaller codebases, but we're still left with the challenge of developing features and moving the product forward in the meantime. Regardless of size, we optimize our codebases so that we can rely on ack, grep, or find in project to help navigate and quickly surface the relevant parts of code. Sometimes this means foregoing the elegant, clever, or metaprogramming solutions that make sense to us, but are difficult for others to consume.
+Making sure your peers can follow a code trail easily or find out about the refactor or new abstraction that you're in the middle of will provide for more confident changes. We've found a mixture of coding techniques, feature coordination, and the right communication goes a long way. Combine all of this with an endless supply of whisky and you get a surprisingly productive and effective way to build products.
+## Brian Morton
+Brian is a software engineer at Yammer in San Francisco where he builds software to change the way the world gets work done. He loves solving hard problems and drinking whisky, but not always in that order. In his free time, he loves contributing to open source, playing Zelda, and spinning records on Serato.
+![Profile picture](
+- [My website](
+- [My twitter](
BIN  brian_morton-developing_for_ackability/profile_picture.jpg
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Something went wrong with that request. Please try again.