<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Tomasz Ślązok</title>
    <description>The latest articles on Forem by Tomasz Ślązok (@nexik).</description>
    <link>https://forem.com/nexik</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F667066%2F20212049-8ba5-4206-a198-61d02aedf96a.jpeg</url>
      <title>Forem: Tomasz Ślązok</title>
      <link>https://forem.com/nexik</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/nexik"/>
    <language>en</language>
    <item>
      <title>How to &lt;br&gt; in GitHub Markdown</title>
      <dc:creator>Tomasz Ślązok</dc:creator>
      <pubDate>Mon, 29 Nov 2021 20:55:22 +0000</pubDate>
      <link>https://forem.com/nexik/how-to-in-github-markdown-45kh</link>
      <guid>https://forem.com/nexik/how-to-in-github-markdown-45kh</guid>
      <description>&lt;p&gt;In Github to create markdown file with list of some links started with emoticons instead of standard bullet points or numbers you can use breakpoint (&lt;br&gt;)&lt;/p&gt;

&lt;p&gt;To do this, the line must end with &lt;strong&gt;two spaces and return&lt;/strong&gt;. It's not something natural you can guess but it works like magic :)&lt;/p&gt;

</description>
      <category>github</category>
      <category>markdown</category>
    </item>
    <item>
      <title>Returning back to Google Chrome</title>
      <dc:creator>Tomasz Ślązok</dc:creator>
      <pubDate>Sun, 28 Nov 2021 10:52:55 +0000</pubDate>
      <link>https://forem.com/nexik/returning-back-to-google-chrome-3fic</link>
      <guid>https://forem.com/nexik/returning-back-to-google-chrome-3fic</guid>
      <description>&lt;p&gt;In last few months I used Brave browser as simpler experience getting research from the web. &lt;/p&gt;

&lt;p&gt;Unfortunately in last month I got a lot of problems with random crashing tabs. Most of the time it was on simple pages so it was big of deal unless it happens on pages that I prepare some kind of content writing in the form and lost all my work :(&lt;/p&gt;

&lt;p&gt;Today I tried to find some pages from my Brave history but after scrolling few days down the whole page refreshed and go to first day fo history making it impossible to work on history of browser :(&lt;/p&gt;

&lt;p&gt;Today I decide to back to old Google Chrome + install additional extension so the experience will be as similiar as it can be (more severe privacy settings)&lt;/p&gt;

</description>
      <category>productivity</category>
    </item>
    <item>
      <title>Code Coverage at Landingi</title>
      <dc:creator>Tomasz Ślązok</dc:creator>
      <pubDate>Wed, 14 Jul 2021 13:58:19 +0000</pubDate>
      <link>https://forem.com/nexik/code-coverage-at-landingi-31af</link>
      <guid>https://forem.com/nexik/code-coverage-at-landingi-31af</guid>
      <description>&lt;p&gt;Code Coverage is a negative metric, because it shows us problems we have, not how we could improve.&lt;br&gt;
At Landingi, we waited a long time before deciding to enforce the code coverage for each Pull Request. We were concerned that people would focus on KPI by writing tests for setters, getters, or other irrelevant stuff.&lt;/p&gt;

&lt;p&gt;Quality does not equal quantity. You should focus on what you test and how to make sure you won’t make yourself harm in the long run. You can write a lot of tests for bad code, as a result, you get situations that it will be very difficult to change anything.&lt;/p&gt;

&lt;p&gt;Ultimately, we decided to implement the rule that every PR is covered in at least 80%. Thanks to the @codecov it was very simple. We wanted to improve psychological safety for our developers and increase productivity in long run. After a few days, we got good feedback from our team. I hope it will be better and better.&lt;/p&gt;

&lt;p&gt;P.S. We have plans to introduce mutation testing to improve our unit tests suites.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
