2 years ago

Category: gitlab, automation, yaml, bitbucket

Docker’s Peter McKee sits down with Uffizzi Co-founders Grayson Adkins – who serves as Head of Product – and Josh Thurman – who serves as Head of Developer Relations – for a Q&A on the CP method. I love the idea of Continuous Previews, tell me what brought you guys to the concept?Grayson Adkins: The kernel of the idea – no pun intended – came from our own challenges in trying to develop our product faster.

At a high level, Continuous Previews equals continuous collaboration – so you have a process and technology that is facilitating a collaborative culture and that’s really when you start to see major improvements in team velocity, cycle times, lead times, and code stability.Peter McKee: I’ve read the CP Manifesto ( www.cpmanifesto.org / https://github.com/UffizziCloud/Continuous_Previews_Manifesto ) that outlines the principles of CP, what inspired you to write and publish that?Josh Thurman: It was clear to us that CP is so much bigger than any tool or service, and we also recognize that it’s easy to confuse tools or products with concepts.

But we also have a GUI and the concept of Templates that are meant to increase accessibility – the CP concept is something that can benefit teams of all sizes and skill levels, and we want to act as a DevOps force multiplier in those cases.Peter McKee: Speaking of barriers, what do you guys see as the biggest hurdle to teams adopting a CP methodology?Josh Thurman: For a method to take off it needs to be paired with a technology that is easy enough to use that it really starts to proliferate.

Of course this is what we are trying to do with Uffizzi in the context of full-stack and microservices applications.