April 27th, 2017
50 mins 3 secs
avocado, emacs, oil
We hear about the days when Charles was drilling for oil. Also, waffles: "I suffered years of floppy-waffles."
April 11th, 2017
38 mins 18 secs
migas, tacos, texas
When you travel, people have a lot of thoughts about Texas.
March 24th, 2017 | 48 mins 32 secs
Charles & Coté reboot their old podcast about regular things. Also, a rant on photo management in Apple-land and how terrible enterprise IT news it. Plus, upcoming topics.
February 11th, 2017
51 mins 14 secs
austin, boy scouts, chef, cloud
Having worked in cloud since before cloud, JJ and I talk about what companies are using various cloud things for. We also discuss the conceptual history of cloud, and what exactly he does as a "business development" person at Chef.
February 7th, 2017
6 mins 56 secs
What's up with all those cash numbers in quarterly reports, and what's the deal with "analyst expectations"? In this brief episode I talk with RedMonk's Rachel Stephens to get some quick tips on what to do with all that stuff.
January 27th, 2017
31 mins 12 secs
Bridget Kromhout, DevOps, culture, meatware, process
We discuss all the human and process changes needed to do good things with computers.
January 27th, 2017
25 mins 34 secs
Josh Long, Pivotal, programming, reactive, spring, spring boot
Josh Long and I discuss “reactive programming."
December 13th, 2016
11 mins 22 secs
bad code, legacy, project management, technical debt
Some reasons people would keep bad code, how management should think through it, and then some options for coping as needed.
November 3rd, 2016
7 mins 8 secs
HCSC, Kansas City, cases, pair programming, pairing
Somewhere around just 20% of people do pair programming. It seems to be an incredibly effective technique, according to people who follow it. I go over some of those reasons and micro case studies of organizations having success with pair programming. It seems like the right thing to do.
November 2nd, 2016
6 mins 23 secs
Leadership, change management, fail fast, small batches
The idea of “failing fast” is popular in DevOps and agile think. That sounds like the exact opposite of what managers at large organizations would like to do. How do you get them to feel all warm and fuzzy about it? Here’s the top three tactics I’ve seen work.