Podcasts about cloud developer advocate

In this episode of the Modern Web Podcast, Danny Thompson and Adam Rackis talk with Abdel Sghiouar, Cloud Developer Advocate at Google, Kubernetes Podcast co-host, and CNCF Ambassador. Abdel shares insights from his global tech journey, from Morocco to Google's largest data center in Belgium, and now Sweden. They discuss cloud computing trends, including WebAssembly, AI-driven serverless workloads, and the shifting lines between frontend and backend. They also explore AI's impact on cloud development, from simplifying tooling to raising questions about job automation. Abdel offers a pragmatic take on AI's role, emphasizing that those who learn to leverage it will thrive.Key points from this episode:- Cultural Differences in Tech – Abdel's global experience shaped his view on work culture, from Morocco's relationship-driven workplaces to Europe's structured work-life balance.- Making Cloud Simpler – He focuses on breaking down cloud concepts and making them more approachable for developers, from high-level serverless tools to hands-on infrastructure.- AI in Cloud & Serverless – AI is improving cloud navigation, troubleshooting, and serverless efficiency, with tools like Google Cloud Assist and Vercel's Fluid Compute.- AI & Tech Jobs – AI won't replace developers but will automate simpler tasks. Understanding fundamentals and problem-solving remain key to staying relevant.0:00 - The challenge of opinionated platforms and integration in cloud0:46 - Welcome to the Modern Web Podcast with Danny Thompson & Adam Rackis1:15 - Guest introduction: Abdel Sghiouar, Cloud Developer Advocate at Google2:01 - Abdel's international journey and how different work cultures shape tech perspectives7:08 - Bridging the cloud knowledge gap for web developers9:38 - Cloud fundamentals: compute, storage, and networking12:19 - Emerging trends: WebAssembly, AI, and serverless evolution16:07 - AI's impact on cloud development: Hype vs. reality22:27 - The future of serverless and infrastructure automation28:22 - Google Cloud vs. Firebase: Balancing simplicity and scalability31:50 - What Abdel is geeking out about: Content creation and AI tools34:51 - Closing thoughts & where to connect

Send me a Text Message hereFULL SHOW NOTES https://podcast.nz365guy.com/569  What happens when a seasoned .NET developer shifts gears to embrace low-code solutions? Scott Durow, a Power Platform and Cloud Developer Advocate at Microsoft, shares his transformative journey from traditional coding to adopting the Power Platform. We delve into the evolution of Microsoft's business applications and the essential resources needed for professional developers to transition smoothly to Power Platform. Scott also offers a glimpse into his life on the scenic west coast of Canada, highlighting how the natural beauty and outdoor activities inspire his work.We tackle key topics like integrating Power Platform with existing .NET ecosystems in enterprise software development, emphasizing the necessity of developer input even in low-code environments. Scott discusses the platform's extensibility through C# plugins, TypeScript, JavaScript, and custom connectors, making it a robust choice for enterprise solutions. We also explore the concept of anti-patterns and how leveraging higher-level abstractions can simplify complex software architecture, ultimately enhancing development efficiency.In a fascinating case study, we examine a major financial institution in Australia transitioning 60 Pega developers to Power Platform. Scott shares practical advice for overcoming the initial learning curve and maximizing the platform's benefits. We also dive into the roles of software and enterprise architecture, touching on the skepticism enterprise architects may have towards low-code solutions like Power Platform. Wrapping up, we reflect on our engaging conversation with Scott and look forward to more insightful discussions in future episodes. Don't miss this episode packed with valuable insights and practical advice for navigating the Power Platform landscape!90 Day Mentoring Challenge 10% off code use MBAP at checkout https://ako.nz365guy.comSupport the Show.If you want to get in touch with me, you can message me here on Linkedin.Thanks for listening

Guests are Marek Siarkowicz , Senior Software Engineer in Google Cloud, Tech Lead of SIG-etcd   AND Wenjia Zhang, Engineering Manager in Google Cloud, Co-Chair of SIG-etcd, Google. We spoke about the project, the recent change to become a Special Interest Group and how to learn etcd.   Do you have something cool to share? Some questions? Let us know: - web: kubernetespodcast.com - mail: kubernetespodcast@google.com - twitter: @kubernetespod News of the week Co-host this week is Mofi Rahman [X, LinkedIn]. Cloud Developer Advocate at Google Karpenter graduated to Beta The Kubernetes SIG Network announced release 1.0 of the Gateway API Ingress2gateway new CLI to migrate from Ingress to Gateway The Call for Proposals for KubeCon EU 2024 will close on Nov 26, 2023 Links from the interview etcd Meaning of etcd etcd history from CoreOs Raft paper On the Hunt for Etcd Data Inconsistencies by Marek Siarkowicz - [youtube] Lessons Learned From Etcd the Data Inconsistency Issues by Marek Siarkowicz - [youtube] The first pancake rule etcd as a Kubernetes sig The Case for SIG-ifying etcd CNCF Contributor License Agreements (CLA) Kubernetes Prow Contributor Experience Special Interest Group Kubernetes Watch Go Serialization and Deserialization Cilium with external etcd Certified Kubernetes Administrator etcd mentorship program etcd @kubecon NA 2023 Links from the post-interview chat Kubernetes considerations for large clusters Operating etcd clusters for Kubernetes Kueue etcd on the podcast The Heartbleed Bug XKCD meme about dependency  

In this episode, Michael catches up with Josh Duffney, Cloud Developer Advocate at Microsoft to talk about Go (golang). Kubernetes, Docker, and Terraform are all written in Go. Josh and Michael talk about their journey into Kubernetes and Go, some fun projects to play with, how to learn Go, and why understanding certain programming languages is crucial for breaking into Kubernetes.

In this episode, Michael catches up with Josh Duffney, Cloud Developer Advocate at Microsoft to talk about Go (golang). Kubernetes, Docker, and Terraform are all written in Go. Josh and Michael talk about their journey into Kubernetes and Go, some fun projects to play with, how to learn Go, and why understanding certain programming languages is crucial for breaking into Kubernetes. The post Kubernetes Unpacked 008: Go – The Language Of Kubernetes appeared first on Packet Pushers.

In this episode, Michael catches up with Josh Duffney, Cloud Developer Advocate at Microsoft to talk about Go (golang). Kubernetes, Docker, and Terraform are all written in Go. Josh and Michael talk about their journey into Kubernetes and Go, some fun projects to play with, how to learn Go, and why understanding certain programming languages is crucial for breaking into Kubernetes. The post Kubernetes Unpacked 008: Go – The Language Of Kubernetes appeared first on Packet Pushers.

In this episode, Michael catches up with Josh Duffney, Cloud Developer Advocate at Microsoft to talk about Go (golang). Kubernetes, Docker, and Terraform are all written in Go. Josh and Michael talk about their journey into Kubernetes and Go, some fun projects to play with, how to learn Go, and why understanding certain programming languages is crucial for breaking into Kubernetes.

In this episode, Michael catches up with Josh Duffney, Cloud Developer Advocate at Microsoft to talk about Go (golang). Kubernetes, Docker, and Terraform are all written in Go. Josh and Michael talk about their journey into Kubernetes and Go, some fun projects to play with, how to learn Go, and why understanding certain programming languages is crucial for breaking into Kubernetes.

In this episode, Michael catches up with Josh Duffney, Cloud Developer Advocate at Microsoft to talk about Go (golang). Kubernetes, Docker, and Terraform are all written in Go. Josh and Michael talk about their journey into Kubernetes and Go, some fun projects to play with, how to learn Go, and why understanding certain programming languages is crucial for breaking into Kubernetes. The post Kubernetes Unpacked 008: Go – The Language Of Kubernetes appeared first on Packet Pushers.

In this episode, Michael catches up with Josh Duffney, Cloud Developer Advocate at Microsoft to talk about Go (golang). Kubernetes, Docker, and Terraform are all written in Go. Josh and Michael talk about their journey into Kubernetes and Go, some fun projects to play with, how to learn Go, and why understanding certain programming languages is crucial for breaking into Kubernetes.

Stephanie Wong and Brian Dorsey are joined today by fellow Googlers Jaisen Mathai and Sara Ford to hear all about Cloud Functions (2nd gen) and how it differs from the original. Jaisen gives us some background on Cloud Functions and why it was built. Supporting seven languages, this tool allows clients to write a function without worrying about scaling, devops, and a number of other things that are handled by Cloud Functions automatically. Customer feedback led to new features, and that's how the second evolution of Cloud Functions came about. Don't worry, first gen users! This will continue to be available and supported. Features in the 2nd gen fit into three categories: performance, cost, and control. Among other benefits, costs stay low or may even be reduced with some of the new features, larger instances and longer processing times mean better performance, and traffic splitting means better control over projects. Sara details an example illustrating the power of the new concurrency features, and Jaisen helps us understand when Cloud Functions is the right choice for your project and when it's not. Our guests walk us through getting started with Cloud Functions and using the 2nd gen additions. Companies like Lucille Games are using Cloud Functions, and our guests talk more about how specific users are leveraging the new features of the 2nd gen. Jaisen Mathai Jaisen is a product manager for Cloud Functions. He's been at Google for about six years and before joining Google was both a developer and product manager. Sara Ford Sara is a Cloud Developer Advocate focusing on Cloud Functions and enjoys working on serverless. Cool things of the week No pipelines needed. Stream data with Pub/Sub direct to BigQuery blog Cloud IAM Google Cloud blog The Diversity Annual Report is now a BigQuery public dataset blog Interview Cloud Functions site Cloud Functions 2nd gen walkthrough video Cloud Functions version comparison docs Lucille Games: Playing to win with Google Cloud Platform site BigQuery site Cloud Run site Eventarc docs Cloud Shell site GCP Podcast Episode 261: Full Stack Dart with Tony Pujals and Kevin Moore podcast Working with Remote Functions docs Cloud Console site Where should I run my stuff? Choosing compute options video What's something cool you're working on? Stephanie has been working on GCP Support Shorts. Hosts Stephanie Wong and Brian Dorsey

