Link: The Improbable Rise of the Daily News Podcast

Turns out there’s money in enclosure tags. Who knew? “In recent weeks, The Daily announced that it was becoming a national radio show. In doing so, it proved that scale can generate millions of dollars in new revenue, as well as (potentially) a hugely valuable spot on the national FM radio dial. That radio slot, in turn, will do wonders not only for The New York Times’ income statement, but also for its standing as a national brand. To put it another way: The Daily’s radio show won’t just make money on its own right, it will sell subscriptions to the newspaper and the website while doing so.”
Original source: The Improbable Rise of the Daily News Podcast

Pivotal Conversations: Debunking Cloud Foundry Myths

Our podcast this week:

There’s a whole slurry of myths about Cloud Foundry. With the platform updating so quickly, many of the issues behind these myths have long been addressed, and many were just false from the get-go. Coté and Richard talk about a recent post dismissing common myths. We also discuss recent news from the infrastructure software world and go over a bunch of upcoming events that Pivotal will be at.

If you use something like Overcast, be sure to check out the overly-extensive chapters and links right inside the podcast.

You should subscribe to the podcast!

Pivotal Conversations: Bringing Agility to Enterprise Data Workflows, with Sina Sojoodi

The summary:

This week we talk with about how organizations are increasingly looking to improve how they use data and workflows around data to innovate in their business. As with discuss with our guest, Sina Sojoodi, More than the usual ideas about “big data” and “machine learning,” we talk about the practical uses of data workflows like insurance claims handling and retail optimization. In many large, successful organizations the stacks to support all this processing are aging and not providing the agility businesses want. Of course, as you can guess, we have some suggestions for how to fix those problems, and also how to start thinking about data workflows differently. We also cover some recent news, mostly around Google Cloud Next and Pivotal’s recent momentum announcement.

Check out the SoundCloud page, or download the MP3 directly.

“[E]verybody likes growth in someone else’s backyard”

So, long run growth comes from one thing, and one thing only: Productivity. New and better ways of doing things. New and better products, new and better companies. It doesn’t come from 90% of the things that we talk about. So, the Federal Reserve, stimulus programs, even anti-inequality programs–over 10-20 years, it’s about productivity. Our ancestors may have, you know, you might have had a grandparent who dug coal with a pickaxe; and how did you get so much richer? Not by your union getting him higher wages and he still digs coal with a pickaxe at 20 cents an hour, not 10 cents. It’s because one guy left and he uses a bulldozer. Right? Growth comes from productivity. And productivity–everybody likes growth in someone else’s backyard. Productivity comes from new companies, doing things new ways, and making life very uncomfortable for everybody else. Uber is the great example. Uber is–that’s a great productivity enhancement. It’s putting a lot of people to work who otherwise couldn’t go to work. And the taxi companies hate it. And most of economic regulation is designed to stop growth. It’s designed to protect the old ways of doing things. So, what we need for growth-oriented policies is exactly that kind of innovation, that kind of new companies coming in an upending the status quo, that make everybody uncomfortable and run to their politician to say, ‘You’ve got to stop this.’

I don’t know the politics of economics enough to figure out if that’s a dick thing to say or not, but it sure makes grim-sense. The rest of the interview has some fun mental gymnastics and suave “turns out”’ing.

(And check out the show notes! That’s some intimidating work.)

Source: “EconTalk: John Cochrane on Economic Growth and Changing the Policy Debate”

071: Unbreakable Docker, or, elephants, er, like other elephants – Software Defined Talk

Eventually, you have to decide how your open source software is going to make money, and your partners probably won’t like it. That’s what the dust-up around Docker is this week, it seems to us. We also talk briefly about VMware’s big conference this week, and rumors of HPE selling off it’s Software group to private equity.

Check out the full show notes for links to the recommendations, conferences, and tech news items we didn’t get to cover:

Listen above, subscribe to the feed (or iTunes), or download the MP3 directly.

With Brandon Whichard, Matt Ray, and Coté.


Show notes

  • Nippers – “Nippers learn about safety at the beach. They learn about dangers such as rocks, and animals (e.g. the blue-ringed octopus), and also about surf conditions, such as rip currents, sandbars, and waves. Older Nippers also learn some basic first aid and may also learn CPR when they reach the age of 13.”

Can someone explain this “Docker forking” hoopla?

  • Coté’s write-up.
  • Docker Inc. doesn’t want to be a commoditized building block
    From a Red Hat person: “The conflict started to escalate earlier this summer, when Docker Inc used its controlling position to push Swarm, it’s own clone of Kubernetes-style container orchestration, into the core Docker project, putting the basic container runtime in a conflict with a notable part of its ecosystem. Docker Inc. then went on to essentially accuse Red Hat of forking Docker – at the Red Hat Summit no less. After that, Docker Inc’s Solomon Hykes came out strongly against the efforts to standardize the container runtime in OCI – an initiative his company co-founded.”
  • Re: that episode where we discuss Docker ecosystem challenges: “Yet on a regular basis, Red Hat patches that enable valid requirements from Red Hat customer use cases get shut down as it seems for the simple reason that they don’t fit into Docker Inc’s business strategy.”
  • A fight over where to draw the line between free/open/commodified and costs/proprietary/competitive: “And while I personally consider the orchestration layer the key to the container paradigm, the right approach here is to keep the orchestration separate from the core container runtime standardization. This avoids conflicts between different layers of the container runtime: we can agree on the common container package format, transport, and execution model without limiting choice between e.g. Kubernetes, Mesos, Swarm.”
  • Don’t bring a pistol to a bazooka fight. Enterprises love RHEL – have you ever tried to sell Ubuntu into organizations? It’s like what selling NT must have been like.

VMware hybrid cloud solutionaring

