<?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 Jared Powers on Medium]]></title>
        <description><![CDATA[Stories by Jared Powers on Medium]]></description>
        <link>https://medium.com/@jarpow44?source=rss-5d63935aa8e0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*9jvU81tNtKcpMSKcRjqrTg.jpeg</url>
            <title>Stories by Jared Powers on Medium</title>
            <link>https://medium.com/@jarpow44?source=rss-5d63935aa8e0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:23:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jarpow44/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[Ruby on Rails]]></title>
            <link>https://medium.com/@jarpow44/ruby-on-rails-8e02dc3ae010?source=rss-5d63935aa8e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e02dc3ae010</guid>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Jared Powers]]></dc:creator>
            <pubDate>Fri, 03 Jun 2016 21:51:58 GMT</pubDate>
            <atom:updated>2016-06-03T21:51:58.776Z</atom:updated>
            <content:encoded><![CDATA[<p>I am going to do my best to give you a concise explanation of the fundamentals of Rails and how they ease our processes as a programmer.</p><p>Rails is a web app development framework written in the language of Ruby. Rails is designed to let you do more for less. With just a few lines of code, a novice programmer can put together something pretty awesome. Pair this with a basic understanding of HTML and CSS/Sass and you have a full stack web app in a matter of hours. The age (20) year old philosophies of Rails still ring true today and allow it to remain a strong resource for web developers to have clearly written, precise code. A few of these philosophies are “Don’t Repeat Yourself”. This falls under the umbrella of abstraction. If you find yourself typing the same 2 or 3 lines of code over and over again, you can throw it in to a method and call it whenever you would like. REST is a pattern for Rails applications and RESTful applications are streamlined to zip like a bullet train through the server. Rails is a complicated language when you first look in to it, but once you start learning the little quirks, it becomes quite simple to write, now I just have to get to where I can write it well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e02dc3ae010" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Form helpers in Rails]]></title>
            <link>https://medium.com/@jarpow44/form-helpers-in-rails-2d07cab7968e?source=rss-5d63935aa8e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d07cab7968e</guid>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Jared Powers]]></dc:creator>
            <pubDate>Fri, 03 Jun 2016 21:45:19 GMT</pubDate>
            <atom:updated>2016-06-03T21:45:19.260Z</atom:updated>
            <content:encoded><![CDATA[<p>Forms are all around us in every walk of life. In some ‘form’ or another, you have probably filled out hundreds of forms in your life without even hardly thinking twice about it. In rails, we have form helpers because we are information hoarders. These form helpers allow us to create forms with different aspects spawning from a “GET” request, labelling what you are to put in the field, the text entry field, and a submit button to “POST” the information to the server. These forms can be made and then reused throughout the application with relative ease.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d07cab7968e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DOM manipulation and jQuery Event Handling]]></title>
            <link>https://medium.com/@jarpow44/dom-manipulation-and-jquery-event-handling-4659448c3528?source=rss-5d63935aa8e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/4659448c3528</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Jared Powers]]></dc:creator>
            <pubDate>Fri, 03 Jun 2016 20:59:12 GMT</pubDate>
            <atom:updated>2016-06-03T20:59:12.743Z</atom:updated>
            <content:encoded><![CDATA[<p>The Dom, or Document Object Model works across platforms and allows us to interact with XML, XHTML, and HTML documents. There is a tree, called the DOM Tree, allowing objects to be pointed to and changed through method use on the objects. A basic understanding of the way the DOM works is important to understanding jQuery and Event Handling.</p><p>jQuery is a JavaScript library allowing interaction with the DOM independently and efficiently. The definition of an event is created by the user him or her self. Think about the things you do when you are browsing the web, hovering, clicking, submitting your information, typing, scrolling, and highlighting. All of these actions are called events, and we can engage actions based on these actions. These functions are known as Event Handlers.</p><p>Try.jQuery.com provides a useful resource for understanding how these properties and actions work together. There are short videos relating to different topics with exercises for reinforcement. I have always enjoyed the gamification of a certain topic. Putting something into competitive or fun terms is an excellent way to learn and learn well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4659448c3528" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JavaScript and… the… FUUUUTURE!]]></title>
            <link>https://medium.com/@jarpow44/javascript-and-the-fuuuuture-e606ce1e600e?source=rss-5d63935aa8e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/e606ce1e600e</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Jared Powers]]></dc:creator>
            <pubDate>Fri, 03 Jun 2016 20:49:49 GMT</pubDate>
            <atom:updated>2016-06-03T20:49:49.463Z</atom:updated>
            <content:encoded><![CDATA[<p>JavaScript was developed in the mid 90’s as a solution to a common problem without really intending for it to withstand the test of time. Now, 20 years later, here we are. JavaScript has a tight grip on the industry and is really trying hard to maintain that stonghold without eventrying at all. The future of programming is an ever changing definition of “ease”. What is easy for one person may rock the world of another. There will be a point where we no longer NEED to use javascript in development, but I think it will continue to be around in some capacity or another until a revolution in the way we program. (The machines are coming)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e606ce1e600e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JavaScript and Event Loops]]></title>
            <link>https://medium.com/@jarpow44/javascript-and-event-loops-7ff9ca7ee718?source=rss-5d63935aa8e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ff9ca7ee718</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Jared Powers]]></dc:creator>
            <pubDate>Fri, 03 Jun 2016 20:44:11 GMT</pubDate>
            <atom:updated>2016-06-03T20:44:11.052Z</atom:updated>
            <content:encoded><![CDATA[<p>JavaScript, as noted in other posts, is hard. It handles one operation at a time, and then moves on to do something else. This can bog down or speed up your runtime respectively. The code from the server must be clean and precise for JavaScript to operate the way it is designed to do. We can get around this single operation behavior with event loops. Removing the caller from the response lets the runtime operate in conjunction with other operations. A program built around this system of call-backs allows the runtime to run though different operations while waiting for input from the network. This is highly useful in user experience programming.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ff9ca7ee718" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[To JavaScript from Ruby]]></title>
            <link>https://medium.com/@jarpow44/to-javascript-from-ruby-8fb576379e38?source=rss-5d63935aa8e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/8fb576379e38</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Jared Powers]]></dc:creator>
            <pubDate>Fri, 03 Jun 2016 20:38:46 GMT</pubDate>
            <atom:updated>2016-06-03T20:38:46.031Z</atom:updated>
            <content:encoded><![CDATA[<p>I felt like I had it mostly together until we got in to JavaScript. Trying to jump between two different languages can present an immense challenge to a novice coder. While the syntax is obviously different, there is a major difference between the way the languages handle functions. In JavaScript the functionality of a function can be obscure. In Ruby the functions are user defined, so, in most cases, they are easy to decipher. In my opinion, JavaScript complicates things further than they should be complicated, but I guess that is the general consensus among most coders, luckily we are stuck with it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8fb576379e38" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React.js… The rabbit hole]]></title>
            <link>https://medium.com/@jarpow44/react-js-the-rabbit-hole-e05373c678f6?source=rss-5d63935aa8e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/e05373c678f6</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Jared Powers]]></dc:creator>
            <pubDate>Fri, 03 Jun 2016 20:30:56 GMT</pubDate>
            <atom:updated>2016-06-03T20:30:56.963Z</atom:updated>
            <content:encoded><![CDATA[<p>React tripped me up. I am not ashamed about it in any way. That stuff is hard. I could see what was going on and why it was happening when we were going over it all in class, but when I sat down to write my own React script, I didn’t even know where to start. I think the issue was it being so much different from ruby. While I blew threw the JavaScript Katas, and actually thought I would like .js frameworks, it really rocked my world. React is a popular framework developed by Facebook. It is what is known as a UI library used to “facilitate the creation of interactive, stateful &amp; reusable UI components.” In fact, Instagram is written entirely in the React.js framework. One of the great draws to React is its interworkings between client and server side. It is a mean, clean, user interface machine.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e05373c678f6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why’s Poignant Guide]]></title>
            <link>https://medium.com/@jarpow44/whys-poignant-guide-4b0035a78bf2?source=rss-5d63935aa8e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b0035a78bf2</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ruby]]></category>
            <dc:creator><![CDATA[Jared Powers]]></dc:creator>
            <pubDate>Fri, 03 Jun 2016 20:23:08 GMT</pubDate>
            <atom:updated>2016-06-03T20:23:08.103Z</atom:updated>
            <content:encoded><![CDATA[<p>Why’s Poignany Guide to Ruby is an interesting tale of a man going through the ins and outs of Ruby through all kinds of completely off the wall stories. It is certainly an interesting take on the presentation of material in ways for someone to understand.</p><p>Ruby is easy on the programmer. In many ways it is a rogue among the plethora of other coding languages we have available to us. The guide tells us if a programmer likes his job, and the work he is doing, he will do better work in turn. I am glad I chose to learn this language for these specific reasons. I have always been interested in building things, and Why’s Poignant Guide hammers home the idea that I can get something up and running with rails in just a few lines of code, and continue adding to that code base indefinitely. When I first started coding the real problem I had was seeing no results. Rails does a great job of outlining what I have done wrong and directing me to the right path to fix the issues.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b0035a78bf2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On the job hunt]]></title>
            <link>https://medium.com/@jarpow44/on-the-job-hunt-26e79a2adbd?source=rss-5d63935aa8e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/26e79a2adbd</guid>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Jared Powers]]></dc:creator>
            <pubDate>Fri, 03 Jun 2016 17:45:34 GMT</pubDate>
            <atom:updated>2016-06-03T17:45:34.491Z</atom:updated>
            <content:encoded><![CDATA[<p>As I have finished up The Iron Yard here in Austin, I have begun the search for employment. While at first, this entire process can seem quite daunting, with cover letters, and styling of resumes, catchy slogans, and buzz words, it is easy to get lost in the process. We read two blog posts relating to the job hunt and the best way to go about finding a job. I took a few new things from these readings and would like to share them with you today.</p><p>David Brady wrote on making about them, while making it about you. The best results from job hunts come from interpersonal networking and the ability to talk with someone, share ideas and develop a relationship. Once these people you have interacted with understand the value of your common ground, they will find a job for you if they do not offer you one on the spot. In our job hunts, it is important to stay away from the drab, internet job posting, and gravitate to one on one human interaction. If we can do this, the jobs will find us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26e79a2adbd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Abstraction and the real world]]></title>
            <link>https://medium.com/@jarpow44/abstraction-and-the-real-world-405bc4168d69?source=rss-5d63935aa8e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/405bc4168d69</guid>
            <category><![CDATA[abstraction]]></category>
            <category><![CDATA[big-data]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Jared Powers]]></dc:creator>
            <pubDate>Mon, 02 May 2016 18:30:27 GMT</pubDate>
            <atom:updated>2016-05-02T18:30:27.356Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fj_93nVH0nufdCEUVixIhQ.jpeg" /></figure><blockquote>Give me a lever long enough and a fulcrum on which to place it, and I shall move the world.” -Archimedes</blockquote><p>As humans we have trouble understanding complex, non-human systems. Through time we have collectively developed a solution in the form of abstraction. Abstraction as Tom Stuart describes it in his talk from RubyConf 2014 is an adapter between these two issues. We are given “Big, friendly levers to pull on instead.” Tom answers three questions in this talk on abstraction.</p><ol><li>Where it’s from.</li><li>What it’s for.</li><li>How we can use it to make our programs better.</li></ol><p>He goes directly in to mathematics which is a massive set of abstractions we learn at a young age, so we take for granted now as adults. Numbers are abstractions from real world observations. The first example used is the Pythagorean theorem and the way in which Pythagoras was able to pull apart each aspect in to something we could easily use as humans. Thus the dawn of (A^2 + B^2 = C^2). Pythagoras was able to find a level of abstraction through thinking about the subject in a different manner. Other examples include trading fruit, taking multiple paths in a town to hit certain points along the way no more than once. The overarching principle of these examples is the essence of abstraction. We spot patterns and build reusable abstractions with the intention of solving more than just the initial problem, but all similar problems related to the initial problem.</p><p>Another great example is music. Music is what happens when you play the violin. The sounds you hear coming from that musical instrument are, at their essence, mathematics. They are waves and frequencies constantly changing and interacting with our eardrums. Mathematics is the product of a simplified world which has been simplified by building abstractions. I think these abstractions are the product of looking at a certain topic with an overarching mindset. Of course we can look at each individual poker hand and see what wins and what loses in reference to card values, or we can write a program that does this for us by abstracting the values of cards. Abstraction is quite important when developing, because a lot of the time it allows us to understand what is happening, but would also allow someone else coming to take a look at your work to understand it near the same level.</p><blockquote>“When a thing looks complicated, it’s possible that we’re looking at it wrong and missing some of the pieces of the puzzle”- Richard Feynman</blockquote><p>The related video can be found <a href="https://youtu.be/tJkoHFjoMuk">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=405bc4168d69" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>