no dogma podcast

Summary Veronika Kolesnikova talks to me about Xamarin and Microsoft Cognitive Services. Details Who she is, what she does. What is Xamarin. What are cognitive services, why so many services; artificial intelligence vs machine learning vs deep learning, training models. He she got started in Xamarin; it's part of Visual Studio, SDKs and testing tools, Xamarin live player debugging on device. Why use cognitive services, examples of use. Types of cognitive services - labs, vision, face, speech, translator, language understanding intelligence service. Should I train my own model. Recommendations API. It started with Bing, how is it to use, examples. People to follow - Paige Bailey, Seth Juarez. Veronika is presenting at Visual Studio Live, Las Vegas.

Summary Tomas Petricek talks about software correctness, its history and future. Details Who he is and what he does, his book on F#. Alan Turing Institute. Software as an engineering discipline, software as art. History of errors in software, errors in hardware. Software was never in crisis. Using types to help with correctness, how different languages do it, some complications, a new language would be needed. Upcoming improvements in correctness. Other projects Tomas is involved in.

Summary Part two of a two part recording with Mark Seemann on dependency rejection. Details No mocking needed for unit testing, command query separation. Do you still use some DI in impure functions; partial applications, Mark is not a fan of DI containers and doesn't know of any for F#. Are partial functions functional, Haskell keeps its impure functions at the edge, "impure-pure-impure sandwich" sandwich - the origin of the word "sandwich", an example of a translator application, don't lose sight of the other tenets of programming, upcoming conferences.

Summary Part one of a two part recording with Mark Seemann on dependency injection and rejection in F#. Details Who he is, what he does. The new video site. Used to earn from C#, now earns from F# but would like to earn from Haskell; how much dev is going on in F#. Dependency rejection; side effects, purity and determinism. Impure functions. Pure and impure calling each other. Dijkstra, abstractions and monoids.

Summary Steve Elliot, CEO of Agile Craft talks to me about re-architecting software, why it should be done, when to do it, and how to do it well. Details Who he is, what he does. When to re-architect, monitor usage patterns, out of date ui, spaghetti code, ratio of bug fixes to new code, not mobile enabled, difficulty recruiting, market opportunity. Making a decision, who gets a say. How to measure success on a long-term project. Practical steps for moving to new architecture. What to start with, easy or hard pieces; what to do next; how to keep the old system going. What about people who don't want to learn new things. Dealing with remote offices. How to keep the project on track and the momentum going.

Summary Jay Gambetta manager for quantum theory and computing at IBM talks to me about the IBM Quantum Experience. Details Who he is, what he does. Why is quantum computing different, entanglement and interference. How do quantum computers look, cryogenic refrigerators, close to absolute zero. IBM's history in quantum computing. What is the quantum experience, how a program goes from the cloud app to the supercooled quantum computer; free and open access to 5 and 16 qbit computers; how to write a program (called a circuit); examples of circuits; is 16 qbits enough for real problems. When can we break encryption with quantum computing, why error correction is so important. Popularity of quantum experience, how soon will a submitted circuit run; using python to submit circuits; what is the "Hello World" of quantum computing; how to write a python program for the quantum experience. Community involvement. Future of quantum, becoming a technology, what about the temperature requirements. Chaotic and exciting times coming.

Summary Doc Norton tells me why measuring agile velocity is a bad idea and what to do instead. Details Who he is, what he does. "Escape Velocity", why he wrote a book on agile metrics. What velocity is, rate of delivering value to customer, "it is useless", estimates are "bunk". "The business" pushes velocity based estimates. Lack of trust throughout organization. Can we really reduce a complex problem down to a simple number. Anti patterns: more velocity, cross team velocity comparisons, estimating with time, measuring individual velocity. Side effects of metrics. Variable velocity. What should we measure, cycle time and lead time, fixing bottle necks, code quality, team joy. Where does dev ops come in. How to find Doc's book. Upcoming conferences.

Summary Angela Dugan tells me about impostor syndrome, why it matters and what you can do about it. Details Who she is, what she does. What impostor syndrome is, Hanselman's post. Who is affected by it. The more you know, the more you realize you don't know; being an "expert"; why is "I don't know" not acceptable, do agile sprints and commitments force unreasonable expectations. Angela's impostor syndrome survey. The opposite of impostor syndrome - Dunning–Kruger. Should one do anything about it; teaching what you learn. Angela might retake the test. Angela suggests helping others with impostor syndrome.

Summary Josh Doody talks about salaries, how they are set and how to negotiate a higher one. Details Who he is and what he does. What is a salary negotiation coach, negotiation by proxy. Who can benefit from Josh's help, how to get his book. Salary structures, what they are and how they work. Estimating your market value; judging your value compared to others, Bryan disagrees with Josh, John Sonmez says "ask for the moon". The interview, preparation, never share your current salary or desired salary. How to negotiate the salary; how to counter offer; the final discussion; "there is nothing fair about salary". How to leave a job. How to ask for more money in a job. Wrap up.

Summary Dustin Campbell talks about the future of C# 7.1, 7.2 and beyond. Details Who he is and what he does, Mads and the other guy, cross platform experience, playing guitar. Why move to incremental c# releases, bug fixes, move language forward more quickly, csharplang on GitHub, changes needed to compiler, C# releases are tied to Visual Studio releases. Could C# become a NuGet package. Preventing accidental use of 7.1. Possible dates. Release cadence, halting problem. Speed of change of c# vs ASP.Net, slow evolution is the plan. Balancing features and performance against ease of use. More pattern types coming. Shapes and extensions, extension everything - properties, constructors. Optional interfaces. The future of c#. A question from Jon Skeet for Dustin.