Josh has been in in IT for 15 years, as a developer, lead dev, tech lead, architect, and enterprise architect. He's worked on big teams, small teams, and been on a team of one. In the process of all of this, he's learned a ton, and he loves to mentor and share that information.
He also loves strategy – laying out plans and figuring out dependencies, which order to do things in. Included in this is a deep love of the complicated business + people + culture + tech (especially tech that makes people's lives easier) of IT strategy.
This DevSecOps Workshop is a unique hands-on experience for building, deploying, and securing containerized cloud-native applications using industry-standard open source technologies.
CRI-O and Buildah and Podman, OH MY. (...and Skopeo, and what on Earth happened with Docker, and......) Containers are really cool, and also useful. Everyone knows it! The open source community has rallied around them and are constantly making improvements and tweaks to their capabilities. But...the tools generated by those open source communities are constantly evolving, and it ends up really hard to keep up on what does what and...why you should care.
Want to bring in [new cool thing X] or [necessary technology change Y] to your company, because you know there's a need for it? GOOD IDEA! Except...now what? If your company is more than about 3 people, how do you explain, enable, and encourage the adoption of this change, especially if it will require some work on everyone’s part?
There is pain inherent in development - monoliths, confusing deployment processes, conflict between dev/ops/business.
A long time ago, in a land far far away, there were monoliths. These fabled artifacts brought consistency and stability to the land - but there was a cost in speed, agility, time, and development pain. Whether Java EE, .NET, or something else, the big ol' integrated plexi-purpose binaries or yore (and also now...) have grown into problems that hurt developers, architects, and the execution of business goals.