SHOW SUMMARY:Don't stress out! In this episode of NgXP, we're joined by Cloud Developer Advocate, international speaker, & author Dan Wahlin who talks with us about dealing with stress & anxiety as a software engineer or programmer. Dan identifies common stressors in the workplace, how to both minimize and overcome them, and shares helpful outlets and resources to manage stress & anxiety at home and at work alike. Please note that none of the panelists on the show today are medical professionals and that our opinions and advice are our own. If you're needing more in-depth and comprehensive care, please seek out the appropriate medical guidance from a licensed professional.LINKS:https://blog.codewithdan.comhttps://app.pluralsight.com/profile/author/dan-wahlinhttps://linktr.ee/danwahlinhttps://www.youtube.com/watch?v=_q-HL9YX_pk&t=1shttps://www.youtube.com/watch?v=tnXO-i7944M&t=4shttps://www.yogajournal.com/practice/beginners/how-to/pranayama/CONNECT WITH US:Dan Wahlin @DanWahlinBrooke Avery @JediBraveryErik Slack @erik_slack

Does it make sense to use .NET with Microsoft 365 (was Office 365)? Carl and Richard talk to Dan Wahlin, now in his new role as a Cloud Developer Advocate, about the power that exists within the Microsoft 365 APIs and what you can do with them with .NET. Dan talks about how Microsoft 365 knows a lot about what's going on in your organization, and how you as a developer can take advantage of the existing file handling, messaging, and interconnects to simplify your projects and make them more visible to users. The conversation explores moving existing brownfield applications into the Microsoft 365 realm, and what code you should be writing, or perhaps turning over to Azure Logic Apps or Power Automate!

Does it make sense to use .NET with Office 365? Carl and Richard talk to Dan Wahlin, now in his new role as a Cloud Developer Advocate, about the power that exists within the Office 365 APIs and what you can do with them with .NET. Dan talks about how Office 365 knows a lot about what's going on in your organization, and how you as a developer can take advantage of the existing file handling, messaging, and interconnects to simplify your projects and make them more visible to users. The conversation explores moving existing brownfield applications into the Office 365 realm, and what code you should be writing, or perhaps turning over to Azure Logic Apps or Power Automate!Support this podcast at — https://redcircle.com/net-rocks/donations

Does it make sense to use .NET with Office 365? Carl and Richard talk to Dan Wahlin, now in his new role as a Cloud Developer Advocate, about the power that exists within the Office 365 APIs and what you can do with them with .NET. Dan talks about how Office 365 knows a lot about what's going on in your organization, and how you as a developer can take advantage of the existing file handling, messaging, and interconnects to simplify your projects and make them more visible to users. The conversation explores moving existing brownfield applications into the Office 365 realm, and what code you should be writing, or perhaps turning over to Azure Logic Apps or Power Automate!Support this podcast at — https://redcircle.com/net-rocks/donations

