Post Microsoft, Luke went work for Amazon on the cloud, specifically EC2. The thing he had in the back of his head for many years was how to bring the programming model into the cloud space. He eventually left Amazon, and set out to combine his love of designing programming languages, with the movement and excitement of the cloud.
Prior to his current venture, he co-founded Automatic, connecting cards to the internet. This eventually sold to SiriusXM for several million dollars. Looking into another problem, he saw that the way people spend money lacked true visibility and connectivity between systems. He asked some questions, got some feedback, and set out to capitalize on the opportunity to build a better solution.
At Alkamai, Shinji worked with large enterprises and saw that there was a problem around data discovery, and that it was growing in the middle market, as more companies migrated to the cloud. She decided to build an automated way for users to discovery and understand their data.
Adrian dropped out of University school, and thought – what next? He didn’t want to do agency work forever. He took a look at how expensive, convoluted and clunky marketing technology tools can be. He vowed to create the ultimate suite of tools, and to do it on WordPress.
The genesis of Brandon’s current venture started with his wife, who manages a family office. At one point, she was switching accountants, which required the transfer of a massive amount of documents… the bulk of which was in email. He thought that there had to be a better way to find these documents, across accounts in the cloud.
In my experience, the need for technical documentation goes way beyond the boundaries of open source. Within the walls of a business, the need to share technical documentation around product architecture, entity relationships, DevOps workflow and even product strategy are absolutely critical in ensuring that everyone is on the same p age to move forward.
At the root, both types of technical documentation have the same goal – to inform the reader on how things should work. This episode was a great discussion on the topic, and I hope you enjoy Episode 8 of the Compiler podcast.
He enjoys building software that invokes an emotion from its user. While he was at Postmates, he got really interested in the way people work, specifically around flow states. He studied the Pomodoro method, and its associated 25 minute cycle. This became the first building block into creating his current venture.
Having been a JS person, he saw an opportunity to build out the frontend layer of the web. To put that in context, think about what Stripe, Twilio, etc. have done for the industry with their foundational, developer first API’s. He decided to create a framework that had no opinion about how you got your data. Along side of this, he created the optimal ecosystem for developers to build very fast – specifically, to develop, preview, and ship.
Growing up, David loved experimenting with sound – playing piano, tuning into radio stations, and tinkering with an old record player. He discovered there was an audio engineering program at school, and set out with the goal of starting a small project recording studio. He met his now wife and co-founder through their first voice recording project… which then, began to be advertised and attract more and more talent.
At a prior company as a developer advocate, Josh started using the Orbit model. He compared the model to being like the funnel for sales, except the Orbit model applies to community. After he left the company, he joined his now co-founder, using the Orbit model in a consulting context. Then, the aha moment occurred – what if we built a product to facilitate this?
After listening to How I Built This for some time, I realized that tech people could really benefit from having a show that was like HIBT, but bent towards tech. So Code Story was born.