<?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 Cole Jr</title>
    <description>The latest articles on DEV Community by Kevin Cole Jr (@kevcole).</description>
    <link>https://dev.to/kevcole</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%2F436677%2F4d14890e-d8b6-41e2-a894-d2cbf09d83af.jpg</url>
      <title>DEV Community: Kevin Cole Jr</title>
      <link>https://dev.to/kevcole</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kevcole"/>
    <language>en</language>
    <item>
      <title>Views from serverless</title>
      <dc:creator>Kevin Cole Jr</dc:creator>
      <pubDate>Wed, 09 Sep 2020 00:43:41 +0000</pubDate>
      <link>https://dev.to/kevcole/views-from-serverless-4bhj</link>
      <guid>https://dev.to/kevcole/views-from-serverless-4bhj</guid>
      <description>&lt;p&gt;After passing the solutions architect exam I found myself thinking “ok, now what?”. I came across the #cloudresumechallenge on Reddit and got to work. Here are some thoughts on the criteria needed to complete the challenge.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;HTML/CSS&lt;/strong&gt; - I’ve always liked front-end since the myspace era. I chose a resume design template I saw on Pinterest a while back and wanted to copy it. It’s minimalist purposely since  this challenge is mostly about connecting things on the backend. I did however remember to take a mobile first design approach. Added in some flexbox for good measure.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Static S3 Website/HTTPS/DNS&lt;/strong&gt; - While studying for the solutions architect exam, I got plenty of practice deploying a static website to S3 as well as setting up HTTPS and DNS pointing. I’m thankful I got this practice because it helped a lot. And we’re moving…&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Javascript&lt;/strong&gt;- It had been a while since I dipped my toe in the waters of javascript and all it’s quirks. But here we are. I used jQuery for an API call to my API Gateway to make it a little easier&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Python / Database&lt;/strong&gt;- I read through the docs a lot for this one. Python is new to me. It seems to be a lot cleaner than Javascript. I wasn’t too much of a database pro coming into this but the docs are pretty good at explaining. The atomic counter was an interesting solution to the problem so I went with that. I’m experimenting with some other personal projects using dynamodb to get more experience working with it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Infrastructure as code&lt;/strong&gt; - I have a love and hate with SAM. SAM made it really easy to setup all my resources. But indentation mistakes gave me errors galore, so it took me a while but I got it. Shoutout to SAM though. It was a pain in the beginning but I expect to use it extensively in the future.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;API&lt;/strong&gt; - API Gateway was an experience. CORS gave me the biggest issue. After going through what seemed like millions of stack-overflow answers, I came to the conclusion that everyone hates CORS. Okay maybe not everyone but I'm thankful for the experience with API Gateway issues. I gained a better understanding of CORS/Proxy troubleshooting.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;CI/CD(Front end)&lt;/strong&gt; - Setting up the CI/CD backend made things a lot simpler. I found a great blog post to guide me along the path to using Github actions for my front-end by Kyle Galbraith here .&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Tests and CI/CD(Back end)&lt;/strong&gt; - This one was a little hard to setup for me. The testing was a pain, especially dealing with Pytest. But once I figured that out I was home free.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Final Thoughts&lt;/strong&gt; - I really appreciate the #cloudresumechallenge. Especially as a newbie to AWS. It made me work hard and read a lot but the end result is a better foundational knowledge of how some key AWS services work and integrate with each other. I plan to do more experimenting and mini projects as I go on this AWS journey.&lt;/p&gt;

&lt;p&gt;Check out my final project &lt;a href="//kevincolejr.com"&gt;here&lt;/a&gt;&lt;/p&gt;

</description>
      <category>aws</category>
      <category>beginners</category>
      <category>architecture</category>
      <category>serverless</category>
    </item>
  </channel>
</rss>
