When I tell people I am the founding PM on Lambda, the question I often get is how the idea for #AWS Lambda/#Serverless came about in the first place. The truth is, its way too hard to point to one person/event as the defining moment.
-
Show this thread
-
It took 100s of customer conversations notes from multiple AWS folks where they told us 1/all the things they wanted to minimize/ not do at all while building applications; 2/architectural patterns they were repeating and wanted a way to build into their development flow.
1 reply 5 retweets 23 likesShow this thread -
It took some serious leaps of faith and acceptance of risk from the people involved, and a constant iteration on what we wanted the final product to look like. This is where I first saw the AMZN "Working backwards" process in action and its brilliance in driving the right focus.
1 reply 4 retweets 30 likesShow this thread -
What I do remember very distinctly is one of my first whiteboards on what became Lambda with
@timallenwagner where he stressed "Its all about the code, the app, the functions". In someways, that became one of the core tenants for how the product evolved.4 replies 13 retweets 47 likesShow this thread -
There be some fun stories in that journey (ask me about Lambda pricing sometime over alcohol) and terrifying ones (like when a big enterprise told us we were building a toy). As with all things, we get some right, we get some wrong, so keep us (AWS) honest with your feedback :)
6 replies 3 retweets 45 likesShow this thread
Drinks on me whenever you make it to NYC or PHL
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.