Actually, it is public -- https://www.linkedin.com/pulse/leadership-principles-aws-new... .
15,525 karma · joined February 24, 2007
Oh yeah, we were in the same row!
https://aws.amazon.com/blogs/aws/amazon_s3/
I do not know if this has anything to do with the cliff that you saw.
In 1979 I was 19 years old and had just started studying CS in community college. Through a lucky break I got a job at a consulting company and my first assignment was to write a 6502 macro assembler from scratch, in 6502 assembly language. At that point I had written less than 100 lines of 6502 code on my Apple ][, but I was fairly good with 8080 and IBM-370 assembly.
My mentor / manager outlined the basic model for the assembler and I wrote the entire thing myself, quickly getting it to the point where it could self-assemble, and adding features from there. I was making about $7 / hour when I started. However, I wrote a FORTRAN simulation of the hashing algorithm that I was asked to use, shared it with my manager, and got a raise to $8-something an hour.
I had macros, a very fancy listing format that showed all of the hex codes generated by the macros in neat rows, and a lot more. The entire thing fit on two tracks of the 8" floppy disks that we were using -- definitely less than 8000 bytes.
Are you referring to the universe or to S3? Corey and I were chatting a few weeks ago during his most recent visit to Seattle and I shared my thoughts with him while we were cooking and eating homemade pizza.
> Paul Allen, who would later become a co-founder of Microsoft, was a couple of years above Gates at school. Together they fixed the school scheduling software to ensure Gates was the only boy in classes of girls.
Pessimists!
Under his guidance I wrote the assembler, and even earned a raise after simulating the hashing function in FORTRAN and finding it lacking.
I still have very fond memories of that job and of the 6502, and would be interested in purchasing a replica as soon as you go into production!
Seriously, this is a very interesting idea. However, after losing both of my parents in the last 4 years, there's a sad but legitimate intermediate state between alive & well, and deceased. People lose their ability to function and make decisions on their own, might not be able to renew your service.
I believe that it addresses many of the OP's reasons for deciding against S3.
I am 100% sure that I did not write that, and I am 100% sure that this comes across as far too Jeff-like for comfort!
"Effective immediately, all S3 GET, PUT, and LIST operations, as well as operations that change object tags, ACLs, or metadata, are now strongly consistent. What you write is what you will read, and the results of a LIST will be an accurate reflection of what’s in the bucket. This applies to all existing and new S3 objects, works in all regions, and is available to you at no extra charge! There’s no impact on performance, you can update an object hundreds of times per second if you’d like, and there are no global dependencies."
Before joining Amazon in 2002, I built and ran Syndic8, a side project site that collected, polled, and organized RSS and Atom feeds for easy discovery. In addition to the web UI, Syndic8 featured a comprehensive web service API, powered by the then-popular XML-RPC protocol.
Syndic8 was built on PHP and MySQL and hosted at a colo provider. I was never able to scale beyond a single instance at my colo, and have sometimes thought about how I would rebuild the site today using EC2, S3, DynamoDB, and so forth.
My operational experience with XML, RSS, and web services was (I was later told) a deciding factor in the decision to hire me.