<?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 Jacob Moore on Medium]]></title>
        <description><![CDATA[Stories by Jacob Moore on Medium]]></description>
        <link>https://medium.com/@jrmoore117?source=rss-12c6f33527d6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*FYGf2tlsQ0sw_0hS</url>
            <title>Stories by Jacob Moore on Medium</title>
            <link>https://medium.com/@jrmoore117?source=rss-12c6f33527d6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:01:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jrmoore117/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[Speed Up Your Initiative Rolls with Handy DnD]]></title>
            <link>https://medium.com/@jrmoore117/speed-up-your-initiative-rolls-with-handy-dnd-40a66b1073d8?source=rss-12c6f33527d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/40a66b1073d8</guid>
            <category><![CDATA[dungeons-and-dragons]]></category>
            <dc:creator><![CDATA[Jacob Moore]]></dc:creator>
            <pubDate>Tue, 12 Feb 2019 05:09:53 GMT</pubDate>
            <atom:updated>2019-02-12T05:09:53.723Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IZZMX-whzntMZNjgDVrqcQ.png" /></figure><p>Bring your initiative rolls out of the Middle Ages and into the 21st Century with <a href="https://handy-dnd.herokuapp.com/">Handy DnD</a>. Rolling initiative is time consuming, tedious, and takes away from the much more fun parts of a DnD play session. With that in mind, Handy DnD was created to help DMs roll initiative for all their players <em>and </em>the monsters in seconds (don’t worry, the app still lets players enjoy the fun of rolling for their attacks in combat).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*naOdVsvN-3tgHjz0riD0MQ.png" /></figure><p>Once you’ve signed up and logged into the app, head to the Campaign page where you can add various monsters and characters to the Combatants panel. After that, clicking Roll Initiative will roll 1d20 for each of the combatants <em>and </em>apply each combatant’s dexterity mod to its roll. The Combatants list will automatically be rearranged according to the initiative roll, and End Combat and Next Turn buttons will appear on screen, providing the DM with the controls they need to keep track of the turn order.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N9PrDaOW7g_eyR874Fx_YA.png" /></figure><p>Additionally, the DM is provided with a display of the current combatant’s stats and a place to track each combatant’s health and armor class.</p><p>Handy DnD also features an ‘encyclopedia’ of detailed information on all DnD’s standard monsters and spells. This way, the DM can access this information even when their players are not in combat. And if the DM prefers to plan ahead for a play session, the app includes a Setup page where they can build encounters and add characters to their campaign for use during the next play session.</p><p>So, if you’re a DM wanting to cut down on some of the tedium of managing a campaign, then give <a href="https://handy-dnd.herokuapp.com/">Handy DnD</a> a try!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40a66b1073d8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Anime.js: The Basics]]></title>
            <link>https://medium.com/@jrmoore117/anime-js-the-basics-39d979f3d91f?source=rss-12c6f33527d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/39d979f3d91f</guid>
            <category><![CDATA[css]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[animation]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Jacob Moore]]></dc:creator>
            <pubDate>Sat, 19 Jan 2019 04:43:54 GMT</pubDate>
            <atom:updated>2019-01-19T04:43:54.671Z</atom:updated>
            <content:encoded><![CDATA[<p>As a web developer, I love how many opportunities I get to mix technical skills with creative ones. Recently, I got to lean a little more into the latter as I worked with a small team to build an app that we called Codex, a simple site for saving your favorite code snippets. Once we got Codex up and running, it was time to polish up the UI, and one tool we used to accomplish this was a powerful but surprisingly-easy-to-learn Javascript animation library called <a href="https://animejs.com/">Anime</a>. Anime provides a long list of tools that you can mix and match to create custom animations. Below, I’ve broken down the code we used to make a basic sidebar animation for Codex. Here’s how it looks:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*yojte8XC_lUwWcv6xY72Hg.gif" /></figure><p>Each new animation is created using the “anime( )” function that’s built into the library. After that, you set keys on the object that’s passed to the function. Here’s the code for the animation:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/520/1*O5brfB7u0f8lMuC6ioGh0g.png" /></figure><p><strong>Step 1: Pick your “easing”</strong></p><p>The first key on the object is your “easing”. This refers to the pattern of acceleration and deceleration that each animated element follows as it moves around the page. If you look closely at my example, you’ll see that each element begins moving quickly onto the page but then decelerates and slowly settles into its final position. All of Anime’s easing properties are based on mathematical functions. In this example, “easeOutExpo” refers to an exponential function, which is why my animated elements ‘exponentially’ decelerate. If I had instead chosen “linear” easing, then the animated elements would have maintained a consistent speed as they approached their final position. Anime details all the possible easings <a href="https://animejs.com/documentation/#linearEasing">here</a> in their documentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/1*88PmTN4mOmAmlbqdx5OCMw.png" /></figure><p><strong>Step 2: Pick your “targets”</strong></p><p>After you have chosen your easing, you will define your targets, which point to the element(s) you want to animate. In my example, I target “.language”, which refers to all the &lt;div&gt; elements on the page with the .language class. Anime’s targeting provides you with all the same options as CSS selectors, so if you know those, then you’re good to go!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/376/1*G5PAsqVXwLXGuJvBKoAXIg.png" /></figure><p><strong>Step 3: Add your animation properties</strong></p><p>This is where you have the most freedom to mix and match all the tools that Anime provides. For the sake of simplicity, I’m going to focus on the two very basic options I chose for animating the Codex sidebar.</p><p>First, I chose to set the opacity to [0, 1], which means that the elements will fade from 0% to 100% opacity as they slide onto the page. If I instead chose to make these values [0.5, 1], then the elements would have started at 50% opacity instead.</p><p>Second, I chose to set translateX to [-250, 0]. Here, 0 is representative of the targeted element’s final position. So, the element will begin -250px on the x-axis (off the boundaries of the page) relative to its final position.</p><p>Combining these with the easing I described above means that each element will simultaneously exponentially decelerate, fade from 0% to 100% opacity, and slide from -250px to 0px from its final position.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*IdFU1FUGjmQgdiA3MwYa2Q.png" /></figure><p><strong>Step 4: Set the duration of the animation</strong></p><p>Anime measures the duration of animations in milliseconds. This means the above animation will take 1 second to complete.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/506/1*nyOQtZ_FGnuCcmwq2ucfHg.png" /></figure><p><strong>Step 5 (optional): Add “offset” and “delay”</strong></p><p>Finally, using Anime’s “delay” and “offset” properties, you can control at what point in time the animation will begin for each targeted element.</p><p>Using the delay property, I was able to make each “.language” element’s animation begin slightly after the one that came before it. So the code above is saying that each element’s animation will begin 100 milliseconds after the element that came before it.</p><p>The offset property is written as a string between the closing curly brace and closing parenthesis. It controls the initial starting time of the entire animation. In this case, Codex executed this animation on page load, so I specify that the animation’s start should be offset by +250 milliseconds (so the animation doesn’t start before the whole DOM has been rendered to the page). If I chose to make the offset “-=250”, then the animation would begin 250 milliseconds earlier than the default start point.</p><p><strong>Step 6: Enjoy your animation!</strong></p><p>While this code only produced a simple sliding animation, it added some much-needed flavor to our sidebar that will hopefully help to catch the user’s eye as they load into the Codex dashboard for the first time. In development, it can be easy to overlook the value of small additions such as this, but I think they’re an important contributor to the overall quality of the final product. Anime is a great user-friendly library, and I encourage anyone interested to give it a try!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39d979f3d91f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[No Alternative to Real-World Practice]]></title>
            <link>https://medium.com/@jrmoore117/no-alternative-to-real-world-practice-bcfdfb3d4300?source=rss-12c6f33527d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcfdfb3d4300</guid>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Jacob Moore]]></dc:creator>
            <pubDate>Thu, 06 Dec 2018 07:05:17 GMT</pubDate>
            <atom:updated>2018-12-06T07:05:17.906Z</atom:updated>
            <content:encoded><![CDATA[<p>Since the beginning of November, I’ve been enrolled in a coding bootcamp, and over the past week, I was one member of a 4-person team working to build an app that we called Keeper. The idea behind the app was to help a shopper more easily decide if they should purchase the article of clothing they’re trying on in the fitting room. The shopper uploads a picture of their potential purchase to Keeper, where other users, or in this case voters, can cast their vote for whether or not they think the pictured article of clothing is a ‘Keeper’. My team and I knew that the first weeks of our coding bootcamp had given us the skills we needed to bring our idea to life, but when it came time to crank out some code, I found myself coming to what now seems an obvious realization: that coding to complete dozens of class activities and a handful of homework assignments was <em>not</em> the same as coding to build our own app. In a class activity, we’re asked to get from point A to B and told which tools to use to make that happen. With Keeper, my team and I had chosen our point B, but this time it was up to us to figure out which tools would be the ones to get us there.</p><p>Navigating this decision-making process and successfully finding my way to Keeper’s completion required me to do a few things consistently. First and foremost, I had to rely on pooling my own knowledge with that of my teammates. In coding, any problem has countless possible solutions, so it only made sense to join forces with my teammates when we came to an obstacle in Keeper’s development. Doing so allowed us to more quickly weed out problematic or inefficient solutions and to hone in on the solution that would work best. If I encountered a road block when working solo, I would think back to class, combing through the skills we’d learned to pick the one that would best equip me to move forward. And when it came down to it, whether I was working alone or with my team, nothing worked better for solving a problem than trial and error. All of this together led to the emergence of a work-flow that I noticed my team following throughout our project: identify the problem, explore and prioritize possible solutions with the team, and put the ideas to the test. If by then you haven’t succeeded, dig into whatever info you can find online and start the process over again.</p><p>Following this system, we were able to make the most of our week, ending with a polished version of Keeper that we’re all proud of. While I’m glad to be done with this project, I’m also glad that I got the opportunity to struggle through it with my team. Next time I find myself in this situation, I’ll be sure to reflect on how the Keeper team tackled such an open-ended assignment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcfdfb3d4300" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>