82 karma · joined September 3, 2012
You need to build something that will get shipped and work for the next little bit. Then, when you have an avalanche of customers you get to replace the engine in mid-flight. That's the dream.
The scenario where you build hugely scalable infrastructure with squeaky clean code is not the dream.
2. Interesting that you think of the stack that way. So you think Facebook will encroach onto Search at some point? What exactly is in the full stack?
And an obligatory reference to Apple, is Apple a different full stack or are they a short stack without search?
Now I want pancakes
Or I'd go with a designer role. Designer within the Data group? Something like that
John Gruber's podcast, touches upon this in the recent episode with Ben Thompson as a guest https://daringfireball.net/thetalkshow/2015/01/24/ep-108
It also helps if you know what is the highest priority and what can get sacrificed.
If you're late, talk about it in your retrospective. Taking time to look back will help you make better estimates in the future. Often times I gauge how reliable an engineer's estimate is based off of how many questions he/she asked me during the kick off meeting.
Part of the reason I wince when someone says, "growth hacker" is that too often I've seen someone with that title parachute in, turn all the knobs up to 11 and then run off to be airlifted into another team's domain. I think a lot of folks treat growth hacking as magic pixie dust that they can sprinkled around to make numbers go up. I'm sorry to say that my introduction to the term was well after it became bastardized.
Personally, I think we a new phrase for all this.
I usually try to take a real lunch, but it is tempting to get a bit of extra time back during midday. It ends up being a slippery slope where it silently goes from once-in-a-while to all-the-freaking-time.
I also probably end up physically leaving my desk, but spending my whole lunch spinning the wheels in my head and that's probably just as problematic.
Anyways, I enjoyed your comments wanted to give my personal opinion & point of view for at least points 1 & 2.
1. You're right that scaling is very hard. If you want a closer look at it, we have a tech blog that even I can read and understand. https://blog.evernote.com/tech/ Perhaps the most reassuring thing I can say is that Evernote runs on Evernote. Err... maybe this is more clear, Evernote (the company) runs on Evernote (the service). We eat our own dog food as they say, which means I've lost count of how many water cooler conversations turn into "there's something weird that Evernote's doing on my computer..."
2. Our Mac and Windows apps let you export your notes into HTML (including resources). Both these apps run natively against local files so you could export if you were offline or if for some reason our service was down. We try to compete by making a great app and a great service. In fact, we don't make money unless we've done a good enough job for you to upgrade to Premium. It seems like your main concern is that your text-only notes export to HTML instead of plaintext, which is a fair point. One of the nice things HTML is that there are third party applications that can convert from HTML into a number of other formats, so we're relying on that if you want your notes in RTF or as a .txt or something else.
It could easily be a scenario where they would rather see much fewer features that were well written and painstakingly cleaned up. However, their question/prompts may have accidentally led you to over-value quantity of features completed. I've seen a number of interviews go side-ways because of miscommunication like that.
It is really hard to tell what happened. If you can get feedback from them, that could be very useful. Otherwise, keep on plugging away.
Good luck to ya
But somewhere in that crowd, there are startups that do great work. Everpix just shut down, but they had a gorgeous product and a 12% conversion rate. With another round of funding they might done quite well.