Sunday, 30 April 2017

Damo's April 2017 Podcast Highlights

I subscribe to many podcasts, you can see the list as it was in 2015 here: Developer podcasts v2. I'm keeping a podcast blog here of the episodes that I find interesting or useful in some way.


[Continuous Discussions] Value Stream Mapping and DevOps

  • Value Stream Mapping helps organizations streamline their DevOps adoption
  • Accelerate releases, optimize pipelines and toolchains, and even transform culture
  • In the IT value stream, success is all about the left-to-right flow of value to the customer — from development to IT Operations


[Agile for humans] Agile Musings with GeePaw Hill

  • A nice flowing wide ranging discussion about all things agile
  • Optimisation of programs vs optimising programming
  • Internal quality vs external quality
  • Generating insights about software
  • The dangers of dogma in agile software development
  • How to debunk the quality vs quantity myth
  • Why maximizing your insights per hour is important
  • What is hurting the agile industry today

[Agile for humans] Lessons from #NoEstimates Critics

  • What is the critic’s view against #NoEstimates?
  • Discuss the many areas of agreement that we have with some of the #NoEstimates critics
  • The remaining time was spent on systems thinking, pre-conditions necessary to question estimation processes and value, and the role of excellent engineering practices in reducing the role of estimates in a software delivery system

[Agile for humans] Product Mastery with Geoff Watts

  • How difficult the role of Product Owner is to do well
  • The tools, mindset, and techniques necessary to be a successful Product Owner
  • Why the Product Owner needs the support of the whole team in order to get their job done


[Software Engineering Radio] Success Skills for Architects with Neil Ford

  • What skills are required to be a successful software architect
  • how to create and maintain them
  • how to transition from other roles, such as software engineering
  • Those looking to make the transition should focus especially on learning “soft skills” before making the move, and exploring the idea of taking an architectural role temporarily to see if it suites you. He also discusses problem solving skills, why understanding history is so important, and how to recognize and avoid increasing complexity

[The InfoQ Podcast] Chris Richardson on Domain-Driven Microservices Design

  • Discussion on how to use DDD and CQRS concepts as a guide for implementing a robust microservices architecture
  • "Microservice architecture" is a better term than "microservices". The latter suggests that a single microservice is somehow interesting
  • The concepts discussed in Domain-Driven Design are an excellent guide for how to implement a microservices architecture
  • Bounded Contexts correspond well to individual microservices
  • Event sourcing and CQRS provide patterns for how to implement loosely coupled servicesWhen converting a monolith to microservices, avoid a big bang rewrite, in favor of an iterative approach

[Docker cast] Microservices + Events + Docker = A Perfect Trio - Docker Captain Chris Richardson

  • Microservices are an essential enabler of agility but developing and deploying them is a challenge
  • In order for microservices to be loosely coupled, each service must have its own datastore, this makes it difficult to maintain data consistency across services
  • Deploying microservices is also a complex problem since an application typically consists of 10s or 100s of services, written in a variety of languages and frameworks
  • In this presentation, you will learn how to solve these problems by using an event-driven architecture to maintain data consistency and by using Docker to simplify deployment.

Programming and testing

[JavaScript Jabber] Clean Code JavaScript with Ryan McDermott

  • Ryan converted the principles in Clean code to apply to javascript
  • Software engineering principles, from Robert C. Martin's book Clean Code, adapted for JavaScript. This is not a style guide. It's a guide to producing readable, reusable, and refactorable software in JavaScript.

[Cucumber Podcast] Property-Based Testing

  • The programmer provides a specification of the program, in the form of properties which functions, methods or objects should satisfy, the framework then tests that the properties hold in a large number of randomly generated cases
  • The core idea is that instead of enumerating expected input and output for unit tests, you write properties about your function that should hold true for all inputs. This lets you write concise, powerful tests.


[The Changelog] How We Got Here with Cory Doctorow

[Complete Developer Podcast] Salary Negotiations with Josh Doody

  • In the episode they talk about some of the common questions developers have about negotiating as well as covering some mistakes that we all make when negotiating for a higher salary.

[This Agile Life] Cat Killed the WiFi

  • Are interviews and the interview progress broken?

[TED Talks] To raise brave girls, encourage adventure

  • Gutsy girls skateboard, climb trees, clamber around, fall down, scrape their knees, get right back up — and grow up to be brave women.
  • Learn how to spark a little productive risk-taking and raise confident girls with stories and advice from firefighter, paraglider and all-around adventurer Caroline Paul.