1. Should that be 7x24 since it is followed by hour?
2. Hero worship is toxic. It like the ultra thin models used for advertising. This just perpetuates unhealthy attitudes toward work.
Edit: changed phrasing of 1
How is someone supposed to come to a conclusion that such companies are successful in spite of and not because of such environments? What a backwards way to build an organization.
These kinds of people have little life outside of work and few interests outside of tech.
There are those of us who seek careers in tech but do not want to go home and think about tech or even read much about it in their off-time.
My first 5 years on the job, I lived and breathed the subject matter - was kind of required since I didn’t study it in school, but to be honest, I have no memory of a social life or hobbies during that time and it kind of skipped past me like a poorly scratched CD... I just missed out on LIFE.
I now default to assuming that people with a lot of voluntary unpaid overtime have a personality disorder. Effectivity/productivity is an orthogonal axis.
Checking out Gold Fig Labs now :).
> We also knew Scala would help us attract good candidates, which it did.
Paul Graham wrote abt how one must beat the averages to be successful in a high risk world of startups [0].
> James and Andrew [the co-founders of Firebase] really treated me like a peer. At no point did I feel like Firebase was not mine.
Sam Altman has repeatedly said that culture is important and the way great companies are built is by making the first 10 or 40 employees feel like they are a part of the founding team.
> James and Andrew [the co-founders of Firebase] really treated me like a peer. At no point did I feel like Firebase was not mine.
This is super nice! Steve Huffman once said adding chat on the frontpage drastically changed hipmunk's understanding of the users of the site as the support was one-click away and they could act on user's frustration the very minute they were inconvenienced.
> At one point, we had a tweet posted on our wall, “Please marry me, Firebase!”
As Paul Buchheit would say, in the early days of the startup, make things a 100 people would love than things that a 1000 might like. u/rahulvohra had a great piece echoing similar sentiment abt HCX (high expectations customer) and how Superhuman found PMF by focusing on a smaller segment of their most demanding user base [1].
> Our highest order bit was to hire kind people. Obviously we wanted people with the right skills and ability to communicate...even on the toughest days, we still took time to take lunch together, walk around SoMa, and enjoyed every step along the journey.
Sam Altman repeatedly stresses on importance of hiring based on shared values and aptitude rather than a skill set in the early days of a startup. I guess, successful YC (?) companies all fit a similar pattern.
> The company was actually working on chat APIs, and then realized that their real-time infrastructure was more useful than the chat tools themselves. We pivoted to Firebase a few months after demo day.
This is one of the right ways to pivot. My favourite pivot story is of a startup that failed to raise money on demo-day, went back to work, tried hard but couldn't make it work, spoke to more users, realised they needed to build something complementary to what they were currently building, they built that and flew past $1 billion in evaluation in 2yrs after another pivot [4]. Like Michael Sibel says, if you've found a burning problem a set of users need solving, don't change the users or the problem in search of PMF, change the solution.
> Extremely high-concentrated messaging, like Kevin Hale telling us to focus on the one thing that’s important to our company right now.
Focusing on one to three things to do really improves velocity and helps with momentum, keeps everyone motivated to build. Breaking milestones into small one or three tasks that can be accomplished every week, you'd find that so much work gets done and importantly the momentum keeps of having done things keeps you moving forward. This hack is something that startupschool drills into you. Also see, producer vs consumer [2].
> And Gustav telling us, “You should launch this thing and you should be embarrassed.”
This has all kinds of nuances and caveats. For instance, Emmett Shear talks abt how if you're in the business of backing-up data (say, dropbox), you mustn't launch something that loses customer data as that would be fatal. So, you might need to get creative: Dropbox's MVP (or Minimumal Remarkable Product as Emmett calls it) was really a landing page with a video describing how Dropbox would work and its benefits to the end users with a sign-up form to get early access. They only launched when they were sure the product did backups really well.
> And we really didn’t know what was possible in us until we had people pushing us, people who wanted us to be as great as they thought we could be.
I met a YC alum recently and they said YC really changes your perspective on what's possible. That they were asked to think in terms of what'd your goals for the company and product be if you had unlimited capital. And it really changed how they ran the company even though they didn't have the capital at the time.
> ...at some point we were concerned that what we were building was too niche... We thought maybe it might be just DevOps managers or the security teams. Turns out, just about every developer has been in that situation.
And that's a huge market. A lot of disruptive tech starts out looking like a toy/niche [3].
Congratulations, Vikrum. All the best.
---
[0] http://www.paulgraham.com/avg.html
[1] https://firstround.com/review/how-superhuman-built-an-engine...
[2] https://news.ycombinator.com/item?id=3555581
[3] https://news.ycombinator.com/item?id=21315942
[4] https://www.youtube-nocookie.com/embed/L325PVEvm7Q?t=20m50s
