<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dwight Doane on Medium]]></title>
        <description><![CDATA[Stories by Dwight Doane on Medium]]></description>
        <link>https://medium.com/@dwightdoane?source=rss-1d122d1f3f8f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*gpXJK9yp1wkbvslq.jpeg</url>
            <title>Stories by Dwight Doane on Medium</title>
            <link>https://medium.com/@dwightdoane?source=rss-1d122d1f3f8f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:40:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dwightdoane/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Pre-populating Angular 1’s templateCache, and not.]]></title>
            <link>https://medium.com/@dwightdoane/pre-populating-angular-1s-templatecache-and-not-fae9511af100?source=rss-1d122d1f3f8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/fae9511af100</guid>
            <category><![CDATA[angularjs]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[gulp]]></category>
            <dc:creator><![CDATA[Dwight Doane]]></dc:creator>
            <pubDate>Mon, 17 Oct 2016 20:46:21 GMT</pubDate>
            <atom:updated>2016-10-17T20:46:21.385Z</atom:updated>
            <content:encoded><![CDATA[<p>So at work I’m building an Angular 1 app. I’m of course using gulp, and the neat little plugin called gulp-angular-templatecache. The problem is I don’t want to put all my .html templates in the cache. That would bloat the file.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8b143b22410933a2a1967bd86be88874/href">https://medium.com/media/8b143b22410933a2a1967bd86be88874/href</a></iframe><p>So what “asyncViews” does is it looks for all the files that have “.async.html” and copies them to a “/templates” directory in my “/build” folder, so that when I need a template, it can fetch it from there asynchronously.<br>It’s an easy way of keeping my templateCache lean, by serving only some of the files from the cache, i.e most used, or templates that are needed quickly, and keep larger or less used templates out, like terms &amp; conditions.</p><p>Of course “views” just goes right on ahead and populates the templateCache as normal. It ignores files with the “.async.html” extensions. Not much going on there.</p><p>This makes it super easy for future maintenance when I have to add a new component with templates. I can toggle whether or not it should load async vs templateCache, just by changing the file name, and the templateUrl.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fae9511af100" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 2 of my “My first React.js project”]]></title>
            <link>https://medium.com/@dwightdoane/part-2-of-my-my-first-react-js-project-e449b3080fdc?source=rss-1d122d1f3f8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e449b3080fdc</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Dwight Doane]]></dc:creator>
            <pubDate>Wed, 03 Aug 2016 17:51:44 GMT</pubDate>
            <atom:updated>2016-08-03T17:51:44.763Z</atom:updated>
            <content:encoded><![CDATA[<p>Lesson learned. <br>Prototype before writing tests. Otherwise you’ll end up doubling your work.</p><p>Now I have to go back and refactor my tests. I guess it helps to know what things are supposed to do before you write the tests.</p><p>Also I’m not a fan of webpack. I spent over an hour trying to get it and webpack-dev-server configured. It was a nightmare. So I gave up. Browserify and BrowserSync do exactly what I need them to do. Maybe I’ll revisit them later but for now they’re just hinderances. The bootcamp I TA at will go over, so I have to learn it at some point.</p><p>So now that I prototyped, I have a better understanding of the moving pieces. Still not sure where to put things, like ajax requests and such, in terms of component hierarchy. Of course it doesn’t help that AWS S3 SDK is confusing… I plan on going through Dan Abramov’s tuts on egghead and see if they clarifies some more things. I wanted to experience the pain points that redux is supposed to solve, in order to have a better understanding and appreciate for redux.</p><p>Later.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e449b3080fdc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 1 of my “My first React.js project”]]></title>
            <link>https://medium.com/@dwightdoane/part-1-of-my-my-first-react-js-project-6bea618e2e21?source=rss-1d122d1f3f8f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6bea618e2e21</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[electron]]></category>
            <dc:creator><![CDATA[Dwight Doane]]></dc:creator>
            <pubDate>Sun, 31 Jul 2016 20:21:14 GMT</pubDate>
            <atom:updated>2016-07-31T20:21:14.479Z</atom:updated>
            <content:encoded><![CDATA[<p>So here goes…</p><p>I needed an AWS S3 file explorer, so I decided to build one. I also wanted to learn more about React, since I haven’t made anything substantial with it.</p><p>It’s also an excuse to try out <a href="http://electron.atom.io/">Electron</a>. I plan on using the AWS SDK with reactjs to view the files, and then on the “server” side use AWS SDK with node.js to handle streaming file uploads. One reason I chose Electron is so I don’t have to have any kind of hosting, but still reap the benefits of node.js (routing, streaming, etc).</p><p>So far I’ve made my &lt;FileList /&gt; and &lt;DirList /&gt; components and have tested them with tape and cheerio, after reading some of what Eric Elliott has written on the subject.</p><p>The FileList component renders the list of files (obviously), and the DirList component renders a list of directories for the current directory I’m in. Next I have to make the Breadcrumb navigation component.</p><p>Still a long way to go, but it’s atleast a start. This is something I can really use at work as well. So here’s to keeping the motiviation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6bea618e2e21" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>