Live data from Hacker News

Employee #1: Amazon

themacro.com

31–40 of 124 posts

Re: Employee #1: Amazon

#31

Earlier quoted context omitted.

People, or at least children, have been running around in parks trying to catch invisible animals for decades. As adults, it has definitely been a positive development for my wife and I.

"it has definitely been a positive development for my wife and I." Seriously? Just curious... what age range are you in?

I'm not the parent, but the new Pokemon game has been amazing for me. I'm 28 and single though. So obviously the target market. I've done more walking since the game came out than I had done in years. I've seen a lot of nature too. I found an owl in the park near my house. It was so close I could almost reach out and touch it.

In the context of the article, Kaphan is talking about technologies that isolate versus technologies that connect people. For the examples he gives:

1 seems to be neutral to me (people talking robotically to voice recognition systems). This is neither isolating nor connecting. It is just a different means of interfacing with a computer. I'm sure someone somewhere made a similar argument when the typewriter was invented.

1 seems isolating. Looking at your phone instead of being mentally present at your current location can be isolating. But then it depends on what you are doing. If you are participating in a text message communication, that's connecting you to someone else while isolating you from the physical world.

But Pokemon seems like it falls in the "connecting" category. I have something new in common with random strangers that we can discuss. I go out with my friends to play the game. The downside for some people seems to be that I am now physically present connecting with them and they would really rather I didn't. They liked the park empty and quiet.

