Earlier quoted context omitted.
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).
How do you do, fellow Kaleidan [1]? We worked together with Eric Benson and Dan Bornstein on ScriptX [2], which was basically Lisp with objects instead of parenthesis. I found ScriptX quite useful for web programming [3]: "Link Globally, Interact Locally"! ScriptX's legacy lives on: After Kaleida shut down, John Wainwright, the architect of ScriptX, created a very similar language called MaxScript [4] for 3D Studio M…
Employee #1: Amazon
111–120 of 124 posts
Re: Employee #1: Amazon
#112Re: Employee #1: Amazon
#113Earlier quoted context omitted.
> 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.
This rings a bell right now. :-) Last week I integrated with a service using (shudder) SOAP. I tried the XML call with curl and couldn't get it to work. I cursed, I frothed. The reply error was some Java dump, not helpful. It took me embarrassingly long to realize I got the HTTP header fields for SOAP from something wrong I googled -- it worked when I copied the header line from old code I wrote before... :-) :-(
Re: Employee #1: Amazon
#114Earlier 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?
Re: Employee #1: Amazon
#115Earlier quoted context omitted.
So I got down voted on this for WHAT reason?
Maybe because you are just guessing. Anyone can do that.
Re: Employee #1: Amazon
#116Earlier quoted context omitted.
Beautiful example of Peter principle and how to promote someone into uselessness and inefficacy.
I wouldn't call that the Peter Principle; he wasn't promoted above his skill set (per se) due to things like time in grade, which is what Laurence Peter wrote about. In the Peter Principle book the person causes damage through having responsibility without the ability to execute in that particular role. As others mentioned it was more a great way to reward someone who now didn't really have a specific spot. This is f…
At Sun, if they didn't actually want an executive to continue working for the company, they'd promote them to Vice President of Looking for a New Job.
Re: Employee #1: Amazon
#117This is interesting: Craig: Had you and Jeff stayed close? Shel: Not really. When he replaced me in my original job and I was moved into the CTO slot, I was nominally in charge of architecture, but in fact that just meant rubber stamping projects that were 95% complete by the time I saw them. That was all after having told me that my job was mine as long as I wanted it. And I didn’t have resources other than myself t…
Beautiful example of Peter principle and how to promote someone into uselessness and inefficacy.
Beautiful example of being tactful enough not to reply "No fucking way would I want to stay close to that psycho!"
Re: Employee #1: Amazon
#118Earlier quoted context omitted.
There was more Lisp influence than just the CS macros you mention here. Eric Benson was a major contributor to Lucid Emacs and many early Amazon engineers had Lisp experience. SICP was practically issued to every new software engineer--it was that popular. The template language for Amazon's website at the time (catsubst) was a Lisp-inspired prefix notation language with a relatively small number of functions. For exa…
EB and I both worked at Lucid, which produced a Common Lisp system, not to my knowledge a version of Emacs (though maybe so after I left in 1989?). Some other early employees knew and liked Lisp, but we didn't use it on any core functionality. The text substitution logic you mention, that I wrote, was really simple and not particularly Lisp-like. Though again, after I handed it off, who knows what happened.
I started in October 1997 and did Perl work on backend systems, but I had a few friends who worked on the frontend. They used to talk about how Catsubst had a very small set of verbs and that everything was a function, even arithmetic, and that prefix notation was used for all macro calls. They thought it was Lisp-inspired, but they were also pretty junior programmers too. I never worked with Catsubst myself, so my information is second-hand, while yours is zero-hand since you wrote it. :-)
Thanks for all the work you did on Amazon's infra!