<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gene Gotimer</title>
    <description>Repeatability, quality, security: each of them is dependent on the other two, which just makes agile and DevSecOps that much more important to software development.</description>
    <link>https://speakerdeck.com/otherdevopsgene</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/otherdevopsgene.rss"/>
    <lastBuildDate>2019-10-02 19:26:17 -0400</lastBuildDate>
    <item>
      <title>How Fast Is My App? Performance Testing 101</title>
      <description>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.</description>
      <media:content url="https://files.speakerdeck.com/presentations/42d2f1caabb9473e8386090d523aaafc/preview_slide_0.jpg?15562971" type="image/jpeg" medium="image"/>
      <content:encoded>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.</content:encoded>
      <pubDate>Thu, 28 May 2020 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/otherdevopsgene/how-fast-is-my-app-performance-testing-101</link>
      <guid>https://speakerdeck.com/otherdevopsgene/how-fast-is-my-app-performance-testing-101</guid>
    </item>
    <item>
      <title>Get to Green: How to safely refactor legacy code</title>
      <description>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.</description>
      <media:content url="https://files.speakerdeck.com/presentations/2a28d9b74c7e4b62a9dfbe6747bb6ff4/preview_slide_0.jpg?14168839" type="image/jpeg" medium="image"/>
      <content:encoded>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.</content:encoded>
      <pubDate>Thu, 14 Nov 2019 00:00:00 -0500</pubDate>
      <link>https://speakerdeck.com/otherdevopsgene/get-to-green-how-to-safely-refactor-legacy-code</link>
      <guid>https://speakerdeck.com/otherdevopsgene/get-to-green-how-to-safely-refactor-legacy-code</guid>
    </item>
    <item>
      <title>A Hands on Intro to Docker for Testers</title>
      <description>Docker is one of the hottest technologies in our industry today. It lets you create and manage containers—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 systems. 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.

NOTE: This workshop is a hands-on introduction for anyone interested in learning Docker--you will need your laptop. We will walk through building docker containers, starting out simple but moving to more pragmatic setups. As we iterate, we will discuss how you can use and reuse Docker containers for a variety of uses. And then I’ll show how all of this evolves to a fully-functional web application and test environment.</description>
      <media:content url="https://files.speakerdeck.com/presentations/b140864c577941d3bb53bd0047f215e4/preview_slide_0.jpg?13768830" type="image/jpeg" medium="image"/>
      <content:encoded>Docker is one of the hottest technologies in our industry today. It lets you create and manage containers—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 systems. 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.

NOTE: This workshop is a hands-on introduction for anyone interested in learning Docker--you will need your laptop. We will walk through building docker containers, starting out simple but moving to more pragmatic setups. As we iterate, we will discuss how you can use and reuse Docker containers for a variety of uses. And then I’ll show how all of this evolves to a fully-functional web application and test environment.</content:encoded>
      <pubDate>Tue, 01 Oct 2019 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/otherdevopsgene/a-hands-on-intro-to-docker-for-testers</link>
      <guid>https://speakerdeck.com/otherdevopsgene/a-hands-on-intro-to-docker-for-testers</guid>
    </item>
  </channel>
</rss>
