So you've been working away on some code, and it works great. You then rebase on master, and it breaks.

aarrgghhhh!!!! Steam-from-the-ears!!! pulling-of-hair!!!

Until now, I'd either be checkoing out one branch at a time & testing, or doing some kind of cherry-picking into a new branch - either way, it's a pain keeping track of what's working & what's not.

The Senario

You are developing a plugin to an extension for a product, and you need to test functionality as you write.

Rancher (https://rancher.com) is a Kubenetes Cluster management tool.

When deployed as a single-node install, upgrades have consiquences - in the case of Rancher, the cluster goes off-line for a few seconds.

The Proof is in the pudding

Perl conference, 14th-17th August, Glasgow.

Perl 5 & Perl 6 are essentially the same language. Yes, there are some differences (using `.` rather than `->` for object references for example, however 95% of what your "perl-head" will still be valid)

When I started in this game, and I freely admit that was last century, "Full Stack" meant web servers and LAMP, and LAMP stood for Linux, Apache, Mysql, and PHP (or maybe Python).

Now, to be fair, that misses CSS... but the point is still that "Full Stack" was pretty simple.