Tag: amazon
Amy and I watched the Amazon series Goliath last month. It was deeply awesome. Deeply deeply awesome. We also watched The Night Manager which we loved almost as much. And, at the end of each, I said to Amy, “They should end this now and not do a Season 2.”
Goliath captured my attention more.It had amazing character development. Bill Bob Thornton, who I’ve always liked, was at his best, William Hurt was excruciatingly delicious, Nina Arianda made me root for her every time she said something, and Molly Parker had mastery over the role of ruthless, hateful, and utterly self-centered, manipulative lawyer. The filming, while against the standard LA backdrop, was rich and unique. There were many tense moments that just kind of hung on for an extra few beats, which I loved. Each of the eight episodes had at least one unexpected twist and turn. The backstory was complex and finally all came together in the last episode, which was magnificent.
I thought the climactic moments were breathtaking. In the back of our minds we knew we were watching the last episode. And then the screen went black and it was over.
I expect it’s easy for Hollywood to crank out a Season 2. Take the complex characters, subtract a few, add a few new ones, put in a new current story, continue to unfold pieces of the backstory, and keep going. Hollywood knows how to do this.
But wouldn’t it be special if this was it? Just one season. An eight hour movie, instead of an annual TV show.
I have no idea what the economics of the movie business is, especially with all the new Amazon, Netflix, Showtime, AMC, SyFy, and HBO series. But I am intrigued with what feels like a new type of show – the six to eight hour movie. It’s a little too long to watch in one setting but you can watch it over a three to five day period. It becomes immersive without taking over everything. It doesn’t drag you out week by week with mildly unsatisfying endpoints. And it doesn’t end up being a 13 hour bingfest, which can be done (ala House of Cards) but doesn’t stay with you (or at least stay with me) as much.
I let this idea sit for a few weeks (I wrote the headline for this post three weeks ago after we finished Goliath.) When I saw it this morning, it still felt right to me. I wonder if, as the tech to deliver content continues to evolve, we will start seeing the one season / 6-8 hour show that ends at a peak moment, rather than is cancelled because it sucks.
I love Alexa. Of all the various tech things I’ve bought in 2016, Amazon’s Alexa has become the most consistently used new thing in my world. I’ve even had a breakthrough on the home front as Amy now regularly says “Alexa, play …” We’ve got them everywhere and the Echo Dot that showed up in October is centrally located on my office desk at Foundry Group.
On Wednesday, Techstars and Amazon announced the Alexa Accelerator, powered by Techstars. Applications will open in January and the first program will start in July 2017.
Amazon, through their Alexa Fund, has been investing in companies that are using Alexa Voice Service, Alexa Skills Kit, or companies working on the science behind voice technology, including text to speech, natural language understanding, automatic speech recognition, artificial intelligence and hardware component design. Several companies we’ve invested in, including TrackR, Rachio, and Dragon Innovation now count the Alexa Fund as investors.
It’s exciting to me to see Amazon and Alexa take it to the next level with their partnership with Techstars. I expect that will add another reason for me to spend even more time in Seattle.
Amazon is setting up Kindle bookshelves for some people, including me. If you want to see some of my favorite books from 2016 that I read on my Kindle, take a look at my Feld Thoughts 2016 Books.
I log all the books I read (Kindle or physical) on my Goodreads page. Interestingly, Goodreads is also owned by Amazon. It’ll be fun to see if / how they ultimately integrate all this stuff.
As I noticed quotes from the Code Conference dominate my Twitter feed yesterday, I saw a few from the Jeff Bezos interview that made me say out loud “Jeff Bezos is amazing.” I love his use of the phrase “cultural norms” (it’s one of my favorite phrases) and I particularly thought his comments on Donald Trump and the Peter Thiel / Gawker situation were right on the money.
The interview prompted me to think about how biases affect my thinking. I’ve been struggling with the Peter Thiel / Gawker stuff and have asked a few friends closer to the situation and the people involved to give me their perspectives as I’ve tried to determine whether my biases are overwhelming my perspective on it. As a result, I haven’t discussed it publicly, and instead have thought harder about it at a meta-level, which is actually more interesting to me.
I don’t know Jeff Bezos and have never met him, so my strong positive reaction to the interview reinforced this notion around unscrambling my biases as part of better critical thinking. If we use Amazon as an example, my relationship with the company, and my corresponding experiences over the years, have created a set of biases that I map to my impression of Bezos. And, as you read though the list below of my experiences / viewpoints, you’ll quickly see how the biases can create a chaotic mind-mess.
Following are the quick thoughts that come to mind when I think about Amazon.
- Love it as a customer
- Frustrated with how they have handled relationships with companies I’m an investor in
- Delighted with how they have handled relationships with companies I’m an investor in
- Moments of misery with interactions around difficult things
- Brilliance and clarity of thought from Bezos
- Wasted money on Amazon products that sucked
- Amazing delight with Amazon products that I use every day, including my Kindle
- Sucky experience as an author
- Distribution that otherwise wouldn’t exist for me as an author
- Many friends at Amazon
- Sympathy for the stupid way Colorado has dealt with them around affiliates and sales tax
I could probably come up with another 50 bullet points like this. Given that Bezos is the CEO and public face of Amazon, I map my view of the company to him. I know that is only one dimension of him – and his experience as a human – but it’s the one that I engage with.
Then I remember we are all human. Shit is hard. We make lots of mistakes. And, when I sit and listen to Bezos talk to Walt Mossberg, I have an entirely new level of amazement, appreciation, and intellectual affection for him, and – by association – Amazon.
I know that many different kinds of biases get in my way every day. I’ve learned the names for some of them, how they work, and how to overcome them through various work of mine over the year. But at the root of it, I realize that a continuous effort to unscramble them when confronted with something that has created dissonance in my brain is probably the most effective way to confront and resolve the biases.
For those of you in the world who tolerate me saying “what do you think of thing X” and then give me a thoughtful response, thank you, especially when you know I’m wrestling with trying to understand what I think about X. Now you know that part of what I’m asking you to help me with it to unscramble my biases around the particular person or situation that is represented by thing X.
I expect most of you know the fable of the scorpion and the frog, but if you don’t, it goes like this (quoted from Wikipedia):
“A scorpion asks a frog to carry him over a river. The frog is afraid of being stung during the trip, but the scorpion argues that if it stung the frog, both would sink and the scorpion would drown. The frog agrees and begins carrying the scorpion, but midway across the river the scorpion does indeed sting the frog, dooming them both. When asked why, the scorpion points out that this is its nature. The fable is used to illustrate the position that no change can be made in the behaviour of the fundamentally vicious.”
Over the weekend, there was some commentary on AWS in fight of its life as customers like Dropbox ponder hybrid clouds and Google pricing. Amazon turned in slightly declining quarter-over-quarter revenue on AWS, although significant year-over-year quarterly growth, as explained in Sign of stress or just business as usual? AWS sales are off slightly.
“Could Amazon Web Services be feeling the heat from new public cloud competitors? Maybe. Maybe not. Second quarter net sales of AWS — or at least the category in which it is embedded– were off about 3 percent sequentially to $1.168 billion from $1.204 billion for the first quarter. But they were up 38 percent from $844 million for the second quarter last year. In the first quarter, growth in this category year over year was 60 percent. So make of that what you will.”
Could Amazon’s nature be catching up with it, or is it just operating in a more competitive market? A set of emails went around from some of the CEOs of our companies talking about this followed by a broader discussion on our Foundry Group EXEC email list. It contained, among other comments:
- AWS is not the low price provider.
- AWS is not the best product at anything – most of their features are mediocre knock offs of other products.
- AWS is unbelievably lousy at support.
- Once you are at $200k / month of spend, it’s cheaper and much more effective to build your own infrastructure.
While we are in the middle of a massive secular shift from owned data centers to outsourced data centers and hardware, anyone who remembers the emergence of outsourced data centers, shared web hosting, dedicated web hosting, co-location, and application service providers will recognize many of the dynamics going on. Predictably in the tech industry, what’s old is new again as all the infrastructure players roll out their public clouds and all the scaled companies start exploring ways to move off of AWS (and other cloud services) into much more cost effective configurations.
Let’s pick apart the four points above a little bit.
1. AWS is not the low price provider. When AWS came out, it was amazing, partly because you didn’t need to buy any hardware to get going, partly because it had a very fine grade variable pricing approach, and mostly because these two things added up to an extremely low cost for a startup relative to all other options. This is no longer the case as AWS, Microsoft, and Google bash each other over the head on pricing, with Microsoft and Google willing to charge extremely low prices to gain market share. And, more importantly, see point #4 below in a moment. Being low priced is in Amazon’s nature so this will be intensely challenging to them.
2. AWS is not the best product at anything – most of their features are mediocre knock offs of other products. We’ve watched as AWS has aggressively talked to every company we know doing things in the cloud infrastructure and application stack, and then rather than partner eventually roll out low-end versions of competitive products. We used to think of Amazon as a potential acquirer for these companies, or at least a powerful strategic partner. Now we know they are just using the bait of “we want to work more closely with you” as market and product intelligence. Ultimately, when they come out with what they view of as a feature, it’s a low-end, mediocre, and limited version of what these companies do. So, they commoditize elements of the low end of the market, but don’t impact anything that actually scales. In addition, they always end up competing on every front possible, hence the chatter about Dropbox moving away from AWS since AWS has now come out with a competitive product. It appears that it’s just not in Amazon’s nature to collaborate with others.
3. AWS is unbelievably lousy at support. While they’ve gotten better at paid support, including their premium offerings, these support contracts are expensive. Approaches to get around support issues and/or lower long term prices like reserved instances are stop gaps and often a negative benefit for a fast growing company. I’ve had several conversations over the years with friends at Amazon about this and I’ve given up. Support is just not in Amazon’s nature (as anyone who has ever tried to figure out why a package didn’t show up when expected) and when a company running production systems on AWS is having mission critical issues that are linked to AWS, it’s just painful. At low volumes, it doesn’t matter, but at high scale, it matters a huge amount.
4. Once you are at $200k / month of spend, it’s cheaper and much more effective to build your own infrastructure. I’ve now seen this over and over and over again. Once a company hits $200k / month of spend on AWS, the discussion starts about building out your own infrastructure on bare metal in a data center. This ultimately is a cost of capital discussion and I’ve found massive cost of capital leverage to move away from AWS onto bare metal. When you fully load the costs at scale, I’ve seen gross margin moves of over 20 points (or 2000 basis points – say from 65% to 85%). It’s just nuts when you factor in the extremely low cost of capital for hardware today against a fully loaded cost model at scale. Sure, the price declines from point #1 will impact this, but the operational effectiveness, especially given #3, is remarkable.
There are a number of things Amazon, and AWS, could do to address this if they wanted to. While not easy, I think they could do a massive turnaround on #2 and #3, which combined with intelligent pricing and better account management for the companies in #4, could result in meaningful change.
I love Amazon and think they have had amazing impact on our world. Whenever I’ve given them blunt feedback like this, I’ve always intended it to be constructive. I’m doubt it matters at all to their long term strategy whether they agree with, or even listen to, me. But given the chatter over the weekend, it felt like it was time to say this in the hope that it generated a conversation somewhere.
But I worry some of the things they need to be doing to maintain their dominance is just not in their nature. In a lot of ways, it’s suddenly a good time to be Microsoft or Google in the cloud computing wars.
As we gear up to release Uncommon Stock, our first FG Press book, we just had an internal discussion about book blurbs. The concept of a blurb was apparently invented in 1907. The origin story of the blurb is amusing – according to Wikipedia:
“The word blurb originated in 1907. American humorist Gelett Burgess’s short 1906 book Are You a Bromide? was presented in a limited edition to an annual trade association dinner. The custom at such events was to have a dust jacket promoting the work and with, as Burgess’ publisher B. W. Huebsch described it, “the picture of a damsel — languishing, heroic, or coquettish — anyhow, a damsel on the jacket of every novel” In this case the jacket proclaimed “YES, this is a ‘BLURB’!” and the picture was of a (fictitious) young woman “Miss Belinda Blurb” shown calling out, described as “in the act of blurbing.”
While the history lesson is cute, the blurb has long since ceased to be useful. As a reader, I’m incredibly suspicious of them because as a writer, I know how they are manufactured. More on that in a bit, but for now, take a few minutes and check out some #HonestBlurbs.
Our internal back and forth on whether to include blurbs on our FG Press books resulted in the following rant from me.
I think endorsements like this are bullshit. I’m literally getting asked daily (5 times / week – sometimes more) to endorse books. I used to do it, now I say no unless it’s a friend, and even then they usually write the endorsement.
It’s an artifact of the publishing business that existed before “earned media” – blog posts, reviews, etc.
I’d love to just BLOW UP blurbs.
I think we should be focusing on real earned media, real reviews, real substantive support, rather than marketing nonsense the industry has been pushing since the early 1900s.
We had a little more back and forth but the more I thought about it, the more I have no interest in blurbs. I’ve been saying no to a lot of the requests I get recently, after having my name on probably 50 blurbs for other books in the last few years. At first, I always read the book before writing the blurb. Then, I started skimming the book before writing the blurb. Recently, I’ve been either asking the writer to send me a draft of the blurb they’d like, or I’ve just said something generically positive but non-substantive.
I’ve watched the other direction work the same way. It’s similar to press release quotes – it ends up being manufactured PR stuff, rather the authentic commentary. The idea that a static, short, manufactured blurb from a well known person as an endorsement of a book is so much less authentic than Amazon reviews, GoodReads, and blog posts from people who actually read the book.
When people send me a note that they liked my book, I ask them to put up a review on Amazon if they are game. When someone writes with constructive feedback on a book I’ve written, I ask them to put up a review on Amazon, with the constructive feedback, if they are game. I appreciate all the serious feedback – both good and bad. Sure – I get trolled by some people who say things like “Feld is a moron, this book is another stupid thing he’s done.” I ignore that kind of thing, and feel that most rational humans can separate the signal from the noise.
So, at least for now, we aren’t going to do blurbs on FG Press books. Instead, we’ll ask people to put up reviews on Amazon, GoodReads, their blog, and other sites that make sense. And, when someone requests a blurb from me, I’m going to start passing and defaulting to writing a review on this site and putting up the review on Amazon on GoodReads, like I have for many of the books I’ve read.
If you think Amazon Prime Air is neat, you’ll love the new Amazon Prime Ground.
Spheros and Quadcopters are available with shipping still in time for Christmas.
As a part of Startup Phenomenon, I’m going to spend a half hour with Jason Illian, the CEO of BookShout!, on Thursday, November 14th at 4:30pm. It’ll be at the Boulder Public Library, which is right across Boulder Creek from the St. Julien and downtown Boulder.
We’ll be talking about the Startup Revolution book series (which include Startup Communities and Startup Life), as well as the wonderful platform that Jason and his team have built.
I’ve been a fan of BookShout! for a couple of years now.
As an author, I’m always looking for ways to connect with my audience. I spend time with the people from the local startup scene all the time but connecting with aspiring entrepreneurs from around the country, and around the global, is an entirely different beast. Comments on Amazon are one-directional, and definitely do not encourage reader-to-reader interaction. Buying a book in a bookstore is an individualistic experience. Getting a book at a conference means reading it after the conference is over, which doesn’t leave any time for in-person discussion or engagement.
Enter BookShout!. First glance, it’s nothing special. Simple but effective distribution of books. All the goods when it comes to commenting and rating. Where BookShout! really shines is how it brings an audience and an author together, on the same page – both literally and figuratively – and allows them to have an unfiltered conversation around the content of the book.
It’s a powerful tool for authors and an interesting site for readers. If you’re either, check it out.
And if you’re in Boulder tomorrow afternoon, for Startup Phenomenon or not, come on by the Boulder Library and hang out with me and Jason.
See you there!
RSVPs are requested. Please do so here. While you’re there, check out some of the Master Classes that Startup Phenomenon is offering.
When the Second Edition of Venture Deals: Be Smarter Than Your Lawyer and Venture Capitalist came out, I was baffled that the books were listed as two separate Amazon items. The biggest impact was that all the reviews for the first edition did not sync with the second edition, so anyone coming across the second edition wouldn’t see all the first edition reviews. There was also a bunch of other content missing from the Second Edition page. In frustration, I wrote a post titled The Mess of a Second Edition Book.
For several weeks I dug into this with Wiley (my publisher) to no avail. I kept hearing back that the Second Edition is considered an entirely new book. I accepted that (it has a separate ISDN number), but I still wanted the two pages to be linked. The First Edition pointed to the Second Edition, but the Second Edition didn’t point to the first edition. And – none of the content on the pages was synchronized. I kept thinking some version of “c’mon guys – this is just meta-data – how hard could this really be?”
Dane McDonald, who works for me, eventually just took it on himself to figure this out. He went to the Amazon Author Central site, found, and followed the instructions.
- Login to your Amazon Author Page.
- Click on the “Help” button in the navigation Bar.
- Click on the “Contact Us” button in left hand sidebar of your screen.
- Under “Select an issue,” select My Books.
- Under “Select details,” select Update information about a book.
- In the field that appears, select Update something else.
- In the next field that appears, select I want to link one edition of my book to another edition.
- Make sure to include your email address as well as both ISBN #’s for the two editions of the book you would like to link.
- It takes 1-3 business days for the link to take effect.
Voila. Several days later what Wiley had said was impossible now worked. The two editions were linked and all was good in the world. Until the other day, when the books magically unlinked. Boo.
Yesterday, I followed the instructions again to relink the editions. This time I got a disappointing email from Amazon.
I understand you would like us to link ISBNs 978-1118443613 and 978-0470929827.
The books requested for linking, Venture Deals: Be Smarter Than Your Lawyer and Venture Capitalist ISBN 978-1118443613 and 978-0470929827 don’t meet the qualifications to be linked. Please accept my sincere apologies for this disappointment.
In order to be linked, books must have the same content. Linking books such as the hardcover and paperback edition is meant to allow customers to choose between different formats, but customers should be able to expect to read the same content. Newer editions of nonfiction books generally have additional primary content, and therefore aren’t considered materially the same.
Books that are different parts of a set, or derivations of one another can’t be linked, even though they may be similar.
Thank you for contacting Author Central. We hope to see you again soon.
Double boo. I guess I should be frustrated, but pretty much everything about the old school publishing process baffles and perplexes me. Almost none of it is from a reader or author’s perspective. The publishers and distributors have their own magic language, special rules, and byzantine processes. Everything is harder than it needs to be, doesn’t work quite as expected, and has a bunch of extra words around each step.
I’ve let go of my frustration. Now I’m just amused. And I’m glad stuff like Bookshout exists – hopefully it’ll stimulate another wave of reader-centric disruption.