<?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: Alex Daro</title>
    <description>The latest articles on DEV Community by Alex Daro (@al_daro).</description>
    <link>https://dev.to/al_daro</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%2F335513%2Fbf8217cd-e464-4a4b-a791-3bc3424f68a5.jpg</url>
      <title>DEV Community: Alex Daro</title>
      <link>https://dev.to/al_daro</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/al_daro"/>
    <language>en</language>
    <item>
      <title>Scheduling Website Content With JavaScript and AWS CloudWatch</title>
      <dc:creator>Alex Daro</dc:creator>
      <pubDate>Fri, 14 Feb 2020 05:24:56 +0000</pubDate>
      <link>https://dev.to/al_daro/scheduling-website-content-with-javascript-and-aws-cloudwatch-3f5e</link>
      <guid>https://dev.to/al_daro/scheduling-website-content-with-javascript-and-aws-cloudwatch-3f5e</guid>
      <description>&lt;p&gt;Hi, devs! 🤓&lt;/p&gt;

&lt;p&gt;I'm getting close to wrapping the first round of development with my new side-project newclick.io so I figured I'd share some insight on how I built an API for &lt;a href="https://www.alexdaro.com/writing/scheduling-website-content-with-javascript-and-aws-cloudwatch"&gt;scheduling website content&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;To be honest I was having trouble finding the confidence to publish this. I wanted to write this in-depth, ground shattering post on scheduling Lambda functions with Amazon Cloudwatch but every time I sat down to write it seemed like an insurmountable task... Quite honestly it was bumming me out! So what I did instead was implemented some Tim Ferris voodoo logic and asked my self: "What would this look like if it were easy?". That was the thing that got me over the hump...&lt;/p&gt;

&lt;p&gt;I changed the opening sentence from "In this article, I'll describe everything that went into developing the newclick.io Scheduling API." -- to -- "In this article, I'll briefly describe some of the things that went into developing the newclick.io Scheduling API. "&lt;/p&gt;

&lt;p&gt;This helped me hone in what I wanted to say and get it out the door. Every blog post doesn't need to be a novel. A simple, easy to read how-to guide was good enough.&lt;/p&gt;

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