Software Defined Interviews

Software Defined Interviews

By Software Defined TalkBusinessNewsTechnologyTech NewsManagement
Download on the App Store

Software Defined Interviews episodes

  • Episode 23: “I don’t have a horse or gun.” Or: We were born in Austin. Or: “you may all go to hell. I am going to Texas.”

    When you travel, people have a lot of thoughts about Texas.

    Links:

    • Skype Call Recorder
  • Topic list
  • That podcast we used to do
  • “You may all go to hell and I will go to Texas.”
    • — It was Davy Crockett.
  • "Don't mess with Texas"
    • — “The campaign is credited with reducing litter on Texas highways roughly 72% between 1986 and 1990.”
  • O'Tacos
    • — Panini "tacos" in Paris.
  • Cooper's now in Austin
  • The Splendid Table with Lynne Rossetto Kasper
  • Original My Little Pony theme song
  • South American pan pipe sounds
  • Houston, Dallas, and San Antonio are top 10 US cities, by population
    • — Austin is #11.
  • Who invented the breakfast taco?
  • Header image of blue bonnets from rubengarciajrphotography
    • 39 min
  • Episode 22: The Regular Show, Apple’s problem’s, Enterprise tech news blows

    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.

    Links:

    • Screenhero
  • Oracle's financials, past three years
    • — They're pretty much "flat."
  • The Software Paradox
    • — Among other things, Stephen O'Grady analyzes Oracle's finances and what it says about their software portfolio and what companies are now buying, i.e., SaaS.
  • Kubernetes tool saves eBay from its OpenStack woes
  • Kara Swisher on the Ezra Klein show
  • 451 Research
    • 49 min
  • Episode 20: Reading tech company financials, with Rachel Stephens

    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.

    Find her in Twitter (@rstephensme) and on her RedMonk blog. See also this fine mound of cheese.

    Special Guest: Rachel Stephens.

    7 min
  • Episode 17: Ignoring bad code on purpose

    Sometimes you have to live with bad code. No one will let you change it. There’s many good and bad reasons, so make sure you’re consciously making the decision instead of accidentally doing it. I discuss some reasons people would keep bad code, how management should think through it, and then some options for coping as needed.

    It was Joel, back in 2000, who said not to re-write code.

    I recorded this with a Mevo, hence the kind of echo'y noise. See the video over in Facebook where I LIVESTREAMED IT!

    12 min
  • Episode 16: Pair programing doesn't stink

    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.

    Links:

    • My Pairing column from October at The Register
    — The comments section is especially good for common sentiment about pair programming.
  • Charles Lowell
    • — We used to do a podcast.
  • Gartner survey on pair programming adoption
    • — I got the number wrong: it's actually around 20%, not just 10%.
  • Mark Ardito goes over HCSC’s astonishing success with pair programming
    • — They thought it'd take 12-15 weeks to get their MVP done, but it actually took 5.5 to 6 weeks we finish.
  • Selecting people for pair programming and their enthusiastic response
    • — More from Mark Ardito on HCSC's adoption of pair programming.
  • Phil Horowitz talks about how exhausting pairing is at first
    • — At Perforce: "This makes pair programming intense, especially at the beginning. At the end of the first day, I couldn't go home. Before I could face humans again, I put my phone on airplane mode, ignored my usual online accounts, and went to the gym for two hours of self-imposed isolation."
    8 min
  • Episode 15: Getting executives to fail fast

    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.

    Links:

    • Failing fast for the uptight
    — One of my explanations of "failing fast": it actually means learning; here, a recording of a March 2015 talk.
  • Getting Started — picking your first cloud native projects, or, Every Digital Transformation Starts with One Project
    • — My tips on picking a series of small projects to build up internal momentum to do larger ones.
  • Digital transformation: the what, the why and the how
    • — The sad donut: "Less than 25% of organizations that participated in a recent 451 Research survey (451 Research VoCUL, April 2016) said they had a well-defined formal digital transformation strategy."
    7 min
  • Episode 14: Building a cloud in 30 minutes, metrics are a distraction

    "I get to see your face during this podcast," Matt says as we start talking about SpringOne Platform. Both of us were there and we recap Matt's talk on managing 10 Pivotal Cloud Foundry instances, namely, how they figured out using a Concourse pipeline to automate much of that management. We discuss "how to do the transformation" talks we liked, like the Citi talk.

    In addition to some other random digital transformation topics, we also discuss how HR policies are struggling to change with things like pair programming and DevOps.

    Subscribe: iTunes, RSS Feed

    Show-notes and Links
    • Matt Curry: @mattjcurry
    • Coté: @cote, cote.io

      • Libsyn downloads as of 20160912: 643

      50 min

    About Software Defined Interviews

    From the publisher's feed

    Deep discussions about technology, enterprise IT, and the like