Screaming in the Cloud with Corey Quinn features conversations with domain experts in the world of Cloud Computing. Topics discussed include AWS, GCP, Azure, Oracle Cloud, and the "why" behind how businesses are coming to think about the Cloud.
Jon Myer is a partner solutions architect for cloud management tools at AWS. Prior to joining AWS, Jon worked as a senior cloud solutions architect at NetEnrich AWS, an AWS consultant for DevOps and Solutions at MetroStar Systems, and an AWS course author at Linux Academy. A self-described evangelist for all things AWS, Jon holds a host of AWS certifications and blogs at TheAWSBlogger.com.
Join Corey and Jon as they discuss what a partner solutions architect for cloud management tools does at AWS, the company’s top partners for cloud management, what it’s like to be part of the AWS team, what it’s like to work from home during the COVID-19 pandemic and how it compares to working from home during “normal times,” how working from home will become the new normal in the near future, why you can’t measure work-from-home productivity effectively during COVID-19, two new features Jon just realized Chime has and what he hopes to see added to the video meeting tool in the near future, why Jon launched his own AWS-focused blog, what AWS’ response to his blog has been, and more.
Tim Bray—the founder of OpenText, one of Canada’s biggest software companies—is a self-professed general-purpose Internet software geek with more than 35 years of experience in the world of technology. In April 2020, he resigned from his job as a senior principal engineer/distinguished engineer at AWS, where he worked in the Serverless group. Other positions he’s held over the years include developer advocate at Google and director of web technology at Sun Microsystems.
Join Corey and Tim as they discuss the genesis of XML and JSON along with their shortcomings, what it was like being a distinguished engineer at AWS and resigning due to ethical concerns, why Tim believes capitalism doesn’t work when companies get too big, the Streisand effect and what happens when you fire whistleblowers, how AWS was the best place Tim worked in his career but why he had to leave anyway, what Tim likes about Kubernetes, the technology trends that interest Tim the most, what the future looks like, Tim’s interest in public sector procurement, and more.
Katie Bullard is the president of A Cloud Guru, a cloud education platform. She’s also a board member at Conservice, ChildCareCRM, and Journyx, Inc. Katie previously served as president and chief growth officer at ZoomInfo (formerly DiscoverOrg), VP of marketing, product and corporate development at Mitratech, director of marketing at Accruent, and chief of staff and leader of corporate strategy at Dun & Bradstreet, among other positions.
Join Corey and Katie as they discuss Katie’s tenure at A Cloud Guru, how three months feels like both three weeks and three years at the same time, how everyone has a different learning style and what A Cloud Guru is doing to accommodate all of them, how not knowing something makes us vulnerable whether or not we want to admit, what it was like for Katie to accept a new position only to find out six days later A Cloud Guru was acquiring Linux Academy, how A Cloud Guru has both B2B and B2C products, what it’s like to run a company founded by other people, and more.
Liz Fong-Jones is the Principal Developer Advocate at Honeycomb, a company that helps developers visualize, understand, and debug software. Prior to joining Honeycomb, Liz worked at Google for over 11 years, wearing many different hats over that period, including Staff Developer Advocate, Staff Site Reliability Engineer, and Site Reliability Engineering Manager.
Join Corey and Liz as they discuss why people either love or hate Honeycomb, how Honeycomb has been pretty awesome to Corey over the years, why Liz left Google after an 11-year run, what Liz’s opinions on AWS and GCP are, how nobody really has a good understanding of AWS’ offering, why Liz doesn’t think anyone has to worry about GCP being deprecated, what boards and VCs tend to do once they hear the word “union,” how there isn’t an ethical leader among cloud providers, and more.
Forrest Brazeal is Cloud Bard who doubles as a senior manager at A Cloud Guru, an e-learning company that helps people learn about the cloud. Previously, he worked as a senior cloud architect at Trek10, Inc. and team lead for cloud architecture and services at Infor. One of the original AWS Serverless Heroes, Forrest holds a master’s in computer science at Georgia Tech, where he earned a 4.0 GPA.
Join Corey and Forrest as they discuss what it’s like to be a cloud bard, why you should try to pull fun things into your job so you can get paid to do what you love, what it’s like to design and scale cloud training initiatives, how not everyone knows what the cloud is, the role empathy plays in cloud education, how Forrest wrote a book about the cloud in verse, how Forrest believes there will be hundreds of millions of developers by the end of the decade, what Forrest thinks is an effective way to teach people the cloud, and more.
Melanie Cebula is a staff software engineer at Airbnb who’s focused on cloud infrastructure. She’s a 2016 graduate of UC Berkeley, where she earned a bachelor of arts degree in computer science. Prior to joining Airbnb full-time, she interned there on the payments team. She’s also worked as a teaching assistant at UC Berkeley (CS 164 - Programming Languages and Compilers and CS 61B - Data Structures) and has interned at Facebook, too.
Join Corey and Melanie as they discuss the differences between junior, senior, staff, and principal engineers, what a staff engineer’s job looks like at Airbnb, why cloud cost efficiency is a hard-but-great problem to work on, why some engineers are hesitant to turn anything off, how much of optimizing cloud spend involves picking off low-hanging fruit, why it’s more fun to talk to technologists about cloud problems than vendors, how Airbnb uses Kubernetes and what that means for AWS spend analysis, and more.
Conrad Heiney is a principal cloud engineer at Glidewell Dental, a company that distributes high-quality dental lab products to dentists and laboratory professionals around the world. Conrad has more than 20 years of experience as a system administrator, working for companies like Fox Sports, Buzznet, DIRECTV, Tierzero, and ZestFinance along the way. He specializes in Unix system administration, AWS cloud services, Opscode Chef management, MySQL DBA management, and a host of other areas.
Join Corey and Conrad as they discuss the path that led Conrad to the world of computers, what it was like to be part of the generation that was essentially inventing the modern internet, how great it is to work alongside a developer who knows ops, what it was like to work at a newspaper in the 1980s (hint: everyone hated each other), why in the age of containers and serverless it’s still important for companies to understand what’s going on in the proverbial black box, why Conrad thinks tech workers aren’t more special than anyone else, the role empathy and humility should play in tech, and more.
Jessy Irwin is the Founder at Amulet. Prior to this role, she ran her own consultancy, Jessysaurusrex LLC, for seven years, worked as a vice president of privacy and security at a privately owned public affairs firm, and was a security empress advocating for password managers at AgileBits, Inc.
Join Corey and Jessy as they discuss the best job title in the world, how majoring in art history was the best life decision Jessy made, why security needs to be as mundane as vacuuming the house, what Jessy is doing to make security more enjoyable, the role consumer branding plays in the adoption of security tools and practices, why Jessy thinks security problems are akin to lifestyle choices, why security practitioners should be focused on raising the cost of an attack, one of Jessy’s endless frustrations about working in blockchain, why Jessy generally avoids using the b word, and more.
Dwayne Monroe is a senior cloud architect at Cloudreach, an organization that helps enterprises maximize their cloud investments, who’s focused on Azure. Prior to joining Cloudreach, Dwayne worked as a senior Microsoft and cloud architect at High Availability, Inc., a Microsoft cloud solutions architect at McGraw-Hill Education, and a Microsoft Technologies Architect at MedRisk, Inc., among other positions.
Join Corey and Dwayne as they discuss the journey that led Dwayne to Azure, how and why the typical customer ends up in Azure, the kinds of new services Dwayne sees being built on Azure, why it’s important to understand an enterprise’s legitimate concerns as they consider cloud migration, how Visual Studio Code is awesome and would be even better if it worked on an iPad, how the people who use Azure tend to be more concerned about operational things than very flashy things, how negotiating with Microsoft has gotten considerably easier in recent years, and more.
Wes Miller is a research analyst at Directions on Microsoft who’s focused on Microsoft identity, security, and management. Over the years, he’s worn many different hats, including serving as director of product management for Invodo and CoreTrace, a contributing editor for TechNet Magazine, an engineering manager at Pluck Corporation, and a product technology strategist at Winternals Software. He also did an eight-year stint at Microsoft, working as a product manager, program manager, implementation manager, and intranet web developer.
Join Corey and Wes as they discuss the Directions on Microsoft origin story, the wild world of software licensing, how Azure currently plays second fiddle to AWS, how trying to figure out cost savings in the cloud is akin to untying a Gordian knot, Wes’ “cloud paradox” and what it means for predicting cloud spend, why Wes believes there should be a dedicated individual analyzing spend at a vendor when the numbers are high enough, why Microsoft is still the same old Microsoft despite what many people think, how marketing and developers often speak different languages, and more.
David Boeke is the CTO and VP of Services at Turbot, a cloud governance platform that automates compliance, security, and operational controls for the public cloud. Prior to joining Turbot, David served as the global head of healthcare technology and the global director of architecture and integration at Janssen, a Johnson & Johnson subsidiary. Before those roles, he worked at Johnson & Johnson for 17 years, rising to the senior director of enterprise architecture during that time.
Join Corey and David as they discuss what exactly it is that Turbot does; how the cloud makes it easier to keep track of all of your assets thanks to its searchable nature; how David’s background in pharma helped him bring a regulation-first mindset to the cloud; how large organizations sponsor conferences like re:Invent to attract talent; how Turbot works with one-person IT shops all the way up to enterprise with two dozen developers; why tagging resources is important even though it’s one of the least sexy things you can do; why teams should focus on one thing at a time, automate that thing, and move on to the next thing; how Turbot reimagined its dashboard reporting design to give users more peace of mind; and more.
Chris Hill is the CEO of HumblePod, a company that helps businesses develop authentic podcasts and happens to produce Screaming in the Cloud. Prior to founding HumblePod, Chris worked as a business development director and Chief Operating Officer at Smallball Media, a sales development manager at Finworx, a project manager at High Profile Enterprises, and an account manager at AT&T, among other positions. Chris lives in Knoxville, Tenn.
Join Corey and Chris as they discuss how Chris got started in the podcast business, the genesis of the name HumblePod, how the feedback model is remarkably different for podcasts versus newsletters, how podcasting opens up the doors to having conversations with titans of industries that would otherwise be impossible, why Chris thinks podcasting is like a magic wand, why people are more willing to hop on a podcast than sit down for a video interview, the importance of having high-quality equipment to record podcasts with, why podcasting makes attribution difficult for advertisers, and more.
Miles Ward is the Chief Technology Officer at SADA, a global business and cloud consulting firm that is Google’s largest partner. Prior to this role, Miles worked as the director of solutions and global lead at Google Cloud for five years and served as the senior management of solutions architecture at Amazon Web Services for four years. He’s also held director-level positions at Visible Technologies and Insurgent Technologies.
Join Corey and Miles as they discuss hybrid and multi-cloud environments, what Andy Jassy believes is the biggest impediment to AWS’ growth, why Miles decided to leave Google after a life-changing five-year run, how managing a team of 80 makes it nearly impossible to get your hands dirty with tech, what a solutions architect does and whether the job description changes from company to company, the product Miles killed at Google and what the experience was like, how much Miles believes it costs Google to turn off products, what the Achilles heel of every public cloud is, and more.
Alex DeBrie is the founder of DeBrie, LLC, a cloud-native training and AWS consulting company with a focus on DynamoDB and serverless technologies. He’s also the author of The DynamoDB Book, a 450-page tome that offers tips, strategies, and more about data modeling in DynamoDB. Prior to starting his own company, Alex was an engineer at Serverless Inc. and Hudl. Before that, he worked as an associate attorney for a law firm in Nebraska after earning his J.D. from the University of Virginia School of Law.
Join Corey and Alex as they discuss what got Alex so interested in DynamoDB in the first place, why Alex isn’t worried about AWS pricing, why you should view your cloud provider as a partner instead of an enemy, the many hats Alex wore at Serverless, Inc., why Dynamo is the database of choice for serverless applications, why auto-scaling doesn’t work quite as well with DynamoDB as it does for EC2, the most egregious uses of DynamoDB Alex has encountered to date, how Alex made the leap from law school to engineering and tech, the time Alex was the number two Django contributor on Stack Overflow over a six-month period even though he’d never done any real production, and more.
Stephen O’Grady is a cofounder of RedMonk, the open source industry analyst firm, and he works as a principal analyst there. Prior to joining RedMonk in November 2002, Stephen held several different analyst and consultant positions at companies like Illuminata, Blue Hammock, DiaLogos, and Keane, Inc. He’s also the author of two books: The New Kingmakers and The Software Paradox.
Join Corey and Stephen as they talk about what RedMonk is and how it’s different from other analyst firms, why Stephen decided to write books that were about half as long as other similar books, how the prominence of the developer within the organization has shifted over the last few years, why having a lot of software solutions at your fingertips is both a good and a bad thing, what Stephen’s next book might look like, what it’s like to make predictions that go against what the big firms are saying, why listening is one of the most important skills in business, and more.
Sid Rao is the GM of Amazon Chime, AWS’ communications platform for voice and video calls. Prior to joining AWS, Sid worked at CTI Group, serving as the company’s CTO for a decade before joining its board of directors. Over the years, Sid’s worn many other hats, including working as a consultant for DaVinci Capital and a program manager at Microsoft. He was also the founder and vice president of R&D at I/O Medical Systems, makers of a device that could acquire multiple physiological indicators using a tablet device.
Join Corey and Sid as they discuss the newly announced Amazon Chime and Slack and partnership and what it means for virtual meetings, where the optimal place to host a video meeting between a user in New York City and a user in Taiwan is, how chat becomes exceptionally difficult when you’re trying to scale to hundreds of thousands of users, how the Amazon Chime team responds to user feedback, how Amazon’s own usage of Chime doubled in recent months and Chime scaled without a hitch, why the Chime team focused on and perfected the app’s plumbing first and how it’s now shifting its attention to polishing the porcelain, why the Chime interface displays a region label, what Sid thinks the number one misunderstanding about Chime is, and more.
Jeff Sandquist is the corporate vice president of developer relations at Microsoft, a place he’s called home for more than 20 years of his career. Other positions he’s held there include senior director of developer product management, senior director of developer relations, and general manager of the cloud and enterprise group. In 2013, Jeff left Microsoft for an 18-month stint at Twitter, where he was the company’s global director of developer and platform relations.
Join Corey and Jeff as they discuss what Jeff does at the helm of Microsoft’s developer relations group, how Microsoft defines “developer relations,” the critical role docs play in developer success, how Microsoft was able to seamlessly transition Build into a fully remote event during the COVID-19 pandemic, how successful documentation is more of a lifestyle than an initiative, how Microsoft writes docs before they write code, the one thing that makes Microsoft tick, Microsoft Teams’ 776% growth in daily active users, and more.
Colin Percival is the founder of Tarsnap, a secure online backup service. He’s also an AWS community hero. For the last 16 years, Colin has contributed to the FreeBSD project, and he led efforts to bring FreeBSD to EC2. An alumnus of Simon Fraser University, Colin has a D.Phil. in computer science from the University of Oxford.
Join Corey and Colin as they discuss what FreeBSD is, why Colin started using it in the first place, how Colin is responsible for getting FreeBSD working on EC2 in the early days, how FreeBSD’s generous open source license raises other issues, what’s changed about communicating with AWS over the last several years, how Colin’s company Tarsnap makes online backups for the “truly paranoid,” how Colin turned down a job offer from Google to start his own company, what Colin’s AWS architecture looks like, why Colin doesn’t care if Tarsnap never becomes a publicly traded company, and more.
Prashanth Chandrasekar is the CEO of Stack Overflow who’s tasked with driving the company’s overall strategic direction and results. Prior to this role, Prashanth worked for Rackspace for seven years, rising to Senior VP & GM of the company’s cloud and infrastructure business. He’s also worked for Barclays Investment Bank, Zephyr Management LP, and Capgemini. Prashanth is a member of the board of trustees for the World Affairs Council of San Francisco and holds a B.S. in computer engineering from the University of Maine, a master’s in engineering and engineering management from Cornell, and a MBA from Harvard Business School.
Join Corey and Prashanth as they discuss Prashanth’s tenure at Rackspace and how the company redefined itself in the competitive cloud era, how Stack Overflow has an incredible foundation of support that most companies dream of, how the company has helped developers around the world build the cloud, what Stack Overflow is focused on in 2020 and beyond, how the company is trying to make newcomers feel more welcome, how diversity and inclusion is a top priority for Stack Overflow and initiatives they’re working on in that arena, how Stack Overflow is a bona fide SaaS business, and more.
Bryan Liles is a senior staff engineer at VMware who leads the developer experience group, which focuses on improving Kubernetes productivity. Previously, Bryan worked as an engineer at Heptio, served as the director of Capital One’s cloud engineering team, worked as a cloud engineer at DigitalOcean, and was the CTO at Thunderbolt Labs, among other positions.
Join Corey and Bryan as the explore what it’s like to be on the VMware engineering team, why Bryan spends a lot of his time conducting research, what Corey think the future of Kubernetes looks like and why Bryan agrees, why Twitter’s DM feature leaves much to be desired, what VMware is focusing on over the coming months and years, what Corey’s recipe for the best jokes looks like, how Bryan is focused on being “forever positive” and his advice for other people on taking control of their futures, how Bryan got fired from his first two jobs and what he learned from those experiences, and more.
Jill Rouleau is a senior software engineer at Red Hat Ansible who maintains AWS and other cloud modules. Prior to working on Ansible, they worked as an OpenStack engineer on TripleO, an OpenStack deployment project. Over the years, Jill also worked as a cloud reliability engineer at Canonical Ltd.; was the owner of Bespoke Software Solutions, a consultancy specializing in open source, cloud, and emerging technologies; and served as an operations engineer for Limelight Networks.
Join Corey and Jill as they discuss what it’s like to be on the Ansible engineering team, what Jill thinks about various programming languages, including Python, YAML, and XML, how familiarity with languages can help accelerate open source adoption and contributions, what Jill does to encourage first-time open source contributors to stick around, how answering the what can I do to help? question can be tricky, what Ansible is doing to increase contributions in the future, Jill’s advice on what you can do to start a career in tech, why diversity in experience and backgrounds is critical for tech companies, and more.
Jeffery Smith is the director of production operations at Centro. Over the course of his 20-year career, Jeffery has held a number of technology roles. Prior to joining Centro, he worked at Grubhub as a site reliability engineer manager, a senior systems engineer, and a system admin. Before that, Jeffery also worked for Wolters Kluwer as a website support analyst and for Instant Technology as a Windows/Solaris administrator, among other positions.
Join Corey and Jeffery as the discuss the inspiration behind Jeff’s book, Operational Anti-Patterns with DevOps Solutions, why Jeff believes that change management is one of the biggest anti-patterns that can be found across a lot of organizations, how automation can help optimize change management initiatives, why Corey thinks consultants are incapable of changing company cultures despite what many of them might say, why it’s impossible to learn from the fabled “perfect story,” why no one in an audience should ever leave a conference talk feeling crappy, what Jeff’s book-writing experience was like, and more.
Yulan Lin is a former developer advocate for Google’s Data Studio, a position she held for the two-plus years, and has since gone on to become a software engineer for Google Chrome. Prior to joining Google, Yulan worked as a software engineer for Valador Inc. at the Johnson Space Center in Houston. She also served as a registration analyst for the InterVarsity Christian Fellowship and was a self-employed musician for a bit, working as an accompanist, voice coach, and assistant choir conductor.
Join Corey and Yulan as they discuss how Yulan went from studying chemistry and researching bioinformatics to becoming a developer advocate at Google and a self-described data nerd, how organizations tend to be good at collecting data but not always at making sense of it, why the definition of “big data” changes from one use case to the next, what Google’s Data Studio is and how it supports data visualization, what Yulan does in her developer advocacy role, how data visualizations change depending on the audience, some of the most egregious examples of misusing data visualizations, and more.
Hiro Nishimura is the founder of AWS Newbies, a company that helps newcomers to AWS learn the ropes. She’s also the CEO of 24 Villages, an edtech consulting company, and a technical course instructor at LinkedIn. Prior to these roles, Hiro worked as a system admin and a technical services engineer at Intersection Co., an IT support analyst at Citrin Cooperman, and an IT help desk engineer at CAC American Corporation.
Join Corey and Hiro as they discuss the origin story of AWS Newbies, how it’s hard for any newcomer to get up to speed on AWS quickly, how starting a blog led Hiro to an opportunity to work with LinkedIn, why jargon and acronyms aren’t really that helpful for communicating with most people, how making content more accessible increases audience-wide engagement, why Corey thinks that explaining something to a novice can help you learn more than talking to an expert about the same topic, what made Hiro decide to go out on her own instead of joining a cloud education company, using Twitter to get business, how Hiro is overcoming health issues as an entrepreneur, and more.
Known as xssfox online, Michael is a developer from Australia who recently released Big Buck AWS, a tool that exploits code vulnerabilities to enable users to host up to 75 gigs of data in AWS for free.
Join Corey and Michael as they discuss why Michael is a “code terrorist,” how to get 75 gigs of free storage in AWS with a tool called Big Buck AWS, how AWS might potentially shut this loophole down or why they might end up deciding to let it roll, what inspired Michael to even tinker with this idea in the first place, how Michael looks at each new AWS service and tries to push their limit, why Michael hopes nobody is actually using Big Buck AWS in production, ideas for other tools like this, and more.
Sandy Carter is VP of Partners and Programs at Amazon Web Services. In her spare time, she also serves as an adjunct professor at Carnegie Mellon University Silicon Valley, an advisory board member for the IoT Community, a strategic advisor for SmartVizX and Betagig, and Chairman of the Board for Girls in Tech, Inc. Prior to wearing this many hats at once, Sandy served as a General Manager and CMO at IBM, Chief Sales Officer & Evangelist at Lotus Software, and CEO at Silicon Blitz.
Join Corey and Sandy as they discuss the journey that led Sandy from running AWS’ Windows operations to becoming VP of Public Sector Partners and Programs, how AWS’ customer-centricity drives the company forward, the day Michael Jordan and Stacey King combined to score 70 points, the secret sauce that leads to AWS products being adopted rapidly, how satisfying it is to help large companies migrate from legacy infrastructure to the “new world” of the cloud, why Sandy loves mentoring women in tech, the importance of diversity and inclusion and what it really means, and more.
Ben Sigelman is the CEO and co-founder of LightStep, makers of tools that deliver observability at scale for modern applications. Prior to that, he served as a mentor and advisor for Code for America and an advisor for Librato, Inc. He also worked at Google as a senior staff software engineer for more than nine years where he co-created Dapper.
Join Corey and Ben as they discuss the journey that led Ben to co-founding LightStep, including what it was like to be “born” at Google and help build Dapper, what Ben believes the point of distributed tracing is, why Ben is not a fan of Facebook, what it was like building a social network for depressed introverts, why building enterprise software is more validating that building a social network, what it’s like being involved with the OpenTelemetry project, and more.
Farrah Campbell is the Ecosystems Director at Stackery, a software company that builds tools that support and accelerate the development and delivery of serverless applications. She also serves as the speaker liaison and runs business development for TechfestNW, a conference that brings business leaders, innovators, and entrepreneurs together to talk all things tech. Previously, Farrah worked in customer and people ops at Reflect Technologies and as director of operations at Chirpify.
Join Corey and Farrah as they discuss career advice Farrah got from Kara Swisher, what an AWS Serverless Hero is and what it’s like to be one, what Corey’s done to earn the AWS Villain moniker, Farrah’s experience as a single mom raising two kids and the mindset that comes with it, what evangelizing for a new technology really means, how serverless is a mindset, an innovation strategy, and a paradigm shift, how to use Route 53 as a database, and more.
Tobi Knaup is the co-founder and CTO of D2iQ, an enterprise-grade cloud platform provider that helps customers build cloud-native applications. In his spare time, he doubles as continuity advisor at Y Combinator. Previously, Tobi worked as a tech lead at Airbnb, signing on as the fourth engineer and helping scale the company’s product to millions of users around the world. He also co-founded Knaup Multimedia, a company that built websites for small- and medium-sized businesses, when he was 15.
Join Corey and Tobi as they discuss why Mesosphere rebranded as D2iQ and what that new name means; why the Kubernetes community deserves the credit for the widespread adoption of the container orchestration platform; how D2iQ helps customers build end-to-end data pipelines with tools like Kafka, Cassandra, and Spark; how D2iQ solves one industrial IoT use case with a mini edge cloud; how many people assume Kubernetes is all they need, why that’s a mistake, and what other tools they end up having to use; why Tobi thinks that multi-cloud is the future; what it was like for Tobi to grow up in Germany and hear about Silicon Valley; joining Airbnb as the company’s fourth engineer; and more.
Gene Kim is an author who writes about topics like DevOps and the digital age. His works include The Phoenix Project, The Unicorn Project, and The DevOps Handbook. Prior to picking up a pen, Gene served as CTO and founder of Tripwire, was the founder and director of research at IT Process Institute, and worked as an independent director of the Energy Sector Security Consortium in Portland, Oregon. He’s also the founder of the DevOps Enterprise Summit.
Join Corey and Gene as they discuss what it was like to revisit the Parts Unlimited world for The Unicorn Project, where Corey stands on the should I stick around or should I leave the company spectrum, the Five Ideals, how Corey helped Gene zero in on his core audience for The Unicorn Project, what Gene admires about the DevOps Enterprise Summit community, the tremendous impact that Gene believes the DevOps community will have on the future, and more.
Jeremy Bowers is the Director of Engineering at the Washington Post who’s currently leading a team that’s focused on the 2020 presidential election. Prior to joining the Post, Jeremy held many other news-focused roles, including working at the New York Times as a senior editors for news applications and a senior software engineer; serving as a news applications developer at NPR, and wearing many hats at the Tampa Bay Times, including news technologist and online operations specialist.
Join Corey and Jeremy as they explore the common engineering dilemmas newsrooms face, how data visualizations in newspapers have evolved over the centuries, how the Washington Post uses data to examine trends and test hypotheses—like whether Texas will become a blue state in the next election, what the hardest part about bringing data to the surface in a newsroom is (hint: it’s not data ingestion or cleanup), how a lot of reporting is the same as it was 30 or even 40 years ago, why Jeremy thinks reporters won’t be replaced by robots, how newsroom technology has evolved over the last decade, and more.
Join Corey and Kelsey as they explore the journey that led Kelsey to Kubernetes; where Corey feels Kubernetes falls short; how Kubernetes is just another step in the evolution of technology, with more to follow in the future; why Corey used to argue against the cloud; why Kelsey believes Kubernetes makes hyperspecialization worthwhile; Kelsey’s general feelings about multi-cloud; what Kelsey believes is the biggest thing that’s misunderstood about Kubernetes; what the future of Kubernetes looks like; and more.
Rob Zuber is the CTO of CircleCI, makers of a full-service CI/CD platform. Before that, he co-founded Copious, a social marketplace built around people and their interests, and Yoohoot, a mobile advertising company that was acquired by Appconomy. He also served as VP and chief mobile strategist at Critical Path, CTO at AdPerk, VP of business development at Kobo, and an instructor at Marakana, among other positions.
Join Corey and Rob as they discuss the ins and outs of continuous integration and continuous delivery and touch upon why it’s hard to scale CI/CD, why many companies end up focusing on what’s called undifferentiated heavy lifting and why that’s a bad thing, what keeps AWS awake at night (hint: something to do with money), why at the end of the day, it’s all about the product, how developer relations is really a marketing endeavor, how CircleCI is a team of engineers solving problems for another team of engineers, why distributed teams are becoming the norm, and more.
Andreas Wittig is an author, entrepreneur, and AWS cloud architect and software engineer at widdix, a tech firm based in Germany. He’s also a senior consultant at tecRacer who focuses on AWS. Andreas recently co-wrote Amazon Web Services in Action with his brother, Michael, and together they run cloudonaut.io, an AWS-focused consultancy. Among other career highlights, Andreas once migrated the complete IT infrastructure of a leading German bank to AWS.
Join Corey and Andreas as they discuss both of their journeys to AWS, how Andreas gets his ideas for AWS-inspired content, why Andreas thinks Fargate is a great tool for deploying applications on AWS—and why it’s even better than Lambda in some instances, the inspiration behind the Wittig brother’s new book, the two promises of Global Accelerator and when the tool is particularly valuable, additional AWS services Andreas believes don’t get enough attention, the concept of “infrastructure bootstrapping,” and more.
Thomas Hazel is CTO and founder of CHAOSSEARCH, a powerful search and analytics platform for AWS that’s backed by S3 as a data store. He’s also an official member of the Forbes Technology Council, a hall of fame member at the University of New Hampshire, and advisor to ecoText, Inc. Previously, Thomas founded the Deep Software Foundation, served as chief architect for algorithms at Akiban Technologies, and worked as lead architect of Oracle VM, among other positions.
Join Corey and Thomas as they discuss the journey that led Thomas to CHAOSSEARCH, why the company has the name it has, what Corey likes about the CHAOSSEARCH approach, why Corey believes oftentimes you need to “start kidnapping princesses” in order to pay for log analytics, use cases when Thomas thinks Elasticsearch could be a better option than CHAOSSEARCH, the features CHAOSSEARCH is currently working on adding to its platform, why CHAOSSEARCH is in ALL CAPS, what the company has in the hopper for 2020, and more.
Join Corey and Dai as they explore the world of tech reporting and Dai’s recent article on AWS in particular while touching on a number of topics, including how AWS evolved from a platform everyone built on top of to one that runs everything built on top of it, why it’s incredibly difficult to capture all the nuances of the world of open source in a single article, the collaborative nature of writing the news, how a journalist can tell when they’ve written a story that doesn’t have mistakes, why Amazon as a trillion-dollar company should expect more scrutiny, what it was like to try to get people to go on the record talking about AWS, and more.
Leon Adato is a head geek and technical evangelist at SolarWinds, a software company that delivers affordable IT infrastructure management solutions. He’s also the founder and operator of AdatoSystems, a provider of low-cost web solutions. Leon has nearly three decades worth of experience in the tech world, having worn all kinds of IT-related hats for companies like Nestle, PNC Financial Services Group, and Cardinal Health.
Join Corey and Leon as they explore the fabled world of on-premises data centers and touch upon a number of topics, including how the world of IT has evolved over the last 30 years, Leon’s mindset on monitoring,the lone genius’ IT domination in the ‘90s, how the perception of IT has changed over the last several years, the path Leon took from a degree in theater to a career in IT, Corey’s musings on the configuration management wars, the concept of “technical empathy,” why you always need to be ready to pivot, how what you learn today bleeds into what you need to know tomorrow, and more.
Adam Jacob co-founded Chef Software and created Chef, a platform that helps DevOps teams ship software faster. Though he still serves on Chef’s board, Adam has a new role these days: serving as CEO and co-founder of a new startup called The System Initiative. For more than a decade, Adam has been designing, building, and managing large production systems. He has more than 20 years of experience working in tech.
Join Corey and Adam as they explore the pros and cons of taking venture capital, why Adam believes VC money unfairly gets a bad rep, how great 1Password is and why Adam believes the company’s $200 million raise makes sense, when to take VC money and when to turn it down, how expanding from a tool that performs a specific function to a platform business can be a scary thing for end users, how not all VCs are alike, how “bad founders” exist, why the people who tend to dislike venture capitalists usually aren’t the ones making the tough decisions, and more.
Jessie Frazelle, Steve Tuck, and Bryan Cantrill founded the Oxide Computer Company. They’re building a rack-scale server design to deliver cloud hyperscale innovations around density, efficiency, cost, reliability, manageability, and security to everyone running on-premises compute infrastructure.
Join Corey, Jessie, Steve, and Bryan as they discuss how and why a lot of companies still run on-premises infrastructure in the cloud era; the last time Corey bought a box; what happens when you rely on myriad vendors for your hardware and software needs; why two-person startups should start in the cloud and when they should move on-prem; how if the cloud is renting a hotel, on-prem is owning a house; musings on tech and sustainability; how the cloud is not a panacea; the current status of Moore’s law; and more.
Rachel Stephens has worked as an analyst at RedMonk, a firm focused on software developers, for the last four years. Prior to that, she held several other analyst positions for companies like Western Union, Dish Network, Frontier Airlines, and LaSalle Investment Management. She’s also volunteered as a grant writer and mentor for Minds Matter, a nonprofit that helps students from low-income families.
Join Corey and Rachel as they discuss what an analyst firm actually is, how RedMonk helps companies understand the link between developer preferences and business strategy, the disconnect between financial and engineering departments and how to bridge the gap, how finance has become more interested in the way IT costs come together, why engineers don’t like being referred to as IT people, why finance isn’t always keen on digital transformation initiatives, how engineers aren’t always interested in making money or generating revenue, Rachel’s number one recommendation for effective financial controls in engineering, and more.
Pete Cheslock is an advisor and consultant who helps startups with product strategy, messaging, and other go-to-market needs. Prior to going out on his own, he worked at a slew of tech companies, holding positions such as VP of Products at CHAOSSEARCH, VP of Technical Operations at Threat Stack, Inc., Director of DevTools at Dyn, and Director of Technical and Cloud Operations at Sonian. Pete holds a master's in business administration from Babson and a bachelor's in communications from Michigan State University.
Join Corey and Pete as they discuss the differences between CHAOSSEARCH and Elasticsearch, proper etiquette for the conference badge-scanning experience, how tech can be a bubble and not everyone might know the tools you do, the increasingly prominent roles artificial intelligence and machine learning play in the AWS ecosystem, why the re:Invent experience is like a marathon, what it’s like listening to a talk on a pair of headphones, which re:Invent announcement made the least waves, why diversity amongst chip manufacturers is a good thing, and more.
Chloe Condon is a senior cloud advocate at Microsoft, where she evangelizes on behalf of Azure. Prior to that, she held developer evangelist roles at companies like Sentry and Codefresh. She’s also a freelance writer and has performed in over 30 musicals in the Bay Area, in theaters large and small (50 seats to 4,000 seats). Chloe, who holds a degree in theatre performance from San Francisco State University, is also a graduate of Hackbright Academy, a highly selective accelerated software development program.
Join Corey and Chloe as they discuss what it’s like to be a developer advocate, why Chloe built a fake boyfriend alert and how she got a retweet from Smash Mouth, the importance of making the cloud “fun,” what it was like to leave an industry dominated by women and join one dominated by men, how the tech industry stands to benefit from outside perspectives (e.g., stage managers and sommeliers), the role Chloe played in the resurgence of Clippy, and more.
Cody Ogden is the founder of Killed by Google, an open source project that tracks the life and death of Google’s product portfolio. He’s also a software engineer at CannabizMedia and a founding partner at Rocket Squirrel, a company that specializes in delivering exemplary user experiences.
Join Corey and Cody as they explore everything there is to know about the life and death of products like Google Reader and Hire by Google, why companies might want to think twice about relying on the G Suite platform, how “long-term” means different things to different people, the fate of Fitbit, what happens when Google and AWS decide to decommission products, the rise of Alphabet and what it means for certain Google brands, how Google and Amazon’s customer service offerings stack up, and more.
Russ Savage is the product manager at InfluxData, makers of InfluxDB, the open source time series database. Prior to holding that position, Russ wore many hats in the tech industry, including working as an application engineering team lead at Cask Data, a systems architect at Elastic, a marketing engineer at Box, and a product manager at Orbitz.
Join Corey and Russ as they discuss how the evolution of computing power is rendering Hadoop irrelevant, what it’s like selling open source software, what it means to be a “true” open source company, the important role community engagement plays in open source projects, the pros and cons of mutli-cloud, why you might want to monitor events at the nanosecond level, the best use cases for time series data, how time series databases have evolved over time, and more.
Since 1996, Tiffany Farriss has been one of the driving forces behind Palantir.net, an open-source powered web design and development firm she co-owns and currently serves as CEO. From 2009 to 2017, she also sat on the Board of Directors of Drupal, a popular open-source content management system. Prior to that, Tiffany held similar advisory roles at AIGA Chicago and Northwestern Student Holdings.
Join Corey and Tiffany as they discuss how to build stronger open source communities; Tolkien, Snow Crash, and Ender’s Game; why companies have several different levels of obligations for giving back to open source projects; why it’s hard for companies that build products on top of open-source tools to be incentivized to give back; the history of Drupal; Usenet and rise of Eternal September; Slack vs. IRC and losing the open-source mentality; succession planning in open source projects; and more.
Sasha Rosenbaum began her career working as an IT systems administrator for the Israel Air Force. Shen then took a position as an R&D software engineer at Elbit Systems, an Israeli-based aerospace company, before joining 10th Magnitude, an IT services company based in Chicago. Over the last four years, she’s held several positions at Microsoft. Currently, she’s the senior program manager for the Azure DevOps engineering team.
Join Corey and Sasha as they explore what being a senior program manager for the Azure DevOps engineering team entails, what the relationship become Azure DevOps and GitHub looks like, what happens when a company sells two competing products, how building Azure DevOps on Azure DevOps results in a stronger product, the pros and cons of open-source software, when to use SaaS tools and when to build from scratch, how attending conferences strategically can eliminate many life expenses, and more.
Tanya Janca began her career as a software developer at Canadian Bank Note before holding the same role for the Canadian government for nearly 10 years. She then shifted her focus to application and IT security for the government before joining Microsoft as a senior cloud advocate specializing in application security. Today, she’s the CEO and co-founder of Security Sidekick, a company that helps developers create secure applications.
Join Corey and Tanya as they discuss what it’s like to work at Microsoft and how putting in two years there is like putting in 1,000 years somewhere else, how Security Sidekick takes 48 hours to do what a consultant does in a year or more, the challenges that stem from multi-cloud environments, how SaaS tools are improving everything—including the massage space, how Superman inspires Tanya, effective altruism, and more.
For 15 years, Josh Doody held several different software engineering roles at companies like Raytheon, ADP, and Appirio. Today, he owns a consultancy called Fearless Salary Negotiation and helps software developers get paid what the market commands.
Join Corey and Josh as they discuss how software developers can get paid more, what the current tech job market looks like, when devs should start thinking about compensation in their next roles, when salary negotiations actually begin, why the goal of a negotiation isn’t always about getting more money, the biggest mistakes people make in negotiations, and more.
Paul Dix is the cofounder and CTO at InfluxDB, makers of an open source time-series database. Over the last 20-plus years, he’s held technology, consultant, and leadership positions at companies like Microsoft, McAfee, Google, and Thomson Reuters.
Join Corey and Paul as they discuss everything there is to discuss about time-series databases, the two different kinds of time-series events, the importance of timing when launching a product, how to build applications on top of time-series data, creating a new programming language (Flux), why you should create new programming languages when it makes sense, and more.
Paul Chin Jr. grew up using egg rolls to gauge profitability at his parents’ Chinese restaurant in Norfolk, Va. Today, he’s a cloud solutions architect at Cloudreach and a strong proponent of cloud, serverless, and open source technologies—and also a prophet of Nicolas Cage, a national treasure.
Join Corey and Paul as they face off with plenty of time to kill and cover many topics related to severless and cloud technologies, including how software can be an army of one for any business; how popular tools can be gone in 60 seconds as new solutions emerge while slower-moving businesses are left behind with legacy systems; how Paul solves customer problems through understanding and adaptation; and how severless means everyone can build computer programs—without computer science training, either. Don’t think so? It happened to Paul. It could happen to you—and even the weather man—too.
Paul Johnston cares a great deal about climate change and believes the tech world needs to do more. He’s the interim CTO for cloud and serverless consulting and technology strategy services at Roundabout Labs, a company he founded and served as CEO for eight years before joining AWS as a senior developer advocate for serverless. Join Corey and Paul as they discuss the early days of being a developer advocate for AWS for serverless, how data centers and cloud computing are impacting climate change, why you shouldn’t run workloads in us-east-1, why cryptocurrency is bad for the environment, and more.
Nicole Forsgren grew up in a small farm town in Idaho. After working as a programmer, a software engineer, and a systems administrator at IBM, she went back to school to get her PhD in Management Information Systems. Now, she leads research and strategy at Google and oversees the production of the annual State of DevOps Report. Join Corey and Nicole as they discuss what the cloud is, how people define it and why we need a common definition for it, which organizations benefit from the cloud, why it’s largely time to ditch in-house tools, and more.
Andrew Peterson launched his career working in sales at North Face. After stints at Google, the Clinton Foundation, and Etsy, he launched his own company—Signal Sciences—makers of a next-gen WAF and RASP web application protection solution that detects and stops attacks wherever applications run. Join Corey and Andrew as they explore why Signal Sciences is an “accidental” security vendor, why security is no longer solely about preventing breaches but increasingly about responding to them quickly and effectively, how organizations are taking a more proactive approach to security and privacy in the GDPR era, and more.
AJ Stuyvenberg began his career writing software for St. Jude Medical. Today, he’s a senior software engineer at Serverless, Inc., makers of the increasingly popular open source Serverless framework designed to make it easier to deploy applications across cloud vendors.
Join Corey and AJ as they discuss what a day in the life of an engineer at Serverless looks like, what the Serverless framework actually is and how it helps developers, how an open source company makes money, how Serverless differentiated itself from AWS, the differences between Serverless plugins and components, what’s in the company’s future, and more.
Cloud security makes Josh Stella tick. In 2013, he founded Fugue, a company that brings native security and simplified operations to cloud architecture. Join Corey and Josh as they discuss why Fugue is called Fugue, how the approach hackers take has changed in recent years, why cloud security is actually more of a physics and biology problem than a technology problem, the recent Capital One data breach, how it likely happened, why the bank didn’t necessarily do anything wrong, why cloud security should be automated, and more.
For the last five years, Matt Broberg has worn many different developer advocate hats. These days, his developer hat looks a bit … red ... as he’s an advocate, writer, and editor for opensource.com at Red Hat. Join Corey and Matt as they discuss IBM’s recent acquisition of Red Hat, open source culture and how to contribute without submitting code, the rise of developer relations and whether the term “DevRel” will stick, what developer relations actually is, what its future looks like, and more.
Nicole Forsgren grew up in a small farm town in Idaho. After working as a programmer, a software engineer, and a systems administrator at IBM, she went back to school to get her PhD in Management Information Systems. Now, she leads research and strategy at Google and oversees the production of the annual State of DevOps Report. Join Corey and Nicole as they discuss what it’s like to put together said reports, why people are so passionate about their DevOps team’s unique approach, the four metrics you can use to grade DevOps teams, how to scale DevOps teams, and more.
Be honest: How many people decide to launch a weekly podcast actually end up publishing hundreds upon hundreds of episodes? Richard Campbell, founder and chairman of the Humanitarian Toolbox and host of RunAsRadio podcast, is someone who actually did. Join Corey and Richard as they talk about what it’s like to host 1,650-plus podcast episodes, building open source tools for disaster relief, moving away from legacy tech, the power of admitting you don’t understand something, how snarkiness often gets lost in translation, the thanklessness of good IT, and more.
Supercomputers used to be gigantic monstrosities that would take up enormous rooms. Now, you can run them in the cloud. Just ask Mike Warren, CTO and co-founder of Descartes Labs, a company that provides Earth imagery to help folks understand planetary changes—like deforestation, water cycles, agriculture, and more. Join Corey and Mike as they discuss what it’s like to build supercomputers on top of AWS and how “easy” it is, the power of Amazon’s Spot blocks, building Beowulf clusters in the ‘90s, what Descartes Labs’ platform-agnostic infrastructure looks like (spoiler alert: nothing is on-prem), how AWS accelerates the development process, petaflop machines, the evolution of high-performance computing over the last few decades, and more.
Another week, another high-profile data breach. Well, that’s what it seems like anyway. As Director of Cyber Risk Research at UpGuard, Chris Vickery knows a thing or two about why these breaches are occurring—and what organizations can do to minimize the likelihood they do. Join Corey and Chris as they talk about why so many companies leave S3 buckets publicly exposed, raising the bar of low-hanging fruit for data security, why organizations can’t blame third parties for breaches, why AWS isn’t liable for everything that goes wrong in the cloud, the recent Capital One breach, and more.
Microsoft has undergone a major transformation over the last several years. Just ask Tara Walker, principal software engineer, who recently rejoined the company after a four-year hiatus at AWS. Join Corey and Tara as they talk about this transformation, why the world of IoT gets more exciting every day, what Microsoft is focused on today, why Tara is now pursuing a master’s degree at Georgia Tech, and much more.
For two decades, Custom Ink has helped folks around the world create unique T-shirts, jackets, activewear, promotional products, and more. Today, the company has hundreds of applications and services in the cloud. But their infrastructure didn’t always look like that. Join Corey as he talks with Ken Collins, a staff engineer at Custom Ink, about the value of AWS certification, moving the Custom Ink’s monolithic Rails apps to AWS Lambda and EC2, why they still love Ruby, what technologies they’re eying for the future, and how and why they’re transforming into a cloud-native shop.
Azure Sphere is Microsoft’s push into Internet of Things security, promising lifetime security updates and more. In this episode, Dr. Galen Hunt explains why Azure Sphere is so important to device manufacturers, and gives some examples of real-world uses.
Before she held her current role as senior cloud advocate at Microsoft, Christina Warren was a self-proclaimed “content engineer.” These days, who follows a traditional career path anyway? Tune in to hear Corey and Christina discuss how to give killer conference talks, what it means to be a developer advocate, what the next generation of cloud developers looks like, why grizzled IT veterans shouldn’t be wary of moving to the cloud, and more
HashiCorp has embraced the multi-cloud, and in this episode, Corey asks Founder and CTO Mitchell Hashimoto to explain how that’s working out. From Terraform’s humble beginnings to the answer to “why HCL?” Hashimoto explains what makes HashiCorp tick, and why it continues to do so.
VMware is shifting its business as more companies move code to the cloud. What does that mean for the company internally? In this episode, Corey gets an inside view of this shift and discusses some recent acquisitions the company has made to change its business model.
Another chat with another Corey but this time Corey Sanders has a shiny new title: Corporate VP of Microsoft Solutions. In this episode the two Coreys discuss the Microsoft mission statement, more real-world Azure examples, and why “vendor lock in” is both simpler yet more complicated today than ever.
Serverless deployment is picking up steam in the industry, and Austen Collins has been leading the charge since 2015. In this episode, Collins talks about his work with AWS, building the Serverless Framework, and why it’s solving so many problems.
Emily Freeman’s book on DevOps is an approachable read for all types, not just techies. As DevOps for Dummies is set to hit the shelves, she sat down to talk to Corey about the process of writing a book, what she learned during that process, and how teams of all types can learn from her insights on management.
Anna Spysz offers a different perspective, coming from communications first and engineering second. In this episode, she describes the hybrid model employed at Stackery for developing cloud applications that can save time and frustration, plus she’s got a few tips for liberal arts majors looking to get into tech.
Scott Guthrie shares his experiences at Microsoft as the company has shifted its strategy and corporate culture. He answers questions about Azure, working with partners, and why Microsoft’s customer-first focus has led to multiple learnings across the organization. There are few people with such a perspective in the industry, and Guthrie provides key insights for those looking at cloud solutions, or anyone considering migrating from on-premises to cloud architecture.
There are a lot of choices for managing and encrypting secrets in Kubernetes. Kamus is one of those solutions, and it was developed as an open-source project by Omer Levi Hevroni.
Today we’re talking with Omer, a DevSecOps engineer with Soluto at Asurion, about his work on Kamus, its origins, and how it’s being applied for secrets management in Kubernetes.
Amazon’s AWS offers a tantalizing range of services at incredible prices. While not a panacea to all your cloud computing needs, it’s definitely risen fast to become a critical piece of the pie for many companies looking to scale up quickly. Valentino Volonghi is CTO of AdRoll, who uses AWS extensively. In this episode, Volonghi relates his years of experience with AWS, and all its growing pains. Today? There’s a lot of magic in S3 as well, and Volonghi explains how AdRoll leverages this magic.
In the same way that the cloud can be incredibly helpful, it can also be the source of a few headaches. Just like the printing press, technology can help eliminate the arduous parts of our jobs and help create new specialties. But it doesn’t mean that we have the golden ticket.
Today we are talking to Cloud Data Engineer, Richard Boyd, of iRobot about the perils of getting services to talk to each other and keeping your career flexible in the ever-evolving tech world.
Today, data service is becoming more like a utility and that affects the expectations and practical uses of the cloud in almost every form.
Today we are talking to Richard Hartmann about the logistics of serverless infrastructure from how data centers are built to how the cloud is kind of just more of the same in the technology world.
While cloud architecture has many forms from container to serverless, the value of open source infrastructure never changes.
Today we talk to Jess Frazelle of Twitter fame about role of GitHub in the cloud and how open source is beneficial to the community. Even though the way the cloud if built might change, open source will always be important to the growth of developers as well as the industry.
While a valuable investment, the value of AWS training is still not always well understood. With a library of free digital training and a variety of certifications validating baseline as well as more specific expertise, there are many reasons to look at investing the Amazon’s training program.
Today, we are talking to Maureen Lonergan who works hard to bring value to the training programs for AWS and doesn’t take your time and investment in their cloud services for granted.
What if every time you washed your dishes, your dishwasher got smarter? Now imagine your dishwasher getting smarter every time someone else washed their dishes.
Today, we are talking to Roger Barga, the General Manager of AWS Robotics. We discuss the recent advances in robotic programming as well as the benefits of the cloud in commercial and domestic applications.
Today we are talking with Silvia Botros, Principal Engineer at SendGrid. They specialize in email marketing that is trusted by developers and marketers for time-savings, scalability, and delivery expertise. Our discussion centers around SendGrid’s migration to AWS and the unique career paths that the company has been evolving over the past several years.
The job market in the AWS world is complex and often confusing to both employers and employees. Wouldn’t it be great to have over 43,000 data points to draw a larger picture of the market and where you fall in line?
Today, we are talking to Kate Powers who walks us through the AWS Salary Survey from Jefferson Frank and discusses some interesting insights as well as real world examples of the findings.
Some of the highlights of the show include:
The AWS job market at large
Training Certificates: what’s their value
How much value is in a job title
Most desirable skills from employers
Gender representation in the industry
The discrepancy in compensation based on geography
Years ago, if you wanted to launch an Internet company or Web application, you had to own necessary hardware. Now, the economics have changed drastically with the ease of Cloud computing. It’s still a new industry that people are trying to figure out, especially when it comes to cost and optimization.
Today, we’re talking to Dann Berg, a Cloud ops analyst at Datadog. He helps others understand and lower the cost of Cloud operations. Dann is a detective who is dedicated to figuring out why a company’s Cloud bill is so high.
Some of the highlights of the show include:
Companies struggle with field of Cloud economics; can be overwhelming because there’s so much to learn about products and implementation
Companies use the Cloud to grow quickly, which makes their Cloud costs grow quickly and more than expected
Only access to full list of every resource being used is the Cloud bill; there’s no comprehensive inventory service available
Companies need to offer visibility to Cloud bill; not everyone has access to understand how their actions impact the bill
Cost of Cloud bill is dependant on different factors, including new features, new users, and cost of goods sold (COGS)
Scale and manage bill by using a platform app or hiring a consultant/team
Understand pricing of AWS and learn best practices for cost controls early on
Don’t leave money on the table by focusing on engineering time - not best use of resources; focus on the smallest things that have the biggest impact
Cost is important, but don’t slow down those developing in the Cloud; open lines of communication to create culture to understand cost, value what’s measured
Dann Berg on Twitter
If you use MongoDB, then you may be feeling ecstatic right now. Why? Amazon Web Services (AWS) just released DocumentDB with MongoDB compatibility. Users who switch from MongoDB to DocumentDB can expect improved speed, scalability, and availability.
Today, we’re talking to Shawn Bice, vice president of non-relational databases at AWS, and Rahul Pathak, general manager of big data, data lakes, and blockchain at AWS . They share AWS’ overall database strategy and how to choose the best tool for what you want to build.
Some of the highlights of the show include:
Database Categories: Relational, key value, document, graph, in memory, ledger, and time series
AWS database strategy is to have the most popular and best APIs to sustain functionality, performance, and scale
Many database tools are available; pick based on use case and access pattern
Product recommendations feature highly connected data - who do you know who bought what and when?
Analytics Architecture: Use S3 as data lake, put in data via open-data format, and run multiple analyses using preferred tool at the same time on the same data
AWS offers Quantum Ledger Database (QLDB) and Managed Blockchain to address use case and need for blockchain
Authenticity of data is a concern with traditional databases; consider a database tool or service that does not allow data to be changed
Lake Formation lets customers set up, build, and secure data lakes in less time
DocumentDB: Made as simple as possible to improve customer experience
AWS Culture: Awareness and recognition that it takes many to conceive, build, launch, and grow a product - acknowledge every participant, including customers
Amazon Quantum Ledger Database
Amazon Managed Blockchain
Amazon Lake Formation
Does operating system (OS) choice even matter anymore to most people? Especially with the emergence of serverless and containers? Debian may not see its name up in lights much these days, but it’s still very much front, center, and relevant to what people are doing in Cloud environments.
Today, we’re talking to Elana Hashman, a Python packager and Debian developer. Everything inside a base operating system may not be interesting to end users, but such a collection of components is necessary to create a functioning Linux system.
Some of the highlights of the show include:
Alternative Linux operating systems, including Amazon Linux 2
Level of awareness about free software when choosing and distributing an OS
What is a Python packager? How do you become one?
Python is the new default language due to growth and adoption of its ecosystem
Packaging community off-putting to beginners; find someone who understands the system to guide you
Elana Hashman on Twitter
Elana Hashman on Mastodon
A tale of three Debian build tools
Python Packaging Authority
The Debian Women Project
Amazon Linux 2
Jordan Sissel on Twitter
Companies can find working in the Cloud quite complicated. However, it’s a lot easier than it used to be, especially when trying to comply with regulations. That’s because Cloud providers have evolved and now offer more out-of-the-box services that focus on regulation requirements and compliance.
Today, we’re talking to Elliot Murphy. He’s the founder of Kindly Ops, which provides consulting advice to companies dealing with regulated workloads in the Cloud.
Some of the highlights of the show include:
Technical controls are easier, but requirements are stricter
Risk Analysis: Putting locks on things to thinking about risks to customers
Building governance and controls; making data available and removable
Secondary Losses: Scrub services to make scope and magnitude of loss smaller
Computing became ubiquitous and affordable; people started collecting data to utilize later - nobody gets rid of anything
General Data Protection Regulation (GDPR) set of regulations apply to marketing technology stacks to manage systems
Empathy building exercise and security culture diagnostic help companies understand compliance obligations
Security Culture: Beliefs and assumptions that drive decisions and actions
Evolution of understanding with public Cloud’s security and availability
Raise the bar and shift mindset from pure prevention to early detection/ mitigation; follow FAIR (factor analysis of information risk)
Amazon Web Services (AWS)
Relational Database Service (RDS)
Google Cloud Platform (GCP)
Nist Cybersecurity Framework
People-Centric Security by Lance Hayden
Society of Information Risk Analysts (SIRA)
More and more enterprises and on-prem applications are moving to the Cloud. Therefore, flexibility, agility, time-to-market, and cost effectiveness need to be created to address a lack of visibility and control.
Today, we’re talking to Archana Kesavan, senior product marketing manager at ThousandEyes. The company offers a network intelligence platform that provides visibility to Internet-centric, SaaS, or Cloud-based enterprise environments. Our discussion focuses on ThousandEyes’ 2018 Public Cloud Performance Benchmark Report.
Some of the highlights of the show include:
Purpose of Report: Reveals network performance and architecture connectivity for Amazon Web Services (AWS), Google Cloud (GCP), and Microsoft Azure
Report gathered more than 160 million data points by leveraging ThousandEyes’ global fleet of agents that simulate users’ application traffic
Data collected during four-week period was ran through ThousandEyes’ global inference engine to identify trends and detect anomalies
Internet X factor when calibrating network performance of public Cloud providers; best-effort medium that has no predictability and is vulnerable to attacks
AWS’ performance predictability was lower than GCP Cloud and Azure leveraged their own backbones to move user traffic
Certain regions, such as Asia, were handled better by GCP and Azure than AWS
Customers should understand value of long-distance Internet latency when selecting a Cloud provider
Determine what the report’s data means for your business; conduct customized measurements for your environment
ThousandEyes on Twitter
2018 Public Cloud Performance Benchmark Report
Amazon Web Services (AWS)
AWS Global Accelerator for Availability and Performance
If you’re looking for older services at AWS, there really aren’t any. For example, Simple Storage Service (S3) has been with us since the beginning. It was the first publicly launched service that was quickly followed by Simple Queue Service (SQS). Still today, when it comes to these services, simplicity is key!
Today, we’re talking to Mai-Lan Tomsen Bukovec, vice president of S3 at AWS. Many people use S3 the same way that they have for years, such as for backups in the Cloud. However, others have taken S3 and ran with it to find a myriad of different use cases.
Some of the highlights of the show include:
Data: Where do I put it? What do I do with it?
S3 Select and Cross-Region Replication (CRR) make it easier and cheaper to use and manage data
Customer feedback drives AWS S3 price options and tiers
Using Glacier and S3 together for archive data storage; decisions and constraints that affect people’s use and storage of data
Feature requests should meet customers where they are, rather than having to invest in time and training
Different design patterns and best practices to use when building applications
Batch operations make it easier for customers to manage objects stored in S3
AWS considers compliance and retention when building features
Mentorship: Don’t be afraid of the bold ask
Do you have to deal with data protection? Do you usually mess it up? Some people think data protection architecture is broken and requires too many dependencies. By the time a business needs to backup a lot of data, it’s a complex problem to go back in time to retrofit a backup solution for an existing infrastructure.
Fortunately, Rubrik found a way to streamline data protection components. Today, we’re talking to Chris Wahl and Ken Hui of Rubrik.
Some of the highlights of the show include:
Transform backup and recovery to send data to a public Cloud and convert it to native format
Add value and expand what can be done with data - rather than let it sit idle
Easy way for customers to start putting data into the Cloud is to replace their tape environment; people hate tape infrastructure more than their backups
Necessity to backup virtual machines (VMs) probably won’t go away because of challenges; Clouds and computers break
Customers leaving the data center and exploring the Cloud to improve operations, utilize automation
Business requirements for data to have a level of durability and availability
People vs. Technology: Which is the bottleneck when it comes to backups?
Words of Wisdom: Establish an end goal and workflow/pathway to get there
Chris Wahl on Twitter
Chris Wahl on LinkedIn
Ken Hui on Twitter
Ken Hui on Medium
Amazon EC2 Instances
Azure Virtual Machine Instances
Do you have some spare time? Can you figure out an easier way to do something? Then, why not build some software?!
Today, we’re talking to Ian Mckay of Kablamo, an Amazon Web Services (AWS) consultancy. He is the author of Console Recorder, which is a browser extension that records your actions in the Management Console to convert them into SDK code and infrastructure as code templates.
Some of the highlights of the show include:
Timeline to build Console Recorder
Infrastructure as Code: How to code repeatedly without starting over and take ownership of what you built by hand
AWS vs. Individual Achievements: People asked AWS for years to create something to record console click-throughs that Ian did in his spare time
Console Recorder support for any browser that exports Web extensions
Sharp edges of what’s expected of Console Recorder to speed up development
Management Console’s unreadable responses require reverse engineering
Console Recorder: Recommended use cases and areas
How to alleviate security concerns with Console Recorder
Changes to Management Console that may break things
Ian’s past, present, and future projects and products
Words of Wisdom: If you don’t like something, just fix it yourself
Ian Mckay on Twitter
AWS Console Recorder
Google Cloud Platform
AWS Management Console
A Manager README is a document designed to establish clarity between a manager and those who report to them. These documents are especially useful for onboarding content. For example, if you have someone new starting on your team, there's so many things you need to share with them - pieces of advice and guidance that help them to make the best decision about what to do in specific situations. A Manager README sets some expectations in advance to make things easier and reduce friction and anxiety for team members.
Today, we’re talking to Matt Newkirk, who manages Etsy’s localization and translation group. He explains that even if your company has an intensive onboarding program and review process, some things are still left out. A Manager README is a helpful and proactive piece of content that prompts conversations about how people perceive things.
Some of the highlights of the show include:
Avoid writing READMEs that are extremely self-centered/arrogant
READMEs clarify what to do until a relationship is established between the manager and their employee
Get feedback early on to make sure that what you include in the document is helpful; it should reflect reality and be discussed
Share README with your manager to make sure you’re both on the same page about team philosophies and expectations
README is a living document that needs to be updated occasionally because things change
README adds context; it’s not designed to make employee feel like they’re back in school and panicking because they’re not prepared
Manager README - Not Matt’s best selection of terminology
Who’s the best boss you ever had? Why? They can be a force that shapes your life and career from the right perspective
Philosophy of Management: Don’t do what terrible managers have done; be transparent about strategic reasons for priorities changing
Matt Newkirk on LinkedIn
Matt Newkirk on Twitter
Share your Manager README
Etsy’s Job Openings
Shane Garoutte on LinkedIn
Would you like access to unlimited retention of your data within your Amazon S3, which costs far less than online storage on disc? Well, the next time you’re at re:Invent, visit CHAOSSEARCH’s booth.
Today, we’re talking to Pete Cheslock, vice president of products at CHAOSSEARCH and former vice president of operations at Threat Stack. CHAOSSEARCH helps people get access to their login event data using Amazon S3.
Some of the highlights of the show include:
re:Invent - Year of the Pin: People go nuts for conference swag and were collecting pins as if they were gold
Scan Your Badge and Drip Emails: Annoying and passive-aggressive marketing trends meant to be spontaneous and interesting
Need a job? Corey’s looking to hire a “Quinntern” to use a tag email address to gather conference swag at the next re:invent; if interested, contact him
Corey and Pete’s Swag Rules: Something you want or can use, continues to be valuable, no sizes, no socks
Densify Drama: Conference flyer to generate leads failed, created complaints
Track and analyze data, but don’t use it to invade privacy or become creepy
Las Vegas: Right place for conferences, such as re:Invent?
Rather than focusing on going to conference sessions, make meeting and talking to people doing interesting things your priority
Midnight Madness Event: Only place Corey could do stand-up Cloud comedy
re:Invent 2019: Plan appropriately, identify what you want to get out of it, register ASAP to get a nearby hotel, and schedule meetings with AWS staff
Pete Cheslock on Twitter
Pete Cheslock on LinkedIn
Corey Quinn’s Newsletter
Corey Quinn on Twitter
Corey Quinn’s Email
AWS re:Invent 2018 - Keynote with Andy Jassy
AWS re:Invent 2018 - Keynote with Werner Vogels
Have you ever had high expectations about a new software product? Did you think it was going to be spectacular? Instead, did it become less about solving a problem for you and more about reaching a bunch of billable consultants? The dynamics of open source communities and the Cloud platform can make or break software products.
Today, we’re talking to Andrew Clay Shafer, who was a notable voice during the days of OpenStack. He had high hopes for OpenStack, which was an effort to bring a democratized solution of Cloud computing to anyone’s data center. He describes the importance of understanding the challenges associated with open source projects in order for them to be successful.
Some of the highlights of the show include:
Open source is not a business model; capture value for customers, or they’ll go with a different solution
Openness/Closure: Every open source project has its own community dynamics
Losing sight of level of expertise for profitability and easy path to useage
Whether to become a product or service company - difficult to be both effectively or go from being one to the other; build partner relationship, focus, and say “no”
Lack of awareness about AWS Outposts admitting public Cloud is no longer a viable business model
Amazon relentlessly focuses on what its customers want and tries to keep promises about what it can and can’t do
Cloud Native: Not where you run, but how you run; confining variables
Self-fulfilling prophecy to under deliver when you make the bad decision to under source IT across the board
Cloud Native, DevOps, SRE: Buzzwords that equal one thing and work together
Dilemma of not building everything and buying some things, but you can’t buy everything; humans like to shop and go with the easiest option
Andrew Clay Shafer on Twitter
Andrew Clay Shafer on LinkedIn
AWS Ground Station
Maslach Burnout Inventory
You can't make money selling to developers! The bottleneck of getting business requirements and creating business value used to mean waiting for the next waterfall release. That’s not the case anymore in the venture community. There’s programmatic access to infrastructure and DevOps/agile developments that offer super-fast cycle times. Now, the bottleneck is about how fast your developers can move and how much they can get done.
Today, we’re talking to Joseph Ruscio, general partner at Heavybit Industries, which is an accelerator for seed-stage companies and focuses on developer-first products. Tools and products that get you more leverage out of your developers are incredibly valuable.
Some of the highlights of the show include:
Measuring maturity of startups’ engineering teams by looking at SaaS list - what products they have in place and how many are using out-of-house vendors
Customers don’t care how curated or artisan a piece of your stack is, they only care that it works
Not all claims (scales infinitely or never fails) are true when it comes to products on the market, so people are skeptical
Heavybit focuses on helping businesses build a bottoms-up, grassroots community around its products and a disciplined inside/direct sales motion
Build vs. Buy: Whatever people try to do themselves is a costly, pale imitation of something they can buy
Advice for New Entrepreneurs: Never compete with AWS on hosting compute because it will obliterate and Amazon is great at plumbing, terrible at painting
AWS’s version of your product won't be as sophisticated; continually work on it to deliver a more seamless product and customer success experience
Measure downtime/outages in terms of dollars by using monitoring tools that deliver more holistic, integrated, comprehensive experience than CloudWatch
Starting a company is easier; even if you're the 800-pound gorilla in the category you created, keep innovating and building or Amazon’s coming after you
Azure, unlike GCP, has ability to meet customers where they are, rather than telling them where they should be
Understand the problem your customer is trying to solve and understand how far out of their current comfort zone they're willing to go to solve that problem
Software exists to create business value; it doesn't matter what it's written in or how it's hosted, so some systems will be around for a long time
Joseph Ruscio on Twitter
High Leverage Podcast
Do you like to hear yourself talk? Especially while on a stage and in front of a lot of people? How do you come up with ideas to talk about? What process do you use to build a conference talk or presentation?
Today, we’re talking to Matty Stratton of PagerDuty. His job involves building conference talks and finding ways to continuously improve them. Public speaking can be intimidating, so he shares some tips and tricks that have worked for him.
Some of the highlights of the show include:
Avoid creating something brand new for every event
Don’t tell flattering stories about things that happened to you; may be uplifting, but doesn't resemble reality
Failure stories are fantastic because people relate to making terrible decisions
Everyone who gives a talk panics, gets nervous, and thinks they’re about a sentence away from stammering and falling off the stage; almost never happens
Audience wants you to succeed because they're there to learn; no one is hoping a presenter messes up
Preparation is key; could build a talk at the last minute, but it would be much better, if you prepared for it
Don’t intentionally try to think of something; have conversations with people and listen to other talks to develop anecdotes, stories, and cold opens
Humor can be tricky; what you think is funny, other people might not
Make things memorable; show good ideas by showing bad ideas - it’s the ‘don't do this, do this instead’ model
Submit early and often, but submit appropriately; if you are always submitting stuff that’s inappropriate for an event, your stuff starts to be ignored
Sometimes, you may want to avoid slides that auto advance; if you trip over yourself: Stop, repeat, back up, take questions, etc.
Try not to read from notes or slides; takes the life and engagement out of the talk
People can only do one thing at a time - listen or read
Practice: Record yourself every time you practice and watch it; focus on blocking and tackling
You have about 45 seconds to grab people's interest before they look at their phone; get them engaged via a story, picture, or anecdote
Matty Stratton’s Presentations
Matty Stratton on Twitter
Hot Takes, Myths, And Fake News—Why Everyone Is Wrong About DevOps, Except For Me
Rebel Without A Crew
Adam Jacob from Chef
Terrible Ideas in Git
Don't You Know Who I Am?!
Do you understand how tabs work? How spaces work? Are you willing to defeat the JSON heretics? Most people understand the power of the serverless paradigm, but need help to put it into a useful form. That’s where Stackery comes in to treat YAML as an assembly language. After all, no one programs processors like they did in the '80s with raw assembly routines and no one programs with C. Everyone is using a higher-level scripted or other programming language.
Today, we’re talking to Chase Douglas, co-founder and CTO of Stackery, which is serverless acceleration software where levels of abstraction empower you to move quickly. Stackery has an intricate binding model that gives you a visual representation - at a human logical level - of the infrastructure you defined in your application.
Some of the highlights of the show include:
Stackery builds infrastructures by using best practices with security applications
What's a VPC? Way to put resources into a Cloud account that aren’t accessible outside of that network; anything in that network can talk to each other
Lambda layers let developers create one Git layer that includes multiple functionality and put it in all functions for consistency and management
Git is an open-source amalgam of different programming languages that has grown and changed over time, but it has its own build system
Stackery created a PHP runtime functionality for Lambda; you don't want to run your own runtime - leave that up to a Cloud service provider for security reasons
Should you refactor existing Lambda functions to leverage layers? No, rebuild everything already built before re-architecting everything to use serverless
Many companies find serverless to be useful for their types of workloads; about 95% of workloads can effectively be engineered on a serverless foundation
Trough of Disillusionment or Gartner Hype Cycle: Stackery wants to re-engage and help people who have had challenges with serverless
Is DynamoDB considered serverless? Yes, because it’s got global replication
Puritanical (being able to scale down to zero) and practical approaches to the definition of serverless
Aurora Serverless Data API
Ruby on Rails
What’s hiring in the world of Cloud like? What are companies looking for in possible employees? What kind of career trajectory should applicants display?
Today, we’re talking to Don O’Neill, who has had an interesting career path and the archetype of who most companies want to hire. He’s been an independent contributor, platform leader, and Cloud consultant. Currently, Don is platform engineer manager at Articulate, an eLearning software solution for course authoring and eLearning development. He works with platform engineers to automate Blue Ocean pipelines with Docker, Terraform, and various Amazon Web Services (AWS) technologies, such as Elastic Beanstalk.
Some of the highlights of the show include:
Don reached out to his network to ask people that he had a professional relationship with about who was hiring and what challenges they faced
Don’s “Therapy”: Go to meet-ups to talk about DevOps topics; serves as a “I’ve-got-to-get-my-hiney-out-of-the-house-and-get-some-social-time”
Don’s journey from being a “wee lad in the industry” to a senior member/leader and giving back as a way to recognize those who helped him along the way
Hiring Horror Stories: People going through borderline ridiculous levels of hiring games and terrible interview paradigms
Companies sometimes look for something too specific - exact match instead of fuzzy match; they never have time to train, but time to look for a perfect unicorn
Articulate’s Hiring Process: Day 1 - Slack interview; Day 2 - Technical pieces; and Day 3 - Pairing with others
Articulate looks for people enthusiastic about technology, able to learn, and with emotional intelligence; company values independence, autonomy, and respect
Companies that spend several hours to make a hiring decision tend to have less success with those they hire
Cloud Certificates/Certifications: Can be valuable for applicants with no real-world experience; they don’t indicate how they’re going to work or learn
Applicants need to demonstrate a base level of knowledge; if they don’t have a skill set, they should start a project to learn about something - learning is fun
If you’re established in your career, reach out to someone just starting out to guide them
If you’re starting out in your career, reach out to people to talk about the next steps to take in your career (contact Corey or Don)
Don O’Neill on Twitter
Switch App (Tinder for Jobs)
Spotify in Stockholm
Do you enjoy watching sports? Wear your favorite team or player’s jersey? Are you a fan who has shopped at Fanatics on the Cloud?
Today, we’re talking to Johnny Sheeley, director of Cloud engineering at Fanatics, which is a sports eCommerce business that manufactures and sells sports apparel. Fanatics runs Cloud engineering to provide a robust and reliable set of services by building and deploying applications on top of the Azure Data Lake Store (ADLS) platform.
Some of the highlights of the show include:
If you compete with Amazon, be ready for it to come after you; some companies avoid its Cloud perspective or go multi-Cloud (paranoia-based movement)
Focus on your ability to make your business function smoothly
Transition, migration, and abstraction may be painful, but should not stop work; paying for Cloud-agnostic technology may not be worth it
Challenges of governing use of Cloud resources to prevent mistakes/problems related to Fanatics’ security and budget
Data collected focuses on what’s trending up or down to select an instance type that calculates costs; remain flexible and be aware of what you pay
Natural instinct is to blame people; mistakes are made, especially when a human factor is introduced to an automated system
Creating a mindset that focuses on feature and detail-oriented is challenging
Cottage industry of code bases running in Big Data and other expensive realms
As a product continues to evolve and grow, governance comes along for the ride and AWS bills are streamlined
Will serverless, Lambda, and RDS change how Amazon charges in the future?
State of scale of AWS and developing a more palatable method for releases because people can’t keep up with them and stop paying attention
Two-Pizza Team: Amazon’s management philosophy that any team that works on a service should be able to be fed with two pizzas
Such small teams work quickly and have the freedom to fail, but Amazon has a reliability for the longevity of its different services
Johnny Sheeley's Email
Johnny Sheeley on Twitter
Rands Leadership Slack
Getafix: How Facebook Tools Learn to Fix Bugs Automatically
Accidentally Quadratic Blog
Jeff Barr’s AWS News Blog
Lots of Amazon's projects have failed...and that's ok, says Amazon's Andy Jassy
Did you know that you can now run Lambda functions for 15 minutes, instead of dealing with 5-minute timeouts? Although customers will probably never need that much time, it helps dispel the belief that serverless isn’t useful for some use cases because of such short time limits.
Today, we’re talking to Adam Johnson, co-founder and CEO of IOpipe. He understands that some people may misuse the increased timeframe to implement things terribly. But he believes the responsibility of a framework, platform, or technology should not be to hinder certain use cases to make sure developers are working within narrow constraints. Substantial guardrails can make developers shy away. With Lambda, they can do what they want, which is good and bad.
Some of the highlights of the show include:
Companies are using serverless as a foundation and for critical functions
Serverless can be painful in some areas, but gaps are going away
Investing in the Future: Companies doing lift-and-shift to AWS are looking at technology they should choose today that’s going to be prominent in 3 years
Serverless empowers new billing models and traces the flow of capital; companies can choose to make pricing more complicated or simplified
What value are you providing? Serverless can offer flexible pricing foundation
When something breaks, you need to be made aware of such problems; Amazon bill doesn’t change based on what IOpipe does, which is not true with others
Developers are the ones woken up and on call, so IOpipe focuses on providing them value and help; they are not left alone to figure out and fix problems
Serverless and event-driven applications offer a new type of instrumentation and observability to collect telemetry on every event
For serverless to go mainstream, AWS needs to up its observability level to gather data to answer questions
AWS, in the serverless space, needs to make significant progress on cold starts in other languages, and offer more visibility and easier deployment out of the box
Episode 16: There are Still Servers, but We Don't Care About Them
Google App Engine
In the early days, angry nerd corners on the Internet viewed Slack and some of its predecessors as, “Oh, it’s just IRC. Now, you pay someone for it.” Many fell into that trap of wondering about what value such systems offered.The big differentiator? Slack is built as a collaborative business tool.
Today, we’re talking to Holly Allen, who helped make government software better while serving as the director of engineering at 18F. Now, she’s a senior engineering manager at Slack, a collaborative chat program where you can do most of your work through a rich platform of integrations. Holly enjoys taking a weird set of skills that make a computer do things and convincing people who know how to make computers do things do things.
Some of the highlights of the show include:
Safety engineering brings chaos and resilience engineering, incident management, and post-mortem processes together for resiliency and reliability
Slack strives to move really fast while being in complete control
Slack is primarily on AWS, but is working on a multi-Cloud strategy because if AWS is down, Slack still needs to work
Slack has a close relationship with AWS and is a collaborative company; it has immediate access to AWS staff anytime there’s a problem
Slack uses Terraform and Chef and working to determine if its production workflows in Kubernetes would be worthwhile
Disasterpiece Theater: Real scenario that might happen and surmise what will happen; don’t cause production issues, but teach Slack employees
Slack hires collaborative, empathetic people to create a collaborative environment where everyone works together toward a goal
Slack was firmly in a centralized operations model, but is transforming toward development teams to increase responsibility and service ownership
Slack doesn’t encourage remote work because it’s not in a position to put in that investment; day-to-day work happens in hallways and between desks
Slack sees itself as an enterprise software company; an enterprise software company must have enterprise software reliability, stability, and processes
Slack has thousands of servers, so events and disruptions happen more often; system needs to respond, react, and repair itself without human intervention
Holly Allen on Twitter
If you’ve been doing DevOps for the past 10-20 years, things have really changed in the industry. There’s no longer large pools of help desk support. People aren’t climbing around the data center and learning how to punch down cables and rack servers to gradually work their way up. Now, entry level DevOps jobs require about five years of experience. So, that’s where internships play a major role. But how can an internship program be set up for success? Where is the next generation of SREs or DevOps professionals coming from? Where do we find them?
Today, we’re talking to Fatema Boxwala, who has been an intern at Rackspace, Yelp, and Facebook. She’s a computer science student at the University of Waterloo in Canada, where she’s involved with the Women in Computer Science Committee and Computer Science Club. Occasionally, she teaches people about Python, Git, and systems administration.
Some of the highlights of the show include:
Mentors made Fatema’s intern experience positive for her; made site reliability and operations something she wanted to do
Academic paths don’t tend to focus on such fields as SRE, and interns tend to come exclusively from specific schools
Fatema’s school requires five internships to graduate and receive a degree; upper-year students are already very qualified professional software engineers
Companies don’t have time to train and want to find someone with an exact skill set; instead of hiring someone, they spend months with an unfilled position
Continuity Problem: You can’t train someone to be a systems administrator, if you aren’t willing to give them certain privileges due to inexperience
Use a low-stakes environment to train, where mistakes can be made; most systems aren’t on a critical path - don’t keep people away from contributing
If you have never broke production, that means either you’re lying or you’ve been in an environment that didn’t trust you to touch things that mattered
Internship should mimic the kind of work that everyone else is doing; give them responsibilities where their work has an impact
Bad mentors lead to bad internships; person in charge of your success doesn’t have the necessary skills; needs to be a good communicator, set expectations
As the intern, ask about possible outcomes of internship early on; mentors should be clear about expectations, feedback, and offers
Fatema Boxwala on Twitter
Jackie Luo on Twitter
Julia Evans Zines on Twitter
Are you interested in computer science? How would you like to go to school for free and learn what you need to in just a few months? Then, check out Lambda School!
Today, we’re talking to Ben Nelson, co-founder and CTO of Lambda School, which is a 30-week online immersive computer science academy. Lambda School has more than 500 students and takes a share of future earnings instead of traditional debt. So, it's free until students get a job.
Some of the highlights of the show include:
Bootcamps were created to address engineering shortages and quickly move people into technical careers
Lambda is not explicitly a bootcamp; its 30-week program gives students more instructions and more time spent on developing a portfolio
Employers appreciate the school’s in-depth and advanced approach, which results in repeat hires
Lambda avoids the typical reputation of traditional for-profit educational institutions by being mission-driven and knowing its investors want ROI
Lambda aligns its incentives with those of students; an income share agreement means the school doesn’t make money, unless students are successful
Lambda’s 7-month program is less of a risk for someone later in their career; some don't have capital to support their family while going to school for 4 years
Lambda incentivizes healthy financial habits; after two years of repayment, students can put that money into retirement, savings, and investments
5 Tracks Now Offered by Lambda: iOS development, UX, Full Stack Web development, data science, and Android development
Mastery Based Progression System: When you're learning something sequentially, where knowledge builds, you don't move on until you’ve mastered it
Lambda’s acceptance rate is around 5% and based on people who can keep up
Lambda works with different partner companies to help them find qualified graduates - people they want to hire
Ben Nelson on Twitter