<?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 Jordan Gamble on Medium]]></title>
        <description><![CDATA[Stories by Jordan Gamble on Medium]]></description>
        <link>https://medium.com/@jgamble482?source=rss-6611e416082b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*6r5rA33s3Q10tUBVRYkKnA.jpeg</url>
            <title>Stories by Jordan Gamble on Medium</title>
            <link>https://medium.com/@jgamble482?source=rss-6611e416082b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 09:47:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jgamble482/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[Designing an App from Nothing (For the first time)]]></title>
            <link>https://medium.com/@jgamble482/designing-an-app-from-nothing-for-the-first-time-8c6f4ab3d930?source=rss-6611e416082b------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c6f4ab3d930</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[app-design]]></category>
            <category><![CDATA[ironhack]]></category>
            <dc:creator><![CDATA[Jordan Gamble]]></dc:creator>
            <pubDate>Tue, 04 Feb 2020 17:55:41 GMT</pubDate>
            <atom:updated>2020-02-04T17:55:41.518Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Assignment</h3><p>I was assigned two weeks to fully design a digital product based on an original idea. For this assignment, I wanted to think of a digital product that I could be passionate about, but I also wanted to create something that could be useful to a wide variety of people. Therefore, I decided to create a digital product related to the food industry.</p><p>The idea came from my observations of daily life. I have always noticed that there are lots of people who do not have adequate culinary knowledge. However, these same people want access to homemade meals in order to add variety and authenticity to their cooking routine. Therefore, I decided to design an app that could connect busy young professionals to homemade meals.</p><h3>Background Research</h3><p>First, I had to validate the viability of my product with user research. I created a Google Form survey, and I conducted in-person interviews to see if there were any potential users of my service. I was also curious to see their mealtime preferences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mkv-v43nPXAhx5ViApcZOg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7yZ_MSCWeX6ymlEDYsEKbQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KDcR8wBB1BrtCX_Mo5vHHg.png" /></figure><p>The next step of the process was face to face interviews. The responses that I got validated the use case for my app. Many people replied that they would use such an application. However, the knowledge of a viable user base was not the most valuable information I gained from the interviews. I discovered that people value the social aspect of dining. They enjoy cooking for other people, or being granted the opportunity to have people cook for them. I now saw my burgeoning application not only as a means to get something to eat, but also as a social app.</p><p>My next step was to investigate the competition that was already out there. I found four companies that vaguely matched what I was trying to design. However, what I realized is that none of them had the brand identity I was trying to create. All of them were centered around providing more of a formal catered dining type experience. I wanted my app to be something a user could use in lieu of delivery or takeout food. Based off of this research, I determined that I wanted my brand attributes to be: Social, Casual, Affordable, and Never Upscale.</p><p>The last step of the empathy phase I completed was creating two user personas. In my case, my app has two main user personas. The first one is a person who wants to use the app to get a homemade meal. I imagined this person to be a young professional working in a medium/large metropolitan area. This person has minimal cooking skills and rarely gets a high quality meal (I decided to name him Eric). The secondary user persona is someone who has a passion for cooking or social dining. This person also lives in a medium/large metropolitan area</p><h3>Ideation</h3><p>At this point in time, I really wanted to pivot from working on theoretical ideas to concrete features I wanted to implement in the applications. I began this process via a method called crazy 8. For this brainstorming exercise, I spent eight minutes coming up with ideas for my app to have, spending one minute per idea. This method is good for creating a good volume of ideas of varying quality. The best ideas I came up with were: kitchen registration, chef menu customization, chef/meal reviews, and search filtering by cuisine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4xTM8XTExrw1IbM4Cg70WA.jpeg" /><figcaption>Crazy 8 Ideation Exercise</figcaption></figure><p>The next step was to create the primary and secondary user flows. I determined that the primary user flow would consist of opening the app, registering, and then ordering a chef to come cook a meal. The secondary user flow would consist of opening the app, registering as a chef, and customizing a menu. I outlined the steps on a blank sheet of paper, and I categorized them based on whether the step was a decision, terminator, or process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a8knQ4SAfqP9BEe0W361UA.jpeg" /><figcaption>Primary User Flow: Order a Chef for the First Time</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l3kntu1PzIOaqemTD8Oogw.jpeg" /><figcaption>Secondary User Flow: Register as a Chef and Customize Profile</figcaption></figure><h3>Prototyping</h3><p>Creating the primary and secondary user flows allowed me to figure out the screens that I actually had to create for a Minimal Viable Product or MVP for short. I had to design the screens that would guide the user easily through the user flows that I created.</p><p>To approach this task, I used the practice of creating a low fidelity prototype. I did not waste time with creating it because the true value in a prototype of this nature is the ability to rapidly test and make changes to the design. I repeated this test and revision process roughly 10 to 15 times until I landed on a lo-fi prototype that my testers deemed easy to use. I ended up mocking up over 20 screens after all my testing. I won&#39;t post all of them, but I&#39;ll share a few for you to get the gist of the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*wfnc3X1qvw5Rum5C7b4nzg.jpeg" /><figcaption>Login Screen Lo-fi</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*G0uk-MQ2wX8qP56eCgzCRw.jpeg" /><figcaption>Landing Page Lo-Fi</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*IaVsLMoK0I7EJE_hOMeKkg.jpeg" /><figcaption>Setup Screen Lo-Fi</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*Xo5RNuRwHuUflZsSjQdjtg.jpeg" /><figcaption>Menu Page Lo-Fi</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*OmKc8qlcUo3OxIgsWzyLpw.jpeg" /><figcaption>Confirmation Page Lo-Fi</figcaption></figure><p>If this were a full length project, the next step would be to transition the prototype from low fidelity to mid fidelity. However, given the time constraints (2 weeks), I decided to expedite the process by doing a quick mid-fidelity prototype to use solely for testing color schemes. I changed my low-fidelity ideas to digital screens the best I could using Sketch.</p><p>I knew that the color scheme I selected would be an important aspect of not only my hi-fi prototype, but also my application as a whole, so I wanted to spend more time on it. I did research on food service marketing, and I found that the colors red and orange are frequently used in the industry because they have been found to elicit hunger, so I decided to do my testing based on two separate color schemes (one red and one orange). Another important aspect was the typeface I was going to use. For this, I relied on my core brand attribute of casual by picking the font Noteworthy light.</p><p>After testing, I landed on selecting the orange color scheme. At this point in the process, I could see the light at the end of the tunnel. The app was coming together, and all I had to do was lay the finishing touches on it. I did some more testing with the high-fidelity prototype, and I decided to add a few more intermittent screens, and change a few design attributes based on the feedback I had received.</p><p>The last step of the process was to insert the animations using Principle, so that I could have a fully functioning prototype ready for presentation.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FOCS5LYv_iXc%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DOCS5LYv_iXc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FOCS5LYv_iXc%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/38905059e54f01e40cd75e7f2cae0814/href">https://medium.com/media/38905059e54f01e40cd75e7f2cae0814/href</a></iframe><p>This project taught me that the key to app design is to trust in the design thinking process. Going straight from an idea to an app seems quite daunting at first, but being able to separate it into defined steps is the true key to completion. I still have much to learn about the process, and I look forward to designing and curating more user experiences to come.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c6f4ab3d930" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[First Week]]></title>
            <link>https://medium.com/@jgamble482/first-week-17a8b80edfb1?source=rss-6611e416082b------2</link>
            <guid isPermaLink="false">https://medium.com/p/17a8b80edfb1</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[digital-product]]></category>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[ironhack]]></category>
            <dc:creator><![CDATA[Jordan Gamble]]></dc:creator>
            <pubDate>Fri, 19 Jul 2019 11:00:38 GMT</pubDate>
            <atom:updated>2019-07-19T11:00:38.537Z</atom:updated>
            <content:encoded><![CDATA[<p>On June 3, 2019, I began the first week of Ironhack&#39;s UX/UI design bootcamp in Berlin. I did not know what to expect, but I was definitely excited to embark on a journey to learn a new skill and hopefully ignite my career as a UX/UI designer.</p><h3>The Task</h3><p>For our first project, me and three other members of my cohort were tasked with designing a service that would strengthen the connection between consumers and local, seasonal produce. The project was UX focused, so the main goal was not a high-fidelity prototype. However, it did provide me with a good introduction to the design-thinking process.</p><h3>Research</h3><p>One thing that really stood out to me was the importance of user research. For this particular project, we created a Google Form for quantitative data, and we conducted in-person interviews in our area for qualitative data. The research we conducted provided us insights into how our target user would interact with the product we were designing. We discovered key details about the shopping habits of potential users. For example, we inquired about how often they shop and their preferences in type and origin of the produce that they purchase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ycmP-vmCn2J0JGgD" /><figcaption>Example of some data from our survey</figcaption></figure><h3>Defining the Problem</h3><p>Next, we had to categorize all of the information from our research in order to refine our idea of the problem that we had to solve. We achieved this primarily through an affinity diagram, in which we specified and categorized the information received from users. In my opinion, it helped to visualize all of the &quot;raw data&quot; we gained from users via this sticky-note method (pictured below). The ability to easily organize user input into product attributes made it easier to imagine the product structure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NkBsLbLmFi7p6Rxy" /><figcaption>Affinity Diagram</figcaption></figure><h3>Deeper Empathy</h3><p>In order to empathize with our potential users even further, we created primary and secondary user personas who represented both our target customer and peripheral customer respectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*S_-LRLwBI9SMioa8" /><figcaption>Primary User Persona</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*P_F3ZesvAX2Q88fU" /><figcaption>Secondary User Persona</figcaption></figure><p>Creating theoretical users allowed us to pinpoint frustrations customers have with their current method of grocery-shopping. At this point in the process, I felt like we had a very good grasp on the potential for our product to meet the needs of potential users.</p><p>From the user personas, we created a theoretical daily schedule that we called a user journey, in which we were able to identify the times in the day where our product could be implemented for our users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nfTk3K4z7kod9awU" /><figcaption>User Journey for primary user persona</figcaption></figure><p>This was the last point of specificity that we needed in order to define our problem specifically and to create a hypothesis to solve this problem. After two days of empathizing we came up with this hypothesis:</p><blockquote>We believe that <strong>delivering genuine regional produce</strong> for <strong>conscious consumers</strong> will achieve a <strong>new, convenient, time-efficient shopping experience</strong>. We will know we are right when <strong>first-time users become loyal, regular consumers</strong></blockquote><h3>Ideation</h3><p>From this hypothesis, we used different ideation exercises like round robin and crazy eight to come up with specific features to have in the application. We voted on the best ideas and refined them even further.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-jxxtb2JYQAgocPn" /><figcaption>Idea for produce pickup</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RktSzUyW41-sB9p1" /><figcaption>Idea for promotional deals</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*23B6S6NMLyBLMSuE" /><figcaption>Idea for visual data-tracking</figcaption></figure><p>Finally, we contextualized the ideas into some low-fidelity screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yHeyfWjsQ0Tvigin" /><figcaption>Low fidelity screens</figcaption></figure><p>The next steps of the project would be to develop the low-fi screens into a testable prototype in order to refine the product through reiteration. In a real company context, the product will develop into a high-fidelity prototype for more testing.</p><p>This first project showed me the amount of thought that goes into designing a digital product. It also showed me how assumptions have no value in user research. The more insight that can be gained from potential users, the better the product will become.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17a8b80edfb1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[USC Website Case Study]]></title>
            <link>https://medium.com/@jgamble482/usc-website-case-study-26d677d198bf?source=rss-6611e416082b------2</link>
            <guid isPermaLink="false">https://medium.com/p/26d677d198bf</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Jordan Gamble]]></dc:creator>
            <pubDate>Mon, 03 Jun 2019 06:17:50 GMT</pubDate>
            <atom:updated>2019-06-03T06:17:50.438Z</atom:updated>
            <content:encoded><![CDATA[<p>The University of Southern California is an accredited university located in central Los Angeles. The university offers of variety of both graduate and undergraduate programs in various fields. I was tasked with locating three things from the university website:</p><ol><li>The school mascot</li><li>If the school offers arabic as a foreign language</li><li>The nearest airport to the school</li></ol><p>I was able to find all three of these things but it took me over 4 clicks to find the school mascot, 5 clicks to see if the school offered Arabic as a foreign language, and 4 clicks to see where the nearest airport to the school was.</p><p>When I had other users test the site they were able to find the same attributes generally in +/- 1 click from my tests of the site. The largest paint point I recognized was that the website sends you to a different sub-site just to investigate the majors offered, and then you have to navigate through different drop-down menus to see which specific major you are looking for. Therefore, I began prototyping a solution for finding majors in an easier fashion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/242/1*_j-TpJXb3hKgcFJJlufHSA.jpeg" /></figure><p>I proposed a solution where clicking on the academics tab would result in pulling up an academics page native to the site in which majors and minors were shown in alphabetical order. From this page, links could be implemented to further access separate sub-sites specific to each major.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26d677d198bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wireframing Challenge]]></title>
            <link>https://medium.com/@jgamble482/wireframing-challenge-ee73685e8caa?source=rss-6611e416082b------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee73685e8caa</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jordan Gamble]]></dc:creator>
            <pubDate>Mon, 03 Jun 2019 05:49:14 GMT</pubDate>
            <atom:updated>2019-06-03T05:49:14.917Z</atom:updated>
            <content:encoded><![CDATA[<p>I enjoyed making wireframes with the sketch platform because I was able to communicate my ideas quickly. I personally preferred it over paper wireframes because of the standardization of the elements in the wireframing kit. I also liked forming a new prototype with invision. It allowed me to see just how fast you could actualize an idea in order to apply it to testing.</p><p>Invision prototype of EMOV app: <a href="https://invis.io/WKSBAT0DS28">https://invis.io/WKSBAT0DS28</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee73685e8caa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sketch Visual Design Exercise]]></title>
            <link>https://medium.com/@jgamble482/sketch-visual-design-exercise-d79187db1828?source=rss-6611e416082b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d79187db1828</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[sketch]]></category>
            <dc:creator><![CDATA[Jordan Gamble]]></dc:creator>
            <pubDate>Sun, 02 Jun 2019 01:25:17 GMT</pubDate>
            <atom:updated>2019-06-02T01:25:17.086Z</atom:updated>
            <content:encoded><![CDATA[<p>This particular exercise was interesting for me because the more time I spent on it, the more comfortable I became using sketch (which I imagine was the point). There were many times where I would redo elements on the screens even if they were &quot;passable&quot; in order to either make them sharper or to learn how to make them in a more efficient manner. This exercise also highlighted the sketch skills that I need to work on the most like creating new shapes through editing corners or efficiently manipulating small objects. I also realize that I need to work on my efficiency and speed using sketch, but I know that will come with practice and repetition, which I look forward to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H3N0V2IXLhtP5emu6o3NhQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d79187db1828" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sketch Exercise Kata]]></title>
            <link>https://medium.com/@jgamble482/sketch-exercise-kata-cbed426516ea?source=rss-6611e416082b------2</link>
            <guid isPermaLink="false">https://medium.com/p/cbed426516ea</guid>
            <category><![CDATA[sketch]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jordan Gamble]]></dc:creator>
            <pubDate>Tue, 28 May 2019 14:48:38 GMT</pubDate>
            <atom:updated>2019-05-28T14:48:38.990Z</atom:updated>
            <content:encoded><![CDATA[<p>This was my first time using a design tool like sketch, and my first impressions are widely positive. I had previously always been intimidated by programs like sketch due to the vast capability of the program. However, when I started using it, I discovered that it is pretty intuitive to use, and many of the operations are similar to other pc-based productivity programs. I see that having an easy-to-use interface like sketch is what allows designers to focus on making good designs rather than a taxing UI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/89/1*ROtbOtT2v2z9jAAUdXJkhA.png" /><figcaption>Ready for Liftoff</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cbed426516ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jordan Gamble_Design Thinking Exercise]]></title>
            <link>https://medium.com/@jgamble482/jordan-gamble-design-thinking-exercise-d7ef527af4d5?source=rss-6611e416082b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7ef527af4d5</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[payments]]></category>
            <dc:creator><![CDATA[Jordan Gamble]]></dc:creator>
            <pubDate>Sat, 25 May 2019 18:11:38 GMT</pubDate>
            <atom:updated>2019-05-25T18:11:38.109Z</atom:updated>
            <content:encoded><![CDATA[<p>Whole Bank is a company aiming to cash in on the digital currency/exchange market. They offer money management and saving services, and they are attempting to develop a feature native to their mobile application that can replace using credit cards overseas. When interviewing users about this topic I found two major problems with the current credit card system:</p><ol><li><strong><em>Reliability:</em></strong> I heard multiple situations where users were not able to use their card when they wanted to. Some involved a card that was physically broken (unreadable mag strip/chip), and others involved the banks not being able to register the user being overseas. Either way, I gathered that Whole Bank’s service was going to have to be reliable in order to compete with existing credit/debit cards.</li><li><strong><em>Convenience: </em></strong>When I asked about what the characteristics of an ideal product in this sector would be, multiple people described convenience as an ideal feature. Users don’t want to think about the product that much. They just want it to work quickly and effectively when they need it.</li></ol><p>Therefore, I surmised the main problem I was trying to resolve was the stress and inconvenience involved with using your credit card abroad. Also, this feature would have to be able to compete with related services already on the market like ApplePay, Samsung Pay, Google Wallet, and Venmo.</p><p>In order to maximize the convenience aspect of this payment feature, I wanted it to be accessible from the lock screen of any smartphone. Therefore, it could compete in convenience with the NFC-based services that can be accessed by simply pressing a button. However, I didn’t want the Whole Bank service to be constantly on the lock screen, so imagined that it would only appear when the user’s phone entered a specific geofence of a merchant that accepted this type of payment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LP5x-o3qZ8sktThzqdjerw.jpeg" /></figure><p>My takeaways from this project mainly came from the user interview phase. I did not expect to have multiple people in a such a small sample size to have similar negative experiences with credit cards abroad. This phenomenon highlights the opportunity for a feature with a superior design to enter the market. It also demonstrated to me how important user input and feedback is when developing a product. The user can provide directions and structure in order to design the best product possible.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7ef527af4d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Visual Note-taking]]></title>
            <link>https://medium.com/@jgamble482/visual-note-taking-6e1d40d86394?source=rss-6611e416082b------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e1d40d86394</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jordan Gamble]]></dc:creator>
            <pubDate>Mon, 20 May 2019 22:19:04 GMT</pubDate>
            <atom:updated>2019-05-20T22:19:04.583Z</atom:updated>
            <content:encoded><![CDATA[<p>To be honest, the process felt awkward at first because I am so used to taking notes strictly using words, so my first iteration of the sketch notes came out a little discombobulated. However, on my second try, I was able to see how I could connect different visual elements that I added to the page in order to create a more cohesive, holistic interpretation of the subject matter. I believe that with a bit more practice, I will be able to sharpen this tool in the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qReTGUFrCryyrcdkgH094Q.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e1d40d86394" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>