In this episode, Otto Dobretsberger joined us to introduce us to Photino - a technology for running web-based applications natively on your devices, regardless of the operating system used, using the latest that .NET has to offer.
In this episode, Drake Williams joined us to talk about some of his Open Source projects which he started for fun, including Rom Sorter and the GPS game server Praxis Mapper. He also shares some top tips for building applications without breaking out of your personal bandwidth.
In celebration of the 100th episode, we asked the community of listeners to send in any questions that they had about the show, it’s host, production, or anything. This episode answers those questions
In this episode, Iris Classon returned to talk with us about her new book The Unlikely Success of a Copy-Paste Developer, some of the lessons that all developers must learn throughout their careers, and that it’s OK to get things wrong.
In this episode we talked with Josh Hurley and Norm Johanson about how far .NET has come since the .NET Framework 1.0 days, about the support that Amazon’s AWS has for .NET, and Amazon’s new AWS Microservice Extractor for .NET tool.
In this episode we talked with Dan Clarke about developer productivity, passion for development, and leveraging other people’s code to maintain our individual productivity levels.
In this episode we talked with Dr. Felienne Hermans about her book The Programmer’s Brain. We also discussed things like code reading clubs, and strategies for learning a new code base on a deeper level.
In this episode we talked with Dan Walmsley about Avalonia UI, a cross-platform desktop UI framework for all the .NETs (Framework, Core, and Modern .NET), why you might choose it, and some of the pitfalls that the other desktop UI frameworks may not have come across yet.
In this episode we talked with Geoffrey Huntley about community ownership, and some of the reasons why an open .NET code base with reproducible builds could lead to innovation without having to rely on Microsoft engineers to provide them for us .NET developers.