Suggestions
Steve Dake
Chief Technology Officer and Co-founder, building retrieval augmented language models.
Steve Dake is a distinguished professional with a strong background in Computer Science and Engineering, having studied at Northern Arizona University.
His vast experience includes holding notable positions in various renowned organizations. Currently, he is an Open Source Leader focusing on Cloud Native technologies at IBM.
Previously, Steve served as a Senior Principal Software Engineer at NetApp, showcasing his expertise in software development and engineering.
Steve Dake has also contributed significantly to the tech industry as a Member of the Board of Directors at OpenStack, demonstrating his strategic leadership abilities.
His career highlights feature roles such as Principal Engineer at Cisco, where he played a pivotal role in advancing technological solutions and innovations.
Steve's tenure at Red Hat saw him excel as a Principal Software Engineer in both the OpenStack and Clustering domains, solidifying his reputation as a versatile and skilled professional.
Before his tenure at Red Hat, he made valuable contributions as a Carrier Grade Engineer at MontaVista Software and as a Software Engineer at Intel Corporation, where he honed his technical prowess.
Overall, Steve Dake's career is a testament to his dedication to the tech industry and his remarkable expertise in software engineering and Open Source leadership.
Highlights
This developer video, created by Steven Dake at IBM in January 2019, demonstrates an Istio control plane canary upgrade. Unlike the more common in-place upgrade, a canary (or blue/green) upgrade allows for multiple running control planes simultaneously. This enables mesh traffic to be gradually shifted from one control plane version to another.
In a real-world scenario, an operator could transition services live without interruption over an extended period of months instead of big-bang on a Friday night. A #crowdstrike-like failure, where the configuration was not versioned with the code, is eliminated with this approach. Your internal teams always push straight to production, but the meaning of production varies by the control plane in use.
Thanks to Iris ( Shao Jun) Ding, Mariam John, Ed Snible, John Howard, Alexander Tarpinian, and Brad Topol.
Well done Sanjay Basu PhD! I made a few small changes as the language head didn't seem to exist for BERT. Instead I used the BART model. The results are pretty awesome! Thanks!
