LaineMinor
Laine has been a developer, a technical lead, a stay at home mom, and an IT architect – and that last was a broad enough title that it let her do both technical things AND cultural things.
She realized then that that was her most favorite place to be, in that in-between place of technology and culture.
She also learned that enabling people and organizations is HARD work, and that explaining that in-between place can help.
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.
The world around us exists as a collection of events - things that happen and data points that we take in and process and decide what to do about (or not do about), all the time, every day. So...why shouldn't the systems we interact with be structured in the same way?
The world around us exists as a collection of events - things that happen and data points that we take in and process and decide what to do about (or not do about), all the time, every day. So...why shouldn't the systems we interact with be structured in the same way?
The hardest parts of technology are people and what they do - so, _culture_ and _process_. In the center of that is how to determine the right amount of oversight when implementing technology or the processes around that technology. That "right amount of oversight" is typically referred to as "governance."
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?
What exactly does it mean to be "not a cultural fit" for an organization? Is it a slightly more polite euphemism for "that person was terrible at their job"? Or maybe, "they had no social skills to speak of"? What happens when it means that it's the _organization_ that's...kind of terrible at their job? What if _no one_ is actually terrible at their job and "not a cultural fit" is a simple statement of fact?
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.
Zero fluff.