<?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 Bjarte Djuvik Næss on Medium]]></title>
        <description><![CDATA[Stories by Bjarte Djuvik Næss on Medium]]></description>
        <link>https://medium.com/@bjartedjuviknss?source=rss-fab8dbb3dc6c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*JjqUobrOZR-B-nX4.</url>
            <title>Stories by Bjarte Djuvik Næss on Medium</title>
            <link>https://medium.com/@bjartedjuviknss?source=rss-fab8dbb3dc6c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 10:57:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bjartedjuviknss/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[Quality of the design of your software]]></title>
            <link>https://medium.com/@bjartedjuviknss/quality-of-the-design-of-your-software-58acb409a149?source=rss-fab8dbb3dc6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/58acb409a149</guid>
            <dc:creator><![CDATA[Bjarte Djuvik Næss]]></dc:creator>
            <pubDate>Tue, 01 May 2018 06:55:44 GMT</pubDate>
            <atom:updated>2018-05-01T06:55:44.804Z</atom:updated>
            <content:encoded><![CDATA[<p>If writing tests is hard, the design of your code is bad.</p><p>If writing tests is easy, the design might still be bad. But for other reasons.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58acb409a149" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do not create tests for methods and classes, create tests for behaviours]]></title>
            <link>https://medium.com/@bjartedjuviknss/create-tests-for-methods-instead-of-creating-tests-for-behaviours-a8d6c6963179?source=rss-fab8dbb3dc6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8d6c6963179</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[tdd]]></category>
            <category><![CDATA[unit-testing]]></category>
            <dc:creator><![CDATA[Bjarte Djuvik Næss]]></dc:creator>
            <pubDate>Thu, 26 Apr 2018 19:45:13 GMT</pubDate>
            <atom:updated>2018-04-28T19:12:12.967Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the problems one can run into when doing too granular unit tests, or doing test driven development is that the tests very quickly get coupled to implementation. If you test every single method and class of your system, this is for sure the case.</p><p>If you refactor your system to have a different implementation, but the same behaviour, your tests should (ideally) not break.</p><p>This is very well explained in this video</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FEZ05e7EMOLM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DEZ05e7EMOLM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FEZ05e7EMOLM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a264ce8b52c436641c57280de926c9e4/href">https://medium.com/media/a264ce8b52c436641c57280de926c9e4/href</a></iframe><p>…and the following video gives a very short and consise description of the same problem</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FmT8QDNNhExg%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DmT8QDNNhExg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FmT8QDNNhExg%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f34cb8e720cc18a23be3be7fd5000ce8/href">https://medium.com/media/f34cb8e720cc18a23be3be7fd5000ce8/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8d6c6963179" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Common mistakes when using Entity Framework]]></title>
            <link>https://medium.com/@bjartedjuviknss/common-mistakes-when-using-entity-framework-1686094447c7?source=rss-fab8dbb3dc6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/1686094447c7</guid>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[csharp]]></category>
            <category><![CDATA[entity-framework]]></category>
            <dc:creator><![CDATA[Bjarte Djuvik Næss]]></dc:creator>
            <pubDate>Sun, 15 Apr 2018 06:46:10 GMT</pubDate>
            <atom:updated>2018-04-15T06:47:36.556Z</atom:updated>
            <content:encoded><![CDATA[<p>When using the entity framework to access your database there are a some traps you can fall into.</p><p>One trap is the tight coupling of your application to the Entity Framework, which violates the principle of abstracting away you underlying frameworks. I don’t think this principle always applies, but often it does. It depends…</p><p>The other trap is repeating the same query in your application, which violates the DRY principle. Say you have a user entity with the “<em>IsActive</em>” property to indicate that the user has not been disabled. Every time you query for users you would need to add the “<em>.Where(user=&gt;user.IsActive)</em>” predicate to the query to make sure you only get active users. If change your definition of an active user, you would need to go into all queries using this predicate and update them.</p><p>By abstracting away queries and hiding the IQueryable interface behind a wrapper you can both decouple the framework from the rest of your application and avoid repeating queries.</p><p>Mosh Hamedani has a nice video on this</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FrtXpYpZdOzM%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DrtXpYpZdOzM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FrtXpYpZdOzM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7395b5a3eaf5ffc11d35b5e9c68d85f2/href">https://medium.com/media/7395b5a3eaf5ffc11d35b5e9c68d85f2/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1686094447c7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reading code]]></title>
            <link>https://medium.com/@bjartedjuviknss/reading-code-3f4649a00cc?source=rss-fab8dbb3dc6c------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f4649a00cc</guid>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Bjarte Djuvik Næss]]></dc:creator>
            <pubDate>Mon, 09 Apr 2018 14:34:03 GMT</pubDate>
            <atom:updated>2018-04-10T06:27:52.290Z</atom:updated>
            <content:encoded><![CDATA[<p>Reading code is not sufficient to understand the codebase. The context of the developer who wrote the code is gone. What is the reasoning behind his choices? Did he work under time constraints? Was the system memory constrained? Was he making performance optimizations?</p><p>All of these aspects get lost. To make software understandable for future developers there need to be more documentation than just the code. Documentation can come in many forms like in-line comments, commit messages and even videos about the code.</p><p>Bjarte</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f4649a00cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>