<?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: Kory Tegman</title>
    <description>The latest articles on DEV Community by Kory Tegman (@koryteg).</description>
    <link>https://dev.to/koryteg</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%2F209179%2F16e0e12c-768a-45a2-b788-5c022e3031da.jpeg</url>
      <title>DEV Community: Kory Tegman</title>
      <link>https://dev.to/koryteg</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/koryteg"/>
    <language>en</language>
    <item>
      <title>Why you should put in the time to automate your process.</title>
      <dc:creator>Kory Tegman</dc:creator>
      <pubDate>Thu, 09 Jan 2020 22:37:19 +0000</pubDate>
      <link>https://dev.to/koryteg/why-you-should-put-in-the-time-to-automate-your-process-aa6</link>
      <guid>https://dev.to/koryteg/why-you-should-put-in-the-time-to-automate-your-process-aa6</guid>
      <description>&lt;p&gt;CI/CD doesn't just save you time (and lots of it). there are a ton of other benefits:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;stress: how many times have you been worried pushing the deploy button making sure you checked everything twice? &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;cognitive load: why waste the space in your brain on all these repeat tasks? everything is the same every time!&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;forces better technical decisions: If you are building a feature that will effect production, or could be done in a way that would require manual intervention, CI/CD forces you to think about how to solve this problem in a way that is backwards compatible, can be automated, and wont break production if merged. this leads to more stable code&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;when all these are applied it causes your developer experience to be automated and gives devs the ability to merge often and liberally.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

</description>
      <category>devops</category>
      <category>deployment</category>
      <category>productivity</category>
      <category>javascript</category>
    </item>
    <item>
      <title>Tailwind and React inputs</title>
      <dc:creator>Kory Tegman</dc:creator>
      <pubDate>Wed, 06 Nov 2019 18:27:18 +0000</pubDate>
      <link>https://dev.to/koryteg/tailwind-and-react-inputs-10pd</link>
      <guid>https://dev.to/koryteg/tailwind-and-react-inputs-10pd</guid>
      <description>&lt;p&gt;I have been interested in tailwind css so I wanted to quickly spit out a form I had in my head. here it is. I would love feedback and maybe some iterations on how to make the cod cleaner.&lt;/p&gt;

&lt;p&gt;&lt;iframe height="600" src="https://codepen.io/koryteg/embed/GRRdqyv?height=600&amp;amp;default-tab=result&amp;amp;embed-version=2"&gt;
&lt;/iframe&gt;
&lt;/p&gt;

</description>
      <category>codepen</category>
      <category>react</category>
      <category>css</category>
    </item>
  </channel>
</rss>