About NathenNathen Harvey, Cloud Developer Advocate at Google, helps the community understand and apply DevOps and SRE practices in the cloud.  Nathen formerly led the Chef community, co-hosted the Food Fight Show, and managed operations and infrastructure for a diverse range of web applications. Links: cloud.google.com/devops: https://cloud.google.com/devops 97 Things every Cloud Engineer Should Know: https://shop.aer.io/oreilly/p/97-things-every/9781492076735-9149 Twitter: https://twitter.com/nathenharvey TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored in part by Thinkst. This is going to take a minute to explain, so bear with me. I linked against an early version of their tool, canarytokens.org in the very early days of my newsletter, and what it does is relatively simple and straightforward. It winds up embedding credentials, files, that sort of thing in various parts of your environment, wherever you want to; it gives you fake AWS API credentials, for example. And the only thing that these things do is alert you whenever someone attempts to use those things. It’s an awesome approach. I’ve used something similar for years. Check them out. But wait, there’s more. They also have an enterprise option that you should be very much aware of canary.tools. You can take a look at this, but what it does is it provides an enterprise approach to drive these things throughout your entire environment. You can get a physical device that hangs out on your network and impersonates whatever you want to. When it gets Nmap scanned, or someone attempts to log into it, or access files on it, you get instant alerts. It’s awesome. If you don’t do something like this, you’re likely to find out that you’ve gotten breached, the hard way. Take a look at this. It’s one of those few things that I look at and say, “Wow, that is an amazing idea. I love it.” That’s canarytokens.org and canary.tools. The first one is free. The second one is enterprise-y. Take a look. I’m a big fan of this. More from them in the coming weeks.Corey: This episode is sponsored in part by our friends at Lumigo. If you've built anything from serverless, you know that if there's one thing that can be said universally about these applications, it's that it turns every outage into a murder mystery. Lumigo helps make sense of all of the various functions that wind up tying together to build applications.It offers one-click distributed tracing so you can effortlessly find and fix issues in your serverless and microservices environment. You've created more problems for yourself. Make one of them go away. To learn more, visit lumigo.io.Corey: Welcome to Screaming in the Cloud. I’m Corey Quinn. I’m joined this week by Nathen Harvey, a cloud developer advocate at a small startup called Google. Nathen, thank you for joining me.Nathen: Hey, Corey. It’s really great to be here.Corey: We’ll get to the Google bits in a little, but first, I want to start back in the beginning with your origin story. It turns out, for example, that you were at a lot of places, and the first thing going through your history that I really recognized was way back at the end of 2009, where you were the web operations manager at Custom Ink. They’re a t-shirt company—and other apparel—that I’ve been using for three years now for the charity t-shirt drive here, as well as other sundry things. Longtime listeners of the show might remember we had Ken Collins on to talk about Ruby in Lambda and other horrifying things, before it was cool.Nathen: Yes, indeed, I was at Custom Ink. And, you know, you talk about them being a t-shirt company, and I don’t know… maybe I’m still a shill for Custom Ink, but I really look at them as an experience company. And you’ve recognized that yourself. They produce and help people, really encourage that group and experiences, and really drive what does it mean to connect with other humans, and how can you do that through custom apparel? To me, that’s what Custom Ink has always been about. They’re not selling t-shirts; they are selling an experience.Corey: In my case, I view them as a t-shirt company because, let’s be fair here, I wind up doing charity t-shirt drives, and they’ve always been extremely supportive of—well, there’s really no other way to put this—my ridiculous nonsense. The year I had linked campaigns of the ‘AMI has three syllables’ shirt that was on sale, and then for the Amazonians, ‘ah-mi’ is how it’s pronounced instead and that one was $10 more because there’s a price to being wrong. And all proceeds, of course, went to benefit the charity of the year. And that was a fun thing. And I talked to a number of other folks on this, and they look at me very strangely, and Custom Ink didn’t even blink.Nathen: Right, right. Absolutely. Absolutely.Corey: And yes, they said lots of other apparel, but for whatever reason, it seems that sending out complicated multiple options of things that need each hit minimum order quantities to print during a fundraiser, and the fact that I don’t have to deal with the money because they just wind up sending it over directly. It’s just easier. It’s one of those things where back when I was a single person who was doing this stuff, I didn’t have to worry about it. Now that I’ve grown and my needs have multiplied, I still like doing business with them. Great folks.Nathen: Absolutely. And that’s exactly what I mean by—like, they’ve sold you on that experience. That’s why you continue to do business with them. It’s not just because of the t-shirts. It’s the whole package that goes along with it.Corey: And then in 2012, the world didn’t end. But yours kind of did because you stopped working at Custom Ink and went to another company called Chef. You were there for a little over six years. You started off as a community director and then became the VP of Community Development. And I think you did an amazing job, but first tell me about that, then I will give my hot take.Nathen: All right, great. I’m always up for the hot takes. So listen, Chef was an amazing community of people. Oh, it was also a company. And so I really fell in love with—while I was at Custom Ink, actually, we were using Chef, and I fell in love with the community.And I was doing a lot of community support, running my own podcast, or participating with some co-hosts on a podcast called the Food Fight Show back in the day—it was all about Chef—running meetups and so forth. And at one point I decided, you know, what I should do maybe is stop being on call and start supporting this community full time. And that’s exactly what I did. I went to Chef and yes, as you mentioned, spent just over six years there, or just about six years there, and it was really, really an incredible time. Lots of hugs to be given, and just a great community in the DevOps space.Corey: I took a somewhat, I guess, agreeing or disagreeing position. I was on the Puppet side of the configuration management debate, and it was challenging. And then, ah, I was one of the very early developers behind SaltStack because clearly, the problem with all of these things was that no one had written it correctly, and we were going to fix that. And it turns out no, no, the problem was customers the whole time. But that’s a separate debate.So, I was never in the Chef ecosystem. That was the one system I never really touched in anger. And it’s easy to turn this into a, “Oh, you folks were the competition,” despite the fact I’ve never actually worked directly for either of those companies. But it was never like that because our real enemies were people configuring things by hand, for one because that’s unnecessary toil; don’t do it, and it was also just such an uplifting sense of community. Some of the best people I knew were in the Chef ecosystem, in the Chef orbit.For a while, they’re, on some level—and this is something I’d love to get your thoughts on—it seems that a failure mode that Chef exhibited was hiring directly from its community, where if someone was a big fan of Chef, start a stopwatch, they’re going to be working there before the month is out.Nathen: I think that Chef, the company definitely pulled a lot of community members into the organization. And frankly, when the company started, that was really, really great because it was an early startup. And as the company grew, it was still wonderful, of course, to pull in people from the community to really help drive the future direction, how our customers are using it. But like you said, there is a little bit of a challenge or concern when you start pulling too many of your most vocal supporters out of the community and putting them into the company, sometimes in places or roles where they didn’t have the opportunity to be as vocal, as big a champions for the product, for the services.Corey: I think at some level, it was—again, it helps to have people who are passionate about the product working there, but on the other, it felt like over time, it wound up weakening the community in some respects, just because everyone who worked there eventually found themselves in a scenario of well, I work here, it’s what we do, and now I have to say nice things. It winds up weakening the grassroot story.Nathen: Mmm. There’s definitely some truth to that, but I think there’s also some truths to just the evolution of community as you went from a community in the early days where there were a lot of contributors to over time—gratefully so—the community that—or sort of the proportion of the community that were consumers of Chef versus contributors to Chef, that balance changed. And so you had a lot more customers using the product. So, I don’t disagree with you, but I do think that it’s part of the natural evolution of community as well.Corey: And all things must end. And of course, Chef got acquired, I believe, after you left. So, I mean, at that point, you left, they were rudderless and what else were they to do? And you went to Google. And that is always an interesting story because Google’s community interaction before the time you wound up there, and after—I don’t know that you were necessarily the proximate cause, but I’m going to hang that around your neck because it’s all been a positive change since then—look radically different.Nathen: Yeah. Well, thank you. It is definitely not something that I should wear or carry alone, but going to Google was an interesting choice for me and I recognize that. And, you know, honestly, Corey, one of the things that drove me to Google was a good friend of mine, Seth Vargo. And just to kind of tie the complete throughline here, Seth and I worked together at Custom Ink, we’ve worked together at Chef, he left Chef and went to Hashi, and then went to Google. And the day after I knew that he was going to Google, I called him up and I said, “Seth, come on. Google’s so big. Why? Why? And how? I don’t understand. I don’t understand the move.”Corey: I asked him many of the same questions back in episode three of this show. He was a very early guest when I was scared speechless having conversations. It’s improved since then, a couple hundred in. But yeah, very friendly; very open; very warm.Nathen: Yeah. And, you know—Corey: “Why are you at Google?” was sort of the next follow-on question there in that era.Nathen: [laugh]. Yes, indeed. And I do think that Google, and specifically Google Cloud, has really taken to heart this idea that there’s a lot that we can learn from each other. And I don’t mean from each other within Google. Although, of course, we can learn a lot from each other.But we can also learn a lot from our community, from our customer base. How are they using Google Cloud? How are they using technology to drive their business forward? These are all things that we can learn. It turns out, not every company has Google, and that’s a good thing.Not every company should be Google or Google-sized, and certainly don’t have Google customers. And I think that it’s really important that we recognize that when we work with a customer, they’re the experts in their customers, and in their systems, and so forth.Corey: A lot has changed with Google’s approach to, well, basically everything. It turns out that when you’re a company that is, what, 26 years old now—27, something like that—starting with humble beginnings and then becoming a trillion-dollar entity, things change. Culture change, your community changes, what you do changes, and that becomes something that I think is not necessarily fully appreciated or fully understood in some corners. But then 2018 hit. You went to Google; what did you do then?Because it is such a large company that it is very difficult to know what any individual is up to there, and the primary means that I engage in the DevRel community space—specifically via aggressively shitposting on Twitter—isn’t really your means of interacting with the community. So, from that particular point of view, it’s, “Oh, yeah, he went to Google, and no one ever heard from him again.” What is it you say it is you do there?Nathen: Yeah. So, for sure. What I do here as a cloud advocate, is I really focus in on kind of two areas, I would say: DevOps—and I recognize that is a terrible, terrible word because when I say it, we all think of different things, but I definitely focus on the DevOps—and then SRE practices as well, or Site Reliability Engineering. And specifically what I work on is how do we bring the principles and practices of DevOps, of SRE, into our customer base and into the community at large? How do we drive what is the state of the art?How do we approach these particular topics? And so that’s really what I’ve been focused on since joining Google. Well, frankly, I was focused on that while at Chef, as well, maybe without the SRE bend so much, but certainly at Google SRE comes in, but it’s always—for the past decade for me—been about DevOps and how do we use technology to align the humans and work towards the business outcomes that we’re driving for?Corey: And business outcomes become an interesting story in the world of cloud because it distills down, for a cloud service provider is, we would like people to use our cloud, more of it, in perpetuity. It is not a complicated business model—if I can be direct—because business models inherently are not. “Whatever it is your company does, we would like you to do it here.” And that turns into a bunch of differentiated services across the spectrum, in some cases hilariously so, when it turns into basically pick an English word, and there’s a 50/50 shot that’s part of a service name somewhere. But a lot of it distills down to baseline distinct primitives.You’re talking about the DevOps aspect of it, which is—we talk about, is it culture? Is it tools? No, it’s a means to sell conferences, and books, and things like that. But what is it in the context of a cloud service provider? Specifically, Google because let’s be clear here, DevOps apparently for other providers is Azure DevOps. That’s right. It’s a service name, and DevOps Guru on the AWS side because everything is terrible.Nathen: Absolutely. Look, I think that I used to snark that the only DevOps tool was the manager of DevOps. But the truth is that DevOps is… it is tooling, and it is culture, and to separate the two is really a fool’s errand. I think that your tooling amplifies your culture, your culture amplifies your tooling. Together, this is how we make progress.Now, when it comes to Google, what do we mean when we say DevOps? Well, one of the good things is, shortly after I joined Google Cloud, Google Cloud acquired DORA, the DevOps Research and Assessment Organization.Corey: Jez Humble, and Dr. Nicole Forsgren. And then, for all intents and purposes, they googled it. Relatively shortly thereafter, by which I mean, we never really heard from DORA again. In 2020, the “State of DevOps Report” didn’t exist, which was what they were famous for doing. And it was, “Oh, yep. That’s a Google acquisition all right.” Is that what happened? Did I miss some nuance there?Nathen: Yeah. Let’s talk about that. So first, you’re right, it was Dr. Nicole Forsgren, who founded DORA. So, when the acquisition happened, she came along to Google Cloud, Jez Humble came along through that acquisition as well. And frankly, what happened in 2020? Well, Corey, I don’t know if you noticed, but there was a lot happening in 2020, much of it not very good. I think when we look at the global scale, like, 2020 was not a great year for us—Corey: It was a rebuilding year.Nathen: Oh, all right, fair enough. Fair enough. [laugh]. A rebuilding year. But so here’s what happened with DORA, quite frankly. We—Google Cloud—continue to invest in that research program. And really, in a sense, 2020 was a rebuilding year, in that our focus was really about how do we help our customers and our community apply the lessons of DORA?And so one of the things that we’ve done is we’ve released much of the research under cloud.google.com/devops, including right there, a DevOps quick check where, as a team you can go in and, using the metrics and the research program from DORA, you can assess, are you a low, medium, high, or elite performer?And then beyond that assessment, actually use the research to help you identify which capabilities should my team invest in improving. So, those capabilities might be technical capabilities, things like continuous integration; it might be process or measurement capabilities, or in fact, cultural capabilities. So, all of these capabilities come together to help you improve your overall software delivery and operations performance. And so in 2020, the big thing that we did was release and continue to update this Quick Check, release the research, make it fully available. We’ve also spent some time internally on the program that, you know, is not super interesting to talk about on the podcast.But the other thing that we did in 2020 with the DORA research program was update the ROI research, the return on investment research. This is something that maybe your listeners don’t care about, but their managers might care about, their CIOs, CTOs, CFOs might care about. How do we get money back on this transformation thing? And the research paper really digs into exactly that. How do we measure that? What returns can we expect? And so forth. So, that was released in 2020.Corey: I have a whole bunch of angry thoughts about a lot of takes in that space, but this is neither the time nor the place for me to begin ranting incoherently for an hour and a half. But yeah, I get that it was a year that was off, and now you’re doing it again, apparently, in 2021. And the one thing I never really saw historically because I don’t know if I’m playing in the wrong environments, or I’m certainly not the target [laugh] audience now, if I ever really was, but most years, I missed the release of the survey of where people can go to fill in these questions. I would be interested to know where that is now. And then I would be interested to know, how have you been socializing in that in the past? In other words, where are you finding these people?Nathen: Yeah, for sure. So, the place you go to find the survey right now is cloud.google.com/devops, you’ll find a button on the page that says something like, “Take the survey,” or, “Take the 2021 survey.”And what we’ve done in the past, and really what DORA has done in the past is use a number of different ways to get out information about the survey, when the survey is open, and so forth. Primarily Twitter, but also we have partners, and DORA historically has used partners as well to help share that the survey itself is open. So, I would absolutely recommend that you go and check out the survey because I’ll tell you what, one of the things that’s really interesting, Corey, over the years, I’ve talked to a bunch of people that have taken the survey, and that have read the State of DevOps Report that comes out each year, and some of the consistent feedback I’ve heard from folks is that simply taking the survey and considering the questions that are asked as part of the survey gives great insight immediately into how their team can improve. What things, what capabilities are they lacking? Or what capabilities are they doing really well with and they don’t need to make investments on? They can immediately see that just by answering and carefully considering the questions that are part of the survey.Corey: This episode is sponsored by ExtraHop. ExtraHop provides threat detection and response for the Enterprise (not the starship). On-prem security doesn’t translate well to cloud or multi-cloud environments, and that’s not even counting IoT. ExtraHop automatically discovers everything inside the perimeter, including your cloud workloads and IoT devices, detects these threats up to 35 percent faster, and helps you act immediately. Ask for a free trial of detection and response for AWS today at extrahop.com/trial.Corey: Very often, in some cases looking at things like maturity models and the like, the actual report is less valuable than the exercise of filling it out and going through the process. I mean, compliance reports, audit framework, et cetera, often lead to the same outcomes. The question is, are you taking it seriously, or are you one of those folks who is filling out a survey because do this and you’ll be entered to win a $25 gift card somewhere? Probably Blockbuster because it no longer exists. I get those in my email constantly of, “Yeah, give half an hour of your time in return for some paltry chance to win something.”No, I have a job to do. And I worry if at that level of that approach, who are you actually getting that’s going to sit down and fill this thing out? That said, the State of DevOps Reports have been for a long time, sort of the gold standard in this space and I would encourage people listening to this to absolutely take the time to fill that out. cloud.google.com/devops.I’m looking forward to seeing what comes out of it. And I love it because of the casual shade you can use to throw at other companies, too. Like, “Are you an elite team?” With the implicit baked-in sentiment being, no, you’re not, but I want to hear you say it.Nathen: Yeah, one of the things that really sets DORA apart, also, I think, is just the—well, two of the things I guess I would say. One is the length of time that the research program has been running. It’s going on seven years now that this research program has been running, and so given that, you have tens of thousands of IT professionals that have taken the survey and provided insights into sort of what’s the state of our industry today, and where are we heading, but it’s also an academically rigorous survey. The survey and the research itself has always and continues to be completely platform and program agnostic. This is not a survey about Google Cloud.This is not a survey where we’re trying to help understand exactly what products on Google Cloud should you use in order to be an elite performer. No. That’s not what this is about. It is about, truly, capabilities that your team needs in order to improve their software delivery and operations performance. And I think that’s really, really important.Dr. Nicole Forsgren who founded DORA, she didn’t come up with all of these ideas: “Hey, I think that you get better by doing this.” No. Instead, she researched all of these ideas. She got this input from across organizations of all sizes, organizations in every industry, and that, I think, really sets it apart.And our ability to really stay committed to that academic rigor, and the platform-agnostic approach to capturing and investigating these capabilities, I think is so important to this research. And again, this is why you should participate in the survey because you truly are going to help us move the state of the art of our industry.Corey: No, historically, there’s been a challenge where the mantle of thought leadership in conjunction with Google have intersected because there’s a common trope—historical—and I think that it is no longer accurately true. It’s an easy cheap shot, but I don’t think it holds water like it once did. Where, “Oh, Googler. It’s another word for condescending.” And there is an element of “Oh, this is how DevOps should be; this is how we’re moving things forward.” How do you distance it from being Google says you should do it like this?Nathen: Yeah. This comes up a lot. And frankly, I get in conversations with customers asking, “How does Google do this? How does Google do that?” And my answer always is, “You know, I can tell you how Google does something, and that might be interesting, but the fact is, it’s not much more than that, much more than interesting. Because what really matters is how are you going to do this? How are you going to improve your outcomes, whether that’s you’re delivering faster, you’re delivering more reliable, you’re running more reliable services? You’re the experts. As I mentioned earlier, you’re the experts in your teams, in your technology, and your customers. So, I’m here to learn right along with you. How are you going to do this? How are you going to improve?” Knowing how Google does it, eh, it’s interesting, but it’s not the path that you will follow.Corey: I think that’s one of those statements that can’t ever be outright stated on a marketing website, somewhere; it’s one of those shifts that you have to live. And I think that Google’s done a pretty decent job of that. The condescending Googler jokes are dated at this point, and it’s not because there was ever an ad campaign about, we’re not condescending anymore. It was a very subtle shift in the way that Google spoke to its customers, spoke about themselves. I no longer feel the need to stand up in a blinding white rage in the Q&A portion of conference talks given by Google employees.A lot has changed, and it’s not one thing that I can point to, it’s a bunch of different things that all add up to dramatically shifted credibility models. Realistically, I feel like that is a microcosm of a DevOps transformation. It’s not a tool; it’s not a single person being hired; it’s not, we’re taking an agile class for three days for all of engineering, and now things will be better. It’s a whole bunch of sustained work with a whole bunch of thought, and effort put into making it an actual transformation, which is such a toxically overloaded term, I dare not use it.Nathen: Indeed. And there’s no maturity model that shows, are you there yet? And it is something that you don’t flip on or flip off like a switch, right? It doesn’t happen overnight. It takes iteration and iterative change across the entire organization.And just like every change that you have across an organization, there are places where it’s going better than other places. And how do you learn from that? I think that’s really, really important. And to recognize and to bring some of that humility to the table is so important.Corey: So, what’s interesting about folks that I talk to on this show—well, there are many interesting things, but one of the interesting things is, is that they have a higher rate than the general population of having at one point in their careers, written a book of some form, and you are, of course, no exception. You and Emily Freeman co-authored recently, a book entitled 97 Things every Cloud Engineer Should Know. And it’s interesting because it only has one nine in the title. Okay, that is at least an attempt at being available. I know it’s available wherever most books are sold. Tell me more.Nathen: Yeah, so first, let’s start with the 97. Why 97? Corey, I don’t know if this or not, but 100% is the wrong reliability target for just about everything. So, 97. That feels achievable.Corey: It also feels like three people said they would do it and then backed out at the last minute, but that’s my cynicism speaking.Nathen: Well, for better or worse, O’Reilly. Has a whole 97 Things series and this is part of it. So, it is, in fact, 97 things. The other thing that I think is really important about the book: you mentioned that Emily and I wrote it, and the beauty is, for a long time, I’ve wanted to have written a book, and I have never wanted to be writing a book.Corey: That is what every author has ever said. It’s, no one wants to write a book; they want to have written one. And then you get a couple of beers into people and ask them, “So, I’m debating writing a book. Should I?” The response is, “No. Absolutely not. No.” And at some point, when you calmed them down again, and they stop screaming, they tell you the horrifying stories, and you realize, “Oh, wow, I really never want to write a book.”Nathen: [laugh]. Yes. Well, the beauty of 97 Things and this book in particular, or the whole series, really, is its subtitle is Collective Wisdom from the Experts. So, in fact, we had over 80 different contributors sharing things that other cloud engineers should know. And I think this is also really, really important because having 80-plus contributors to this book gave us, not 97 things that Emily and Nathen think every cloud engineer should know, but instead, a wide variety of experience levels, a wide variety of perspectives, and so I think that is the thing that makes the book really powerful.It also means that those 80-some folks that contributed to the book, had to write a very short article. So, of course, with 80 authors and 97 Things, the book is not—it doesn’t weigh 27 pounds, right? It’s less than 300 pages long, where you get these 97 tidbits. But really, the hope and the intent behind the book is to give you an idea about what should you explore deeper and, just as importantly, who are some people that you can, maybe, reach out to and talk to about a particular topic, a particular thing that a cloud engineer should know. Here are 80 people that are here, helping you and really cheering you on as you take this journey into cloud engineering.Corey: I think there’s something to be said from having the stories for this is what we do, this is how we do it. But the lessons learned stories, those are the great ones, and it’s harder to get people on stage to talk about that without turning into, “And that’s how we snagged victory from the jaws of defeat.” No one ever gets on stage and says and that’s why the entire project was a boondoggle and four years later, we’re still struggling to recover. Especially, you know, publicly traded companies tend not to say those things. But it’s true.You wind up with people getting on stage and talking instead about these high-level amazing things that they’ve done in the project went flawlessly, and you turn to the person next to you and say, “Yeah, I wish I could work in a place like that.” And they say, “Yeah, me too.” And you check, and they work at the same place as the presenter. Because it’s conference-ware; it’s never a real story. I’m hoping that these stories go a bit more in-depth into the nitty-gritty of what worked, what didn’t work, and it’s not always ‘author as hero protagonist.’Nathen: Oh, you will definitely find that in this book. These are true stories. These are stories of pain, of heartache, of victory and success, and learnings along the way. Absolutely. And frankly, in the DevOps space, we do an okay job of talking openly about our failures.We often talk about things that we tried that went wrong, or epic failures in our systems, and then how we recovered from them. And yes, oftentimes, those stories have a great sort of storybook ending to them, but there’s a lot of truth in a lot of those stories as well because we all know that no organization is uniformly good at everything. That may be the stories that they want to share most, but, you know, there’s some truth in those stories that hopefully we can find. And certainly, in this book, you will find the good, the bad, the ugly, the learnings, and all of the lessons there.Corey: Where can people find it if they want to buy it?Nathen: Oh, you know, you can find it wherever you buy books. There are of course, ebooks, O’Reilly’s website, you know with the—Corey: Wherever fine books are pirated. Yes, yes.Nathen: That’s a good place to go for books, yeah. For sure.Corey: And we will, of course, throw a link to the book in the [show notes 00:29:12]. Thank you so much for taking the time to speak with me. If people want to learn more about the rest of what you’re up to, how you’re thinking about it, what wise wisdom you have for the rest of us, okay can they find you, other than the book?Nathen: Yeah, a great place to reach out to me is on Twitter. I am at @nathenharvey. But I should warn you, my father misspelled my name. So, it’s N-A-T-H-E-N-H-A-R-V-E-Y. So, you can find me on Twitter; reach out to me there.Corey: And we will of course include links to all of that in the [show notes 00:29:43] as well. Thank you so much for speaking to me today. I really appreciate it.Nathen: Thank you, Corey. It’s been a pleasure.Corey: Nathen Harvey, cloud developer advocate at Google. I’m Cloud Economist Corey Quinn and this is Screaming in the Cloud. If you’ve enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you’ve hated this podcast, please leave a five-star review on your podcast platform of choice, along with an angry comment telling me that I’m completely wrong. You can instantly get DevOps in your environment if I only purchase whatever crap it is your company sells.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

