History of Amazon Updated +Created
I wonder where the spray painted sign went: twitter.com/profgalloway/status/1229952158667288576/photo/1. As mentioned at officechai.com/startups/amazon-first-office/ and elsewhere, Jeff did all he could to save money, e.g. he made the desks himself from pieces of wood. Mentioned e.g. at youtu.be/J2xGBlT0cqY?t=345 from Video 4. "Jeff Bezos presentation at MIT (2002)".
Video 1.
Amazon.com report by Computer Chronicles (1996)
Source. Contains some good footage of their early storehouse.
Video 2.
Jeff Bezos interview by Chuck Films (1997)
Source. On the street, with a lot of car noise. CC BY-SA, nice.
Video 4.
Jeff Bezos presentation at MIT (2002)
Source. Good talk:
Video 5.
Jeff Bezos Revealed by Bloomberg (2015)
Source.
Video 6.
cosine by Jeff Bezos (2018)
Source.
PDE mention in another video from 2009: youtu.be/TYwhIO-OXTs?t=118
Full original video from The Economic Club of Washington, D.C. (2018): youtu.be/zN1PyNwjHpc?t=1544
Bezos also told PDE stuff in interviews as early as 1999: archive.ph/a3zBK.
Bibliography:
  • archive.ph/ucSHN This is what it was like to work at Amazon 20 years ago (2015). Good annecdotes from the first offices.
Integrated development environment Updated +Created
IDEs are absolutely essential for developing complex software.
The funny thing is that you don't notice this until someone shows it to you. But once you see it, there is not turning back, just like Steve Jobs customers don't know what they want quote.
Unfortunately, after the Fall of Eclipse (archive), the IDE landscape in 2019 is horrible and split between:
  • highly buggy but still feature rich Eclipse
  • many may many other feature lacking options using possibly more trendy and forward lasting implementations like Electron
  • awesome cross-platform proprietary JetBrains IDEs
  • the God-like Windows-only proprietary language-lacking Visual Studio
Programmers of the world: unite! Focus on one IDE, and make it work for all languages and all build systems. Give it all the features that Eclipse has, but none of the bugginess. Work with top project to make sure the IDE works for all top projects.
Projects of the world: support one IDE, with in-tree configuration. Complex integration is often required between the IDE and the build system, and successful projects must to that once for all developers. Either do this, or watch you complex project wither away.
Build tool maintainers: make it possible for IDEs to support your tool! E.g., implement JSON Compilation Database output so that IDEs can read the exact compiler commands from that, in order to automatically determine how files should be parsed! Or better, just use libllvm in your IDE itself as the main parser.
Ciro is evaluating some IDEs at: github.com/cirosantilli/ide-test-projects