<?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>DEV Community: Jon Thor Austen</title>
    <description>The latest articles on DEV Community by Jon Thor Austen (@djangofan).</description>
    <link>https://dev.to/djangofan</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%2F474671%2Ffbc67e1b-43a0-46ef-8aff-0842a182a7ea.png</url>
      <title>DEV Community: Jon Thor Austen</title>
      <link>https://dev.to/djangofan</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/djangofan"/>
    <language>en</language>
    <item>
      <title>Common misconceptions about Bitcoin</title>
      <dc:creator>Jon Thor Austen</dc:creator>
      <pubDate>Tue, 02 Aug 2022 18:42:17 +0000</pubDate>
      <link>https://dev.to/djangofan/common-misconceptions-about-bitcoin-4jlk</link>
      <guid>https://dev.to/djangofan/common-misconceptions-about-bitcoin-4jlk</guid>
      <description>&lt;p&gt;There are a lot of misconceptions and incorrect assumptions being made about Bitcoin.    Every year there are new narratives being created which try to explain why Bitcoin will not succeed. &lt;/p&gt;

&lt;p&gt;It is very likely that these concerns are incorrect.  Here are some curated sources for explanations around these narratives.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://casebitcoin.com/critiques"&gt;https://casebitcoin.com/critiques&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://endthefud.org/"&gt;https://endthefud.org/&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Code Coverage with Cypress &amp; Angular</title>
      <dc:creator>Jon Thor Austen</dc:creator>
      <pubDate>Tue, 14 Dec 2021 19:36:50 +0000</pubDate>
      <link>https://dev.to/djangofan/code-coverage-with-cypress-angular-4je4</link>
      <guid>https://dev.to/djangofan/code-coverage-with-cypress-angular-4je4</guid>
      <description>&lt;p&gt;Forking a new HOWTO from &lt;a href="https://dev.to/muratkeremozcan/combined-unit-e2e-code-coverage-case-study-on-a-real-life-system-using-angular-jest-cypress-gitlab-35nk"&gt;https://dev.to/muratkeremozcan/combined-unit-e2e-code-coverage-case-study-on-a-real-life-system-using-angular-jest-cypress-gitlab-35nk&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;IN PROGRESS...  COMING SOON...   FIRST POST...&lt;/p&gt;

&lt;h2&gt;
  
  
  Istanbul w/Unit Tests
&lt;/h2&gt;

&lt;p&gt;As you know, you might configure unit test code coverage and then run your code coverage report like so:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;ng test --browsers=ChromeHeadless --codeCoverage=true --watch=false --sourceMap=false&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;From that you will generally get a &lt;code&gt;coverage&lt;/code&gt; folder in the root of your project that contains a &lt;code&gt;src&lt;/code&gt; instrumented code folder.   Next to that will be your report results files.&lt;/p&gt;

&lt;h2&gt;
  
  
  Instanbul w/Cypress
&lt;/h2&gt;

&lt;p&gt;TODO&lt;/p&gt;

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