This week, Jeffrey Palermo is joined by return guest, Jeremy Likness! Jeremy is an internationally selling author, keynote speaker, and professional coder with a personal mission to empower developers to be their best! He has worked on commercial enterprise software for 25 years and specializes in web technology. Currently, he is also a Sr. Cloud Developer Advocate for Microsoft, but previously held roles at iVision, Wintellect, and AirWatch.   Last year when Jeremy was on the podcast last, they discussed DevOps automation. In this episode, they focus the discussion on working with data on .NET. Jeremy shares about the work that he had been doing on the .NET Data team for the last year, Entity Framework Core, Microsoft Dataverse, GraphQL, and more!   Topics of Discussion: [:38] Be sure to visit AzureDevOps.Show for past episodes and show notes. [:51] About The Azure DevOps Podcast, Clear Measure, the new podcast Architect Tips, and Jeffrey’s offer to speak at virtual user groups. [1:28] About today’s episode with Jeremy Likness. [1:53] Jeffrey welcomes Jeremy back to the podcast! [2:15] Jeremy gives an overview of his role as the Senior Program Manager working on .NET Data and the work that his team does. [5:37] About Microsoft Dataverse and Jeremy and his team have been working with the Azure Storage and Dataverse teams. [8:28] Of the different methods of working with data in C#, what’s the general distribution? Which methods have greater adoption? [11:17] Jeremy and Jeffrey discuss different .NET project types and whether Entity Framework 5.0 the latest stable release. [11:55] Jeremy shares what is most exciting to him with this upcoming .NET release. [13:25] What’s the go-to store on the client-side? [16:04] The new inheritance strategies in EFCore: are they fully implemented and ready? [19:21] Jeremy talks about the focus on speed for EFCore 6. [21:37] A word from Azure DevOps Podcast’s sponsor: Clear Measure. [22:08] Why developers are “forced” to learn object-oriented programming through EFCore’s features. [24:32] How Jeremy goes about testing code that uses Entity Framework. [27:30] Jeremy highlights where to access invaluable EFCore resources. [28:54] Jeremy touches on how the EF code team uses ReSharper. [29:15] What GraphQL is and why it might be useful if you have a .NET application. [32:40] Jeremy highlights another good QL platform: Hot Chocolate by ChilliCream. [34:06] The architecture of GraphQL and whether it is a database engine or a library. [35:33] If you have a .NET app running in App Service and you’ve already got Azure SQL, and you want to get some of your data and use Graph QL, is this a new Azure resource? Architecturally, what would you do to adopt this? [39:18] Jeffrey thanks for Jeremy for joining the podcast!   Mentioned in this Episode: Architect Tips — New video podcast! Azure DevOps Clear Measure (Sponsor) .NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Available on Amazon! bit.ly/dotnetdevopsebook — Click here to download the .NET DevOps for Azure ebook! Jeffrey Palermo’s Youtube Jeffrey Palermo’s Twitter — Follow to stay informed about future events! The Azure DevOps Podcast’s Twitter: @AzureDevOpsShow Azure DevOps Podcast Ep. 76: “Jeremy Likness on DevOps Automation” Jeremy Likness’ Blog Jeremy Likness’ Twitter Jeremy Likness’ LinkedIn Jeremy Likness’ GitHub Jeremy’s Email: Jeremy.Likness@Microsoft.com  GraphQL Microsoft Dataverse Microsoft Azure Storage Blazor OData Entity Framework Core .NET MAUI Uno Platform Docs.Microsoft.com/EF Azure Cosmos DB GitHub.com/DOTNET/EFCOREReSharper Hot Chocolate by ChilliCream   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

