And so we’ve invested significant energy toward libraries and architectures that let us build something once and use it multiple times.įor example, we use Protocol Buffers extensively for data storage, in-memory data structures, and cross-platform communication. If we had to rebuild the product from scratch on each of our eight platforms, we wouldn’t get very far. Good abstractions are important whenever you’re building software, but good abstractions that work across platforms are particularly essential for our small team. We still have a long ways to go, but here are some of the principles and processes that I’ve seen pay off huge dividends for our small team. And we’ve done so with just 13 engineers (including the two co-founders). We’ve built out comprehensive applications across 8 different platforms (web, Mac, Windows, iPhone, iPad, Android phones, Android tablets, and Apple Watch). We’ve been able to sign on a growing list of customers that love the product, including Facebook, Pinterest, Stripe, Instacart, Product Hunt, New Relic, and many other household names. So far at Quip, this focus on high-leverage activities has paid off. When you have a small team and a bold mission, the only way to make meaningful progress is to focus on the activities that offer you a lot of leverage - ones that give you a big return on your time investment. 2 At Quip, we aspire to build a new class of productivity tool that every person at every company enjoys using every single day. 1 Quora aims to share and grow the world’s knowledge and to build an internet-scale Library of Alexandria. I joined Quora when the team consisted of only 12 people and Quip when it had just 13. That’s a question I’ve often thought long and hard about during my years at Quora and, more recently, at Quip. How do you build a great product that impacts the lives of millions of people with just a small engineering team?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |