4,858 karma · joined February 19, 2007
Previously very interim CEO of OpenAI, YC Partner, and founder and CEO of Twitch.
Email me at emmett@softmax.com.
To someone looking at characters for the first time, it's not obvious that the stroke order matters to the reader as spelling does in English. It's not about fetishization of the process over stroke order, it's really obvious to the reader if you wrote the character incorrectly.
As to how Josh feels about it, I leave you with this link to my TwitchCon keynote presentation: http://www.twitch.tv/twitch/v/17714623?t=37m0s
What makes you believe this is true, beyond simple assertion?
"Yale does not require students to take out loans for their education. Instead, Yale meets 100% of demonstrated need for all admitted students with a financial aid package consisting of need-based scholarships, term-time employment, and a student income contribution."
http://admissions.yale.edu/financial-aid-prospective-student...
So...Yale does what Stanford does already...
Team composition is literally irrelevant.
Stage magicians who obsessively practice the same motion over and over own their work, own their output, and feel empowered by the hard work and the success it brings.
Waiters who do the same thing because a larger machine they do not identify with dictates it feel disconnected.
The work itself is a distraction from the real problem, which is that the employee does not believe that what they are doing is important or valuable and that they don't feel ownership over their own actions.
Your main point (that making high reliability systems more conventionally reliable is building your high wall yet higher still) is definitely valid. But the lossage rate is actually a meaningful number given the extremely large number of objects stored in S3.
I've asked this specific question in interviews before, many times.
It's like a slightly harder version of FizzBuzz. It appears to have near perfect discrimination between "knows enough programming to use nested for loops with if-statements" and "does not". Programmers (good or bad), once the given the formal problem statement, solve it in under 20 minutes. People who don't actually really know how to program will never finish.
You might be imagining a slightly more difficult question, but it really is easy. It's an arbitrary coding challenge, sure, but one designed to not be tricky on purpose. The naive implementation works great.
I agree with what you're saying about video advertising CPMs, though it is quite possible to make a living on Twitch once you add in subscriptions at $5/mo.
Basically: you can't evaluate equity in a vacuum. It's entirely company-and-stage-of-growth-dependent. Those offers might be awesome or terrible.
In fact, that seems like a great policy idea.
There used to be a widespread belief in the VC world that you wanted to prevent founders from seeing any cash until the ultimate exit. As negotiating leverage has shifted towards founders this has gone away.
It's stupid anyway, since allowing founders to see a little cash up front actually aligns incentives much better once the company is somewhat successful.
If a company really wants to buy you, saying no will not make them go away. It will make them up their price.
If you've not advised a large number of fledgling startups, you wouldn't know, but really truly talking to corpdev is demoralizing and dangerous. If they really want you they'll reach out with an dollar figure (albiet probably a low one). If they haven't done that, they aren't serious. Don't waste your time.
If actually you've raised from a VC, a small acquisition means you'll not clear preferences, which means you get nothing other than retention. The VC/founder conflict only comes up when you have a medium successful company that could be really successful. But in that case you can almost certainly sell secondary stock, lock in your $1 million today, and still go for it.
But more than that, YC (and Paul) truly want to support the founders whatever they want. We celebrate the small sales as well as the big ones. It's simply not true this is selfish advise that you should disregard.
Take your Uber example. If you'd done user interviews pre-Uber, it's uncertain whether anyone would have said "yes I want to call a black car on my phone" or not. But I can pretty much guarantee that people would have said "yes, sometimes I have trouble getting a taxi to come pick me up".
User interviews at this stage are about validating the problem, not the solution.
"Nothing else mattered, including YC. Application time came around and we thought about not applying. It seems a bit silly to say now (to us), but it is true."
They'd become focused on the business and product, and that was the key.
Pro-rata is about investing MORE money into the company when you raise a round, to avoid being diluted. It's not something you can get "above".
I think you're talking about liquidity preferences here, which are a separate issue. You could get returns "above and beyond" liquidity preferences, so I'm guessing that's what your investors are actually talking about.
That's assuming a positive outcome that clears preferences of course - if the company goes in a fire sale you're not going to make anything at all. But assuming a billion dollar exit means you're assuming not a fire sale.
I love programming. It's a zen activity for me, turn me loose on a problem and I'll literally lose track of time because I'm so absorbed in the problems. It's one of the purest, most joyous singular activities I've ever had the pleasure of practicing.
After 5 years of doing it 8-10 hours per day, I was getting stale. I was putting in the hours and I think I was productive, but I wasn't encountering new problems very often anymore.
I moved into management shortly thereafter, and being a CEO has been fascinating in its own right. So far (3 years in) I have feel like I'm nowhere near the top of the learning curve. It's a constant challenge, in a way that programming wasn't for me 3 years in. I don't think I've ever been more fully intellectually engaged.
That said, I miss programming. A lot. I find excuses to pick up bug fixes. I wrote an internal tool that manages the distribution of status updates, and at least half the reason was just to be able to code something. I don't regret the career change, but I hope some day I can make programming my main gig again.
As an alternative, I think I could have switched from web programming & DBA work to a new problem domain like graphics or even mobile apps and probably gotten a new lease on learning-curve.
Taking that step back, when I look at where other engineers have gone in their careers within the Twitch organization, the success of a switch into management seems highly idiosyncratic. Some engineers really take to it and enjoy the new challenges; some of them hate it and want to switch back. We've had a number of people try it, decide it wasn't for them, and move back onto the IC (individual contributor) track. We pay top ICs about the same as top managers, so I suppose that might make it easier.
My bottom line advice would be: you don't really know if you'll like management unless you try it. If you're in a workplace where you have the option of switching into a management position, give it a shot. Just know that it's not for everyone.
Are you really saying that going from 10 samples to 11 samples causes a doubling (or 1.2x-ing or tripling or whatever) of the time/work required? That's what exponential means.