JFrog

Trusting Your Ingredients - What Building Go Apps And Cheesecake Have In Common.

In this lightning session at GopherCon 2019, I got the chance to talk about two things I love. Cheesecake and Golang! As a developer, I’ve written code and built apps, and I realized that building apps and creating a cheesecake have a lot in common. In both cases you need to have the right ingredients, you need to trust your suppliers and have transparency in your production process. In this talk, we’ll look at how you can, and why you should, know what is in the app you deploy.

Go modules are here to stay and it’s about time to start modularizing your code. During the meetup at the Go UserGroup in Atlanta we spoke about:

• What Go modules are and why you need them
• The benefits are of using modules
• The differences between modules and the things we did before that
• What you need to do to “switch” to modules.

Go modules are here to stay and I got the chance to talk to the Atlanta chapter of Woman Who Go on what Go modules are and how you can switch to use them.

As a developer, I’ve written code and built apps, and I realized that building apps and creating a cheesecake have a lot in common. In both cases you need to have the right ingredients, you need to trust your suppliers and have transparency in your production process. I got to go to Atlanta and meet with the Docker Meetup Group there, where we got to talk about In this talk, how you can, and why you should, know what is in the app you deploy.

In my talk “Duct Tape and String: Continuously Delivering Serverless Microservices” at swampUP 2019, I got to talk about some best practice for the project that got me excited about both serverless and K8s: OpenFaaS! For me that meant I got to combine a lot of the things I care about (Containers, Serverless, and Golang), while talking about the awesome possibilities that using Artifactory brings you.

The Continuous Delivery Foundation had a colocated event at KubeCon + CloudNativeCon EU 2019 in Barcelona and The New Stack was there to report it. The day featured some awesome sessions from different companies that are part of the founding team of the foundation. I was honored to be interviewed by B. Cameron Gain and that made it into his article on The New Stack.

At the Twistlock Cloud-Native Security Day, a co-located event at KubeCon 2019, I got to talk about what cheesecake and building apps have in common. As a developer you’re responsible for the security of your app. Security in this case should be seen in the broadest sense of the word, ranging from licenses to software packages. A chef creating cheesecake has similar challenges. The ingredients of a cheesecake are similar to the software packages a developer uses. The preparation is similar to the DevOps pipeline, and recipe is similar to the licenses for developers. Messing up any of those means you have a messy kitchen, or a data breach! In this talk we’ll look at:

• Why do we care about licenses?
• How does Sec get into the early stages of DevSecOps?
• What can chefs and devs learn from each other?

Go modules are here to stay and it’s about time to start modularizing your code. At the Go Silicon Valley + Go Bridge meetup I presented a lightning session, which covered:

• Flying through what Go modules are and why you need them;
• What the benefits are of using modules;
• The differences between modules and the things we did before that;
• What you need to do to “switch” to modules.

As we talk to developers we frequently hear the same thing about Docker containers. They’re amazing for managing software, but my app also needs data and configuration. We store those on Docker volumes and we want to reuse those. Now what?

It was awesome to be at DevOps Days Baltimore and engage with the amazing audience there. Together with Baruch Sadogursky I got on stage to talk about how DevOps is usually viewed from a traditional perspective of a collaboration of Dev, Ops, and QA. Together with the fact that DevOps is usually driven by the change in Culture, People, and Process, the question arises how you know where you stand and where to move? As in almost any field, data and metrics give you the gauges and instruments.