Of course there are the incidents of people playing while driving or the one guy who walked off a cliff that one time (99% of the articles I've read slamming Pokemon Go mention the same 3 Reddit posts without attribution). But for me personally, I'm more present and walking around when I play Pokemon than I am when I'm posting on HN.

Re: Employee #1: Amazon

#32
His review of "The Everything Store: Jeff Bezos and the Age of Amazon"

https://www.amazon.com/review/R3J863C5ZP53BA

"I wasn't really planning on reviewing this book, because I was mentioned in it several times and it didn't seem appropriate. But several other people who were also mentioned in the book have already posted reviews, and in fact, MacKenzie Bezos, in her well known 1-star review, suggested that other "characters" might "step out of books" and "speak for themselves".

I was at Amazon for the first 5 years of its existence, so I also have firsthand experience of those times at the company, and I have been a fairly close observer since I left. By and large I found Mr. Stone's treatment of that which I know firsthand to be accurate -- at least as accurate as it is possible to be at this great a remove, and with no contemporaneous documentation of the early chaotic days or access to certain of the principals. Relying on people's memories of nearly twenty-year-old events is of necessity somewhat perilous. Of course there are a few minor errors here and there, but I don't have firsthand knowledge of important mistakes much less anything that appears to be intentionally misleading. But there are a few minor glitches. In my case, I can testify that I did not, in fact, have a bushy beard at age 17 when I worked at the Whole Earth Truck Store & Catalog in Menlo Park. It was a publisher and seller of books and other things, not a lending library. It was in a storefront and was no longer a mobile service operating out of a truck by the time I worked there (p. 32). But I do not think this is a reason to disregard the entire book; it's just some not terribly relevant detail the author got a bit wrong in a way that doesn't change the story materially. MacKenzie listed one error, which didn't seem especially awful or material to me, and then referred only vaguely to "way too many inaccuracies". Without a more explicit list of mistakes it is hard to know what to make of that. Breaking news: a new 372 page book has some errors!

Since Mr. Stone did not have access to Jeff Bezos for this book, but had to rely on previous interviews and the accounts of others, it would be surprising if there weren't a few mistakes regarding his thought processes. As part of my agreement to be interviewed for this book, I was allowed to read a draft of the chapter which covered the time I was there, and I offered a number of corrections, some of which Mr. Stone was able to verify and incorporate. To the extent I am quoted, my quotes are, while not complete, fair and in context. I don't love or agree with everything that Mr. Stone wrote about me -- especially his broader conclusions regarding the circumstances of my departure from the company -- but I do think it was fair and reasonable. I am aware of at least one other interviewee who was also given a chance to check over the chapter in which his story was discussed. I obviously can't know this, but I suspect that if Mr. Stone had been granted access to Jeff Bezos, that he would have extended a similar courtesy. I have a pretty high degree of confidence that Mr. Stone made a significant effort, and did what was in his power, to make the book accurate.

The irony is, of course, that by reviewing the book as MacKenzie Bezos did, she has brought an immense amount more attention to it -- there are dozens of articles referring to her review via Google News this morning -- and its sales rank has shot up considerably. The book is not a fawning hagiography, but it is also hardly a completely negative account either. It describes not only Amazon's ultra-hardball business practices, but the better aspects of their services and products as well. To the extent of my knowledge it is a pretty realistic account, though necessarily incomplete. Of course Mr. Stone has his own point of view, and of course he does what nearly all biographers do, which is to impute thoughts and emotions to the people he writes about. It would be mighty dull reading without that, but I think readers are generally smart enough to understand that when they read biographies, especially unauthorized biographies, the author has to recreate some kind of persona to make the subject appear life-like. That doesn't make it fiction. This was written as a business book for a popular audience anyway, not as an academic treatise, so expecting every "Bezos thought..." to be footnoted, or couched in hypothetical language, is not realistic.

Especially in comparison to the sad collection of awful books that have been written on this subject, this one is much more detailed, more interesting, and a lot more deeply reported. Sure, there is plenty more that could be written about, and maybe someday somebody will. If and when that happens, I can only hope it is also "unauthorized" and not sanitized by a corporate PR department, and that some real investigative journalism is done, like Mr. Stone did here."

Re: Employee #1: Amazon

#33
post #25

Earlier quoted context omitted.

http://imgur.com/gallery/SZPjHwz https://twitter.com/thepracticaldev/status/71639058321702912...

So true. So, so true. So true that I often question technical interviewing practices that look solely for ability to memorize complex algorithms exactly, vs ability to seek out an even better solution and apply it effectively.

At a previous job I put this in to practice. I would give interviewees a short list of questions on a piece of paper and after the interview they could use a browser and take as much time as they needed to answer the questions. Some were logic type questions that would be difficult to Google, some were just process questions that very few people would know off the top of their head but should be able to Google. The idea was to see if someone could find answers when they ran in to problems. Got some great hires using that technique (and avoided some hires that might have been disastrous!) HR killed it, though.

Re: Employee #1: Amazon

#34

Earlier quoted context omitted.

So true. So, so true. So true that I often question technical interviewing practices that look solely for ability to memorize complex algorithms exactly, vs ability to seek out an even better solution and apply it effectively.

At a previous job I put this in to practice. I would give interviewees a short list of questions on a piece of paper and after the interview they could use a browser and take as much time as they needed to answer the questions. Some were logic type questions that would be difficult to Google, some were just process questions that very few people would know off the top of their head but should be able to Google. The i…

Open book exams are known to be tougher!

I don't mind giving candidates access to language reference manuals, man pages and such.

Re: Employee #1: Amazon

#36
"Shel Kaphan was the first employee at Amazon. He is currently pursuing personal interests and still living in Seattle."

Yes bro, live the dream.

Re: Employee #1: Amazon

#37
post #34

Earlier quoted context omitted.

At a previous job I put this in to practice. I would give interviewees a short list of questions on a piece of paper and after the interview they could use a browser and take as much time as they needed to answer the questions. Some were logic type questions that would be difficult to Google, some were just process questions that very few people would know off the top of their head but should be able to Google. The i…

Open book exams are known to be tougher! I don't mind giving candidates access to language reference manuals, man pages and such.

May be so. These were pretty easy questions, though. Like 'What steps/commands would you use to reset the password on a [Make] [Model] managed switch through the serial port?' Very easy to Google.

Surprisingly, some people couldn't get the answer right even using Google.

Re: Employee #1: Amazon

#38
post #34

Earlier quoted context omitted.

Open book exams are known to be tougher! I don't mind giving candidates access to language reference manuals, man pages and such.

May be so. These were pretty easy questions, though. Like 'What steps/commands would you use to reset the password on a [Make] [Model] managed switch through the serial port?' Very easy to Google. Surprisingly, some people couldn't get the answer right even using Google.

> Surprisingly, some people couldn't get the answer right even using Google.

Never underestimate anybody.

I've seen numerous examples wherein folks would copy/paste an obviously inferior answer (or even incorrect) from a Stack Overflow post that contains a much better answer.

Re: Employee #1: Amazon

#39

I was hoping Shel would talk about using Lisp in the early days of Amazon. https://sites.google.com/site/steveyegge2/tour-de-babel#TOC-...

It was used only in the form of Emacs Lisp, as a set of tools for customer service folks to make replying to typical email easier for them. They pretty much built all that themselves (and they didn't start out as programmers).

Re: Employee #1: Amazon

#40
post #28

Earlier quoted context omitted.

Unquestionably! Lets say he had a typical 5%, no conservatively lets guess 1%. So 1% of 366 billion! Let you do the math. On the other hand if he had 10% which would not be unreasonable, he would be very rich.

A quote from a 2011 Geekwire article. " Jeff was working on it full-time already, and his wife, Mackenzie, was writing checks every once in a while. But that was it. I didn’t get founder’s stock." 0. http://www.geekwire.com/2011/meet-shel-kaphan-amazoncom-empl...

No founders stock doesn't imply no stock of any type.
Post reply on HN