vagrant

I'm leaving most of this post to the podcast version as I had a co-host in the form of [Cate Lawrence](https://medium.com/u/529dde579def){.markup--user .markup--p-user data-href="https://medium.com/u/529dde579def" anchor-type="2" user-id="529dde579def" action-value="529dde579def" data-action="show-user-card" action-type="hover" target="_blank"} and we spoke for nearly an hour about Bitspiration, startups in Eastern Europe, Warsaw, WW2, IoT, Booth Babes, Europe vs Silicon Valley and much, much more.

Not so long ago, Vagrant was the prime tool that attempted to solve that time-immemorial problem of "it works on my machine." Developers could create shareable Vagrant files to allow coworkers to spin up replica machines for testing code and the interconnecting parts of a typical modern project. Vagrant is far from dead, but it suffers from a couple of long-lasting issues, including the resource footprint of virtual machines created, the speed of sharing files between the host and virtual machin...

HashiCorp tools have been around and are a standard for their contributions to continuous integration workflows. Learn the basics here. {::options parse_block_html="true" /} <div class="author"> <img src="https://www.rss-specifications.com/rss-spec-rss.gif" style="width: 96px; height: 96;"> <span style="position: absolute; padding: 32px 15px;">{% comment %}Remark that post_url refers to the *original* post url, not Jekyll's post_url variable. Moreover, planet.rb preprocesses the substitutions...