<?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>Michał Kowalczyk</title>
    <description/>
    <link>https://speakerdeck.com/mkk</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/mkk.rss"/>
    <lastBuildDate>2017-11-16 17:27:35 -0500</lastBuildDate>
    <item>
      <title>Test maintainability</title>
      <description>Automatic tests are still considered as a necessary evil. Some developers still claim that clients don't pay for tests so we shouldn't write them. Others say that we shouldn't put much effort into tests, implementation is more important, right? Those developers tend to forget the overall cost of maintenance of their codebase. How many bugs you can find on an early stage of implementation just thanks to automatic tests? What's the cost of maintenance of tests written in a not clean way?

During this talk, I will go through some properties of well maintainable tests, present examples of tests hard to maintain and suggest a few ways to improve them. Presented properties and techniques might be valuable for engineers writing and refactoring tests. Finally, I will dive into the term testable design and discuss how to achieve it.</description>
      <media:content url="https://files.speakerdeck.com/presentations/bdce4ab4569b4fd69e9902c79c5abb61/preview_slide_0.jpg?11042053" type="image/jpeg" medium="image"/>
      <content:encoded>Automatic tests are still considered as a necessary evil. Some developers still claim that clients don't pay for tests so we shouldn't write them. Others say that we shouldn't put much effort into tests, implementation is more important, right? Those developers tend to forget the overall cost of maintenance of their codebase. How many bugs you can find on an early stage of implementation just thanks to automatic tests? What's the cost of maintenance of tests written in a not clean way?

During this talk, I will go through some properties of well maintainable tests, present examples of tests hard to maintain and suggest a few ways to improve them. Presented properties and techniques might be valuable for engineers writing and refactoring tests. Finally, I will dive into the term testable design and discuss how to achieve it.</content:encoded>
      <pubDate>Tue, 23 Oct 2018 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/mkk/test-maintainability</link>
      <guid>https://speakerdeck.com/mkk/test-maintainability</guid>
    </item>
    <item>
      <title>C++ based mobile application</title>
      <description>Slides for a talk given during code::dive 2017.</description>
      <media:content url="https://files.speakerdeck.com/presentations/032507fce6094d6aabf4dd60928e93ee/preview_slide_0.jpg?8988337" type="image/jpeg" medium="image"/>
      <content:encoded>Slides for a talk given during code::dive 2017.</content:encoded>
      <pubDate>Wed, 15 Nov 2017 00:00:00 -0500</pubDate>
      <link>https://speakerdeck.com/mkk/c-plus-plus-based-mobile-application</link>
      <guid>https://speakerdeck.com/mkk/c-plus-plus-based-mobile-application</guid>
    </item>
  </channel>
</rss>
