Podcast
Herding Code
Hosted by Herding Code · EN
A technology podcast with Jon Galloway, Scott Allen, Kevin Dente, Scott Koon
20episodes
Episodes
Newest firstAll episodes
Herding Code 241: The Freaky Friday macOS / Windows Switch
Apr 16, 2020Tap to summarizeRecently Jon switched to developing on macOS, and Rob’s been developing on Windows. It’s time for the Freaky Friday edition! The guys compare notes, what they like, what’s confusing, and what they’ve learned. Download / Listen: Herding Code 241: The Freaky Friday macOS / Windows Switch https://herdingcode.com/wp-content/uploads/HerdingCode-0241-Freaky-Friday.mp3 Links: HomebrewOhMyZSHGitHub CLIAZX.ms Transcript: Kevin: [00:00:08] Hello and welcome to Herding Code. This episode is being recorded on eight April, April 3rd. Is that right? 2028 or is it still March? I feel like it’s still March. Rob: [00:00:19] Kevin. That was smooth, man. You should do this for a living. Kevin: [00:00:24] And I am joined today by, smart ass, Rob Conery and, and Jon Galloway. Jon: [00:00:30] Hello. Kevin: [00:00:31] Okay. And we are here today to talk about, transitioning between Mac and Windows. Jon recently made a, a life change and, is doing more work on the Mac side and Rob has, recently transitioned over, do more Windows stuff. So we thought it’d be fun to talk about how those switches went. Jon wanted, why don’t you, sorry, go ahead. Jon: [00:00:51] we’re calling this, this is the freaky Friday edition. Kevin: [00:00:54] right. Rob and Jon have switched over. Jon: [00:00:56] Over. On a Friday. Yes. Yup. Yeah. So I recently switched to , I’m working, I’m working with the VS for Mac team. I’m kinda like, I’m like, so it’s a little bit less, I don’t know. So my, my role really is just like dotnet dev on a Mac. So, but you know, mostly looking at, Visual Studio for Mac. Yeah. So that’s been fun. I’ve been doing most of my dev work on, on Mac for the past several months, and, and, yeah. Kevin: [00:01:25] So for people who don’t know, like what is, what is Visual Studio for Mac, like what, what’s the kind of the backstory there. <st...
Transcribe →Herding Code 241: The Freaky Friday macOS / Windows Switch
Apr 16, 2020Tap to summarizeEpisode 241 Recently Jon switched to developing on macOS, and Rob's been developing on Windows. It's time for the Freaky Friday edition! The guys compare notes, what they like, what's confusing, and what they've learned. Download / Listen: Herding Code 241: The Freaky Friday macOS / Windows Switch Links: HomebrewOhMyZSHGitHub CLIAZX.ms Transcript: Kevin: [00:00:08] Hello and welcome to Herding Code. This episode is being recorded on eight April, April 3rd. Is that right? 2028 or is it still March? I feel like it's still March. Rob: [00:00:19] Kevin. That was smooth, man. You should do this for a living. Kevin: [00:00:24] And I am joined today by, smart ass, Rob Conery and, and Jon Galloway. Jon: [00:00:30] Hello. Kevin: [00:00:31] Okay. And we are here today to talk about, transitioning between Mac and Windows. Jon recently made a, a life change and, is doing more work on the Mac side and Rob has, recently transitioned over, do more Windows stuff. So we thought it'd be fun to talk about how those switches went. Jon wanted, why don't you, sorry, go ahead. Jon: [00:00:51] we're calling this, this is the freaky Friday edition. Kevin: [00:00:54] right. Rob and Jon have switched over. Jon: [00:00:56] Over. On a Friday. Yes. Yup. Yeah. So I recently switched to , I'm working, I'm working with the VS for Mac team. I'm kinda like, I'm like, so it's a little bit less, I don't know. So my, my role really is just like dotnet dev on a Mac. So, but you know, mostly looking at, Visual Studio for Mac. Yeah. So that's been fun. I've been doing most of my dev work on, on Mac for the past several months, and, and, yeah. Kevin: [00:01:25] So for people who don't know, like what is, what is Visual Studio for Mac, like what, what's the kind of the backstory there. Jon: [00:01:33] Yeah. Well, so this is confusing, right? So there is Visual Studio for Windows that's been around since it was, I dunno, Interdev or whatever. They'll, you know what I mean? It's like early, late nineties, early two thousands, whatever. It's been around quite a long time. Then, there was. There was Mono, there was Mono Develop, and then Mono became Xamarin and they had Xamarin studio and it was really focused on building Xamarin products. And then with the acquisition of, of Xamarin by Microsoft, and then they've kind of productized it into Visual Studio and some of the, you know, like over time. Mono develop Mono is change. Like, so originally it was this cross platform, it was all GTK. It was, There's some tradeoffs to doing that, you know, like in being fully open source cross platform thing too. Like there's not the same kind of quality stability kind of things that you can get out of Visual Studio for Windows. So that's been a lot of the focus. And then the other. Visual studio is Visual Studio Code. And that confuses people. Like, cause we've done things where we'll do like a customer interview and it's like, okay, we're talking to a team that works on Visual Studio for Mac. And then we'll talk to them. And they're like, yeah, I'm on my Mac using Visual Studio Code and you know, and we're like, Oh, okay. Well, so, you know, and that's partly our fault. Like branding and naming is hard. but the idea is Visual Studio Code is like a lightweight editor. You know, it's quick startup. It doesn't, it doesn't have a whole lot of bells and whistles. which is fine for a lot of people that just want to type code and that code really fast. And then there are a bunch of extensions for it. And it's cross platform and open source. And then the idea is, you know, Visual Studio for Windows and Visual Studio for Mac. The idea is more of a. Integrated developer environment. So something where you're, you know, you're going to have more like project templates and scaffolding built in and, and you know, more debuggers and analyzers and, and, that kind of stuff. So, so that's kinda, you know, the difference between the two. Kevin: [00:03:43] Okay. So. Why don't you give us like the quick, you know, like what was the initial transition to being a, a, a real Mac user like for you? Like what were the, what were the, what was the pain points? What was frustrating? What'd you love. Rob: [00:03:59] It was. It was joyous to watch this go down on Twitter, I have to say. Jon: [00:04:04] Okay. Well, so let me give him my full Apple back story. I learned to, I learned to program on an Apple ][ in high school for summary. We had somebody that was a previous Apple exec. Like was part of the board of my school or whatever. And so we had all these Macs. So I was actually like the high school Mac geek and I was, I was doing all this, like I was way into HyperCard and I just loved all the Mac stuff. And then over time I went to college, I'm like, what's this Windows crap where you have to do Windows? And so whatever. I learned some Windows and you know, over time it's, it's, I've had like two brains to it because. There's undeniably like Apple hardware and most software is like the fit and finish is just beautiful and it all just works really well. And there's all, it's like just this one kind of. There's only, you know, one of them. So like they, they test it and make sure it's perfect and it works. And then Windows is kinda, yeah, it's been different. There's, you know, registries and I don't know, there's all kinds of stuff, but I got used to it. Right. So, and then kind of more recently I was looking at my Twitter history cause I was asking stuff about Homebrew and I was like, you know, I was, I would say at Microsoft when .NET Core first was becoming a thing. It was first K project K, and then it was DNX, and then it was, .NET Core, and now it's going back to just .NET. but anyhow, that part of the thing with that was it was cross platform. And so I, I, for a while traveled with two laptops everywhere. You know, I had a Windows laptop and a Mac book air, and I would, you know, pop it out and say like, here's my quick little demo, see it runs.NET core. And then I would put the laptop back away and go back to Windows. You know, I mean, we really like, it was air quotes worked on Mac, but it didn't, I don't know. We didn't really do much with it, you know, we just made sure it compiled and ran, but there was no like IDE for it or editor. And there wasn't much that you could really. You know, w the most, I would say most of Microsoft presenters when they said it runs on Mac, that's about all they do is like, okay, we're done. Rob: [00:06:19] yeah, the punchline, the forever punchline. Jon: [00:06:22] Right. And runs on a Mac. I did have one experience with that though. I was in Moscow speaking at a conference. I was actually doing a, I had like a little five minute, five or 10 minute thing in a keynote at a conference here, and I had my Windows machine and my Mac. And I spilled coffee. I was like sitting in my hotel room. I'm like, I am so ready for this. I've got all these demos ready and everything. I spilled coffee on my Windows machine. And it got into the keyboard and like I could very quickly like turned it upside down, put towels on and everything, and I'm like, okay, it's working fine, it's working fine. Going through, I start typing and I'm like, huh, the letter N isn't actually responding on my keyboard. And then slowly like there is liquid inside the keyboard. It's like slowly like other keys stop working, you know? And I am in full panic mode. Cause I actually had a tech check that afternoon in the keynote the next day and I'm in Moscow. Like, I don't know what to do, you know, and then I'm like, wait a minute, I bet I could do most of these demos on the Mac. And then I, I, I was like, wait a minute, this is an Azure demo. I can do this. I can, I can totally spin it. This is Docker. I can do that, you know? And I was like, I can do this entire thing on Mac. So. Yeah. So that was that. so anyhow, more recently, I, Kevin: [00:07:44] Jon Jon, do you realize that it was your subconscious that made you spill that coffee? Right? It was. Jon: [00:07:51] you should have seen the panic though. I was like, Oh, no, what are we gonna do? So, yeah, so I, I got this MacBook in September and I did the standard stuff. I've always done like I, so the first one I got was a loner and it was previously an intern had it. And I went through and did all the, you know, I got my old scripts, my, my Homebrew, and I did all my stuff and I just, you know, and then, and then I got the real nice one in January. And that was actually where Rob and I started having a conversation. Cause I. was like, do I even need Homebrew and do I need, what's, what's like, I've just always been doing stuff the same way and maybe there's, I don't even, you know, I'm not like a week-in, week-out Mac dev user. So I guess some of some of the stuff that was interesting to me is kind of figuring out the best way to insta...
Transcribe →Herding Code 240: Phil Haack on Working from Home
Mar 25, 2020Tap to summarizeDownload / Listen: Herding Code 240: Phil Haack on Working from Home https://herdingcode.com/wp-content/uploads/HerdingCode-0240-Phil-Haack.mp3 Jon, Kevin, and Rob talk to Phil Haack about working from home. Links: How To Work From HomeHow to Lead From HomeGeographically Distributed Teams When Remote Work Goes WrongHerding Code Podcast on Twitter: “We’re going to be talking to @haacked today about working from home. Questions or comments for him?” / TwitterAmazon.com : TRX ALL-IN-ONE Suspension Training: Bodyweight Resistance System | Full Body Workouts for Home, Travel, and Outdoors | Build Muscle, Burn Fat, Improve Cardio | Free Workouts Included : Home Gyms : Sports & OutdoorsWork in the Time of Corona – Alice GoldfussBe This Manager Now – Nicole Sanchez – MediumHerding Code 63: Victory in Software Development with K Scott Allen – Herding Code Transcript: Note: We’re new at this. Should we publish an SRT file? WEBVTT? Jon: [00:00:00] Welcome to Herding Code. This episode is being recorded March 24 2020. This is Jon Galloway. Kevin: [00:00:16] This is Kevin Dente. Rob: [00:00:17] This is Rob Conery. Jon: [00:00:19] Hey, and today we’re talking to Phil Haack working from home. So before we jump into that, Scott Allen, when one of our hosts passed away in January, and I, I’m sure most of our listeners have probably a...
Transcribe →Herding Code 240: Phil Haack on Working from Home
Mar 25, 2020Tap to summarizeEpisode 240 Download / Listen: Herding Code 240: Phil Haack on Working from Home Jon, Kevin, and Rob talk to Phil Haack about working from home. Links: How To Work From HomeHow to Lead From HomeGeographically Distributed Teams When Remote Work Goes WrongHerding Code Podcast on Twitter: "We're going to be talking to @haacked today about working from home. Questions or comments for him?" / TwitterAmazon.com : TRX ALL-IN-ONE Suspension Training: Bodyweight Resistance System | Full Body Workouts for Home, Travel, and Outdoors | Build Muscle, Burn Fat, Improve Cardio | Free Workouts Included : Home Gyms : Sports & OutdoorsWork in the Time of Corona – Alice GoldfussBe This Manager Now - Nicole Sanchez - MediumHerding Code 63: Victory in Software Development with K Scott Allen – Herding Code Transcript: Note: We're new at this. Should we publish an SRT file? WEBVTT? Jon: [00:00:00] Welcome to Herding Code. This episode is being recorded March 24 2020. This is Jon Galloway. Kevin: [00:00:16] This is Kevin Dente. Rob: [00:00:17] This is Rob Conery. Jon: [00:00:19] Hey, and today we're talking to Phil Haack working from home. So before we jump into that, Scott Allen, when one of our hosts passed away in January, and I, I'm sure most of our listeners have probably already seen that. But, you know, I don't even know what to say. K Scott was an amazing friend, and, we were just so lucky to have him on the show for so many years. Some, some people recommended one of their favorite episodes was episode 63. Rob, I think you brought that one up. That was Victory in Software Development. Rob: [00:00:52] Oh man that was amazing. Jon: [00:00:54] And he was telling the story of the battle of Antietam and, man, I could listen to that show over and over. You know, yeah. Rob: [00:01:02] One thing I was trying to explain to my wife. Cause she, when I told her the news, she, she was like, Oh, right. You knew him. And I started to explain, what, what case Scott was, to me and to everyone. I mean, I've never known anyone with such an insane gift for telling a story. And, and just being affable, and kind. Anyway, I started to tell her about just him and she's like, oh right. We, we met him and went hiking with him in Oslo, and I totally forgot, but it was so cool because it just, all of a sudden, the memory of, of hiking with him, this last June, NDC, Oslo, was just kind of the spur of the moment that he was running downstairs. He and Richard Campbell were going on a hike and they're like, Hey, come with us. And I said, Oh, sure. And that was the last time I ever saw him. And. I can't say enough what a great person. he was, and I, I really, I think we're all the better for knowing him for sure as an industry, but also as people. Jon: [00:02:02] Yeah, I just, looking on Twitter, you know, I always of him as one of my best friends, and he always took time, you know, like when we're at, at a conference or whatever, he'd say like, Hey, Jon, let's, you know, let's go grab a bite and we're just whatever, and we'd just go hang out. And, It was Phil: [00:02:18] Yeah Jon: [00:02:19] seeing how he was very intentional about doing that with so many people, you know, like just everyone kind of sharing their stories about, you know, including people that were like, I him a question at a conference and it was kind of a random question and he spent a lot of time just talking it through with me and you know, like it just, yeah, just so thoughtful and kind. Phil: [00:02:40] Okay Yeah. I really loved talking to him at conferences. I'd only see him in places like London or, or, you know. Oslo or wherever at conferences. Jon, you might remember that, you mean Atwood and, Barnett wrote a book with, Scott Allen a long time ago Jon: [00:02:58] Yeah. Yep. Phil: [00:02:59] The ASP.NET 2.0 anthology And I don't mean the MVC I mean like Jon: [00:03:06] 2.0 Yup Phil: [00:03:11] Yeah, that's right. Jon: [00:03:14] Oh man. Yeah. I actually co-wrote several, cause I picked up that, the MVC book, the five heads book, Rob, that you worked on. And then I, you know, K Scott stayed on for several additions of that and I co-wrote with him. So, Phil: [00:03:26] Okay Jon: [00:03:27] and you know, it was always like I was, I for some reason signed myself up as lead author and I was always chasing down other coauthors and K Scott is like, I always knew that his was just going to be like. You know, on time and perfect. And it's nothing to worry about. Phil: [00:03:43] Yup. Jon: [00:03:44] Yeah. Oh, man. Well, so, Phil: [00:03:49] On that note. Jon: [00:03:50] yeah. Yeah. Well, so these are, these are times. We're all, we're all bunkered down from, from this coronavirus and, You know, people have been talking about working from home. you know, Microsoft has sent everybody home. A lot of other large companies have. and then after that, a lot, a lot of States have gone into and different countries to have gone into some sort of lockdown as well. so we've got, all of us have worked remotely, for a good chunk of our careers. And so Phil: [00:04:22] Okay Jon: [00:04:23] it's been interesting seeing people trying to adapt to it in different, different companies and stuff. So Phil, you wrote a series of blog posts about how to work from home. so for people that don't know you, which is probably nobody, but for people that don't know, what's kind of your background on, how did you transition into working from home. Phil: [00:04:41] Oh, that's a great question. So probably the first time I did a work from home significantly with a long time ago when I started a company with a friend, and Jon, you might remember this, called VelocIT that we hired, Jon was our first employee. And we all work together using the state of the art of collaboration software back then, groove, by Ray Ozzie. Jon: [00:05:05] that's right. Phil: [00:05:07] yeah. And, and then we would use a, I forget what the video conference software, but like, we actually, you know, cobbled together.. Jon: [00:05:15] amount Phil: [00:05:16] Yeah, that's right. It's Skype was around. Then we use Skype and I think we use subversion for the version control. And, you know, we made it work. We did a pretty good job as a remote distributed company, but we were only like, you know, three, four employees, you know, at the time. And then I remember we hired a, Steve Harmon came on and, and, so Simone, but anyways, and then, you know, I went after that, I joined. Microsoft, and that was, you know, right back into being in the office all the time. AI did have this one, coworker who was remote, Scott Hanselman, who, you know, we would try to set up a computer in my office so that he could just dial in at any time and be like a talking head there. Rob: [00:06:01] Okay Phil: [00:06:02] But it was really interesting to, you know, like when I think about those times and how difficult. it must've been for him to be a remote employee in a company that just really didn't get it. And you could tell they didn't get it because their products didn't reflect, what it meant to be remote work. so I left Microsoft after about four years and I joined GitHub and the GitHub was, you know, just night and day, right? This is a company that really. Started off as sort of a remote distributed company. It had it in its DNA and its tools really reflected that as well. In fact, they were really geared towards, you know, teams of open source developers who were all strewn about all over the world, didn't know each other. And I worked there for just shy of seven years. I was started off as a developer. And then, this is at a time when GitHub, didn't even have managers. And then later when they introduced managers, I...
Transcribe →Herding Code 239: Jerome Laban on Uno Platform
Sep 10, 2019Tap to summarizeDownload / Listen: Herding Code 239: Jerome Laban on Uno Platform https://herdingcode.com/wp-content/uploads/HerdingCode-0239-Jerome-Laban.mp3 At Xamarin Developer Summit, Jon talks with Jerome Laban about building applications that run everywhere using the Uno Platform. (00:20) Jerome explains that the Uno Platform is XAML and C# for iOS, Android and WebAssembly using WinUI XAML. On iOS and Android, it’s running on Xamarin.(01:25) Jerome tells the history of the platform, and how they’ve been working on the platform for six years. When the team at nventive saw WebAssembly support coming, they ported their existing framework to run there, too. (02:55) The Uno Platform is free and open source; nventive is a service agency that offers development and support for the platform. Jon asks for more information about nventive. It started as a training and general development company, then did Windows Phone, Windows 8 and Windows 10 applications. When Windows Phone went away, they moved their focus to Xamarin development, predating Xamarin Forms. They believe the strucucture of Uno and UWP is often a better approach for them than Xamarin Forms.(04:55) Jon asks for the relationship between Uno and Xamarin Forms. Jerome explains that they’re generally at the same layer. However, since Uno implements the UWP contract, anything that targets the UWP contract can run on Uno. Xamarin Forms has a part that implements that contract to run on Windows. So… a Xamarin Forms can run on WebAssembly using Uno. You can run Uno components in a Xamarin app, since Uno components are actually Xamarin classic components. You can also run Xamarin components in an Uno application.(07:00) Jon asks how the XAML front end is run in the browser. Jerome says that Uno renders the XAML as HTML elements. If you view source, it’s mostly div’s. HTML is treated as a subsystem that’s abstracted away.(08:37) Jon asks about the Calculator application. The Uno team took the Microsoft open source calculator application, written in C++ and XAML, and got it to run on Uno. Jon was very impressed to bring it up on his phone’s browser. Jerome says that works on Android in the browser, and there are also Android and iOS applications.(09:35) Jon asks how they ported Calc to Uno. Jerome said that the tricky part was to pinvoke into C and C++ from a WebAssembly module – Jerome had to add that support and submitted t...
Transcribe →Herding Code 239: Jerome Laban on Uno Platform
Sep 10, 2019Tap to summarizeEpisode 239 Download / Listen: Herding Code 239: Jerome Laban on Uno Platform At Xamarin Developer Summit, Jon talks with Jerome Laban about building applications that run everywhere using the Uno Platform. (00:20) Jerome explains that the Uno Platform is XAML and C# for iOS, Android and WebAssembly using WinUI XAML. On iOS and Android, it's running on Xamarin.(01:25) Jerome tells the history of the platform, and how they've been working on the platform for six years. When the team at nventive saw WebAssembly support coming, they ported their existing framework to run there, too. (02:55) The Uno Platform is free and open source; nventive is a service agency that offers development and support for the platform. Jon asks for more information about nventive. It started as a training and general development company, then did Windows Phone, Windows 8 and Windows 10 applications. When Windows Phone went away, they moved their focus to Xamarin development, predating Xamarin Forms. They believe the strucucture of Uno and UWP is often a better approach for them than Xamarin Forms.(04:55) Jon asks for the relationship between Uno and Xamarin Forms. Jerome explains that they're generally at the same layer. However, since Uno implements the UWP contract, anything that targets the UWP contract can run on Uno. Xamarin Forms has a part that implements that contract to run on Windows. So... a Xamarin Forms can run on WebAssembly using Uno. You can run Uno components in a Xamarin app, since Uno components are actually Xamarin classic components. You can also run Xamarin components in an Uno application.(07:00) Jon asks how the XAML front end is run in the browser. Jerome says that Uno renders the XAML as HTML elements. If you view source, it's mostly div's. HTML is treated as a subsystem that's abstracted away.(08:37) Jon asks about the Calculator application. The Uno team took the Microsoft open source calculator application, written in C++ and XAML, and got it to run on Uno. Jon was very impressed to bring it up on his phone's browser. Jerome says that works on Android in the browser, and there are also Android and iOS applications.(09:35) Jon asks how they ported Calc to Uno. Jerome said that the tricky part was to pinvoke into C and C++ from a WebAssembly module - Jerome had to add that support and submitted the pull request to Mono. There are three parts - a calculation that dates back to 1999 / Windows 3 that is all C and C++ code that they didn't change; the rest is C++ 11 code which they translated to C# using regular expressions. The XAML and resources are the same.(12:20) The Calculator is in published in 65 languages, so they are getting bug reports in 65 languages. There's good accessibility support, so for instance you can enable voiceover in the mobile application.(13:10) Jon asks how to build an application for Uno Platform. Jerome explains the File / New Project process using the extension.(13:55) Jon asks about deployment. For iOS and Android, the output is the same as any Xamarin project; it's just a standard UWP application, and for WebAssembly it currently tags along with the Blazor tooling.(15:00) Jon asks about other getting started information. Jerome runs through several, and points to the GitHub repo for more links.(16:20) Jon wraps up with a callout to UnoConf on September 19-20, as well as plans for a 2020 UnoConf in the works. Links: https://platform.uno/ https://github.com/unoplatform/calculator https://unoconf.com/
Transcribe →Herding Code 238: Martin Beeby on AWS for .NET Developers
Jun 24, 2019Tap to summarizeDownload / Listen: Herding Code 238: Martin Beeby on AWS for .NET Developers https://herdingcode.com/wp-content/uploads/HerdingCode-0238-Martin-Beeby.mp3 At DevSum Stockholm, Jon talks with Martin Beeby about .NET development on AWS. (00:20) The guys reminisce about Martin’s awesome blog post, Client Requests Through the Years. (03:30) Martin walks us through his career, which includes early adoption of .NET, stepping away for a bit to pursue Node and Java development, and returning to the .NET fold in his current role as a Developer Evangelist focused on .NET for AWS.(08:00) Martin shares to how other developers are returning to .NET and the freshness in the community. .NET developers are progressive with AWS and large systems.(10:40) Martin speaks to his evangelism roles with Microsoft, Oracle and now AWS. Spoiler alert. It’s not just standing at a booth, but real-world storytelling of customer use cases and encouraging platform adoption.(13:15) Jon and Martin talk about the intersection of AWS and .NET development in which AWS is the original cloud hosting option so there are highly skilled, highly progressive .NET shops along with AWS experts that are new to .NET, and .NET developers who are completely new to AWS and cloud computing. (16:35) Jon asks about the fastest way for a .NET developer to get up and running on AWS. Martin talks to the AWS SDK for .NET and AWS Toolkit for Visual Studio, which is an extension that features the AWS Explorer. (18:40) Martin explores AWS deployment options including CLI scripting, AWS CloudFormation Templates, Cloud Development Kit, AWS extensions for CI/CD tools like Jenkins, AWS’s own suite of CI/CD tooling and even Powershell.(20:35) Jon asks about AWS Lambda. Martin touches upon other hosting options including Elastic Beanstalk and containers and then digs into serverless.(22:35) Martin shares how one can spin up a full-blown application which leverages serverless infrastructure using AWS Visual Studio Tools. It’s something along the l...
Transcribe →Herding Code 238: Martin Beeby on AWS for .NET Developers
Jun 24, 2019Tap to summarizeEpisode 238 Download / Listen: Herding Code 238: Martin Beeby on AWS for .NET Developers At DevSum Stockholm, Jon talks with Martin Beeby about .NET development on AWS. (00:20) The guys reminisce about Martin’s awesome blog post, Client Requests Through the Years. (03:30) Martin walks us through his career, which includes early adoption of .NET, stepping away for a bit to pursue Node and Java development, and returning to the .NET fold in his current role as a Developer Evangelist focused on .NET for AWS.(08:00) Martin shares to how other developers are returning to .NET and the freshness in the community. .NET developers are progressive with AWS and large systems.(10:40) Martin speaks to his evangelism roles with Microsoft, Oracle and now AWS. Spoiler alert. It’s not just standing at a booth, but real-world storytelling of customer use cases and encouraging platform adoption.(13:15) Jon and Martin talk about the intersection of AWS and .NET development in which AWS is the original cloud hosting option so there are highly skilled, highly progressive .NET shops along with AWS experts that are new to .NET, and .NET developers who are completely new to AWS and cloud computing. (16:35) Jon asks about the fastest way for a .NET developer to get up and running on AWS. Martin talks to the AWS SDK for .NET and AWS Toolkit for Visual Studio, which is an extension that features the AWS Explorer. (18:40) Martin explores AWS deployment options including CLI scripting, AWS CloudFormation Templates, Cloud Development Kit, AWS extensions for CI/CD tools like Jenkins, AWS’s own suite of CI/CD tooling and even Powershell.(20:35) Jon asks about AWS Lambda. Martin touches upon other hosting options including Elastic Beanstalk and containers and then digs into serverless.(22:35) Martin shares how one can spin up a full-blown application which leverages serverless infrastructure using AWS Visual Studio Tools. It’s something along the lines of AWS Visual Studio Tools > File > New > AWS Lambda and Sample Projects > ASP.NET Core Project, which creates an MVC website with Lambda entry point and provisioned API Gateway, which provides complete MVC sample application hosted in AWS. (25:40) Martin drives home the message that when AWS Lambda isn’t being used, you aren’t paying anything. You only pay for the compute time you consume. Jon speaks to massive scaling and “micro scaling” in the cloud.(27:15) Martin talks further about low cost and low scale with functions as well as statically hosting websites which use serverless for auth and lambda processing. Martin walks through the specific use case of Comic Relief, which benefited greatly (93% cost savings) from serverless hosting. (29:50) Martin speaks to AWS Amplify and there’s more discussion of scalability, burstability, and agility. (31:00) Martin wraps up the chat sharing how functions allow developers to mix-and-match languages, which promotes using the right tool for the job. For example, audio manipulation using Python, when the rest of the application may be written in C#. (33:00) Explore AWS and .NET on AWS.(33:30) Read more from The Beebs. Thanks to Ben Griswold for writing up the show notes!
Transcribe →Herding Code 237: Tess Ferrandez on Three Real World Machine Learning Projects
Jun 17, 2019Tap to summarizeDownload / Listen: Herding Code 237: Tess Ferrandez on Three Real World Machine Learning Projects https://herdingcode.com/wp-content/uploads/HerdingCode-0237-Tess-Ferrandez.mp3 At DevSum Stockholm, Jon talks with Tess Ferrandez about some machine learning applications she’s worked on recently, from sports to shoplifting to cancer detection. Tess talks about the specific ethical considerations that come up when classifying and predicting behavior, and how they worked with them in these real-life examples. Topics: (00:20) Tess has been working on some applied machine learning projects with large customers lately, all focused on computer vision. One project detects soccer goals using computer vision (saving money over hardware based solutions), another detects cancer in microscopy slides, and the third detects shoplifting patterns to minimize (02:55) Tess has been doing this work in Python rather than .NET. Jon asks if it’s possible to use ML.NET, but Tess says Python is necessary, both because the language is better suited and the community libraries are all in Python.(04:35) Jon asks Tess about her experiences moving from .NET to Python, and Tess says it’s a struggle since it’s not strongly typed. You can use testing on the parts that handle data, but not on the machine learning parts.(05:40) Jon asks how much of Tess’ work is done using Jupyter Notebooks. For data exploration, Jypyter works great, but for the actual execution you’ll want to use scripts so it’s testable.(07:00) Jon asks more about how you can detect shoplifting behavior, since it’s an activity that happens over time. Tess says it’s also difficult because the prediction may be biased against a demographic, e.g. 20-40 year old men.(07:54) Tess say ethics and machine learning are close to causing the third machine winter, and goes on to describe the previous two machine winters. We now have the machines and the data, but often the data is so unfair that it could lead to severe ripple effects. This can cause bias in predicting behavior racially, biasing against things like medical analysis due to sample source, etc.(11:30) Jon and Tess discuss the dangers of creating bad feedback loops. Tess talks about an example where Amazon created a system to review CV’s which was biased against women because historically women have had fewer software engineering positions, so this ...
Transcribe →Herding Code 237: Tess Ferrandez on Three Real World Machine Learning Projects
Jun 17, 2019Tap to summarizeEpisode 237 Download / Listen: Herding Code 237: Tess Ferrandez on Three Real World Machine Learning Projects At DevSum Stockholm, Jon talks with Tess Ferrandez about some machine learning applications she's worked on recently, from sports to shoplifting to cancer detection. Tess talks about the specific ethical considerations that come up when classifying and predicting behavior, and how they worked with them in these real-life examples. Topics: (00:20) Tess has been working on some applied machine learning projects with large customers lately, all focused on computer vision. One project detects soccer goals using computer vision (saving money over hardware based solutions), another detects cancer in microscopy slides, and the third detects shoplifting patterns to minimize (02:55) Tess has been doing this work in Python rather than .NET. Jon asks if it's possible to use ML.NET, but Tess says Python is necessary, both because the language is better suited and the community libraries are all in Python.(04:35) Jon asks Tess about her experiences moving from .NET to Python, and Tess says it's a struggle since it's not strongly typed. You can use testing on the parts that handle data, but not on the machine learning parts.(05:40) Jon asks how much of Tess' work is done using Jupyter Notebooks. For data exploration, Jypyter works great, but for the actual execution you'll want to use scripts so it's testable.(07:00) Jon asks more about how you can detect shoplifting behavior, since it's an activity that happens over time. Tess says it's also difficult because the prediction may be biased against a demographic, e.g. 20-40 year old men.(07:54) Tess say ethics and machine learning are close to causing the third machine winter, and goes on to describe the previous two machine winters. We now have the machines and the data, but often the data is so unfair that it could lead to severe ripple effects. This can cause bias in predicting behavior racially, biasing against things like medical analysis due to sample source, etc.(11:30) Jon and Tess discuss the dangers of creating bad feedback loops. Tess talks about an example where Amazon created a system to review CV's which was biased against women because historically women have had fewer software engineering positions, so this system would have reinforced that by preventing women from getting software engineering positions in the future.(13:35) There's also a danger of classifying people based on pictures, since we may assume the computer is unbiased even though the bias may have been introduced due to the sample data. Classifying based in pictures would imply that either people were born criminals or criminality changes their appearance, neither of which are acceptable assumptions.(16:09) Going back to the shoplifting case, we need to make sure we're detecting the action of shoplifting rather than classifying the individual's appearance. For instance, detecting poses, whether the individual was alone. Pre-trained models for things like object and activities help. There are also subtle sources of bias, for instance if all the source videos are from Christmas, the model may be biased against Santa Claus, so you also need to use pre-trained models for background subtraction.(18:13) Jon asks how important it is to be able to understand how the decisions were made. Tess says it depends based on the impact of the decision, and explains how in the case of cancer detection they determined that color differentiation could be used as a predictor, so the actual application didn't require machine learning. In the case of football goal detection, there was such a large amount of data (time, video, and sound), it was possible to get very good results.(21:26) Jon asks how developers can learn more. Tess says that software engineers don't need to start with math - you can use pre-trained models and go from there. She recommends a book called Deep Learning with Python by Francois Chollet - it's very approachable. Tess also recommends the Machine Learning at Microsoft YouTube channel.
Transcribe →