discussions on software development
Similar Podcasts
The Cynical Developer
A UK based Technology and Software Developer Podcast that helps you to improve your development knowledge and career,
through explaining the latest and greatest in development technology and providing you with what you need to succeed as a developer.
New Rustacean
A show about the Rust programming language and the people who use it.
Algorithms + Data Structures = Programs
The Algorithms + Data Structures = Programs Podcast (aka ADSP: The Podcast) is an informal podcast inspired by Magic Read Along. We plan to talk about whatever we feel like - algorithms, data structures, programming languages, latest news in tech and more. Feel free to follow us on Twitter at @adspthepodcast.
#102 Spencer Schneidenbach, REST APIs
Summary Spencer Schneidenbach talks about REST APIs, what makes a good one, who should design it, how to document it and why developer experience is so important. Details Who he is, what he does. Designing an api, the consumer should drive the design, is the developer the main consumer, is the business a customer? What REST is, RPC, nouns not verbs, querying, SEARCH verb, PUT and PATCH, common conventions. Changing how an API works, versioning, version management. Importance of documentation, error code docs, who writes the docs. Consistency, good api design is user experience for developers, Spencer loves Twillo. Full show notes
#101 Andrew Lock, .NET Core
Summary Andrew Lock, blogger and author of ASP.NET Core in Action talks to me about the .NET Core and why you should probably use it instead of Framework. Details Who he is, what he does. His book. Why did Microsoft build .NET Core, the complications of Web API Core running on Framework. Platforms it works on. New configuration system, typed configs. Dependency injection is built-in now, a mention of HttpClientFactory. Middleware, pipelines to perform tasks. Authentication and authorization, policy server. Kestrel server. Full show notes
#100 Jeff Glennon, The Man Who Left Technology for Beer
Summary Jeff Glennon used to be an agile consultant helping companies align their departments to deliver better software, but he left that world behind and is now the Chief Operations Officer at Night Shift Distributing, a distributor of craft beers and other beverages in Massachusetts. Jeff talks to me about his move, the skills he brought with him and what he has learned. Details What he used to do, moving to Nightshift Brewing, bringing his skills from the software world. Setting goals, doing it as a team, "commitments", scaling, going beyond the local customers, opening another location. Being the chief operating officer and leading sales at same time. Differences and similarities between agile consulting and role as COO. An agile approach to beer distribution, partnering with their customers, when to drop a partner. Scaling problems, logistical challenges, capital investments, big decisions affect many families, how they make big decisions, strategy is a day to day and week to week thing. Three to five year plan. It's not lines of code it's beer, the similarities between the software and beer worlds. What he has learned in two years, "the value of stopping for a second", saying no and letting people challenge you is important. Jeff doesn't plan to go back to tech. "It's just beer"
#99 Jimmy Bogard, Diving into Containers
Summary Jimmy Bogard creator of AutoMapper, MediatR and HtmlTags talks to me about his move into the world of containers. Details Who he is, what he does, his open source projects. What containers are, why use them, containers are like Lego bricks. How many apps to a container. Windows containers types. Differences between Windows and Linux containers, why choose over the other, size and ease of scaling; if you choose Linux you need to know something about Linux admin. Do apps need to written in a different way to work on containers. Be mindful of the size of Windows containers. Is an app in a container a microservice. Jimmy Bogard's liver. Jimmy likes Microsoft docs on containers.
#98 Michael Brett, QxBranch – Commercial Quantum Computing
Summary Michael Brett of QxBranch tells me about their work in the world of commercial quantum computing, their software and where he sees the industry going. Details Who he is, what he does, history of QxBranch, predictive analytics - financial, pharmaceutical, gas industries. Quick overview of quantum and the limits of traditional computing. Why Australia has so much quantum computing experience. State of the art. Cloud based quantum computing. Examples of use, financial world. Building software, early stage hardware and simulators; every hardware.
#97 Cliff Agius, Decision Making as a Pilot and Engineer
Summary Cliff Agius, software engineer and pilot of Boeing 787's talks about decision making above the clouds and in the office. Details Who he is, what he does, flying and coding. Critical decision making, what it is, an aircraft has thousands of computers, types of decision - impulsive vs considered, caging the chimp. Types of response, chimp (instinctive) , rule based (check list) , human (think your way through); managing the chimp response in others. TDODAR a decision making framework - time/team, diagnosis, options, decision, assign, review. How to hear more from Cliff.
#96 Steve Gordon, Http Client Factory in .NET Core 2.1
Summary Steve Gordon and I talk about the new Http Client Factory in .Net Core 2.1. We cover what's new, what's different and how to use Polly, the .NET resilience framework with it. Details Who he is, what he does, meetup group, Humanitarian Toolbox. What is wrong with Http Client, exhausting sockets; using a singleton, DNS problems. Http Client Factory, creates a client pool, using DI to create the clients, named and typed clients, testing. Http Client Handlers. Using Polly with Http Client, differentiating between policies for a given endpoint, wrapping, calling delegates.
#95 Ben Watson, High Performance .NET
Summary Ben Watson, software engineer at Microsoft working on Bing and author of Writing High Performance .NET Code talks to me about his book and how to improve your code. Details Who he is, what he does, working on Bing lead to the book, Bing is probably the biggest C# app in the world. Why worry about performance, pay for play, serverless; sometimes more machines are the best solution. Where to start with the CLR, the garbage collector, JIT, be careful of enum flags. More on GC, using generations to improve efficiency, aim for very short lived or very long-lived memory, memory efficiency is as important as CPU efficiency. What about the network, async await all the way down, Ben likes TPL, "immutability is key". LINQ hides allocations, closures delegates. Be careful with Func and Actions, delegates cause allocations. Spans. Concurrent collections. Just in Time, small methods compile faster, Bing loads thousands of dlls. Readability and maintainability vs performance. for vs foreach.
#94 Todd Gardner, Building Your Brand
Summary Todd Gardner, founder of TrackJS talks about building its and his own brands, speaking, and growing a company. Details Who he is, what he does, pub conf. What TrackJS is. Why having a good product is not enough, talk about it as much as building it, present at conferences. How he sold to the big companies like Google, StackOverflow and Microsoft, hiring sales people. Moving from developer to running the company. Todd's brand and the TrackJS brand. How to build a brand, minimum viable personality. Pitfalls as a company grows, don't start at web scale, don't focus on the tech. What Todd likes most about running a business. NDC conference Minnesota and pub conf are coming to Minnesota.
#93 Ben Cull, From Developer to Startup Founder
Summary Ben Cull tells be about his move from being a developer to the founder of a starup, why he decided to make the change and the success and failures along the way. Details Who he is, what he does. Starting a product, knowing what to build. How to transition away from the day job, become a free lancer, when did does the startup start paying. Finding the market fit for your product, target a small market, find advocates among your customers, figuring out your cash flow. Treating your dependencies as relationships, it's all about people.
#92 Felienne Hermans, What is Programming?
Summary Felienne Hermans has been asking the question "What is programming?", in this podcast she tells me why it is an important question and what she has found out. Details Who she is, what she does. Felienne's research into what programming is, why it is important. Her general findings. Excel as an intro to programming, Excel is functional. Programming with kids, code smells, code quality and how it affected understanding. It's hard to see beyond your own bad code. Programming as writing, making it appealing by comparing it to story telling. Transitioning to more formal programming. Programming Sucks article by Peter Welch. Encouraging people to learn programming, how can we help, some home work from Felienne.
#91 Adam Ralph, NServiceBus, Microservices and SOA
Summary Adam Ralph talks about the challenges of distributed systems, queues, coupling, and how NServiceBus helps with microservices, SOA and long running processes. Details Who he is, being "a white space bigot"; what he does; working for Particular, evangelist and engineer. What NServiceBus is, infrastructure for distributed systems, queues, retires. History of NServiceBus, commercial and free versions. Main reasons to us NServiceBus - abstracts the message transport, retires, deduplication and the fallacies of network computing, insights into the flow of messages, monitoring on the transport system. Publish/subscribe. Sagas for long running processes, saving state, an example of a saga in action, sagas can run infinitely. Loose coupling, "pit of success"; different kinds of coupling - temporal, location, logical. an example of decoupled ordering service, thin events vs fat events, contract coupling, set an id very early. What scale do you need to be at to use NServiceBus. How to get started with NServiceBus. Monitoring what is happening. NServiceBus on containers. Adam is running a workshop in May at Micro CPH, Copenhagen.
#90 Kjersti Sandberg and Charlotte Lyng, Norwegian Developer Conferences
Summary Kjersti Sandberg and Charlotte Lyng of the Norwegian Developer Conference tell me what goes into organizing four major conferences around the world. Details Who they are, what they do. A little about how the conferences started. What is the Norwegian Developer Conference; spreading around the world, London, Oslo, Minnesota, Sydney. How they organize the conferences, finding local partners, crew, contractors, quality over quantity. How the conference grew. Balancing the content of the conference to suit attendees, choosing the conference tracks, choosing the speakers, new and established presenters. How NDC attracts the big names. Why attend conferences when there is so much content online. Timeline of a conference, planning starts a year ahead. An invitation to Minnesota, Oslo and Sydney.
#89 Mark Eisenberg, Breaking the Monolith
Summary Mark Eisenberg talks about the very long life of the software monolith, when it started, and how we have been trying to escape it since. Details Who he is, what he does. What is a monolith, tell-tale signs of a monolith, coupling and decoupling. Why we built monoliths. N-tiers and monoliths. Software is rarely a green field. Were we ever able to swap tiers. Advantages of a monolith, it's familiar. Companies need a visionary to effect change. Risk raises its head. SOA didn't work, client server didn't work, n-tier didn't work. Successful companies went from monoliths to microservices when they needed to. RPC is from the 1960s, are you running one piece of code on one machine or ten machines. How to get off the monolith, find a visionary. Time to respond to a challenge is very short. Microsoft is a good example of a large company changing.
#88 Aaron Bedra, Threat Modelling
Summary Aaron Bedra talks to me about threat modelling, why you should do and what to cover. Details Who he is, what he does. What is threat modeling and how he approaches it. Types of security, loss of money, loss of life. Should you secure something if it is not valuable. Are we in a post security world? How often your site is attacked. How to decide what to protect. Regulations and breaches. How to protect your system, watch for outgoing data. How to build secure software from the start. Hashed passwords are not as secure as you think. Encryption and input validation. How to check third party libraries. Better software practices lead to better security. How much security is enough, "if you are investing more than you could lose, you're doing it wrong".