Jenna shares her journey from being bullied as a kid growing up in Detroit, to finding her place as a Cloud Developer Advocate at IBM via their apprenticeship.

Felipe Hoffa, developer advocate, and software engineer at Google. Felipe is originally from Chile and is now based in San Francisco and around the world. If you're involved in big data and data science, you may recognize him as a familiar name and face answering thousands of developer questions on stack overflow and Reddit, which are read by millions of programmers. For Google, he also records tutorial videos on YouTube, gives conference talks on big data, and writes blog posts on the latest developments in cloud tools. Phillipe is a leading voice on Google's cloud computing products.

Today’s guest is Jeremy Likness — an internationally selling author, keynote speaker, and professional coder with a personal mission to empower developers to be their best! Jeremy has worked on commercial enterprise software for 25 years and specializes in web technology. Currently, he is also a Sr. Cloud Developer Advocate for Microsoft, but previously held roles at iVision, Wintellect, and AirWatch. In his free time however, he enjoys running, hiking, and shooting nine-ball and one-pocket.   In today’s episode, Jeffrey and Jeremy discuss DevOps Automation. Jeremy shares his philosophy on starting a new project, provides key insights about Azure DevOps Services, speaks about what is new with Azure DevOps in general, gives his thoughts on GitHub Actions, explains how he’s utilizing Azure ARM templates, and shares some of his best practices and go-to resources.   Topics of Discussion: [:39] Be sure to visit AzureDevOps.Show for past episodes and show notes. [1:08] About today’s guest, Jeremy Likness. [1:49] Jeffrey welcomes Jeremy to the podcast. [1:40] Jeremy describes two of his favorite hobbies: nine-ball and one-pocket. [3:15] Jeremy speaks about his career and how it has progressed over the years. [8:11] Jeremy speaks about his current role at Microsoft and what Cloud Advocate really means. [9:51] Jeremy shares his philosophy on starting a project. [13:58] Jeremy provides some key insights when bringing Azure DevOps Services into the mix. [15:41] What’s new in Azure DevOps in general? [20:38] A word from Azure DevOps Podcast’s sponsor: Clear Measure. [21:03] Jeffrey gives some quick announcements. [22:52] Jeremy gives his thoughts on GitHub Actions. [25:48] Jeremy speaks about what the experience is like with GitHub Actions when you have a release candidate that you’re deploying to your environments (environment 1, environment 2, etc.), all the way up to production. He also provides some examples. [28:14] When deploying, is Jeremy still using Azure ARM templates? Or does he use a mix of things to provision his infrastructure? [34:55] Jeremy gives a quick piece of random nostalgia from his past. [35:47] Jeremy’s go-to resources to learn more about the topics discussed on today’s show. [37:45] Where to get in touch with Jeremy! [38:15] Jeffrey thanks Jeremy for joining him in this episode.   Mentioned in this Episode: Azure DevOps Clear Measure (Sponsor) .NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Available on Amazon! bit.ly/dotnetdevopsebook — Click here to download the .NET DevOps for Azure ebook! bit.ly/dotnetdevopsbookforcommunity — Visit to get your hands on two free books to give away at conferences or events! Jeffrey Palermo’s Youtube Jeffrey Palermo’s Twitter — Follow to stay informed about future events! Jeffrey@Clear-Measure.com — Email Jeffrey for a free 30-point DevOps inspection (regularly priced at $5000!) — Spaces are limited! Jeremy Likness’ Blog Jeremy Likness’ Twitter Jeremy Likness’ LinkedIn Jeremy Likness’ GitHub Jeremy’s Email: Jeremy.Likness@Microsoft.com Azure DevOps Services Abel Wang The Azure DevOps Podcast: “Abel Wang on DevOps Infrastructure - Episode 73” Hugo GitHub Actions Azure Resource Manager (ARM) Microsoft Ignite Blazor Docs.Microsoft.com/en-us/Learn   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

  Anthony is a Cloud Developer Advocate at Microsoft in Vancouver, Canada. He's been a software developer and architect for almost 2 decades, currently focusing on serverless, containers, JavaScript, and .NET. At Microsoft, Anthony is helping make Azure an awesome place for developers to deploy their apps in any language and platform.   Links https://anthonychu.ca/ https://twitter.com/nthonyChu https://www.linkedin.com/in/chuanthony/ https://github.com/anthonychu https://stackoverflow.com/users/3199781/anthony-chu   Links https://docs.microsoft.com https://docs.microsoft.com/en-us/learn/ Azure Functions Documentation Microsoft Learn module with Azure Functions and SignalR Service   "Tempting Time" by Animals As Leaders used with permissions - All Rights Reserved   × Subscribe now! Never miss a post, subscribe to The 6 Figure Developer Podcast! Are you interested in being a guest on The 6 Figure Developer Podcast? Click here to check availability!  

