Enterprise Golf, or, you get what you pay for, Software Defined Talk #27


Do you really need to play golf to make enterprise software sales? We explore that and other topics like FoundationDB shutting off it’s GitHub taps, GigaOm suddently shutting down, and tipcs on how to become a software company.

With Brandon Whichard, Matt Ray, and Coté.

SPONSOR: Pivotal has is releasing a new version of Pivotal Cloud Foundry and you can now run your platform in AWS. Also, check out why we like to say “platform” instead of “PaaS.” See details at https://cote.io/pivotal

SPONSOR: ChefCon, from Matt: Come check out ChefConf! March 31st to April 2nd. DevOps, configuration management, and the little dog. Get a nice discount with when you register with the code BETTERTOGETHER.

Sign up for my newsletter at coteindustries.com/memo.

Subscribe to this podcast: http://feeds.feedburner.com/SoftwareDefinedTalk

Show notes

BONUS LINKS! Not covered in show

We collect up links to talk about during the week but rarely get to all of them. Here’s the ones we neglected.



Finishing projects is hard, starting them is easy. That said, the moment of starting a project is critical, and assembling the team is incredibly impotent. We discuss that staff boot-strapping and the types of people who are good and not good for starting projects. We also discuss microservices and how this emerging style of architecture can help the product and business side out.

Subscribe to the feed: http://feeds.feedburner.com/UnderDevPodcast, or download the MP3 directly if you prefer.

Your friends @cote and @BillHiggins

Starting teams:

  • Projects don’t start often, most of them are “old” ones
  • Bill’s “special projects” LinkedIn status.
  • Keeping a list of people you’d want on your team
  • Recruiting the people – the painful part is the extraction process, moving them from their existing work to the new work
  • Finishing stuff is hard, starting is easy
  • While the project may come and go, the people have probably worked together several times before
  • Check out the Apple take, according to “Mr Ive.”


  • We try to summarize the thinking behind microservices. Other than pointing to existing things – the web – we think of it as “SOA that works this time.”
  • Based on this great write-up from James Lewis and Martin Fowler.
  • Coté’s mindmap on the topic.
  • They seemed to loose track of “speed” in SOA, where-as microservices is very focused on shipping, not perfectly modeling
  • We discuss the “business benefit” of mashups, composite applications, and thus, microservices architecting: enabling experimenting on the side, like all the Evernote apps… pace layering at the architectural layer means you can pace layer at the product management level.