vnorby
Joined 18 years ago
Joined 18 years ago
When customers walk into a Barnes and Noble (or any bookstore) and browse books but don't buy (for example, because they found a cheaper price online), they are most likely to end up on Amazon to complete the purchase. B&N did the work but Amazon got the money.
Amazon doesn't have that problem. They don't need to sell books in the store to "pay the store's operating expense" - they just need people to come in and browse.
Currently, Amazon doesn't compete for a high percentage of books (50%) moved through physical stores [2]. They are in the enviable position of being able to create stores that don't leak sales to competitors. This is the final nail in B&N's coffin.
[1] http://www.thewire.com/business/2014/05/amazon-has-basically...
[2] http://www.dailydot.com/business/ebook-sales-2013-revenue/
We're looking for our first non-founder engineer to join a small team backed by leading VCs and angels. We're working on something amazing and different from most software companies in a huge market. Our founding team of 4 is out of Nest Labs/Google. We're looking for a full stack engineer or front-end web engineer to lead our web team. Market compensation and huge equity stake for the right fit. We're a Ruby on Rails shop with single page apps built on Backbone and React. Please email me at vnorby at icloud dot com.
Imagine a neighborhood of 100 homes where you know all 100 people will return approximately at 6pm in the winter, and they all want 72 degrees. Taking into account the insulation of each home, if you could pre-heat the homes on a rolling schedule (say, heat 25 of them to 75 degrees at 3pm, accounting for 1 degree of heat dissipation per hour, heat another 25 to 74 degrees at 4pm, etc.), you will actually in aggregate save a lot of energy and cost because of inefficiencies in the way we deliver and generate energy during peak times.
(@yitchelle - central data center)
I work at Nest and it may be a little unclear at the moment (we're working on it), but The Nest API does not guarantee that if you send an ETA of 15 minutes (docs: https://developer.nest.com/documentation/eta-guide), the home will heat to the appropriate level in 15 minutes. It's actually filtered through our algorithms to determine the best course of action to not waste energy but also provide the appropriate level of comfort.
This is the important line in the article. Co-founder breakups probably happen more because the startup is not doing well, and not vice versa. I'm not sure if it makes sense to try and optimize for not running into co-founder problems as much as just optimizing for your company's success as normal.
If your company is killing it, and you're a co-founder and you've got 10% and you want to be the CEO and your grad school dropout grace period is ending and you'd rather be working on technical problems, you're most likely going to stick it out regardless.
Origami.com (formerly known as Everyme) is a YC-backed (S11) startup building an online home for families. We are 8 people (5 eng, 2 design, 1 biz) that are passionate about helping families and loved ones communicate and store memories for generations. We are a subscription-based service that is launching soon and already has a passionate base of beta users. We also operate Everyme, a private social network with over 300,000 downloads.
If you're interested, please email me with information about yourself to [email protected] and I'll get back to you right away.
Perhaps what you want to say is that you don't like the benefits packages that startups with young founders provide, because they don't understand what a more senior engineer expects on that side of the compensation equation. That might be more fair.