This Week in Tech Private Equity…

BONUS LINKS! Not covered in podcast.

Spaces vs. Tabs


060: “I’ll tell you this, if it’s support and services, they’re totally fucked.” – Software Defined Talk


If you’re in the container orchestration space, do you need to open source your platform? We use Mesosphere’s recent open sourcing of it all to discuss that topic, plus marketing in the container world and an ongoing arm-chair stratagizing of what’s going on the infrastructure software market right now with respect to containers.

Listen above, subscribe to the feed (or iTunes), or download the MP3 directly.

With Brandon Whichard, Matt Ray, and Coté.


Show notes

Mesosphere and Open Source

  • Tons of launch partners (60?), I wrote a Chef cookbook. 3 horse race of Docker, K8s & DC/OS (formerly Mesosphere)
  • Coverage from The New Stack.
  • 3Tera: Stephen on cloud back then, back when CA bought them
  • Coté’s 451 Research report on Mesosphere, from 2014.
  • The Ducy Docker whiteboard snap.
  • From 451 analyst note, Jay Lyman, March 24th, 2016:
    • Total funding to date: $126m – sweet Jesus! That’s a lot of DevOpsDays and O’Reilly conference booths!
    • Investors: Andreesen Horowitz, Khosla Ventures and Fuel Capital, with new investors A Capital and Triangle Peak Partners – Microsoft and HPE
  • From Jay’s longer report, March 2nd, 2016: “Mesosphere does not disclose its number of paying clients, but says it has dozens of large enterprise customers, its primary target. The company says its experience supporting software deployments in production is among its key differentiators, helped by the use of Apache Mesos by companies such as Twitter, Netflix, Airbnb, PayPal and Yelp, which was featured in a 451 User Deployment Report. Mesosphere says its focus is customer deployments of 500-1,000 nodes per day in production. It also says the bulk of its customers are licensees with professional services accounting for less than 10% of its clients, which tend to move to its subscription software.”
  • Q for Brandon: do you need to be open source to succeed in infrastructure? What’s your reflection across BMC, Sun, Zenoss, CA, Boundary, Solarwinds, and now IBM? You’ve dealt in all the things, in various stages of maturity: what’s the play you need here?
  • a16z podcast episode on selling to developers

How Uber is like deodorant

Feedback and Follow-up

  • Apparently the OpenStack Survey linked to last time was from October, here’s the fresh new April one:
    • NPS is actually fine
    • #1 business driver is saving money
    • Previously reported NPS scores were an error, actually trending up
    • Mistral no longer last most popular project (re; StackStorm Brocade acquisition)
  • A listener from Devoxx Poland contacted Coté about speaking there. THE DRUGS ARE WORKING!
  • Getting into Google Play Podcast – first of all: “Google, welcome to the party. (Oh, and fuck you – again – about Google Reader. I’m still bitter).” Second, I had to resubmit my verification email because I use at WordPress now, and they don’t do catch-all email because stupid reasons I could give a shit about, I’m sure – I went into Feedburner and redid it, and now am awaiting Google to send an email to itself so I can go enter the claim code into Google. WHAT A TIME TO BE ALIVE.

Bonus links, not covered in show

DevOps is Dead

  • Apparently the Cloud killed DevOps, or this title is click-bait
  • “DevOps as a team may be gone sooner than later, but its practices will be carried on to whole development teams so that we can continue to build upon what it has brought us in the past years.”
  • DevOpsDays Austin is officially a wake now!
  • This pieces had a great point to make, but sort of dry-humped it: “And when I say the cloud, I really mean managed services.” Outsourcing, brah. Outsourcing.

Azure and Containers

  • Answering part of last week’s question about “what’s up with containers?”, don’t see anything about Mesosphere here but at least it works with Visual Studio. Azure Stack not just IaaS, but also container manager and heading towards PaaS
  • “While Azure Stack would seem a fine standalone platform for the private cloud, it isn’t Microsoft’s end game. Azure Stack is Microsoft’s on-premises side of their hybrid strategy”


057: “Product managers in any large organization are product janitors.” – Software Defined Talk


In this episode, we discuss Cloud Management Platforms, unikernels, and product management. Also, go to a DevOpsDays!

Listen above, subscribe to the feed, or download the MP3 directly.

With Brandon Whichard, Matt Ray, and Coté.


Subscribe to this podcast: iTunes, RSS Feed

Show notes

BONUS LINKS, not in episode


The Requirements of Cloud Native – Interview on The New Stack

A little while ago I was on The New Stack Makers podcast with Alex Williams, talking cloud and Pivotal. Check it out:

Here’s what we go over:

In this podcast with Michael Coté, who works at Pivotal in technical marketing, he and The New Stack founder Alex Williams talk about current production systems and development environments for building applications. According to Coté, Pivotal describes these new systems and environments as “cloud native.”

Over the course of this interview, Coté discusses best practices and illustrates three requirements for cloud native development and deployment: utilizing the patterns of microservices architecture, implementing a DevOps approach, and striving for continuous delivery as the primary vehicle for software delivery.

Check it out!

053: I think I mighta gotten a heart from one of you guys – Software Defined Talk


After covering out genius new business model, we talk about Twitter, how Wall Street values tech companies, the Austin startup scene, follow-up on kick-off meetings, and recommendations.

Listen above, subscribe to the feed, or download the MP3 directly.

With Brandon Whichard, Matt Ray, and Coté.

SPONSOR: Interested in speeding your software’s cycle time, reducing release cycles, and a resilient cloud platform? Check out the free ebook on Cloud Foundry or take Cloud Foundry for a test drive with Pivotal Web Services. See those and other things at

Subscribe to this podcast: iTunes, RSS Feed

Show notes