際際滷shows by User: ggotimer / http://www.slideshare.net/images/logo.gif 際際滷shows by User: ggotimer / Wed, 16 Oct 2024 15:49:55 GMT 際際滷Share feed for 際際滷shows by User: ggotimer Clean Your Cloud with Cloud Custodian slides /slideshow/clean-your-cloud-with-cloud-custodian-slides/272470133 cloudcustodian-241016154955-88820951
One of the great things about using the cloud is how easy it is to spin up resources and use them. The downside is it is really easy to spin up resources and forget about them. Sprawl becomes a real problem. You waste money if you fail to shut them down when you finish with them or even overnight. And it isnt just costs. Managing a cloud infrastructure can be a real pain. Who spun this up? What project is it for? Does it need to be shut down? When? Shouldnt it be encrypted? Cloud Custodian is an easy-to-use framework that allows simple YAML files to specify how to gather, filter, and act on cloud resources across accounts and providers. Generate reports, automatically tag items, shut down non-compliant resources, or even reconfigure them to be compliant. Join Gene as he shows you how to manage your cloud resources.]]>
One of the great things about using the cloud is how easy it is to spin up resources and use them. The downside is it is really easy to spin up resources and forget about them. Sprawl becomes a real problem. You waste money if you fail to shut them down when you finish with them or even overnight. And it isnt just costs. Managing a cloud infrastructure can be a real pain. Who spun this up? What project is it for? Does it need to be shut down? When? Shouldnt it be encrypted? Cloud Custodian is an easy-to-use framework that allows simple YAML files to specify how to gather, filter, and act on cloud resources across accounts and providers. Generate reports, automatically tag items, shut down non-compliant resources, or even reconfigure them to be compliant. Join Gene as he shows you how to manage your cloud resources.]]> Wed, 16 Oct 2024 15:49:55 GMT /slideshow/clean-your-cloud-with-cloud-custodian-slides/272470133 ggotimer@slideshare.net(ggotimer) Clean Your Cloud with Cloud Custodian slides ggotimer One of the great things about using the cloud is how easy it is to spin up resources and use them. The downside is it is really easy to spin up resources and forget about them. Sprawl becomes a real problem. You waste money if you fail to shut them down when you finish with them or even overnight. And it isnt just costs. Managing a cloud infrastructure can be a real pain. Who spun this up? What project is it for? Does it need to be shut down? When? Shouldnt it be encrypted? Cloud Custodian is an easy-to-use framework that allows simple YAML files to specify how to gather, filter, and act on cloud resources across accounts and providers. Generate reports, automatically tag items, shut down non-compliant resources, or even reconfigure them to be compliant. Join Gene as he shows you how to manage your cloud resources. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/cloudcustodian-241016154955-88820951-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> One of the great things about using the cloud is how easy it is to spin up resources and use them. The downside is it is really easy to spin up resources and forget about them. Sprawl becomes a real problem. You waste money if you fail to shut them down when you finish with them or even overnight. And it isnt just costs. Managing a cloud infrastructure can be a real pain. Who spun this up? What project is it for? Does it need to be shut down? When? Shouldnt it be encrypted? Cloud Custodian is an easy-to-use framework that allows simple YAML files to specify how to gather, filter, and act on cloud resources across accounts and providers. Generate reports, automatically tag items, shut down non-compliant resources, or even reconfigure them to be compliant. Join Gene as he shows you how to manage your cloud resources.
Clean Your Cloud with Cloud Custodian slides from Gene Gotimer
]]> 23 0 https://cdn.slidesharecdn.com/ss_thumbnails/cloudcustodian-241016154955-88820951-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 A Hands-on Intro to Containers- Nebraska.Code() /slideshow/a-hands-on-intro-to-containers-nebraska/270324571 handsoncontainers-240718223142-d63b24a5
https://github.com/OtherDevOpsGene/intro-to-docker Containers are one of the hottest technologies in our industry today. They are like virtual machines but smaller and faster. They can provide on-demand, disposable test environments that start quickly, repeatably, locally or in the cloud. When you want, you can tear down the environment and recreate a pristine copy within seconds. And since the process is automated, anyone on the team can use the same commands to get their own test systems. Then, when you finish testing, those containers can be deployed directly into production. At each stage, the environments for development, test, and production will all look and behave the same. This workshop is a hands-on introduction for anyone interested in learning about containers in general and more specifically Dockeryou will need your laptop. You will walk through building docker containers, starting out simple but moving to more pragmatic setups. Youll test those systems locally and in the cloud. As you iterate, you will build out tests and capabilities. And then Gene will show you how all of this evolves to a full-blown, production-ready setup.]]>
https://github.com/OtherDevOpsGene/intro-to-docker Containers are one of the hottest technologies in our industry today. They are like virtual machines but smaller and faster. They can provide on-demand, disposable test environments that start quickly, repeatably, locally or in the cloud. When you want, you can tear down the environment and recreate a pristine copy within seconds. And since the process is automated, anyone on the team can use the same commands to get their own test systems. Then, when you finish testing, those containers can be deployed directly into production. At each stage, the environments for development, test, and production will all look and behave the same. This workshop is a hands-on introduction for anyone interested in learning about containers in general and more specifically Dockeryou will need your laptop. You will walk through building docker containers, starting out simple but moving to more pragmatic setups. Youll test those systems locally and in the cloud. As you iterate, you will build out tests and capabilities. And then Gene will show you how all of this evolves to a full-blown, production-ready setup.]]> Thu, 18 Jul 2024 22:31:42 GMT /slideshow/a-hands-on-intro-to-containers-nebraska/270324571 ggotimer@slideshare.net(ggotimer) A Hands-on Intro to Containers- Nebraska.Code() ggotimer https://github.com/OtherDevOpsGene/intro-to-docker Containers are one of the hottest technologies in our industry today. They are like virtual machines but smaller and faster. They can provide on-demand, disposable test environments that start quickly, repeatably, locally or in the cloud. When you want, you can tear down the environment and recreate a pristine copy within seconds. And since the process is automated, anyone on the team can use the same commands to get their own test systems. Then, when you finish testing, those containers can be deployed directly into production. At each stage, the environments for development, test, and production will all look and behave the same. This workshop is a hands-on introduction for anyone interested in learning about containers in general and more specifically Dockeryou will need your laptop. You will walk through building docker containers, starting out simple but moving to more pragmatic setups. Youll test those systems locally and in the cloud. As you iterate, you will build out tests and capabilities. And then Gene will show you how all of this evolves to a full-blown, production-ready setup. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/handsoncontainers-240718223142-d63b24a5-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> https://github.com/OtherDevOpsGene/intro-to-docker Containers are one of the hottest technologies in our industry today. They are like virtual machines but smaller and faster. They can provide on-demand, disposable test environments that start quickly, repeatably, locally or in the cloud. When you want, you can tear down the environment and recreate a pristine copy within seconds. And since the process is automated, anyone on the team can use the same commands to get their own test systems. Then, when you finish testing, those containers can be deployed directly into production. At each stage, the environments for development, test, and production will all look and behave the same. This workshop is a hands-on introduction for anyone interested in learning about containers in general and more specifically Dockeryou will need your laptop. You will walk through building docker containers, starting out simple but moving to more pragmatic setups. Youll test those systems locally and in the cloud. As you iterate, you will build out tests and capabilities. And then Gene will show you how all of this evolves to a full-blown, production-ready setup.
A Hands-on Intro to Containers- Nebraska.Code() from Gene Gotimer
]]> 16 0 https://cdn.slidesharecdn.com/ss_thumbnails/handsoncontainers-240718223142-d63b24a5-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 A Developer's Guide to Kubernetes Security /slideshow/a-developer-s-guide-to-kubernetes-security/270324569 adevsguidetokubernetessecurity-240718223142-51a82f5d
Kubernetes is spreading like crazy across our industry, but most of us are just thrown into the deep end and expected to learn it ourselves. And we do, sort of. We figure out just enough to get our job done, but we have none of the experience to know if we are doing it right. There is a lot to learn in a technology that is rapidly evolving. The good news is that there are tools and practices to help show us the way. We will build some containers and get them safely deployed into a Kubernetes cluster. We will make sure they are available, resilient, and secure. Well be using Kubernetes to help us deploy software, not worrying if it will get us fired.]]>
Kubernetes is spreading like crazy across our industry, but most of us are just thrown into the deep end and expected to learn it ourselves. And we do, sort of. We figure out just enough to get our job done, but we have none of the experience to know if we are doing it right. There is a lot to learn in a technology that is rapidly evolving. The good news is that there are tools and practices to help show us the way. We will build some containers and get them safely deployed into a Kubernetes cluster. We will make sure they are available, resilient, and secure. Well be using Kubernetes to help us deploy software, not worrying if it will get us fired.]]> Thu, 18 Jul 2024 22:31:42 GMT /slideshow/a-developer-s-guide-to-kubernetes-security/270324569 ggotimer@slideshare.net(ggotimer) A Developer's Guide to Kubernetes Security ggotimer Kubernetes is spreading like crazy across our industry, but most of us are just thrown into the deep end and expected to learn it ourselves. And we do, sort of. We figure out just enough to get our job done, but we have none of the experience to know if we are doing it right. There is a lot to learn in a technology that is rapidly evolving. The good news is that there are tools and practices to help show us the way. We will build some containers and get them safely deployed into a Kubernetes cluster. We will make sure they are available, resilient, and secure. Well be using Kubernetes to help us deploy software, not worrying if it will get us fired. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/adevsguidetokubernetessecurity-240718223142-51a82f5d-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Kubernetes is spreading like crazy across our industry, but most of us are just thrown into the deep end and expected to learn it ourselves. And we do, sort of. We figure out just enough to get our job done, but we have none of the experience to know if we are doing it right. There is a lot to learn in a technology that is rapidly evolving. The good news is that there are tools and practices to help show us the way. We will build some containers and get them safely deployed into a Kubernetes cluster. We will make sure they are available, resilient, and secure. Well be using Kubernetes to help us deploy software, not worrying if it will get us fired.
A Developer's Guide to Kubernetes Security from Gene Gotimer
]]> 43 0 https://cdn.slidesharecdn.com/ss_thumbnails/adevsguidetokubernetessecurity-240718223142-51a82f5d-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Fixing Git Catastrophes - Nebraska.Code() /slideshow/fixing-git-catastrophes-nebraska-code/270324568 fixinggitcatastrophes-240718223141-fecc0cfa
The code is written and the tests pass. I just have to commit this last round of changes to my branch. Wait, why does that say committed to main? Did I commit all those changes to main? Arghh! I cant redo all of this! Committing changes to the wrong branch, forgetting files, misspelling the commit message, and needing to undo commits are some of the advanced features of Git that we normal people run into way too often and need help with. The fixes are often easy once you know what they are. But in the heat of the moment, with the deadline (or Friday afternoon) approaching, it isnt always easy to figure out what magic spell to cast to get Git to do what you need. Well spend some time looking at typical Git situations people get themselves into, and then well demonstrate how to get out of them. This isnt about Git internals or a Git masters class this real-world Git when things arent going right. And there will be plenty of time for questions, so bring your best Git nightmare scenarios so we can figure out how to recover.]]>
The code is written and the tests pass. I just have to commit this last round of changes to my branch. Wait, why does that say committed to main? Did I commit all those changes to main? Arghh! I cant redo all of this! Committing changes to the wrong branch, forgetting files, misspelling the commit message, and needing to undo commits are some of the advanced features of Git that we normal people run into way too often and need help with. The fixes are often easy once you know what they are. But in the heat of the moment, with the deadline (or Friday afternoon) approaching, it isnt always easy to figure out what magic spell to cast to get Git to do what you need. Well spend some time looking at typical Git situations people get themselves into, and then well demonstrate how to get out of them. This isnt about Git internals or a Git masters class this real-world Git when things arent going right. And there will be plenty of time for questions, so bring your best Git nightmare scenarios so we can figure out how to recover.]]> Thu, 18 Jul 2024 22:31:41 GMT /slideshow/fixing-git-catastrophes-nebraska-code/270324568 ggotimer@slideshare.net(ggotimer) Fixing Git Catastrophes - Nebraska.Code() ggotimer The code is written and the tests pass. I just have to commit this last round of changes to my branch. Wait, why does that say committed to main? Did I commit all those changes to main? Arghh! I cant redo all of this! Committing changes to the wrong branch, forgetting files, misspelling the commit message, and needing to undo commits are some of the advanced features of Git that we normal people run into way too often and need help with. The fixes are often easy once you know what they are. But in the heat of the moment, with the deadline (or Friday afternoon) approaching, it isnt always easy to figure out what magic spell to cast to get Git to do what you need. Well spend some time looking at typical Git situations people get themselves into, and then well demonstrate how to get out of them. This isnt about Git internals or a Git masters class this real-world Git when things arent going right. And there will be plenty of time for questions, so bring your best Git nightmare scenarios so we can figure out how to recover. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/fixinggitcatastrophes-240718223141-fecc0cfa-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> The code is written and the tests pass. I just have to commit this last round of changes to my branch. Wait, why does that say committed to main? Did I commit all those changes to main? Arghh! I cant redo all of this! Committing changes to the wrong branch, forgetting files, misspelling the commit message, and needing to undo commits are some of the advanced features of Git that we normal people run into way too often and need help with. The fixes are often easy once you know what they are. But in the heat of the moment, with the deadline (or Friday afternoon) approaching, it isnt always easy to figure out what magic spell to cast to get Git to do what you need. Well spend some time looking at typical Git situations people get themselves into, and then well demonstrate how to get out of them. This isnt about Git internals or a Git masters class this real-world Git when things arent going right. And there will be plenty of time for questions, so bring your best Git nightmare scenarios so we can figure out how to recover.
Fixing Git Catastrophes - Nebraska.Code() from Gene Gotimer
]]> 21 0 https://cdn.slidesharecdn.com/ss_thumbnails/fixinggitcatastrophes-240718223141-fecc0cfa-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 KCDC- Keeping Secrets Out of Your Pipeline /slideshow/kcdc-keeping-secrets-out-of-your-pipeline/269947553 keepingsecrets-240628144003-f276a9db
Commit your code, push a button, and everything is deployed the Holy Grail of DevOps. Nobody has to type any commands or passwords to push your app live, everything lives in source control and it all just works. Wait a second! My passwords are in source code? How did they get in there? How can I stop it from happening again? And how can I keep credentials out of source code and still make them available to my DevOps pipeline? Well talk about using the open-source TruffleHog tool to find sensitive information in our source code repositories. And how to catch credentials before they are exposed. Finally, well look at HashiCorp Vault, another open-source tool designed specifically to securely store and retrieve secrets from the pipeline without making them available to everyone. ]]>
Commit your code, push a button, and everything is deployed the Holy Grail of DevOps. Nobody has to type any commands or passwords to push your app live, everything lives in source control and it all just works. Wait a second! My passwords are in source code? How did they get in there? How can I stop it from happening again? And how can I keep credentials out of source code and still make them available to my DevOps pipeline? Well talk about using the open-source TruffleHog tool to find sensitive information in our source code repositories. And how to catch credentials before they are exposed. Finally, well look at HashiCorp Vault, another open-source tool designed specifically to securely store and retrieve secrets from the pipeline without making them available to everyone. ]]> Fri, 28 Jun 2024 14:40:03 GMT /slideshow/kcdc-keeping-secrets-out-of-your-pipeline/269947553 ggotimer@slideshare.net(ggotimer) KCDC- Keeping Secrets Out of Your Pipeline ggotimer Commit your code, push a button, and everything is deployed the Holy Grail of DevOps. Nobody has to type any commands or passwords to push your app live, everything lives in source control and it all just works. Wait a second! My passwords are in source code? How did they get in there? How can I stop it from happening again? And how can I keep credentials out of source code and still make them available to my DevOps pipeline? Well talk about using the open-source TruffleHog tool to find sensitive information in our source code repositories. And how to catch credentials before they are exposed. Finally, well look at HashiCorp Vault, another open-source tool designed specifically to securely store and retrieve secrets from the pipeline without making them available to everyone. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/keepingsecrets-240628144003-f276a9db-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Commit your code, push a button, and everything is deployed the Holy Grail of DevOps. Nobody has to type any commands or passwords to push your app live, everything lives in source control and it all just works. Wait a second! My passwords are in source code? How did they get in there? How can I stop it from happening again? And how can I keep credentials out of source code and still make them available to my DevOps pipeline? Well talk about using the open-source TruffleHog tool to find sensitive information in our source code repositories. And how to catch credentials before they are exposed. Finally, well look at HashiCorp Vault, another open-source tool designed specifically to securely store and retrieve secrets from the pipeline without making them available to everyone.
KCDC- Keeping Secrets Out of Your Pipeline from Gene Gotimer
]]> 18 0 https://cdn.slidesharecdn.com/ss_thumbnails/keepingsecrets-240628144003-f276a9db-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 How Fast Is My App? Performance Testing 101 /slideshow/how-fast-is-my-app-performance-testing-101/269932100 howfastismyapp-240627210448-4b957871
Product owners and stakeholders love to ask about performance. Is the app fast? How fast? What do those questions even mean? Are they interested in the number of transactions per second? The time for the page to load? How many users it can support at once? Performance testing is a much broader topic than just being able to say an application is fast or slow. There is load testing, stress testing, and soak testing. You can measure transaction times, concurrency, and capacity. You can address some performance issues with more systems, others with more memory or faster processors or a better network. It all depends on what you mean by "How fast?" Join Gene Gotimer as he showcases open source tools like JMeter and Gatling to measure different types of performance testing. He'll also discuss how Firefox and Chrome can show what the user experience is like in terms of performance. You will leave with a better understanding of what performance testing is, as well as some tools to get started implementing it in your delivery pipeline. ]]>
Product owners and stakeholders love to ask about performance. Is the app fast? How fast? What do those questions even mean? Are they interested in the number of transactions per second? The time for the page to load? How many users it can support at once? Performance testing is a much broader topic than just being able to say an application is fast or slow. There is load testing, stress testing, and soak testing. You can measure transaction times, concurrency, and capacity. You can address some performance issues with more systems, others with more memory or faster processors or a better network. It all depends on what you mean by "How fast?" Join Gene Gotimer as he showcases open source tools like JMeter and Gatling to measure different types of performance testing. He'll also discuss how Firefox and Chrome can show what the user experience is like in terms of performance. You will leave with a better understanding of what performance testing is, as well as some tools to get started implementing it in your delivery pipeline. ]]> Thu, 27 Jun 2024 21:04:48 GMT /slideshow/how-fast-is-my-app-performance-testing-101/269932100 ggotimer@slideshare.net(ggotimer) How Fast Is My App? Performance Testing 101 ggotimer Product owners and stakeholders love to ask about performance. Is the app fast? How fast? What do those questions even mean? Are they interested in the number of transactions per second? The time for the page to load? How many users it can support at once? Performance testing is a much broader topic than just being able to say an application is fast or slow. There is load testing, stress testing, and soak testing. You can measure transaction times, concurrency, and capacity. You can address some performance issues with more systems, others with more memory or faster processors or a better network. It all depends on what you mean by "How fast?" Join Gene Gotimer as he showcases open source tools like JMeter and Gatling to measure different types of performance testing. He'll also discuss how Firefox and Chrome can show what the user experience is like in terms of performance. You will leave with a better understanding of what performance testing is, as well as some tools to get started implementing it in your delivery pipeline. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/howfastismyapp-240627210448-4b957871-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Product owners and stakeholders love to ask about performance. Is the app fast? How fast? What do those questions even mean? Are they interested in the number of transactions per second? The time for the page to load? How many users it can support at once? Performance testing is a much broader topic than just being able to say an application is fast or slow. There is load testing, stress testing, and soak testing. You can measure transaction times, concurrency, and capacity. You can address some performance issues with more systems, others with more memory or faster processors or a better network. It all depends on what you mean by &quot;How fast?&quot; Join Gene Gotimer as he showcases open source tools like JMeter and Gatling to measure different types of performance testing. He&#39;ll also discuss how Firefox and Chrome can show what the user experience is like in terms of performance. You will leave with a better understanding of what performance testing is, as well as some tools to get started implementing it in your delivery pipeline.
How Fast Is My App? Performance Testing 101 from Gene Gotimer
]]> 10 0 https://cdn.slidesharecdn.com/ss_thumbnails/howfastismyapp-240627210448-4b957871-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 A Developers Guide to Kubernetes Security /slideshow/a-developers-guide-to-kubernetes-security/262324497 adevsguidetokubernetessecurity-231016213615-7f71616f
Kubernetes is spreading like crazy across our industry, but most of us are just thrown into the deep end and expected to learn it ourselves. And we do, sort of. We figure out just enough to get our job done, but we dont have the experience to know if we are doing it right. There is a lot to learn in a technology that is rapidly evolving. The good news is that there are tools and practices to help show us the way. Join Gene as he shows you what you need to know as a developer to use Kubernetes safely and effectively. Hell show you some tools you can use to ensure your containers are available, resilient, and secure. They wont slow you down, wont cost an arm and a leg, and wont need you to be a security expert or experienced cloud architect. Well use Kubernetes to help us deploy software, not worrying if it will get us fired.]]>
Kubernetes is spreading like crazy across our industry, but most of us are just thrown into the deep end and expected to learn it ourselves. And we do, sort of. We figure out just enough to get our job done, but we dont have the experience to know if we are doing it right. There is a lot to learn in a technology that is rapidly evolving. The good news is that there are tools and practices to help show us the way. Join Gene as he shows you what you need to know as a developer to use Kubernetes safely and effectively. Hell show you some tools you can use to ensure your containers are available, resilient, and secure. They wont slow you down, wont cost an arm and a leg, and wont need you to be a security expert or experienced cloud architect. Well use Kubernetes to help us deploy software, not worrying if it will get us fired.]]> Mon, 16 Oct 2023 21:36:14 GMT /slideshow/a-developers-guide-to-kubernetes-security/262324497 ggotimer@slideshare.net(ggotimer) A Developers Guide to Kubernetes Security ggotimer Kubernetes is spreading like crazy across our industry, but most of us are just thrown into the deep end and expected to learn it ourselves. And we do, sort of. We figure out just enough to get our job done, but we dont have the experience to know if we are doing it right. There is a lot to learn in a technology that is rapidly evolving. The good news is that there are tools and practices to help show us the way. Join Gene as he shows you what you need to know as a developer to use Kubernetes safely and effectively. Hell show you some tools you can use to ensure your containers are available, resilient, and secure. They wont slow you down, wont cost an arm and a leg, and wont need you to be a security expert or experienced cloud architect. Well use Kubernetes to help us deploy software, not worrying if it will get us fired. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/adevsguidetokubernetessecurity-231016213615-7f71616f-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Kubernetes is spreading like crazy across our industry, but most of us are just thrown into the deep end and expected to learn it ourselves. And we do, sort of. We figure out just enough to get our job done, but we dont have the experience to know if we are doing it right. There is a lot to learn in a technology that is rapidly evolving. The good news is that there are tools and practices to help show us the way. Join Gene as he shows you what you need to know as a developer to use Kubernetes safely and effectively. Hell show you some tools you can use to ensure your containers are available, resilient, and secure. They wont slow you down, wont cost an arm and a leg, and wont need you to be a security expert or experienced cloud architect. Well use Kubernetes to help us deploy software, not worrying if it will get us fired.
A Developers Guide to Kubernetes Security from Gene Gotimer
]]> 105 0 https://cdn.slidesharecdn.com/ss_thumbnails/adevsguidetokubernetessecurity-231016213615-7f71616f-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 How I Learned to Stop Worrying and Love Legacy Code /slideshow/how-i-learned-to-stop-worrying-and-love-legacy-code-258569096/258569096 gotimer-lovelegacycode-230622221817-54b2a89b
Many developers would love to work on brand-new, cutting-edge, greenfield projects, never dealing with the mess of unintelligible code someone else left behind. But most of us spend most of our time maintaining existing code, and it is often spaghetti code with no unit tests, no documentation, and, if we are lucky, a comment that says, Not sure how this works, but it does so dont touch it. We need to make changes, but we cant even figure out what the code is supposed to do. You know your changes will pile on and make it worse. You cant change the code safely without adding tests, but you cant add tests without making changes. So how do you tackle this chicken-and-egg problem? You do it slowly and methodically, building a safety net along the way. Join Gene as he talks about helping to maintain and improve code on an infamous software project- it was so bad it made the national news. Hell explain his approach to breaking the code into manageable, maintainable chunks. Hell talk about adding unit tests that actually test the code using mutation testing- one of his favorite subjects. If you have inherited a pile of code and want to clean it up into something you arent afraid to touch, this talk is for you. Youll hear about some tools and approaches to help you turn legacy code into code you dont hate.]]>
Many developers would love to work on brand-new, cutting-edge, greenfield projects, never dealing with the mess of unintelligible code someone else left behind. But most of us spend most of our time maintaining existing code, and it is often spaghetti code with no unit tests, no documentation, and, if we are lucky, a comment that says, Not sure how this works, but it does so dont touch it. We need to make changes, but we cant even figure out what the code is supposed to do. You know your changes will pile on and make it worse. You cant change the code safely without adding tests, but you cant add tests without making changes. So how do you tackle this chicken-and-egg problem? You do it slowly and methodically, building a safety net along the way. Join Gene as he talks about helping to maintain and improve code on an infamous software project- it was so bad it made the national news. Hell explain his approach to breaking the code into manageable, maintainable chunks. Hell talk about adding unit tests that actually test the code using mutation testing- one of his favorite subjects. If you have inherited a pile of code and want to clean it up into something you arent afraid to touch, this talk is for you. Youll hear about some tools and approaches to help you turn legacy code into code you dont hate.]]> Thu, 22 Jun 2023 22:18:16 GMT /slideshow/how-i-learned-to-stop-worrying-and-love-legacy-code-258569096/258569096 ggotimer@slideshare.net(ggotimer) How I Learned to Stop Worrying and Love Legacy Code ggotimer Many developers would love to work on brand-new, cutting-edge, greenfield projects, never dealing with the mess of unintelligible code someone else left behind. But most of us spend most of our time maintaining existing code, and it is often spaghetti code with no unit tests, no documentation, and, if we are lucky, a comment that says, Not sure how this works, but it does so dont touch it. We need to make changes, but we cant even figure out what the code is supposed to do. You know your changes will pile on and make it worse. You cant change the code safely without adding tests, but you cant add tests without making changes. So how do you tackle this chicken-and-egg problem? You do it slowly and methodically, building a safety net along the way. Join Gene as he talks about helping to maintain and improve code on an infamous software project- it was so bad it made the national news. Hell explain his approach to breaking the code into manageable, maintainable chunks. Hell talk about adding unit tests that actually test the code using mutation testing- one of his favorite subjects. If you have inherited a pile of code and want to clean it up into something you arent afraid to touch, this talk is for you. Youll hear about some tools and approaches to help you turn legacy code into code you dont hate. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/gotimer-lovelegacycode-230622221817-54b2a89b-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Many developers would love to work on brand-new, cutting-edge, greenfield projects, never dealing with the mess of unintelligible code someone else left behind. But most of us spend most of our time maintaining existing code, and it is often spaghetti code with no unit tests, no documentation, and, if we are lucky, a comment that says, Not sure how this works, but it does so dont touch it. We need to make changes, but we cant even figure out what the code is supposed to do. You know your changes will pile on and make it worse. You cant change the code safely without adding tests, but you cant add tests without making changes. So how do you tackle this chicken-and-egg problem? You do it slowly and methodically, building a safety net along the way. Join Gene as he talks about helping to maintain and improve code on an infamous software project- it was so bad it made the national news. Hell explain his approach to breaking the code into manageable, maintainable chunks. Hell talk about adding unit tests that actually test the code using mutation testing- one of his favorite subjects. If you have inherited a pile of code and want to clean it up into something you arent afraid to touch, this talk is for you. Youll hear about some tools and approaches to help you turn legacy code into code you dont hate.
How I Learned to Stop Worrying and Love Legacy Code from Gene Gotimer
]]> 29 0 https://cdn.slidesharecdn.com/ss_thumbnails/gotimer-lovelegacycode-230622221817-54b2a89b-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Ten Ways To Doom Your DevOps /slideshow/ten-ways-to-doom-your-devops/255247534 tenwaystodoomyourdevops-230110023948-5deebf5e
Well do whatever it takes to make DevOps work!" followed by, "No, we cant change that! Almost every organization manages to sabotage its own DevOps transformation or get in its own way to ensure that successful adoption isnt likely. Henry Ford called it when it comes to change: Whether you think you can or you think you cant, youre right. Organizations that dont want to change or dont think they can almost always fail. Those that change themselves and their processes get to the culture they want. Based on experiences working with government agencies, Gene Gotimer highlights ten practices that doom a DevOps effort from the get-go and describes the DevOps-enabling alternative.]]>
Well do whatever it takes to make DevOps work!" followed by, "No, we cant change that! Almost every organization manages to sabotage its own DevOps transformation or get in its own way to ensure that successful adoption isnt likely. Henry Ford called it when it comes to change: Whether you think you can or you think you cant, youre right. Organizations that dont want to change or dont think they can almost always fail. Those that change themselves and their processes get to the culture they want. Based on experiences working with government agencies, Gene Gotimer highlights ten practices that doom a DevOps effort from the get-go and describes the DevOps-enabling alternative.]]> Tue, 10 Jan 2023 02:39:47 GMT /slideshow/ten-ways-to-doom-your-devops/255247534 ggotimer@slideshare.net(ggotimer) Ten Ways To Doom Your DevOps ggotimer Well do whatever it takes to make DevOps work!" followed by, "No, we cant change that! Almost every organization manages to sabotage its own DevOps transformation or get in its own way to ensure that successful adoption isnt likely. Henry Ford called it when it comes to change: Whether you think you can or you think you cant, youre right. Organizations that dont want to change or dont think they can almost always fail. Those that change themselves and their processes get to the culture they want. Based on experiences working with government agencies, Gene Gotimer highlights ten practices that doom a DevOps effort from the get-go and describes the DevOps-enabling alternative. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/tenwaystodoomyourdevops-230110023948-5deebf5e-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Well do whatever it takes to make DevOps work!&quot; followed by, &quot;No, we cant change that! Almost every organization manages to sabotage its own DevOps transformation or get in its own way to ensure that successful adoption isnt likely. Henry Ford called it when it comes to change: Whether you think you can or you think you cant, youre right. Organizations that dont want to change or dont think they can almost always fail. Those that change themselves and their processes get to the culture they want. Based on experiences working with government agencies, Gene Gotimer highlights ten practices that doom a DevOps effort from the get-go and describes the DevOps-enabling alternative.
Ten Ways To Doom Your DevOps from Gene Gotimer
]]> 37 0 https://cdn.slidesharecdn.com/ss_thumbnails/tenwaystodoomyourdevops-230110023948-5deebf5e-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Keeping Your Kubernetes Cluster Secure /slideshow/keeping-your-kubernetes-cluster-secure-254002353/254002353 keepingyourkubernetesclustersecure-221104130358-b7f69be5
Many organizations are shifting to containers and Kubernetes, and that move means learning new ways to secure their environments. Kubernetes clusters have to be hardened at different levels. We have to consider the nodes where the Kubernetes control plane is running. We also need to secure the Kubernetes workloads and check the code that creates them. And we need to inspect the containers we are using for vulnerabilities and watch for unusual behavior. Gene will show you some open-source tools that can find issues and vulnerabilities at each layer. You will see how they can be used to build your Kubernetes cluster safely and keep it secure.]]>
Many organizations are shifting to containers and Kubernetes, and that move means learning new ways to secure their environments. Kubernetes clusters have to be hardened at different levels. We have to consider the nodes where the Kubernetes control plane is running. We also need to secure the Kubernetes workloads and check the code that creates them. And we need to inspect the containers we are using for vulnerabilities and watch for unusual behavior. Gene will show you some open-source tools that can find issues and vulnerabilities at each layer. You will see how they can be used to build your Kubernetes cluster safely and keep it secure.]]> Fri, 04 Nov 2022 13:03:58 GMT /slideshow/keeping-your-kubernetes-cluster-secure-254002353/254002353 ggotimer@slideshare.net(ggotimer) Keeping Your Kubernetes Cluster Secure ggotimer Many organizations are shifting to containers and Kubernetes, and that move means learning new ways to secure their environments. Kubernetes clusters have to be hardened at different levels. We have to consider the nodes where the Kubernetes control plane is running. We also need to secure the Kubernetes workloads and check the code that creates them. And we need to inspect the containers we are using for vulnerabilities and watch for unusual behavior. Gene will show you some open-source tools that can find issues and vulnerabilities at each layer. You will see how they can be used to build your Kubernetes cluster safely and keep it secure. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/keepingyourkubernetesclustersecure-221104130358-b7f69be5-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Many organizations are shifting to containers and Kubernetes, and that move means learning new ways to secure their environments. Kubernetes clusters have to be hardened at different levels. We have to consider the nodes where the Kubernetes control plane is running. We also need to secure the Kubernetes workloads and check the code that creates them. And we need to inspect the containers we are using for vulnerabilities and watch for unusual behavior. Gene will show you some open-source tools that can find issues and vulnerabilities at each layer. You will see how they can be used to build your Kubernetes cluster safely and keep it secure.
Keeping Your Kubernetes Cluster Secure from Gene Gotimer
]]> 136 0 https://cdn.slidesharecdn.com/ss_thumbnails/keepingyourkubernetesclustersecure-221104130358-b7f69be5-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Keeping your Kubernetes Cluster Secure /slideshow/keeping-your-kubernetes-cluster-secure-250991842/250991842 keepingyourkubernetesclustersecure-220113215310
Many organizations are shifting to containers and Kubernetes, and that move means learning new ways to secure their environments. Kubernetes clusters have to be hardened at different levels. We have to consider the nodes where the Kubernetes control plane is running. We also need to secure the Kubernetes workloads and check the files that create them. And we need to inspect the containers we are using for vulnerabilities and unusual behavior. Gene will show you some open-source tools that can find issues and vulnerabilities at each layer. You will see how they can be used in a pipeline to build your Kubernetes cluster safely and keep it secure. ]]>
Many organizations are shifting to containers and Kubernetes, and that move means learning new ways to secure their environments. Kubernetes clusters have to be hardened at different levels. We have to consider the nodes where the Kubernetes control plane is running. We also need to secure the Kubernetes workloads and check the files that create them. And we need to inspect the containers we are using for vulnerabilities and unusual behavior. Gene will show you some open-source tools that can find issues and vulnerabilities at each layer. You will see how they can be used in a pipeline to build your Kubernetes cluster safely and keep it secure. ]]> Thu, 13 Jan 2022 21:53:09 GMT /slideshow/keeping-your-kubernetes-cluster-secure-250991842/250991842 ggotimer@slideshare.net(ggotimer) Keeping your Kubernetes Cluster Secure ggotimer Many organizations are shifting to containers and Kubernetes, and that move means learning new ways to secure their environments. Kubernetes clusters have to be hardened at different levels. We have to consider the nodes where the Kubernetes control plane is running. We also need to secure the Kubernetes workloads and check the files that create them. And we need to inspect the containers we are using for vulnerabilities and unusual behavior. Gene will show you some open-source tools that can find issues and vulnerabilities at each layer. You will see how they can be used in a pipeline to build your Kubernetes cluster safely and keep it secure. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/keepingyourkubernetesclustersecure-220113215310-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Many organizations are shifting to containers and Kubernetes, and that move means learning new ways to secure their environments. Kubernetes clusters have to be hardened at different levels. We have to consider the nodes where the Kubernetes control plane is running. We also need to secure the Kubernetes workloads and check the files that create them. And we need to inspect the containers we are using for vulnerabilities and unusual behavior. Gene will show you some open-source tools that can find issues and vulnerabilities at each layer. You will see how they can be used in a pipeline to build your Kubernetes cluster safely and keep it secure.
Keeping your Kubernetes Cluster Secure from Gene Gotimer
]]> 163 0 https://cdn.slidesharecdn.com/ss_thumbnails/keepingyourkubernetesclustersecure-220113215310-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Explain DevOps To Me Like Im Five: DevOps for Managers /slideshow/explain-devops-to-me-like-im-five-devops-for-managers/250991840 explaindevopstomelikeimfive-220113215247
Organizations and leaders are often supportive of DevOps, but they dont always understand what DevOps is and what it will change. It isnt a one-size-fits-all issue; different environments need different benefits from a DevOps transformation. Join Gene Gotimer as he explains the most important parts of understanding DevOps. We'll discuss how to determine what parts of DevOps your organization needs to concentrate on first and how you should measure improvement. This session boils DevOps down to its most basic parts and makes sure you have a foundation for understanding how to make it work for your situation and organization. ]]>
Organizations and leaders are often supportive of DevOps, but they dont always understand what DevOps is and what it will change. It isnt a one-size-fits-all issue; different environments need different benefits from a DevOps transformation. Join Gene Gotimer as he explains the most important parts of understanding DevOps. We'll discuss how to determine what parts of DevOps your organization needs to concentrate on first and how you should measure improvement. This session boils DevOps down to its most basic parts and makes sure you have a foundation for understanding how to make it work for your situation and organization. ]]> Thu, 13 Jan 2022 21:52:46 GMT /slideshow/explain-devops-to-me-like-im-five-devops-for-managers/250991840 ggotimer@slideshare.net(ggotimer) Explain DevOps To Me Like Im Five: DevOps for Managers ggotimer Organizations and leaders are often supportive of DevOps, but they dont always understand what DevOps is and what it will change. It isnt a one-size-fits-all issue; different environments need different benefits from a DevOps transformation. Join Gene Gotimer as he explains the most important parts of understanding DevOps. We'll discuss how to determine what parts of DevOps your organization needs to concentrate on first and how you should measure improvement. This session boils DevOps down to its most basic parts and makes sure you have a foundation for understanding how to make it work for your situation and organization. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/explaindevopstomelikeimfive-220113215247-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Organizations and leaders are often supportive of DevOps, but they dont always understand what DevOps is and what it will change. It isnt a one-size-fits-all issue; different environments need different benefits from a DevOps transformation. Join Gene Gotimer as he explains the most important parts of understanding DevOps. We&#39;ll discuss how to determine what parts of DevOps your organization needs to concentrate on first and how you should measure improvement. This session boils DevOps down to its most basic parts and makes sure you have a foundation for understanding how to make it work for your situation and organization.
Explain DevOps To Me Like Im Five: DevOps for Managers from Gene Gotimer
]]> 127 0 https://cdn.slidesharecdn.com/ss_thumbnails/explaindevopstomelikeimfive-220113215247-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Keeping your Kubernetes Cluster Secure /slideshow/keeping-your-kubernetes-cluster-secure/243059346 kubernetes-security-tools-210219164939
From NOVA Cloud and Software Engineering Group meetup, Feb. 17, 2021 https://youtu.be/a5uPm1mPLKQ. Hardening a Kubernetes cluster happens at different levels. We have to examine the nodes where Kubernetes is running. We want to secure the Kubernetes objects and workloads and review the files we used to create them. And we need to look for vulnerabilities in the containers we are using. Gene will show you some open-source tools that can find issues and vulnerabilities at each layer. All of them can be used in a pipeline to build your Kubernetes cluster safely and keep it secure. Gene Gotimer is the meetup organizer and a DevSecOps Senior Engineer at Steampunk, focusing on agile processes, secure development practices, and automation. Gene feels strongly that repeatability, quality, and security are all strongly intertwined; each depends on the other two, making agile and DevSecOps that much more crucial to software development.]]>
From NOVA Cloud and Software Engineering Group meetup, Feb. 17, 2021 https://youtu.be/a5uPm1mPLKQ. Hardening a Kubernetes cluster happens at different levels. We have to examine the nodes where Kubernetes is running. We want to secure the Kubernetes objects and workloads and review the files we used to create them. And we need to look for vulnerabilities in the containers we are using. Gene will show you some open-source tools that can find issues and vulnerabilities at each layer. All of them can be used in a pipeline to build your Kubernetes cluster safely and keep it secure. Gene Gotimer is the meetup organizer and a DevSecOps Senior Engineer at Steampunk, focusing on agile processes, secure development practices, and automation. Gene feels strongly that repeatability, quality, and security are all strongly intertwined; each depends on the other two, making agile and DevSecOps that much more crucial to software development.]]> Fri, 19 Feb 2021 16:49:39 GMT /slideshow/keeping-your-kubernetes-cluster-secure/243059346 ggotimer@slideshare.net(ggotimer) Keeping your Kubernetes Cluster Secure ggotimer From NOVA Cloud and Software Engineering Group meetup, Feb. 17, 2021 https://youtu.be/a5uPm1mPLKQ. Hardening a Kubernetes cluster happens at different levels. We have to examine the nodes where Kubernetes is running. We want to secure the Kubernetes objects and workloads and review the files we used to create them. And we need to look for vulnerabilities in the containers we are using. Gene will show you some open-source tools that can find issues and vulnerabilities at each layer. All of them can be used in a pipeline to build your Kubernetes cluster safely and keep it secure. Gene Gotimer is the meetup organizer and a DevSecOps Senior Engineer at Steampunk, focusing on agile processes, secure development practices, and automation. Gene feels strongly that repeatability, quality, and security are all strongly intertwined; each depends on the other two, making agile and DevSecOps that much more crucial to software development. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/kubernetes-security-tools-210219164939-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> From NOVA Cloud and Software Engineering Group meetup, Feb. 17, 2021 https://youtu.be/a5uPm1mPLKQ. Hardening a Kubernetes cluster happens at different levels. We have to examine the nodes where Kubernetes is running. We want to secure the Kubernetes objects and workloads and review the files we used to create them. And we need to look for vulnerabilities in the containers we are using. Gene will show you some open-source tools that can find issues and vulnerabilities at each layer. All of them can be used in a pipeline to build your Kubernetes cluster safely and keep it secure. Gene Gotimer is the meetup organizer and a DevSecOps Senior Engineer at Steampunk, focusing on agile processes, secure development practices, and automation. Gene feels strongly that repeatability, quality, and security are all strongly intertwined; each depends on the other two, making agile and DevSecOps that much more crucial to software development.
Keeping your Kubernetes Cluster Secure from Gene Gotimer
]]> 93 0 https://cdn.slidesharecdn.com/ss_thumbnails/kubernetes-security-tools-210219164939-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Creative Solutions to Already Solved Problems II /slideshow/creative-solutions-to-already-solved-problems-ii/173384867 gotimer-190918133527
This code is bad and the authors should feel bad. Creative solutions to already solved problems is the term one of our teams came up with for bad code. ]]>
This code is bad and the authors should feel bad. Creative solutions to already solved problems is the term one of our teams came up with for bad code. ]]> Wed, 18 Sep 2019 13:35:27 GMT /slideshow/creative-solutions-to-already-solved-problems-ii/173384867 ggotimer@slideshare.net(ggotimer) Creative Solutions to Already Solved Problems II ggotimer This code is bad and the authors should feel bad. Creative solutions to already solved problems is the term one of our teams came up with for bad code. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/gotimer-190918133527-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> This code is bad and the authors should feel bad. Creative solutions to already solved problems is the term one of our teams came up with for bad code.
Creative Solutions to Already Solved Problems II from Gene Gotimer
]]> 93 0 https://cdn.slidesharecdn.com/ss_thumbnails/gotimer-190918133527-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Creative Solutions to Already Solved Problems /slideshow/creative-solutions-to-already-solved-problems/173384594 creativesolutionstoalreadysolvedproblems-190918133427
Creative Solutions to Already Solved Problems is our name for the ridiculous code that our team has found in our project. These show a massive lack of understanding of common Java constructs and tools. Unfortunately, these examples are real and we had plenty to choose from. ]]>
Creative Solutions to Already Solved Problems is our name for the ridiculous code that our team has found in our project. These show a massive lack of understanding of common Java constructs and tools. Unfortunately, these examples are real and we had plenty to choose from. ]]> Wed, 18 Sep 2019 13:34:27 GMT /slideshow/creative-solutions-to-already-solved-problems/173384594 ggotimer@slideshare.net(ggotimer) Creative Solutions to Already Solved Problems ggotimer Creative Solutions to Already Solved Problems is our name for the ridiculous code that our team has found in our project. These show a massive lack of understanding of common Java constructs and tools. Unfortunately, these examples are real and we had plenty to choose from. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/creativesolutionstoalreadysolvedproblems-190918133427-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Creative Solutions to Already Solved Problems is our name for the ridiculous code that our team has found in our project. These show a massive lack of understanding of common Java constructs and tools. Unfortunately, these examples are real and we had plenty to choose from.
Creative Solutions to Already Solved Problems from Gene Gotimer
]]> 118 0 https://cdn.slidesharecdn.com/ss_thumbnails/creativesolutionstoalreadysolvedproblems-190918133427-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Get to Green: How to Safely Refactor Legacy Code /slideshow/get-to-green-how-to-safely-refactor-legacy-code/164143044 gotimer-gettogreen-190816002635
For many of us, legacy code is a fact of life. Code without tests -- no safe way to make changes, no safety net, no hope of untangling the web of accumulated ugliness, an incomplete understanding (or less) of how it really behaves. And your next set of changes is just going to add to the garbage pile and make it worse. You need tests so you can safely make changes, but you can't add tests without changing the code. It is a chicken-and-egg problem. So how do you turn legacy code into code you can change confidently? Slowly, one step at a time. Join Gene as he shares his experiences working with a monolithic codebase that was so bad it made national news. He'll go over the steps he and his team used to refactor the code safely by using mocking frameworks, mutation testing, and patience to build an understanding of how the code worked so that they could change it confidently. This talk is for anyone that has inherited legacy code that they aren't confident in and wants to make it something they can work on and improve. You'll leave with some tools and techniques that will help you change your legacy code into something maintainable. ]]>
For many of us, legacy code is a fact of life. Code without tests -- no safe way to make changes, no safety net, no hope of untangling the web of accumulated ugliness, an incomplete understanding (or less) of how it really behaves. And your next set of changes is just going to add to the garbage pile and make it worse. You need tests so you can safely make changes, but you can't add tests without changing the code. It is a chicken-and-egg problem. So how do you turn legacy code into code you can change confidently? Slowly, one step at a time. Join Gene as he shares his experiences working with a monolithic codebase that was so bad it made national news. He'll go over the steps he and his team used to refactor the code safely by using mocking frameworks, mutation testing, and patience to build an understanding of how the code worked so that they could change it confidently. This talk is for anyone that has inherited legacy code that they aren't confident in and wants to make it something they can work on and improve. You'll leave with some tools and techniques that will help you change your legacy code into something maintainable. ]]> Fri, 16 Aug 2019 00:26:35 GMT /slideshow/get-to-green-how-to-safely-refactor-legacy-code/164143044 ggotimer@slideshare.net(ggotimer) Get to Green: How to Safely Refactor Legacy Code ggotimer For many of us, legacy code is a fact of life. Code without tests -- no safe way to make changes, no safety net, no hope of untangling the web of accumulated ugliness, an incomplete understanding (or less) of how it really behaves. And your next set of changes is just going to add to the garbage pile and make it worse. You need tests so you can safely make changes, but you can't add tests without changing the code. It is a chicken-and-egg problem. So how do you turn legacy code into code you can change confidently? Slowly, one step at a time. Join Gene as he shares his experiences working with a monolithic codebase that was so bad it made national news. He'll go over the steps he and his team used to refactor the code safely by using mocking frameworks, mutation testing, and patience to build an understanding of how the code worked so that they could change it confidently. This talk is for anyone that has inherited legacy code that they aren't confident in and wants to make it something they can work on and improve. You'll leave with some tools and techniques that will help you change your legacy code into something maintainable. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/gotimer-gettogreen-190816002635-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> For many of us, legacy code is a fact of life. Code without tests -- no safe way to make changes, no safety net, no hope of untangling the web of accumulated ugliness, an incomplete understanding (or less) of how it really behaves. And your next set of changes is just going to add to the garbage pile and make it worse. You need tests so you can safely make changes, but you can&#39;t add tests without changing the code. It is a chicken-and-egg problem. So how do you turn legacy code into code you can change confidently? Slowly, one step at a time. Join Gene as he shares his experiences working with a monolithic codebase that was so bad it made national news. He&#39;ll go over the steps he and his team used to refactor the code safely by using mocking frameworks, mutation testing, and patience to build an understanding of how the code worked so that they could change it confidently. This talk is for anyone that has inherited legacy code that they aren&#39;t confident in and wants to make it something they can work on and improve. You&#39;ll leave with some tools and techniques that will help you change your legacy code into something maintainable.
Get to Green: How to Safely Refactor Legacy Code from Gene Gotimer
]]> 363 4 https://cdn.slidesharecdn.com/ss_thumbnails/gotimer-gettogreen-190816002635-thumbnail.jpg?width=120&height=120&fit=bounds document Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 DevOps for Leadership /slideshow/devops-for-leadership/149013681 devopsforleadership-45-190606233331
To survive in todays market, organizations need to deliver higher quality, more secure software than ever before, and they need to do it faster. Todays leaders need to understand what DevOps is all about and how to implement it across the enterprise to remain competitive, react to changing conditions, and facilitate growth. This interactive workshop will explain what DevOps is and isnt, what benefits we should expect adopting it, and what we need to do to adjust to a DevOps mindset. Well look at our current delivery processes and discuss how we can deliver higher quality, more secure software, and how we can do it faster, more reliably, and have more confidence in the result. We will focus on the culture and process, only touching on the tools that enable us to work better. It is not a technical deep dive. This workshop is designed for executives and leaders, managers, project managers, and team leads to help them prepare for successful DevOps transformation and leadership.]]>
To survive in todays market, organizations need to deliver higher quality, more secure software than ever before, and they need to do it faster. Todays leaders need to understand what DevOps is all about and how to implement it across the enterprise to remain competitive, react to changing conditions, and facilitate growth. This interactive workshop will explain what DevOps is and isnt, what benefits we should expect adopting it, and what we need to do to adjust to a DevOps mindset. Well look at our current delivery processes and discuss how we can deliver higher quality, more secure software, and how we can do it faster, more reliably, and have more confidence in the result. We will focus on the culture and process, only touching on the tools that enable us to work better. It is not a technical deep dive. This workshop is designed for executives and leaders, managers, project managers, and team leads to help them prepare for successful DevOps transformation and leadership.]]> Thu, 06 Jun 2019 23:33:31 GMT /slideshow/devops-for-leadership/149013681 ggotimer@slideshare.net(ggotimer) DevOps for Leadership ggotimer To survive in todays market, organizations need to deliver higher quality, more secure software than ever before, and they need to do it faster. Todays leaders need to understand what DevOps is all about and how to implement it across the enterprise to remain competitive, react to changing conditions, and facilitate growth. This interactive workshop will explain what DevOps is and isnt, what benefits we should expect adopting it, and what we need to do to adjust to a DevOps mindset. Well look at our current delivery processes and discuss how we can deliver higher quality, more secure software, and how we can do it faster, more reliably, and have more confidence in the result. We will focus on the culture and process, only touching on the tools that enable us to work better. It is not a technical deep dive. This workshop is designed for executives and leaders, managers, project managers, and team leads to help them prepare for successful DevOps transformation and leadership. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/devopsforleadership-45-190606233331-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> To survive in todays market, organizations need to deliver higher quality, more secure software than ever before, and they need to do it faster. Todays leaders need to understand what DevOps is all about and how to implement it across the enterprise to remain competitive, react to changing conditions, and facilitate growth. This interactive workshop will explain what DevOps is and isnt, what benefits we should expect adopting it, and what we need to do to adjust to a DevOps mindset. Well look at our current delivery processes and discuss how we can deliver higher quality, more secure software, and how we can do it faster, more reliably, and have more confidence in the result. We will focus on the culture and process, only touching on the tools that enable us to work better. It is not a technical deep dive. This workshop is designed for executives and leaders, managers, project managers, and team leads to help them prepare for successful DevOps transformation and leadership.
DevOps for Leadership from Gene Gotimer
]]> 215 2 https://cdn.slidesharecdn.com/ss_thumbnails/devopsforleadership-45-190606233331-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Pyramid Discussion: DevOps Adoption in Large, Slow Organizations /slideshow/pyramid-discussion-devops-adoption-in-large-slow-organizations/149013643 adoptingdevopsdiscussion-190606233243
Notes from Pyramid Discussion: DevOps Adoption in Large, Slow Organizations at Agile + DevOps West 2019. Are you in a large, plodding enterprise that's beginning, in the midst of, or considering a move toward DevOps? Unsure how or even if it will work, but know you have to make a move anyway? Do you want to hear from your peers about how they've managed so far? A pyramid discussion starts as a series of one-on-one conversations between the participants. After each pair hashes out their thoughts with each other, they join another couple to refine their points and hear pros and cons. After a while, those four join with four more, and so on until there is only one discussion, with everyone sharing and discussing. All attendees will get a chance to have their ideas and experiences heard while building on the thoughts and experiences of others. Even if you aren't ready to take over the discussion in a room of peers, you can proceed through the pyramid of smaller debates to get answers to your questions and hear how others are bringing DevOps to a large, slow organization.]]>
Notes from Pyramid Discussion: DevOps Adoption in Large, Slow Organizations at Agile + DevOps West 2019. Are you in a large, plodding enterprise that's beginning, in the midst of, or considering a move toward DevOps? Unsure how or even if it will work, but know you have to make a move anyway? Do you want to hear from your peers about how they've managed so far? A pyramid discussion starts as a series of one-on-one conversations between the participants. After each pair hashes out their thoughts with each other, they join another couple to refine their points and hear pros and cons. After a while, those four join with four more, and so on until there is only one discussion, with everyone sharing and discussing. All attendees will get a chance to have their ideas and experiences heard while building on the thoughts and experiences of others. Even if you aren't ready to take over the discussion in a room of peers, you can proceed through the pyramid of smaller debates to get answers to your questions and hear how others are bringing DevOps to a large, slow organization.]]> Thu, 06 Jun 2019 23:32:43 GMT /slideshow/pyramid-discussion-devops-adoption-in-large-slow-organizations/149013643 ggotimer@slideshare.net(ggotimer) Pyramid Discussion: DevOps Adoption in Large, Slow Organizations ggotimer Notes from Pyramid Discussion: DevOps Adoption in Large, Slow Organizations at Agile + DevOps West 2019. Are you in a large, plodding enterprise that's beginning, in the midst of, or considering a move toward DevOps? Unsure how or even if it will work, but know you have to make a move anyway? Do you want to hear from your peers about how they've managed so far? A pyramid discussion starts as a series of one-on-one conversations between the participants. After each pair hashes out their thoughts with each other, they join another couple to refine their points and hear pros and cons. After a while, those four join with four more, and so on until there is only one discussion, with everyone sharing and discussing. All attendees will get a chance to have their ideas and experiences heard while building on the thoughts and experiences of others. Even if you aren't ready to take over the discussion in a room of peers, you can proceed through the pyramid of smaller debates to get answers to your questions and hear how others are bringing DevOps to a large, slow organization. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/adoptingdevopsdiscussion-190606233243-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Notes from Pyramid Discussion: DevOps Adoption in Large, Slow Organizations at Agile + DevOps West 2019. Are you in a large, plodding enterprise that&#39;s beginning, in the midst of, or considering a move toward DevOps? Unsure how or even if it will work, but know you have to make a move anyway? Do you want to hear from your peers about how they&#39;ve managed so far? A pyramid discussion starts as a series of one-on-one conversations between the participants. After each pair hashes out their thoughts with each other, they join another couple to refine their points and hear pros and cons. After a while, those four join with four more, and so on until there is only one discussion, with everyone sharing and discussing. All attendees will get a chance to have their ideas and experiences heard while building on the thoughts and experiences of others. Even if you aren&#39;t ready to take over the discussion in a room of peers, you can proceed through the pyramid of smaller debates to get answers to your questions and hear how others are bringing DevOps to a large, slow organization.
Pyramid Discussion: DevOps Adoption in Large, Slow Organizations from Gene Gotimer
]]> 116 4 https://cdn.slidesharecdn.com/ss_thumbnails/adoptingdevopsdiscussion-190606233243-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 A better faster pipeline for software delivery, even in the government /slideshow/a-better-faster-pipeline-for-software-delivery-even-in-the-government/123351861 abetterfasterpipelineforsoftwaredelivery-181118181301
The software delivery pipeline is the process of taking features from developers and getting them delivered to customers. The earliest tests should be the quickest and easiest to run, giving developers the fastest feedback. Successive rounds of testing should increase confidence that the code is a viable candidate for production and that more expensive testsbe it time, effort, costare justified. Manual testing should be performed toward the end of the pipeline, leaving computers to do as much work as possible before people get involved. Although it is tempting to arrange the delivery pipeline in phases (e.g., functional tests, then acceptance tests, then load and performance tests, then security tests), this can lead to problems progressing down the pipeline. In this interactive workshop, Gene Gotimer and Ryan Kenney will discuss how to arrange your pipeline, automated or not, and so each round of tests provides just enough testing to give you confidence that the next set of tests is worth the investment. We'll explore how to get the right types of testing into your pipeline at the right points so that you can determine which builds are viable candidates for production. And well explain some of the experiences weve had with clients, especially in the federal government, trying to build out delivery pipelines. Attendees should be at least roughly familiar with their current delivery process, automated or not, or they should at least have a process in mind. No prior knowledge of DevOps, continuous delivery, or automation is assumed.]]>
The software delivery pipeline is the process of taking features from developers and getting them delivered to customers. The earliest tests should be the quickest and easiest to run, giving developers the fastest feedback. Successive rounds of testing should increase confidence that the code is a viable candidate for production and that more expensive testsbe it time, effort, costare justified. Manual testing should be performed toward the end of the pipeline, leaving computers to do as much work as possible before people get involved. Although it is tempting to arrange the delivery pipeline in phases (e.g., functional tests, then acceptance tests, then load and performance tests, then security tests), this can lead to problems progressing down the pipeline. In this interactive workshop, Gene Gotimer and Ryan Kenney will discuss how to arrange your pipeline, automated or not, and so each round of tests provides just enough testing to give you confidence that the next set of tests is worth the investment. We'll explore how to get the right types of testing into your pipeline at the right points so that you can determine which builds are viable candidates for production. And well explain some of the experiences weve had with clients, especially in the federal government, trying to build out delivery pipelines. Attendees should be at least roughly familiar with their current delivery process, automated or not, or they should at least have a process in mind. No prior knowledge of DevOps, continuous delivery, or automation is assumed.]]> Sun, 18 Nov 2018 18:13:01 GMT /slideshow/a-better-faster-pipeline-for-software-delivery-even-in-the-government/123351861 ggotimer@slideshare.net(ggotimer) A better faster pipeline for software delivery, even in the government ggotimer The software delivery pipeline is the process of taking features from developers and getting them delivered to customers. The earliest tests should be the quickest and easiest to run, giving developers the fastest feedback. Successive rounds of testing should increase confidence that the code is a viable candidate for production and that more expensive testsbe it time, effort, costare justified. Manual testing should be performed toward the end of the pipeline, leaving computers to do as much work as possible before people get involved. Although it is tempting to arrange the delivery pipeline in phases (e.g., functional tests, then acceptance tests, then load and performance tests, then security tests), this can lead to problems progressing down the pipeline. In this interactive workshop, Gene Gotimer and Ryan Kenney will discuss how to arrange your pipeline, automated or not, and so each round of tests provides just enough testing to give you confidence that the next set of tests is worth the investment. We'll explore how to get the right types of testing into your pipeline at the right points so that you can determine which builds are viable candidates for production. And well explain some of the experiences weve had with clients, especially in the federal government, trying to build out delivery pipelines. Attendees should be at least roughly familiar with their current delivery process, automated or not, or they should at least have a process in mind. No prior knowledge of DevOps, continuous delivery, or automation is assumed. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/abetterfasterpipelineforsoftwaredelivery-181118181301-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> The software delivery pipeline is the process of taking features from developers and getting them delivered to customers. The earliest tests should be the quickest and easiest to run, giving developers the fastest feedback. Successive rounds of testing should increase confidence that the code is a viable candidate for production and that more expensive testsbe it time, effort, costare justified. Manual testing should be performed toward the end of the pipeline, leaving computers to do as much work as possible before people get involved. Although it is tempting to arrange the delivery pipeline in phases (e.g., functional tests, then acceptance tests, then load and performance tests, then security tests), this can lead to problems progressing down the pipeline. In this interactive workshop, Gene Gotimer and Ryan Kenney will discuss how to arrange your pipeline, automated or not, and so each round of tests provides just enough testing to give you confidence that the next set of tests is worth the investment. We&#39;ll explore how to get the right types of testing into your pipeline at the right points so that you can determine which builds are viable candidates for production. And well explain some of the experiences weve had with clients, especially in the federal government, trying to build out delivery pipelines. Attendees should be at least roughly familiar with their current delivery process, automated or not, or they should at least have a process in mind. No prior knowledge of DevOps, continuous delivery, or automation is assumed.
A better faster pipeline for software delivery, even in the government from Gene Gotimer
]]> 176 2 https://cdn.slidesharecdn.com/ss_thumbnails/abetterfasterpipelineforsoftwaredelivery-181118181301-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Building the Pipeline of My Dreams /slideshow/building-the-pipeline-of-my-dreams/120066630 gotimer-pipelineofmydreams-181020010930
I often suggest to teams that they should be using all sorts of tools in their pipelines- from simple static analysis checks and automated builds to security scans and performance testing. I've done presentations and talks at conferences. I've lobbied to clients. I've commiserated with my colleagues. But I've never put together my dream pipeline in one of my own projects. There are always reasons that some tests and tools get left out- our policies won't allow them, they will take too long to get approved, we don't have time, we have bigger problems to deal with, it just isn't what the client is looking for right now. And I usually think, if only I were in charge, I'd make sure we were using those... In late 2017 I took over maintenance on an open-source project. Now I have no restrictions. The sky's the limit. No one is around to tell me what I can't do. So why don't I have my dream pipeline in place yet? I'll talk about the trade-offs and compromises I made when building out the pipeline. Why I decided to focus on some tools and tests but skipped others, and what I need to do or change to make this delivery process the pipeline I've always dreamed about, now that I have no one else to blame.]]>
I often suggest to teams that they should be using all sorts of tools in their pipelines- from simple static analysis checks and automated builds to security scans and performance testing. I've done presentations and talks at conferences. I've lobbied to clients. I've commiserated with my colleagues. But I've never put together my dream pipeline in one of my own projects. There are always reasons that some tests and tools get left out- our policies won't allow them, they will take too long to get approved, we don't have time, we have bigger problems to deal with, it just isn't what the client is looking for right now. And I usually think, if only I were in charge, I'd make sure we were using those... In late 2017 I took over maintenance on an open-source project. Now I have no restrictions. The sky's the limit. No one is around to tell me what I can't do. So why don't I have my dream pipeline in place yet? I'll talk about the trade-offs and compromises I made when building out the pipeline. Why I decided to focus on some tools and tests but skipped others, and what I need to do or change to make this delivery process the pipeline I've always dreamed about, now that I have no one else to blame.]]> Sat, 20 Oct 2018 01:09:29 GMT /slideshow/building-the-pipeline-of-my-dreams/120066630 ggotimer@slideshare.net(ggotimer) Building the Pipeline of My Dreams ggotimer I often suggest to teams that they should be using all sorts of tools in their pipelines- from simple static analysis checks and automated builds to security scans and performance testing. I've done presentations and talks at conferences. I've lobbied to clients. I've commiserated with my colleagues. But I've never put together my dream pipeline in one of my own projects. There are always reasons that some tests and tools get left out- our policies won't allow them, they will take too long to get approved, we don't have time, we have bigger problems to deal with, it just isn't what the client is looking for right now. And I usually think, if only I were in charge, I'd make sure we were using those... In late 2017 I took over maintenance on an open-source project. Now I have no restrictions. The sky's the limit. No one is around to tell me what I can't do. So why don't I have my dream pipeline in place yet? I'll talk about the trade-offs and compromises I made when building out the pipeline. Why I decided to focus on some tools and tests but skipped others, and what I need to do or change to make this delivery process the pipeline I've always dreamed about, now that I have no one else to blame. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/gotimer-pipelineofmydreams-181020010930-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> I often suggest to teams that they should be using all sorts of tools in their pipelines- from simple static analysis checks and automated builds to security scans and performance testing. I&#39;ve done presentations and talks at conferences. I&#39;ve lobbied to clients. I&#39;ve commiserated with my colleagues. But I&#39;ve never put together my dream pipeline in one of my own projects. There are always reasons that some tests and tools get left out- our policies won&#39;t allow them, they will take too long to get approved, we don&#39;t have time, we have bigger problems to deal with, it just isn&#39;t what the client is looking for right now. And I usually think, if only I were in charge, I&#39;d make sure we were using those... In late 2017 I took over maintenance on an open-source project. Now I have no restrictions. The sky&#39;s the limit. No one is around to tell me what I can&#39;t do. So why don&#39;t I have my dream pipeline in place yet? I&#39;ll talk about the trade-offs and compromises I made when building out the pipeline. Why I decided to focus on some tools and tests but skipped others, and what I need to do or change to make this delivery process the pipeline I&#39;ve always dreamed about, now that I have no one else to blame.
Building the Pipeline of My Dreams from Gene Gotimer
]]> 182 2 https://cdn.slidesharecdn.com/ss_thumbnails/gotimer-pipelineofmydreams-181020010930-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 https://cdn.slidesharecdn.com/profile-photo-ggotimer-48x48.jpg?cb=1729093769 Gene Gotimer is a DevSecOps Engineer who loves playing with new tools, focusing on agile processes, securing development practices, and automating everything. Gene feels strongly that repeatability, quality, and security are all strongly intertwined; each depends on the other two, making agile and DevSecOps crucial to software development. https://cdn.slidesharecdn.com/ss_thumbnails/cloudcustodian-241016154955-88820951-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/clean-your-cloud-with-cloud-custodian-slides/272470133 Clean Your Cloud with ... https://cdn.slidesharecdn.com/ss_thumbnails/handsoncontainers-240718223142-d63b24a5-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/a-hands-on-intro-to-containers-nebraska/270324571 A Hands-on Intro to Co... https://cdn.slidesharecdn.com/ss_thumbnails/adevsguidetokubernetessecurity-240718223142-51a82f5d-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/a-developer-s-guide-to-kubernetes-security/270324569 A Developer&#39;s Guide to...