Herding Code

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:

• Homebrew
• OhMyZSH
• GitHub CLI
• AZX.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?

W...

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.

Kevin, Jon and Rob talk to Ben Scheirman about developing user interfaces for the Apple platform with SwiftUI and Combine.

Ben screencasts at NSScreencast and is the creator of the Combine Swift course.

Download / Listen: Herding Code 244: Herding Code 244: Ben Scheirman on SwiftUI and Combine

Links:

• Ben is @subdigital on Twitter
• Combine Swift – a Combine course for mere mortals
• NSScreencast – Top-notch tutorials for Swift developers
• SwiftUI overview in Apple developer docs
• Combine overview in Apple developer docs

Transcript:

Herding Code – March 5, 2021 – Ben Schierman on SwiftUI and Combine

Kevin: [00:00:00] Hello, welcome to another episode of Herding Code , our quarterly episode here. This is being recorded on March 367 2021. And today we were talking to Ben Schierman. Ben runs NSScreencast, which is a video training site for all things iOS and Apple development, and Ben’s going to talk to us today about SwiftUI, a relatively new UI framework from Apple for writing Apple platform applications. So thanks for joining us, Ben.

Ben: [00:00:40] Well, thanks for inviting me. It’s good to be here.

Kevin: [00:00:42] So why don’t we start with the sort of high level, you know, what is SwiftUI? What makes it different? Like what, how is it different than what came before it.

Ben: [00:00:50] So there’s a lot of history and the Apple development community. We’ve had AppKit for 30 years now which follows a kind of model view controller based approach. And then when the iPhone came out, they, they sorta took lessons learned from that. And. And created UI kit. And so when you look at creating apps for the Mac or apps for the iPhone, if you squint, they’re extremely similar.

But app kit has that, you know, 20, 30 years of legacy cruft that they just can never throw away. And so you know, things are a little bit different. Like, you know, you have UI color versus NS color UI being the UI kit version for the iOS. And, and then you have things like the coordinate system on the Mac is.

The origins in the lower left corner, which hearkens back to the, I guess the, the way they used to send commands to the printer or something, I don’t really know, but on iOS, the, the origin is, is you know, top left. And so there’s, you know, minor differences here and there, but ultimately you’ve got views that know how to draw themselves they’re object oriented.

So you can have a subclass of a view that is a button or a label. And you know, the API is, are, are pretty strong, but There’s there’s always, you know, as our applications get more complex sometimes people complain about the patterns not being enough. And people joke about MVC standing for massive view controller instead of model view controller.

Because, you know, when you give somebody a pattern and say, this is where you put your logic, they tend to put all the code there. And anyway, so last year wait, Time is meaningless nowadays. This is, you know, at least five years ago in, in COVID time Apple released a SwiftUI, which is kind of a radical new UI framework for, for writing in air quotes, cross-platform applications.

As long as your platform comes from Apple it will work on T V U S and the Mac and the watch and the iPhone and the iPad. And SwiftUI takes just a totally different approach to, to writing user interfaces. So instead of model view controller, instead of your views being object oriented you know, and the model view controller world you would typically have of you that you would create say, I’m going to create like a new UI label and I’m gonna attach it as a sub view of my main view.

And then I might read a model. In order to tell what the text property of my label’s going to be. So like on a viewed load, I could say, okay you know, a model dot first name, I’m going to assign that to my labels, text property. But there’s nothing in that relationship. That’s going to continually keep that up to date.

So I have to respond to events and note or re sort of update my model again. Well, SwiftUI is totally different whe...

Kevin and Jon talk to Shawn Wildermuth about his new documentary film, Hello World. Shawn talks about how this film project began as a “love letter to software development,” exploring how amazing this career can be. As he delved into it he became more aware of the lack representation of women and people of color in this profession, and this film details his exploration of that topic through interviews and historical background.

You can pre-order the film now, and watch it on-demand on a lot of streaming platforms starting December 15,2020.

Download / Listen: Herding Code 243: Shawn Wildermuth on his new film, Hello World

Links:

• Hello World: The Film! (helloworldfilm.com)
• Shawn Wildermuth’s Blog
• Hello World Podcast
• JuneteenthConf – June 19th and 20th 2020

Transcript:

Jon: [00:00:09] Hello, and welcome to Herding Code. This episode is being recorded November 20, 2020. And today we’re talking to Shawn Wildermuth about the Hello World film. Shawn, can you introduce yourself and the film?

Shawn: [00:00:22] I’d be more than happy to. I’m Shawn Wildermuth. I’m a technologist and mostly a teacher these days. They don’t let me around code anymore. But I’ve got a blog at wildermuth.com and I made a documentary about software developers called Hello World.

Jon: [00:00:38] So what’s kind of the main focus. Like how do you approach software developers and you know, what, what are you kind of talking about there?

Shawn: [00:00:48] Sure. I started making the film. I’ll tell it in this kind of story. I started making the film because I wanted to sort of do a love letter to software development because it’s been so incredibly useful to me. Like it has saved me from a life of working in a 7-11 night shift. And I just love everything about.

How interesting the job is, and I want to sort of encourage people who didn’t think they could do it, that they could. And so that was sort of the first approach. And in the middle of that the me too movement came through and some other things in our industry were changing with conferences and such, and I realized that.

I hadn’t really worked with almost any women and certainly not women from the United States or Canada that I’ve worked on exclusively with people that looked like me. You know, I look a lot like a, the comic book guy, if you don’t know what I look like from the Simpsons. Right. I fit the, the stereotype really well.

And so I pivoted the movie to be about the lack of women and people of color, especially in the industry. Because it’s it’s, as I say, in the film, it wasn’t that there weren’t enough women or people of color in, in, in In software development. It was that I had never noticed there weren’t enough.

Like, it just didn’t even occur to me to notice. And I like to think of myself as someone who’s, you know, at least should notice those sorts of things. And so in that same time, I was having a dinner with Richard Campbell years and years ago. And he was mentioning about the early women in software development, being the first programmers, which was a story I didn’t know.

And, and that’s part of what we talk about is sort of the history. Of software development and how this sort of went from one thing to another. And then I looked back and it had been five years and I didn’t know what I was doing with my life.

Jon: [00:02:43] it’s a, it’s really fascinating that you’ve kind of created a documentary during a time of some transition. And some of my favorite documentaries that I’ve seen have kind of. Almost, but either through discovery during the filming, or just kind of by happy accident with evolution, you know, with history of evolving have kind of captured things.

I remember there was a documentary I saw called startup.com and it happened during the.com startup time and that startup bust and it followed these founders and, you know, getting huge valuation and going and interviewing. You know, in the white house and then everything. And then they get into huge fights and then the whole thing comes crashing down and the, and the film captured all that.

And it sounds to me like, I mean, and just observing everything that’s gone on, it’s b...

Continue reading "Herding Code 236: Will Green on Going Serverless With AWS"