<?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: Kevin</title>
    <description>The latest articles on DEV Community by Kevin (@kmwill23).</description>
    <link>https://dev.to/kmwill23</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%2F133874%2F6259ef0e-9fb7-4304-ab9f-5aa963cbaf4e.png</url>
      <title>DEV Community: Kevin</title>
      <link>https://dev.to/kmwill23</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kmwill23"/>
    <language>en</language>
    <item>
      <title>Reinvent the Wheel</title>
      <dc:creator>Kevin</dc:creator>
      <pubDate>Fri, 27 Dec 2019 19:23:20 +0000</pubDate>
      <link>https://dev.to/kmwill23/reinvent-the-wheel-a30</link>
      <guid>https://dev.to/kmwill23/reinvent-the-wheel-a30</guid>
      <description>&lt;p&gt;While I tagged this as JavaScript, it applies everywhere.&lt;/p&gt;

&lt;p&gt;Don't believe the folks who state that you shouldn't design and code a system that already exists. Similarly, never be afraid to revisit existing code to upgrade it with all your newest tricks.&lt;/p&gt;

&lt;p&gt;The TLDR is simple: everything is a learning experience.&lt;/p&gt;

&lt;p&gt;Do take into account, however, the needs of your organization. I have the advantage of being able to crank out code like there's no tomorrow, so I always take a little time to refactor and reinvent.&lt;/p&gt;

&lt;p&gt;Focusing on the reinvent. When you download a massive Swiss army knife, we all have a good example I am sure (Dev Express for this example), you know it will do alot, but also have many limitations. Say you need a smart excel-like table tool. You could use an external system with it's blessings and flaws, or you could steal the design and reimplement.&lt;/p&gt;

&lt;p&gt;Half the work is done. You know the tool you are borrowing from, and you know your specific requirements. You know the things you like, need, don't need from the other tool. So you begin the process of coding off of those designs and requirements.&lt;/p&gt;

&lt;p&gt;Along the way you will learn tons, re-enforce tons, and have an outcome that may be better or may not.&lt;/p&gt;

&lt;p&gt;Here's always my biggest take-away from these mini-projects: through the process you will either learn why the original had the perceived flaws, or you will find out that you were able to master those flaws and have a product that has the feature-set and the implementation you need, without any bloat.&lt;/p&gt;

&lt;p&gt;Or you could have just constructed the largest pile of pasta you've ever seen.&lt;/p&gt;

&lt;p&gt;But the TLDR is still true! You learned stuff.&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Good news in the office!</title>
      <dc:creator>Kevin</dc:creator>
      <pubDate>Fri, 20 Dec 2019 22:54:28 +0000</pubDate>
      <link>https://dev.to/kmwill23/good-news-in-the-office-8ok</link>
      <guid>https://dev.to/kmwill23/good-news-in-the-office-8ok</guid>
      <description>&lt;p&gt;Ahoy and happy holidays!&lt;/p&gt;

&lt;p&gt;Today is a landmark day in our office. We notified our clients that in our next major release we would no longer be supporting Internet Explorer.&lt;/p&gt;

&lt;p&gt;It was a great holiday gift for me! While there are a ton of modern JavaScript features I am looking forward to using, the first one on my list is the async function.&lt;/p&gt;

&lt;p&gt;What is your favorite newish JavaScript feature, and how has it made your life easier? I am not ashamed to state I plan to steal all your good ideas 😋.&lt;/p&gt;

</description>
      <category>javascript</category>
    </item>
    <item>
      <title>The Case Against JS Frameworks.</title>
      <dc:creator>Kevin</dc:creator>
      <pubDate>Wed, 04 Dec 2019 06:07:45 +0000</pubDate>
      <link>https://dev.to/kmwill23/the-case-against-js-frameworks-294m</link>
      <guid>https://dev.to/kmwill23/the-case-against-js-frameworks-294m</guid>
      <description>&lt;p&gt;Gotcha! This will not likely be the grand debate you are looking for. I think I will make some form of point or observation though. Maybe.&lt;/p&gt;

&lt;p&gt;Oh, and first post. Long time lurker, etc.&lt;/p&gt;

&lt;p&gt;Before I joined the Client Apps team, Jesse over in Internal Systems started modernizing the ye old webforms app using a Handlebars variant.&lt;/p&gt;

&lt;p&gt;Me, I brought in 10 years of JS experience, love, and my Homebrew JS and jQuery plugin system. You could almost call it a framework...but it's not, more of a pattern. I jumped right in that heap of webforms and started flying on all sorts of new projects!&lt;/p&gt;

&lt;p&gt;About six months in, we had a meeting to discuss what Frameworks we should be using. I'm like, "okay, good teams agree on their architecture. I'm game." I presented AngularJS as my personal choice, having tinkered in it before. That was rejected, but only because Bob, a former employee, had thrown together some projects with KnockoutJS, before leaving the company. So we did that.&lt;/p&gt;

&lt;p&gt;But it really isn't an arcitecture, more of a tool. So I kept busting out projects with my personal system, making incremental improvements. Actually removed jQuery at the appropriate time (es5).&lt;/p&gt;

&lt;p&gt;I am productive. Dangerously so. It's hard to beat my numbers. I am the one folks go to when they need something fast and quality. I am not ego-tripping, only making this point because...&lt;/p&gt;

&lt;p&gt;While every team is discussing what framework they are going to use, on top of other existing frameworks, and competing with other teams' framework choices, I just cruise along with my well-documented and proven coding patterns.&lt;/p&gt;

&lt;p&gt;What's weird is no one ever asks me about using it officially. At least they do borrow code/pattern/style. Just like I do from every bit of code I browse.&lt;/p&gt;

&lt;p&gt;I think I promised a point of some kind. Learn to love JavaScript. Don't be afraid of it. Stop trying to find a framework that will hide the implementation and do things for you. One day you'll realize that you don't need the 3000 ton hammer to build that drop-down widget.&lt;/p&gt;

&lt;p&gt;Wait, nowhere in the post did I actually imply any of that. Oh well! &lt;/p&gt;

&lt;p&gt;&lt;em&gt;Yawns&lt;/em&gt; bedtime I think... Let me publish this right before bed. That always tends to work out without any drama.&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>framework</category>
    </item>
  </channel>
</rss>