Diva Tech Talk interviewed actor-turned-technologist/evangelist, Chloe Condon , Cloud Developer/Advocate for Microsoft.    Chloe is a passionate supporter of women in technology, with an extensive social media brand following, and  “non-traditional background,” since she “grew up doing musical theater in all shapes and forms.”  Chloe’s father is a director/playwright. Her mother is a theatrical costume designer and graphics designer.  “So, I grew up in a trunk!” She had little exposure to tech. “I had blinders on. I just knew that I wanted to be an actress.” After performing arts high school, Chloe matriculated at San Francisco University for a bachelors’ degree in theater performance. “I booked my first starring role, playing Kira in Xanadu,” a San Francisco stage production.  Reality brought Chloe up short when “they handed me $500 for three to four months of rehearsal.” She addressed cash flow through “bizarre 9-to-5 jobs to support my nights/weekends in theater.” She took numerous retail jobs, then landed an Account Executive position at (pre-IPO) Yelp. She became fascinated by the startup, tech environment, but “was terrible at sales.”   She “stumbled into other tech roles” including Zirtual, the first virtual personal assistant company.  There she met Ben Parr, (then editor-at-large of Matchable), who co-founded VC fund The Dominate Group. Ben has gone on to be a columnist at Inc., a sought after speaker, and philanthropist. During this discovery period, Chloe was unhappy, from a deficit of free time combined with minimal personal autonomy.  Then she attended a Google-sponsored talk focused on girls interested in programming. It inspired her to find a bootcamp for coders (“these can be life-changing”).   She chose “HackBright Academy, since it was all women. It felt very empowering.”  Hackbright’s message, to the male-dominated programming world, is “change the ratio!”  Initially, Chloe suffered from “Impostor Syndrome” which she thinks is more pervasive in technology than other field. A key to making progress, at the bootcamp, was to adjust learning style from simply reading about concepts to reading AND doing.  “I had to think of it like choreography,” she said. Her tenure at the focused camp culminated in a project: a social media application that rigorously timed postings to achieve optimal exposure, no matter your time zone. As she prepared for “Demo Night,” Chloe’s revelation was that “building the app was hard; talking about it was not. I had always viewed my theater degree as a setback but I use my theater degree, every day, as an engineer, and doing public speaking.” Initially interviewing for junior engineering roles, Chloe experienced “a significant change” when she “pivoted my brand to be more ‘developer relations’.”  Her blend of speaking, performing, and communications merged with newly minted programming skills. She was hired by start-up Code Fresh, specializing in Docker innovation.  After a year, Chloe left Code Fresh  to join Sentry.io, a company focused on error-tracking for developers working in open source. She lauded the company’s culture.  “You wanted to go to work, every day. The people were so fun and cool.” There, she reveled in creative, fun projects. Through that work, she collaborated with Microsoft, who gave her “an offer I couldn’t refuse.” At Microsoft, Chloe currently works with the cloud-based Azure platform.  Most recently, she concentrated on cognitive services, infusing applications, websites and bots with intelligent algorithms to interpret in natural language. “I built an app that analyzes images of Cosplay Mario Kart characters to determine their mood and emotions. 95% of my demos are funny, quirky or solve a unique problem. I try to have fun elements in everything I do.” Chloe shared classic advice. “Treat people like humans. As they say in The Book of Mormon, let’s just be really nice to everyone. It’s not that hard.”  When faced with a challenge that seems insurmountable (like code not working) Chloe advised: “Take a walk and come back with the solution.”  She also counseled people to take breaks to achieve higher productivity. And “ask for help!” She cited Twitter as a rich source of feedback and advice.  Chloe is amazed by the generosity of experts in the tech industry. “People are willing to help. This community is welcoming and warm.” Chloe has evolved to revel in her differences.  “I do not look like an engineer. And I fully embrace that,” she said, discussing the male, middle-aged technocrat stereotype. “I think it educates people” when she is the keynote speaker at a tech conference.  In 2017, she wrote an article matter-of-factly describing how it feels to be a sole woman at a tech conference.  It went viral because it allowed others to empathize without judgement. To protect herself, from Internet intrusion, she wryly said “I am very sharp, and witty, on Twitter.  Anyone who comes at me, publicly, will get destroyed by my awesome jokes!” More pragmatically, she is building a bot to respond to inappropriate DM’s. In terms of job-hunting, Chloe urged women to be selective.  “Work at a place you are comfortable.” She cited “red flags” like a company uncomfortable with negotiation; or a company displaying paucity of women leaders in the interview process.  Positively, she expressed appreciation for companies who cultivate sensitivity to diversity issues. She also cited Ru Paul’s advice to “silence your inner saboteur” and proceed with confidence. Chloe noted the industry is missing the mark by not considering those with degrees that are not technical. “If you are going to claim you are a diverse company, be open to hiring people from bootcamps! Put your money where your mouth is.” As an evangelist for Microsoft, Chloe measures success by “folks approaching me and telling me that the work I am doing changed something fundamental for them.  At the end of the day, if I have affected one person, or opened eyes to something new, that is success for me!” For other women in the field, she urged “be authentically you. Don’t feel like you must act like one of the guys. We need more ideas, and diverse thoughts.” Make sure to check us out on online at www.divatechtalk.com, on Twitter @divatechtalks, and on Facebook at https://www.facebook.com/divatechtalk. And please listen to us on SoundCloud, Stitcher, or your favorite podcasting channel and provide an online review.

Live from ChefConf 2019, I talk with Nathen Harvey about outages, lunch and a life spent in technology. This was one of my favorite podcast interviews because Nathen is one of my major influences and mentors in what we do in Developer Advocacy and Relations in technology. He's taught me so much over the years and has done his best to check in with me during the tough moments, like another member of the on-call team might do during a rough incident. Nathen Harvey, Cloud Developer Advocate at Google, helps the community understand and apply DevOps and SRE practices in the cloud. Nathen is a co-host of the Food Fight Show, a podcast about Chef and DevOps, and is part of the DevOps Days conferences global organizing committee. Nathen is part of the Google DevRel team and can be found at the following links: https://twitter.com/nathenharvey https://linkedin.com/in/nathen

Speaking in conferences and traveling the world, can be challenging as is. But what happens when you have a baby? How can you still do it? In this episode Britt hosts Shmuela, who has been traveling with her baby all over the world, giving talks and workshops, and smiling the whole time! Shmuela shares her experience, with some challenges and how to overcome them. The message is clear and loud - continue to do what you love, everything is possible! She also gives some ideas for organisers on how to make it a little easier for parents to speak and attend, in the hope that even more events will become more inclusive to parents. Shmuela Jacobs is a Cloud Developer Advocate at Microsoft, and the founder of ngGirls. She is also a part of Google Developer Expert Program for web. Britt Barak is a Google Developer Expert for Android, originally from Tel Aviv, newly based in London. She's a part of Nexmo's Developer Relations & Experience team. More of her content is on brittbarak.com

In Episode 10 of DevTalk, I speak to Laurent Bugnion about what it means to be a Senior Cloud Developer Advocate at Microsoft. Links: How A Blind Developer Uses Visual Studio by Saqib Shaikh Expert Day for Xamarin Munich on June 14, 2019

Together we talked about Erik's first hacking feats and how he got his first job in the IT world. We then brushed over his learnings at Disney and Comcast before joining Microsoft to help other developers. Erik then encouraged us to question our perception of ourself, and compare ourselves only against our former self. We then touched on the definition of seniority. We discussed Erik's experience getting to know the Go language and organize the first GopherCon conference. And we finally talked about the ways we learn.Erik St. Martin has spent the last decade building and securing distributed systems for large enterprises such as cable providers, credit bureaus, and fraud detection companies. He now works for Microsoft as a Sr. Cloud Developer Advocate. He co-authored a book on the Go programming language, podcasts with GoTimeFM, and co-organizes GopherCon, the annual conference for the Go community.Here are the links of the show:Twitter: https://twitter.com/erikstmartinKatharina Owen Mind the gap https://www.youtube.com/watch?v=ClPIeuL9HnIGopherSlack https://invite.slack.golangbridge.orgSpeaking backlog: https://erikstmartin.com/speakingGophercon https://www.gophercon.comCreditsMusic Aye by Yung Kartz is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 License.Your hostSoftware Developer‘s Journey is hosted and produced by Timothée (Tim) Bourguignon, a crazy frenchman living in Germany who dedicated his life to helping others learn & grow. More about him at timbourguignon.fr.Want to be next?Do you know anyone who should be on the podcast? Do you want to be next? Drop me a line: info@devjourney.info or via Twitter @timothep.Gift the podcast a ratingPlease do me and your fellow listeners a favor by spreading the good word about this podcast. And please leave a rating (excellent of course) on the major podcasting platforms, this is the best way to increase the visibility of the podcast:Apple PodcastsStitcherGoogle PlayThanks!Support the show (http://bit.ly/2yBfySB)

