<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jakub Gimiński on Medium]]></title>
        <description><![CDATA[Stories by Jakub Gimiński on Medium]]></description>
        <link>https://medium.com/@giminski?source=rss-1d7b1defd454------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*AaDhrNgtgBHP_JufB_jR3g.jpeg</url>
            <title>Stories by Jakub Gimiński on Medium</title>
            <link>https://medium.com/@giminski?source=rss-1d7b1defd454------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:16:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@giminski/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Values - Who Needs Them, Right?]]></title>
            <link>https://medium.com/@giminski/values-who-needs-them-a1418fc81da6?source=rss-1d7b1defd454------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1418fc81da6</guid>
            <category><![CDATA[compassion]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[values]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Jakub Gimiński]]></dc:creator>
            <pubDate>Wed, 10 May 2023 16:13:40 GMT</pubDate>
            <atom:updated>2023-05-10T16:42:22.430Z</atom:updated>
            <content:encoded><![CDATA[<p>A few years ago, I was sitting at a company town hall meeting, listening to a presentation given by the CTO. Roadmap, goals, numbers — nothing surprising, but then they started talking about something that baffled me — company values. Who needs them, I thought to myself at the time, before quickly dismissing the whole idea as naive and meaningless.</p><p>Today, with a few years more under my belt, I believe values play a fundamental role in guiding our decisions. We all have them, mostly conditioned by experiences. However, through self-reflection, we can consciously determine the person we aspire to become and embody those traits, regardless of the experiences.</p><p>There are two values in particular that I preach to everyone I work with, as they foster an atmosphere of trust, purpose, and unity within the team.</p><p>The first value is <strong>“</strong>F<strong>reedom and Responsibility”</strong>. It means that we should have the freedom to act responsibly.</p><ul><li>Freedom to manage our time</li><li>Freedom to make decisions required to drive concerns forward</li><li>Responsibility for our work</li><li>Responsibility for the work of our colleagues</li></ul><p>The second value, which goes hand in hand with the first one, is called <strong>“Transparency, Honesty, Compassion”.</strong></p><p>It means that we should always be up-front and honest about our intentions, actions, and opinions. Secrets, lies, and dishonesty are toxic.</p><p>Additionally, we should always give and receive feedback with compassion. We never really know what the other person might be going through. Maintaining good relationships is key to a healthy team.</p><p>I advocate for these two values in the pursuit of cultivating healthy environments where self-sufficient teams can thrive, work harmoniously, and deliver ongoing value to the business. If this sounds nothing like the environment you’re in, perhaps reflect on your values, or even consider adopting the ones I’ve outlined here.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1418fc81da6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Losing Head Over Code Coverage]]></title>
            <link>https://medium.com/better-programming/loosing-head-over-code-coverage-c2d955bd4c3c?source=rss-1d7b1defd454------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2d955bd4c3c</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Jakub Gimiński]]></dc:creator>
            <pubDate>Tue, 05 Jul 2022 15:13:21 GMT</pubDate>
            <atom:updated>2022-07-26T12:54:15.868Z</atom:updated>
            <content:encoded><![CDATA[<h4>And how to incorporate test coverage into development</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_8sSkRABSES9okXA" /><figcaption>Photo by <a href="https://unsplash.com/@8moments?utm_source=medium&amp;utm_medium=referral">Simon Berger</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Relationships can be hard, no doubt, but also in many ways schematic. Patterns may be observed and phrases defined.</p><p>A peculiar pattern I have observed in relationships between development teams and code coverage.</p><p>First, there is the ignorance phase, where developers ignore the metric of code coverage completely, however many tests they might be writing.</p><p>Then, once the metric is discovered, developers tend to obsess over it, treating it as the one and only determinant of test suite quality — that’s the obsession phase.</p><p>Ultimately, the relationship would evolve into the final phase, where the code coverage is one of many metrics for software quality assurance, treated with proper caution.</p><p>Developers writing automated tests is industry standard, required to produce software is a maintainable and scalable fashion.</p><p>Everyone writes tests nowadays, but not nearly as many incorporate test coverage into their workflows. If you find yourself in this category, let me tell you about the coverage.</p><blockquote><em>In computer science, test coverage is a percentage measure of the degree to which the source code of a program is executed when a particular test suite is run.</em></blockquote><p>For example, 50% means half of our code is executed at least once during the test suite run and the other half is completely omitted.</p><p>100% means the source code is fully covered with tests. That doesn’t guarantee bugless code, but if done right, gets you pretty close, while not being a huge burden on development and maintenance processes.</p><p>Here’s how to incorporate test coverage into development:</p><ul><li>When writing new code, use IDE with the debugger to inspect which lines of the new source code are hit by the tests and which aren’t. You’ll be surprised.</li><li>Make coverage measurement part of the CI/CD pipeline. Have Pull Requests indicate how they’re affecting the overall coverage (increase/decrease/neutral). Also, put a coverage badge at the top of the repo’s readme file.</li></ul><p>The natural next step of “the relationship” seems to be the obsession phase, where developers tend to favor test coverage over any other metric.</p><p>They write high-level tests only (because they come with the cheapest coverage), and all of their confidence is derived from this single statistic.</p><p>Sadly, that often isn’t enough, because, by the end of the day, the ultimate statistic is how many bugs we let slip through to the end user. When in the obsession phase, you most likely won’t find those two metrics correlating as expected.</p><p>Here’s how to bring your software quality assurance to the next level:</p><ul><li>Be mindful about the logical side of your tests, and not just lines of code covered. Make assertions meaningful and strict.</li><li>Test different paths extensively. Don’t easily dismiss code as tested once the lines have been hit. Often, testing different paths requires covering the same lines multiple times.</li><li>Treat tests as first-class citizens of peer review.</li><li>Retrospectively analyze bugs and work on improving the test suite to prevent the same type of bugs in the future.</li></ul><p>The bottom line is that as much as I encourage developers to rely on code coverage, keep in mind that there are other aspects in play in terms of test suite quality.</p><p>After all, the ultimate purpose of test automation is to enable fast development with high confidence, and the ultimate determinant of its quality is bugs getting through to the end user.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2d955bd4c3c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-programming/loosing-head-over-code-coverage-c2d955bd4c3c">Losing Head Over Code Coverage</a> was originally published in <a href="https://betterprogramming.pub/">Better Programming</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>