Folding Air, Software Development With Damian Stanger: Damo's Podcast Highlights 2016 #42

I subscribe to many podcasts, you can see the list as it was in 2015 here: Developer podcasts v2 but I thought I would start to keep a weekly log of the episodes that I found interesting or useful in some way.

[Software Engineering Daily] DevOps Handbook with Gene Kim http://softwareengineeringdaily.com/2016/10/13/devops-handbook-with-gene-kim/

The intent of the DevOps movement is to get organizations moving faster and more effectively by breaking down siloes, and improving communication. Gene Kim’s book The Phoenix Project illustrated this by telling the fictional story of a company adopting a DevOps mentality. Although that book was fiction, Gene is an experienced engineer, having worked as founder and CTO of Tripwire, a software company that makes security and compliance automation software.
In his new book The DevOps Handbook, Gene presents a practical companion to The Phoenix Project. Together with his co-authors, Gene has written a guide for how to move an organization toward DevOps, and in this episode we explore some of the topics from his book

We first interviewed Paul Stovell a few years back when he started a micro-ISV he was calling "Octopus Deploy." Now it's a fully formed and successful company whose flagship product Octopus Deploy is used all over. Damian Brady joins Scott and explains why deployment is more subtle then you think.

Jia Jiang knows first-hand how the fear of rejection can hold us back. The tendency to avoid it at all costs can be detrimental to our lives, our careers, our dreams
Chasing your dream requires you put everything out there and deal with the consequences. When aspiring entrepreneur Jia Jiang left corporate life to build his dream company, he had no idea it also meant facing crushing rejection. The best way to recover? 100 Days of Rejection Therapy

In this episode, we take our first dive into the book Clean Code by Robert Martin and specifically we talk about writing meaningful names for all things code related. You’ll be amazed at how following some decent rules that you can start naming things that will help you and fellow coders understand your code at a glance.
As always with coding blocks skip skip skip all the news and chit chat to get to the meat of the conversation
Lots of good show notes

[YOW! 2015] Adrian Cockcroft - It's Complicated... https://www.youtube.com/watch?v=iMJymSrKqF4

What does it mean to be complicated?
How can we manage complexity when we scale up systems?
Why do people find it horrifying when the internal complexity of monolithic apps is replaced by a “death star” diagram of the relationships between microservices?
Are many microservices less complicated than one monolith?
Why do people expect complex adaptive systems to behave predictably?
How does complicated relate to intuitive?
How can small fast release processes reduce risk, speed up teams and reduce costs?

[Rocky Mountain Ruby 2016] Kill "Microservices" before its too late by Chad Fowler https://www.youtube.com/watch?v=-UKEPd2ipEk

Keep changing things, even if you don’t need to
Microservices make it easier to replace than to change
Unit tests are a design smell (tests optimise for permanence, creates coupling)
Use metrics instead , esp business metrics. Use alerting around the metrics to perform true testing of the system
Small projects vs large projects, success vs failure, stay small, go for impermanence
Microservices is not an architecture and small is not the goal, its health longevity
Systems that survive are made of components that can change
If it hurts do it more often

What is Infrastructuralism and how can it help you think differently about software and large problems? Scott sits down with Everett Harper, CEO of Truss. They talk about how applying some old ideas in new ways helped them fix healthcare.gov.
How we should avoid succumbing to the Black swan theory

Folding Air, Software Development With Damian Stanger