<?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 Jason Poland on Medium]]></title>
        <description><![CDATA[Stories by Jason Poland on Medium]]></description>
        <link>https://medium.com/@GimmeYerGold?source=rss-7a669a44650a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*x9sHM7NBTj5F412f.png</url>
            <title>Stories by Jason Poland on Medium</title>
            <link>https://medium.com/@GimmeYerGold?source=rss-7a669a44650a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 07:54:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@GimmeYerGold/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[Baby’s First Weather App]]></title>
            <link>https://medium.com/@GimmeYerGold/baby-s-first-weather-app-c6dce8791aca?source=rss-7a669a44650a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6dce8791aca</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Jason Poland]]></dc:creator>
            <pubDate>Thu, 31 Mar 2016 03:30:05 GMT</pubDate>
            <atom:updated>2016-03-31T03:30:05.059Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/953/1*KDSn3UknrlgPKe4Xo6aIyg.png" /></figure><p>While my <a href="https://medium.com/@GimmeYerGold/the-amazing-rijksmuseum-api-ac0297d81e72#.l6u8d2rvh">previous app</a> dealt with making JSON requests from a museum API, this next project focused on making requests to a live and ever-updating Weather API found at <a href="https://developer.forecast.io/">The Dark Skies Weather API.</a></p><p>I liked working with this API — the documentation was straight forward, and the app was simple and useful enough that it would be something I could see myself using on a regular basis.</p><p>Although, I felt like anything I could come up with would pale in comparison to <a href="http://dogeweather.com/">dogeweather.com</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*QhiiKA8S4-7FTy61stKQ-g.png" /><figcaption>Genius.</figcaption></figure><p>What’s cool about dogeweather is that it’s a github project! I can go and see the code firsthand. Perhaps this was made as a code school project just like my own.</p><p>The end goal of our own weather app project was to have multiple views, one for current, one for daily, and one for hourly. This was to be accomplished with Backbone routing, which is a powerful tool. You can send a link of the url, and the hash will render the same results each time.</p><p>MAGIC.</p><p>However, my first attempt is not perfect — there are some snags on rendering the default view. I want to go back and implement new frameworks into the weather app because I feel it would be a good portfolio project to showcase. Also, I had planned to theme the app to make it snazzier. I will post an update when that’s ready!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6dce8791aca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[There’s Text Adventure Game Hiding in my Terminal!]]></title>
            <link>https://medium.com/@GimmeYerGold/there-s-text-adventure-game-hiding-in-my-terminal-17e6c4615631?source=rss-7a669a44650a------2</link>
            <guid isPermaLink="false">https://medium.com/p/17e6c4615631</guid>
            <category><![CDATA[games]]></category>
            <category><![CDATA[terminal]]></category>
            <category><![CDATA[adventure]]></category>
            <dc:creator><![CDATA[Jason Poland]]></dc:creator>
            <pubDate>Wed, 30 Mar 2016 12:14:28 GMT</pubDate>
            <atom:updated>2016-03-30T12:14:28.253Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E0ykGi0NbyxjImV4jau4IQ.png" /><figcaption>This takes me back.</figcaption></figure><p>While researching my last post, I was making the logical leap from javascript objects to text-based adventure games, and lo and behold, I discovered a command that unlocks a text game built into the mac terminal!</p><p>It’s a secret to everybody! Here, give it a try:</p><p><strong>emacs -batch -l dunnet</strong></p><p>My first computer was an Apple II GS, which we purchased from a neighbor, and it came with a copy of ZORK. I think I was reading the Hobbit at the time, and I was instantly sucked into this interactive narrative. The game was difficult, but that made it even more captivating.</p><p>Text adventures have maintained a healthy following even after the graphical capacity of computer games eclipsed this era of text-only gaming. There’s a great documentary on text games called <a href="http://www.getlamp.com/">Get Lamp</a>, that’s enjoyable not only as a love letter to these “forgotten” games, but as a historical survey in computer gaming, the hobby community, and the industry as a whole.</p><p>I think I’ll keep this text game open in its own terminal so I can check it out during my breaks. I’d like to make my own short text game — it’ll be great way to test the skills that I’ve learned so far.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17e6c4615631" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Constructor Junction, What’s Your Function?]]></title>
            <link>https://medium.com/@GimmeYerGold/constructor-junction-what-s-your-function-8124b6e888cb?source=rss-7a669a44650a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8124b6e888cb</guid>
            <category><![CDATA[abstract]]></category>
            <category><![CDATA[es6]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Jason Poland]]></dc:creator>
            <pubDate>Wed, 30 Mar 2016 12:03:17 GMT</pubDate>
            <atom:updated>2016-03-30T12:03:17.363Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IVi6eDH0-3paGiDNuahGuw.png" /><figcaption>I gotta ASCII a question</figcaption></figure><p>We’re pretty deep in Javascriptland at the moment — thinking in the abstract is key since we’re not producing visual results like we were during our more CSS and HTML intensive times, other than console logs. Something about constructors really hits home with me in that respect though. We are making objects! I can’t help but think of text-based games when working like this.</p><p>I imagine an object constructor could be used to create an inventory system for an adventure game. The constructor has the “default” values for each item, like weight and size, and then when the new instance of the object is called, unique parameters are set, like name and descriptions.</p><p>Whether it’s thinking of game applications for constructors, or just the way they work, something about them is “fun” to me. Having declared a constructor and then later invoking it and applying custom parameters onto it seems playful and intuitive.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8124b6e888cb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Amazing Rijksmuseum API]]></title>
            <link>https://medium.com/@GimmeYerGold/the-amazing-rijksmuseum-api-ac0297d81e72?source=rss-7a669a44650a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac0297d81e72</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[museums]]></category>
            <category><![CDATA[art]]></category>
            <dc:creator><![CDATA[Jason Poland]]></dc:creator>
            <pubDate>Wed, 30 Mar 2016 03:04:37 GMT</pubDate>
            <atom:updated>2016-03-30T11:20:18.113Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*FMBuJFoDtAJHjVsWi3zZ1Q.png" /></figure><p>There are some great APIs out, and when I started looking for more — I soon found the <a href="https://www.rijksmuseum.nl/en/api">Rijksmuseum API</a>. This is what I like to see!</p><p>It seems to be the norm rather than the exception that fine art and academia lag behind when tech is involved. This API is so robust! You can even search images by prominent color. So much work went into this!</p><p>People who truly *love* art, and want to help other people *love* art made this. Even without diving into the JSON data, you can utilize a user-friendly framework that exploits all that data. You can sort and favorite over 250,000 exhibit pieces from the archives.</p><p>Accessing the API gives you access to all that data, and all the ways to parse that data by year, medium, artist, and more and more and more. Getting a key is easy. and the documentation is pretty straightforward.</p><p>I’ve barely scratched the surface, but I put together a small app that takes a dip in the water. You can search a sample of images from the API, and generate a scroll of images with descriptions of the work.</p><p>You can check it out here: <a href="http://gimmeyergold.github.io/rijksfeed/">http://gimmeyergold.github.io/rijksfeed/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac0297d81e72" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[API Data Finds a Way...]]></title>
            <link>https://medium.com/@GimmeYerGold/api-data-finds-a-way-cfd3a717c700?source=rss-7a669a44650a------2</link>
            <guid isPermaLink="false">https://medium.com/p/cfd3a717c700</guid>
            <category><![CDATA[open-data]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Jason Poland]]></dc:creator>
            <pubDate>Wed, 30 Mar 2016 02:55:04 GMT</pubDate>
            <atom:updated>2016-03-30T02:55:04.110Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*gViBSV6vqIRDrOP6iS5iEQ.jpeg" /></figure><p>My first introduction to API and JSON requests left me thinking about all the possibilities a developer has when working with all this data—this is what I feel makes open source development so exciting! All that data can be requested and parsed out onto a webpage, making it come alive.</p><p>If HTML is the skeleton, CSS is the skin, and Javascript the muscles that make it all move, API data is the blood that flows through it all, giving it life.</p><p>Some API documentation is more difficult to work with than others, however, depending on the data, my threshold for frustration goes further.</p><p>We began our first API project with generating our github profile pages. This was pretty dry data, but what made it difficult was the cap that github has in place for unauthorized requests to their API — the best solution would be A) look into accessing my api key without displaying it in the code (which would result in the api key being revoked, or B) learn a more better workflow that doesn’t require refreshing the page so often to confirm my page is rendering correctly.</p><p>After several hours of working on the project, and two API requests for the repo API endpoint and the user profile API every 5 minutes or so, I soon exceeded my cap, and was blocked for the next hour.</p><p>Even after pushing the completed project the github, the cap was still in place. I was ready to work with less “dry” data, and with less restrictions.</p><p>I understand the restrictions — there is sensitive data on github, and the API can be exploited. It’s a double-edged sword allowing an API to be public, so I understand the restrictions.</p><p>On one hand, API data is necessary, and needful. Static spreadsheets of dead data are the dinosaurs of our age. However, bringing that data to life comes at a price, and it’s the job of the API developers to balance usefulness with mindfulness.</p><p>Sometimes what you *can* do with API data isn’t necessarily what you *should* do with it. If you know, if you aren’t evil and stuff.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cfd3a717c700" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Set Interval and Hexadecimal Colors]]></title>
            <link>https://medium.com/@GimmeYerGold/set-interval-and-hexadecimal-colors-f1911e307a16?source=rss-7a669a44650a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f1911e307a16</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[time]]></category>
            <category><![CDATA[css]]></category>
            <dc:creator><![CDATA[Jason Poland]]></dc:creator>
            <pubDate>Wed, 30 Mar 2016 02:07:12 GMT</pubDate>
            <atom:updated>2016-03-30T14:29:05.793Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*7ZP28Uw1VxnmuSyrbXRz5A.gif" /></figure><p>We were tasked with creating a “ticking” clock that displayed a hexadecimal color generated from the current time. This was a fun project that combined new javascript material, as well has a chance to flex my newfound CSS muscles.</p><p>Date methods like getHours() and slice() returned a human-readable time, while toString() converted the numbers into a value that could be read as a hexadecimal color, with a hash included of course. A hover pseudo selector displayed the current hex color. I also employed an overlay div that gave the background a nice gradient.</p><p>Check it out here on my github: <a href="http://gimmeyergold.github.io/color-clock/">http://gimmeyergold.github.io/color-clock/</a></p><p>One of the challenges I ran into with this project was the progressively generating time bar beneath the current time. It is meant to increase at each second, and then reset at second zero, then increase again. I used a trick here: rather than think of the bar literally filling 100% of its div at the 60 second mark, I made the div larger than, and the 1:1 ratio of seconds to percentage of div filled only reaches 60%, but has the appearance of “fullness.” Looking back on this, I would have created a simple formal that translated 1/60 to 1/100, and keep the div at a width no larger than the current time.</p><p>I could see how some would argue this fix was “cheating,” and that finding the best solution would of course take more time (and exercise more skills in the process), however, others (like myself at the time!) might think it a clever fix in fact, and a nice solution on a short deadline, rather than hitting a brick wall too soon looking for the “most right” answer, and having an incomplete project.</p><p>I’m still learning, so this is the best time to examine both sides.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1911e307a16" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Event Loops are Your Friend]]></title>
            <link>https://medium.com/@GimmeYerGold/event-loops-are-your-friend-85dc5495fdd4?source=rss-7a669a44650a------2</link>
            <guid isPermaLink="false">https://medium.com/p/85dc5495fdd4</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Jason Poland]]></dc:creator>
            <pubDate>Mon, 22 Feb 2016 00:41:26 GMT</pubDate>
            <atom:updated>2016-02-22T00:41:26.555Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/859/1*cFs9TUWCN1O4ED62OPgn5Q.png" /><figcaption>Philip Robert’s insightful explanation of Event Loops on youtube: <a href="https://www.youtube.com/watch?v=8aGhZQkoFbQ">https://www.youtube.com/watch?v=8aGhZQkoFbQ</a></figcaption></figure><p>I have never heard of Event Loops before this video. That makes sense since I’m just starting out in code, but I imagine that ELs are a black box to even intermediate coders, because you don’t really have to know how they do what they do to take advantage of their functionality, but it certainly helps!</p><p>Instead of working in a straight call stack, one task after another, you can ease up lag time between time-consuming functions by exploiting run timers, and pushing those tasks out of the stack and on to the webapi, where they will be count down until they are pushed to the EL. Here, they will wait until the stack is cleared, then they will be run.</p><p>I had to watch the video twice to understand it better, but for me, thinking of the stack, the webapi and the EL, reminded me of the way we structure our HTML, CSS, and javascript in the DOM. Javascript is kept at the bottom of the html, and saved for last, so that the html can be painted, and styled by CSS. This makes sense because the structural and visual elements are modified by JS, so putting JS first would slow everything down.</p><p>Following this analogy, functions and calls that require a wait time should be earmarked with run time, and pushed into a queue so that less arduous tasks can be addressed in the meantime while they process.</p><p>I’ve yet to utilize run time in any real world situations, but I can see conceptually how it will make things much more efficient for both the coder and the user.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85dc5495fdd4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Handle Big Code Problems: Break em’ Down into Little Cubes!]]></title>
            <link>https://medium.com/@GimmeYerGold/how-to-handle-big-code-problems-break-em-down-into-little-cubes-aabed961b594?source=rss-7a669a44650a------2</link>
            <guid isPermaLink="false">https://medium.com/p/aabed961b594</guid>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Jason Poland]]></dc:creator>
            <pubDate>Tue, 16 Feb 2016 02:28:53 GMT</pubDate>
            <atom:updated>2016-02-16T02:28:53.676Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/660/1*2QKcn4vK-s2ojgZmUcTqmw.png" /><figcaption>Picasso breaking down all his problems into little cubes! Comic by Michael Kupperman</figcaption></figure><p>One of the hardest things about learning and executing code (and I expect it will continue to be a problem long after my introductory phase!), is knowing where exactly to begin when faced with a Big Daunting Problem.</p><p>Often times, I reach further than my grasp, and begin coding right away, not knowing exactly where I’m heading, but under the assumption that making any code at all is better than making none at all. This leads to a lot of wasted time, and strained eyes staring at a computer screen.</p><p>This Michael Kupperman comic about Picasso busting down his problems into little cubes is silly and somewhat non-sequitur, but I really enjoy it for a number of reasons. No matter the trouble that plagues Picasso, his approach is the same: break them down into little cubes! As a cubist, he understands cubes, they’re something he works with everyday!</p><p>For a beginning coder, it’s easy to think that there’s a magic code that will make short work of a bigger problem, but the magic happens when we put in the work to break down the problem first — into little cubes. Instead of approaching the end goal of a function, for instance, it’s best to think of what can be done step by step, with what we know already, then build from there. There are plenty of functions and methods that have special uses, and can make short work of a code problem, but it seems like good practice to build with a few simple cubes of the introductory syntax before me try to utilize the fancy Rubik’s cube. Little cubes can be experimented with, and examined with a curious eye. Also, “little cubes” is a better way to think about good code. Good code can be interchangeable, and is not reliant on tight coupling. And who knows, the little cube solution from one problem might be applicable later in another problem.</p><p>The next thing I relate to in this comic is Picasso’s “cool-down” phase with his cartoon duck. He’s still thinking about cubes, of course, but for the moment, he’s stepped away from the confrontations. Coding is exhaustive work, and even when we are making progress it’s hard to see the end. It’s too easy to get burned out and be hard on yourself, especially during the early learning phases. A little distance can help get perspective on a tough code problem. Right now, I’m dreaming in code, and thinking in code, it’s always on my mind. Being too zoomed can literally make the problem seem too big.</p><p>The next time you see a big code problem, walk right up to it and say, “I’m gonna break you down into little cubes!”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aabed961b594" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learnin’ CSS Layout]]></title>
            <link>https://medium.com/@GimmeYerGold/learnin-css-layout-d6ead621bbcf?source=rss-7a669a44650a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6ead621bbcf</guid>
            <category><![CDATA[layout]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Jason Poland]]></dc:creator>
            <pubDate>Wed, 03 Feb 2016 03:27:02 GMT</pubDate>
            <atom:updated>2016-02-03T03:27:02.394Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c3Jjrnunm89KjbDrFPbX4A.png" /><figcaption>Codepen helped immensely with this early endeavor.</figcaption></figure><p>I dived in headfirst to a HTML/CSS project today, and while I completed it, I realized there were probably some CSS “better practices” I could have exercised.</p><p><a href="http://learnlayout.com/">Learn CSS Layout</a> had some tips for demystifying some of the ways CSS can optimize your webpages. Here are 15 things I learned:</p><ol><li>There are always default borders, margins, and padding in place that must be considered and must be overwritten with custom code.</li><li>Max-width is a more responsive way to negotiate the layout of a page, because it responds to the changes in screen size on mobile devices.</li><li>Despite the term, “static” positioning is the default for elements.</li><li>Absolute and relative positions can be used in combination to “nest” certain elements together, rather than fixing each element individually.</li><li>“em” is a unit of measurement relative to the current font size. For example, 1em is the same size, 2em is twice the size, etc.</li><li>Float can be used to wrap text around an image.</li><li>However, float can be troublesome to use, and should be used conservatively.</li><li>Percentage is a means of establishing layout that is more responsive to changing screen sizes, and can quicker sometimes, too.</li><li>Sites should be designed with mobile and iOS platforms considered first, because often times elements that look okay on the desktop can look not so okay elsewhere.</li><li>“@ media screen and” is a way to establish rules for how a layout should respond when viewed on a mobile device.</li><li>inline-block is a preferred method to float for aligning elements that would normally dominate an entire line on the page.</li><li>Many of the more robust CSS features that create column are not supported in all browsers.</li><li>Flexbox is just that —a flexible way to create layouts with less fuss. It’s something I need to look into more.</li><li>auto margin is a useful tool, but a max-width must be declared.</li><li>CSS Frameworks are another thing I’d like to look into, however I’ve been warned they’re no substitute for knowing good CSS!</li></ol><p>My classmate Josh remarked that a good programmer could be called a “lazy programmer,” because why do the extra work to style a page when there is a more efficient and smarter way to complete the task?</p><p>While this certainly isn’t an exhaustive list of what there is to learn about CSS, it’s a great start, and has piqued my CSS QUEST FOR KNOWLEDGE.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6ead621bbcf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[First Day of Class]]></title>
            <link>https://medium.com/@GimmeYerGold/first-day-of-class-c6201cacf40c?source=rss-7a669a44650a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6201cacf40c</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[houston]]></category>
            <category><![CDATA[iron-yard]]></category>
            <dc:creator><![CDATA[Jason Poland]]></dc:creator>
            <pubDate>Mon, 01 Feb 2016 22:56:46 GMT</pubDate>
            <atom:updated>2016-02-01T22:56:46.471Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/659/1*ncLJYF8vNVB5eiLZPyXGoA.png" /><figcaption>Here is my first script, which generates a series of folders and files for a blank HTML project.</figcaption></figure><p>I’m very happy to be learning again, and especially learning code. Each day of class at the Iron Yard was divided between a lecture period and a lab period, where we worked on the homework assignment. In between we took a break for lunch, and I talked with some of my classmates and the TAs. It’s fantastic to realize all of the different backgrounds we all arrived from. Each day I plan to chat with a new person, and get to know as many classmates as possible. Making better connections with people is a goal of mine, apart from learning the code.</p><p>To begin, we installed an ultimate installer package that gave us the necessary resources for class, as well as some optimizing software. I’m always looking for ways to optimize battery life, and storage capacity. Learning how to get the most out of my machine is something that interests me.</p><p>Today we learned the basics of terminal navigation, and commands, and some basic HTML. In our two take-away assignments, I found the terminal scriptwriting assignment more difficult, because it required abstract logic thinking — it was not immediately present in visuals what was going on. I got better at using the terminal, and made myself use it in favor of looking up my results in the finder.</p><p>I plan to upload the code for my assignments to my github, just to get used to that platform.</p><p>Overall, I feel that front end engineering is what I’m predisposed to. The instant gratification of seeing code turn into content, however it would be cool to develop my skills to pick up more back end skills.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6201cacf40c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>