Jeremy Likness is a Cloud Developer Advocate for Azure at Microsoft. Jeremy has spent two decades building enterprise software with a focus on line of business web applications. He is the author of several highly acclaimed technical books including Designing Silverlight Business Applications and Programming the Windows Runtime by Example. He has given hundreds of technical presentations during his career as a professional developer. In his free time Jeremy likes to run, hike, and maintain a 100% plant-based diet.Jeremy first explained how he felt in love with computers at the age of 7... and ended up droping out of college and abandoning the idea of a career in software. He told us about the detours he took and how he got back in IT through the back door. We touched on his learning patterns and how he got into public speaking and conferences. We devised on how each step of his career prepared him for his current job as a developer advocate. Finally, we spoke about hiring and mentoring younger developers.Here are the links of the show:@jeremylikness on Twitter: http://twitter.com/@jeremyliknessBlog: https://blog.jeremylikness.comUpcoming talks: https://blog.jeremylikness.com/upcoming-talks-eaf27ff8a3a7CreditsMusic Aye by Yung Kartz is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 License.Your hostSoftware Developer‘s Journey is hosted and produced by Timothée (Tim) Bourguignon, a crazy frenchman living in Germany who dedicated his life to helping others learn & grow. More about him at timbourguignon.fr.Want to be next?Do you know anyone who should be on the podcast? Do you want to be next? Drop me a line: info@devjourney.info or via Twitter @timothep.Gift the podcast a ratingPlease do me and your fellow listeners a favor by spreading the good word about this podcast. And please leave a rating (excellent of course) on the major podcasting platforms, this is the best way to increase the visibility of the podcast:Apple PodcastsStitcherGoogle PlayThanks!Support the show (http://bit.ly/2yBfySB)

GUEST BIO: Jasmine Greenaway is a Cloud Developer Advocate for Microsoft.  She has been working as a .NET developer since late 2009 which has given her the opportunity to travel the world and make use of Visual Studio’s extensibility framework in an open source environment.  Jasmine also teaches at a local community college and co-organises BrooklynJS. EPISODE DESCRIPTION: Phil’s guest on today’s show is Jasmine Greenaway. She has evolved her career as a web developer into an exciting life, full of opportunities and interest. Jasmine rarely says no to a chance to take her IT career in a new direction. As a result, today, she is a well-known public speaker, mentor and teacher. All of this is in addition to working as a Cloud Developer Advocate at Microsoft. She also co-organises BrooklynJS. KEY TAKEAWAYS: (00.57) – So Jasmine, can you expand on that brief introduction and tell us a little bit more about yourself? Jasmine explains that after leaving university, she decided to move to New York. This was a good move for her because it helped grow her confidence and get past being shy. She started public speaking, while in New York. First, she gave really short, lightning talks. In time, she graduated to making 30-minute presentations. Today, she regularly speaks at IT conferences. After joining the GitHub team she was asked to speak at a conference about the GitHub Visual Studio project she was working on. That led to someone from Microsoft reaching out to her and offering her the Advocate position. Despite not being very familiar with Azure, at the time, she took the plunge, which turned out to be a great decision for everyone involved. When someone asked her to teach web development in a local Queens’ community college she said yes to that too. She has been doing it for 2 years now and really enjoys seeing her students grow. Her work there combined with her speaking and meetups have helped her to build up a great network of friends, colleagues and collaborators. (4.00) – What have you learned working in what must be quite an interesting environment? Jasmine said that often she is dealing with students who have never opened a text editor or seen an ID. In those situations, she has learned to go slow and recap regularly. Going from nothing to doing a full project in just four months is a big task, which can be overwhelming. So, students need to be led along the path to success carefully. Phil asks if her students feel a sense of accomplishment once they have completed the course. Jasmine, says yes that is definitely the case. In the end, a lot of her students thank her for taking the time to go back over things they were struggling with. She often sits down with students for one to ones, even as they start their IT careers. Often, they are really close to achieving their goals. All they need is a little advice or encouragement to get there.  (6.28) – Can you please share a unique career tip with the I.T. career audience? Jasmine says that it is important to be comfortable with what you know. Don’t let what you do not know, overwhelm you. Use what you have and recognize that you can easily learn the rest of what you need. It is all too easy to become overwhelmed and be too hard on yourself. Phil agrees that is very good advice and adds that breaking an objective down into smaller chunks makes things easier to understand. When you do that the task becomes far easier to achieve. Jasmine says that is the exact approach she uses when programming, especially if she has to learn something new to be able to complete the project.  (8.07) – Can you tell us about your worst career moment? Jasmine explained that at one point in her career she let imposter syndrome overwhelm her. At the time, she was working on a team where everyone, except her, was a senior developer. Fairly quickly, she began to feel she was not contributing and could not get anything right. Fortunately, someone took her aside and told her she was doing a good job. They also told her not to be afraid to ask for help. Once she started doing that everything was OK. To this day, she is thankful for that team for picking up on the fact that she was struggling and reaching out to her to let her know they were there to help. (9.25) – What did you learn from that experience? It taught Jasmine to believe in herself and her capabilities. In that situation, the only person that thought she was not capable was herself. Once she was convinced otherwise by the team Jasmine was able to make rapid progress.  (10.14) – What was your best career moment? Jasmine said that was the talk she gave in August 2018 with a co-worker. For fun, they decided to see if they could uncover the identity of the famous, but anonymous, horse.js using machine learning. The person who runs that Twitter account takes web development tweets and copies a sentence from them and tweets that back out again. Weirdly, this simple process produces some very amusing results. Because it is funny and quirky horse.js has a huge Twitter following. Jasmine and her co-worker used a combination of machine learning, data statistics and other methods to work out who horse.js is. At the latest JSConf they gave a presentation that explained how they did it. At the end, there was a pre-planned piece of pantomime, where the organizers would shoo them off of the stage before they could reveal who it was. Clearly, some in the audience thought they were going to uncover horse.js, which they definitely were not. They actually got booed off and ended up leaving the conference venue through the back entrance. Despite this, the project and speech were great fun for Jasmine. It gave her the chance to work collaboratively with her team using JavaScript. A language she rarely gets to work in. Plus, they produced a website about the process and the person they had concluded was horse.js agreed to having his name revealed on the site. Although he has still not confirmed or denied being horse.js. Basically, it was a fun project, that stretched Jasmine, helped her to gel with her team and become better known in the community. So, it has been a career highlight on many different levels. (14.00) – Can you tell us what excites you about the future of the IT industry and careers? The fact that if she wanted to try something else in the industry there are so many different paths she could take excites Jasmine. Her background is mostly software engineering, but she also now has her developer advocate and relations work to add into the mix. Jasmine especially enjoys being a part of a “choose your own adventure” style of team. If you are good at speaking, that can be your focus, while someone else might write a lot of code or seek out feedback from product teams. Jasmine is also excited by the fact that working for Microsoft automatically opens up all kinds of possibilities. She can easily move internally to try something different or take up an opportunity outside the business. She also enjoys the fact that the information you need to learn something new is now freely available. You just need to find a tutorial or blog post and get started.  (15.54) – What drew you to a career in IT? For Jasmine, her journey into IT started when she wanted to customize her GeoCities, Neopets and MySpace accounts. Making little sites for herself was the spark. The fact that she wanted to be a meteorologist also pusher her into the IT world. It was part of the reason she decided to minor in computer science. She liked it so much that she ended up switching her major. (16.52) – What is the best career advice you have ever received? Don’t be afraid to ask questions. If you don’t you are not doing your job properly. Asking questions is tricky because you have to admit you don’t know something. But, it is essential. You end up feeling so much worse if you get things wrong because you did not seek clarification.  (17.21) – If you were to begin your IT career again, right now, what would you do? Jasmine says she would probably get involved in the IT security field. Probably as a white hat hacker, right now, it is a really interesting sector to work in. (17.55) – What clear objective are you currently focusing on? Jasmine is now part of a fresh team that is focused on reaching out to the education community. Currently, she is looking for ways in which she can shine in this role. She is looking for ways to self-advocate and progress the team's objectives at the same time. (19.12) – What is the number one non-technical skill that has helped you the most in your IT career, so far? Being an effective communicator has been essential for Jasmine. She mostly works remotely, so has to be particularly careful to communicate well. It is essential to tailor what you are saying to take account of the audience you are speaking to. You have to adapt your approach to ensure that what you are saying is easy to digest and understand. Jasmine has found that getting involved in things like hobby channels has helped her with this. Sharing tips, suggestions, jokes and things in a casual setting has helped her to hone her communication skills. (20.58) – Phil asks Jasmine to share a final piece of career advice with the audience. She says it is the same as the advice she received – Don’t be afraid to ask questions. It is the only way to get the clarification you need to be able to move forward. If you do not get into this habit you will very likely stall. At first, you may feel embarrassed doing it. But, it is like a muscle. The more you do it the easier it gets. Phil says that he has also found this to be true. He has noticed that the more questions you ask the more confident you become, which is the opposite of what you might expect. BEST MOMENTS: (6.22) JASMINE – "Sometimes it's just, you know, one little thing that they just need to clear the air on to get them to where they need to be." (7.23) PHIL – "break down that objective into smaller chunks, so that it becomes easier to understand.” (14.23) JASMINE – "If I wanted to try something else in the industry, there are so many paths I can take." (16.54) JASMINE – "If you’re not asking questions, you’re not doing your job." (21.55) PHIL – "The more you ask questions, the more confident you get.”   CONTACT JASMINE: Twitter: https://twitter.com/paladique LinkedIn: https://www.linkedin.com/in/jasminegreenaway Github: https://github.com/paladique  

