danmccorm

Nice post. How do you customize the Damerau-Levenshtein algorithm? Did you write a new from scratch?

Great article. Designing a/b systems always seems (relatively) simple at the start, but in my experience there are 1,000 things you don't think of until you have massive amounts of worthless results. Add this to the list of things to watch out for.

Cool beans! I like that.

I think using them together is crucial. Qualitative research gives you insight into what you should look for through quantitative research. It's important to start with some basic qualitative research (talking to a few customers) and then scale it through quantitative methods (analyzing logs).

Phabricator's awesome, but this list is more for hosted services.

I like the part about arming others to help you. I've found this to be critical. The more your job specs reflect the excitement of working at your company, the more other people can evangelize that for you.

Shutterstock - New York, San Francisco, Remote, Visa

We're hiring all sorts of software engineers and data scientists. We've got some pretty fun problems -- image search, video search, storage scalability, tons of behavioral data to mine -- and an awesome team. We prefer folks to work in one of our offices, but are always willing to consider remote superstars.

Take a peek at http://www.shutterstock.com/jobs

Shutterstock - New York, San Francisco, Berlin, Remote, Visa

We're hiring all sorts of software engineers and data scientists. We've got some pretty fun problems -- image search, video search, storage scalability, tons of behavioral data to mine -- and an awesome team. We prefer folks to work in one of our offices, but are always willing to consider remote superstars.

Take a peek at http://www.shutterstock.com/jobs

Shutterstock - New York, San Francisco, Berlin, Remote

We're hiring all sorts of software engineers and data scientists. We've got some pretty fun problems -- image search, video search, storage scalability, tons of behavioral data to mine -- and an awesome team. We prefer folks to work in one of our offices, but are always willing to consider remote superstars.

Take a peek at http://www.shutterstock.com/jobs

Shutterstock - New York, San Francisco, Berlin, Remote

We're hiring all sorts of software engineers and data scientists. We've got some pretty fun problems -- image search, video search, storage scalability -- and an awesome team.

Take a peek at http://www.shutterstock.com/jobs

Great questions! Each team has a specific domain -- we have a customer experience team, a contributor team, a search team, etc. Each team also has one or more stakeholders -- business folks that help set the high-level direction of the team. The teams work with their stakeholders (some of whom are super hands-on, others aren't) to pick 2-3 projects per quarter to focus on. We try to talk in terms of the problems each team should solve, and let the team itself work out the best solution.

It has taken us years to refine our process, and it's been a great journey. I'm happy to chat more about it with anyone -- hit me up at dan at shutterstock.com

Spotify has a great article on this, if you haven't seen it: http://ucvox.files.wordpress.com/2012/11/113617905-scaling-a...

We have about 14 teams. The topic of management is a great one. We've shifted our approach over the years. That story might make a good blog article in itself. We've ended up with what's sometimes called a "matrix" structure, where people's day-to-day activities are based on what the team is doing, but each role (dev, tester, UX) reports into a manager (who's usually not on the team) with expertise in that domain. We've mostly avoided middle managers who only manage -- nearly all our managers are also on teams and, if they're devs, code. But we've also learned that having more than five direct reports can get pretty overwhelming, and so we've had to expand our org chart as we've grown for that reason.

What would you like to know? :)

Nope, usually about 6 people: 2-3 devs, 1 tester, 1 UX, 1 PO.

Umm: ERROR WITH QUERY: SELECT * FROM deal WHERE added_date >= '2013-11-08' - INTERVAL 30 MINUTE AND from_id IN(19) AND ship_id = ORDER BY cpd ASC LIMIT 0, 100 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ORDER BY cpd ASC LIMIT 0, 100' at line 1

http://cruisesheet.com/?from=Bayonne%2C+New+Jersey&ship=Expl...

Great post. I think this isn't discussed enough (which just benefits those companies who have nailed it). This ties into one of my prime lessons of tech management: always be recruiting. To do that well, you have to start with an awesome idea/company and then hone your message to get the best people working with you.

Yup, that's fair. I meant more that it encourages you not to get carried away with things that don't matter. But you're right, there's still a lot to be said for regular refactoring.