Nous discutons des Azure Durables Functions avec Maxime Rouiller, Cloud Developer Advocate chez Microsoft.  Les fonctions durables sont une extension des fonctions Azure qui permettent de garder état dans un environnement serverless. Bio anglaise: I've been in the tech industry since the 2000s. I've always been working with .NET for as far as I can remember. I've built my profile on being a master of all trade. I've setup VMs, SharePoint environments, built servers and what not. I've coded from desktop apps to server apps, but I've truly found my passion around the web, however. Since then, I've been consulting independently for 3 years before seeing an opportunity to join Microsoft. I co-manage a local user group in Montreal, I own my own blog. Liens "Ugly Christmas sweater" de Microsoft Les "Cloud Advocates" de Microsoft aka.ms/DurableFunctionsSample aka.ms/DurableFunctionsNodeSample aka.ms/ServerlessMixtape Formation Azure de Guy  

How to you scale a startup, a mid size company or an enterprise software organization? Can we learn from the Spartans or the Romans? And how can we explain DevOps to a Dummy?In this fun filled episode with Emily Freeman (@editingemily), Cloud Developer Advocate at Microsoft, we get answers to all these questions and get inspired to join Emily’s appearance at the upcoming devone.at conference in Linz, Austria where she dives deeper into how to successfully scale development organizations from startup to enterprise. Later in 2019 make sure to watch out for the written version of our discussion on DevOps for Dummies – Emily is using her writing skills to bring it to paper!https://emilyfreeman.io/

How to you scale a startup, a mid size company or an enterprise software organization? Can we learn from the Spartans or the Romans? And how can we explain DevOps to a Dummy?In this fun filled episode with Emily Freeman (@editingemily), Cloud Developer Advocate at Microsoft, we get answers to all these questions and get inspired to join Emily’s appearance at the upcoming devone.at conference in Linz, Austria where she dives deeper into how to successfully scale development organizations from startup to enterprise. Later in 2019 make sure to watch out for the written version of our discussion on DevOps for Dummies – Emily is using her writing skills to bring it to paper!https://emilyfreeman.io/

Christina Warren, tech commentator, podcaster and Cloud Developer Advocate at Microsoft drops by to talk about using a Mac at work, the state of PowerPoint and how to get the most out of tech when traveling the world.

This episode of HashiCast features Zachary Deptawa, Cloud Developer Advocate at Microsoft, and Christie Koehler, Developer Advocate at HashiCorp. Join us as we talk to Zachary and Christie about their careers and experiences in the technology field.

David Smith (@revodavid) is the Cloud Developer Advocate and R Community Lead at Microsoft. Prior to Microsoft, David was the Chief Community Officer (and is current editor-in-chief) of Revolution Analytics, a daily news about using open source R for big data analysis, predictive modeling, data science, and visualization since 2008.David has a knack for building user communities and is currently the Vice President of Community for REvolution Computing, David focuses on promoting and supporting the commercial use of the open-source data analysis software system R.David is a co-author of the tutorial manual An Introduction to R, one of the originating developers of ESS: Emacs Speaks Statistics and is also a member of the board of the R Consortium.You can listen right here on iTunesIn our wide-ranging conversation, we cover many things, including: * The ethical problems of analyzing data * Why AI will affect so many massive industries * How governments need to start thinking about AI/ML * The reason David thinks artificial intelligence will create more jobs than it destroys * Why we're still decades off from artificial general intelligence * The tech giant effect on AI and data science * How Microsoft is leading the way towards tech future * David's thoughts on the future of tech monopolies * Why the battle for the future is based on attracting developers * Where cloud computing is headed from here * Why open ecosytems and opensource almost always wins--Make a Tax-Deductible Donation to Support FringeFMFringeFM is supported by the generosity of its readers and listeners. If you find our work valuable, please consider supporting us on Patreon, via Paypal or with DonorBox powered by Stripe.Donate   

Jeremy Likness is a Cloud Developer Advocate for Azure at Microsoft. Jeremy has spent two decades building enterprise software with a focus on line of business web applications. He is the author of several highly acclaimed technical books including Designing Silverlight Business Applications and Programming the Windows Runtime by Example. He has given hundreds of technical presentations during his career. In his free time Jeremy likes to run, hike, and maintain a 100% plant-based diet.

Cecil Phillip is a software developer with almost a decade of experience with creating enterprise grade software solutions. Over his career, he has specialized in creating solutions using web technologies, .NET and Microsoft Azure. Today, he's employed by Microsoft as a Cloud Developer Advocate where he helps guide developers in moving their applications to the cloud. He also a passion for software architecture, testing and API design. Cecil currently resides in South Florida, but he stays very connected to his Caribbean roots. Links: Website: http://cecilphillip.com  Github - @cecilphillip Twitter - @cecilphillip  Podcast - http://awayfromthekeyboard.com 

Christina interviews Ruth Yakubu, a CDA focused on Java, AI, and cloud analytics. In this one-on-one interview, Ruth shares how she became interested in tech, and the career path that led her to Microsoft.In addition to her technical work, Ruth is also a fashion and beauty obsessed entrepreneur. She shares the journey with her bootstrapped startup, Poshbeauty.com. Ruth discusses some of the challenges with launching a startup, while also working a day job as an engineer.Ruth also shares her thoughts on how we can encourage younger women to enter tech and entreprenurship.You can (and should!) follow Ruth on Twitter @ruthieyakubu

Christina interviews Ruth Yakubu, a CDA focused on Java, AI, and cloud analytics. In this one-on-one interview, Ruth shares how she became interested in tech, and the career path that led her to Microsoft.In addition to her technical work, Ruth is also a fashion and beauty obsessed entrepreneur. She shares the journey with her bootstrapped startup, Poshbeauty.com. Ruth discusses some of the challenges with launching a startup, while also working a day job as an engineer.Ruth also shares her thoughts on how we can encourage younger women to enter tech and entreprenurship.You can (and should!) follow Ruth on Twitter @ruthieyakubu

Damian's Bio: Damian is a Cloud Developer Advocate specializing in DevOps. After spending a year in Toronto, Canada, he returned to Australia – the land of the dangerous creatures and beautiful beaches – in 2018. Formerly a dev at Octopus Deploy and a Microsoft MVP, he has a background in software development and consulting in a broad...

Damian’s Bio: Damian is a Cloud Developer Advocate specializing in DevOps. After spending a year in Toronto, Canada, he returned to Australia – the land of the dangerous creatures and beautiful beaches – in 2018. Formerly a dev at Octopus Deploy and a Microsoft MVP, he has a background in software development and consulting in a broad...

Jasmine Greenaway is a Cloud Developer Advocate in the Microsoft Azure Organization. She spends her days presenting at conferences and helping our product teams make .NET the best developer platform for building all your apps. Jasmine has had Software Engineer roles at Sears, Rockstar Games and GitHub. Watch this episode to learn more about her journey to Microsoft.GALs is a show about the women who work in Tech (at Microsoft or outside) from three ladies that currently work on the Channel 9 team. Golnaz Alibeigi, Soumow Atitallah, and Kaitlin McKinnon have started a new series featuring women in Tech who work in development, management, marketing and research who have interesting stories to share about their success in the industry and ideas on how to grow diversity in IT.Follow @CH9Follow @Golnaz89Follow @Paladique

Jasmine Greenaway is a Cloud Developer Advocate in the Microsoft Azure Organization. She spends her days presenting at conferences and helping our product teams make .NET the best developer platform for building all your apps. Jasmine has had Software Engineer roles at Sears, Rockstar Games and GitHub. Watch this episode to learn more about her journey to Microsoft.GALs is a show about the women who work in Tech (at Microsoft or outside) from three ladies that currently work on the Channel 9 team. Golnaz Alibeigi, Soumow Atitallah, and Kaitlin McKinnon have started a new series featuring women in Tech who work in development, management, marketing and research who have interesting stories to share about their success in the industry and ideas on how to grow diversity in IT.Follow @CH9Follow @Golnaz89Follow @Paladique

In this episode of GALs, Golnaz sits down with Kris Nova to learn more about the girl behind the code.Kris Nova has been involved with free and open source software since hacking her parents computer as a child. She spends a lot of time contributing in the Go, Kubernetes, and Container open source spaces, and has a deep passion for building communities. She recently joined Microsoft as a Cloud Developer Advocate focusing on Linux and Containers. Watch the video to learn more about her journey to Microsoft.You can learn more about her Open Source work on her GitHub page, her blog nivenly.com or via twitter Follow @Kris__Nova.

In this episode of GALs, Golnaz sits down with Kris Nova to learn more about the girl behind the code.Kris Nova has been involved with free and open source software since hacking her parents computer as a child. She spends a lot of time contributing in the Go, Kubernetes, and Container open source spaces, and has a deep passion for building communities. She recently joined Microsoft as a Cloud Developer Advocate focusing on Linux and Containers. Watch the video to learn more about her journey to Microsoft.You can learn more about her Open Source work on her GitHub page, her blog nivenly.com or via twitter Follow @Kris__Nova.