<?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 Quinn on Medium]]></title>
        <description><![CDATA[Stories by Jordan Quinn on Medium]]></description>
        <link>https://medium.com/@jpquinn605?source=rss-e2313ed3d951------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*u5qbHYzFnxNIVOkR.</url>
            <title>Stories by Jordan Quinn on Medium</title>
            <link>https://medium.com/@jpquinn605?source=rss-e2313ed3d951------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:58:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jpquinn605/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[A Decade in Review]]></title>
            <link>https://medium.com/@jpquinn605/a-decade-in-review-bfc808cf4bd?source=rss-e2313ed3d951------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfc808cf4bd</guid>
            <category><![CDATA[mindfulness]]></category>
            <category><![CDATA[wellness]]></category>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[blog]]></category>
            <dc:creator><![CDATA[Jordan Quinn]]></dc:creator>
            <pubDate>Mon, 06 Jan 2020 15:24:05 GMT</pubDate>
            <atom:updated>2020-01-06T15:24:05.120Z</atom:updated>
            <content:encoded><![CDATA[<p>For those of you who aren’t tired of being inundated with this information yet: we’re officially into 2020 now. With that brings the fact that it’s time to come to terms with the fact that I’m soon to be in my <em>late</em> 20s. This is the 3rd decade of the Gregorian Calendar I’ll be taking part in, having been born in 1994. 25 years of my life have come and gone as I write this. Some of those years brought more challenges and/or joy than others, but they all brought a metric buttload of lessons. I’m hoping to effectively communicate some of those as we scroll through this page together.</p><p>At the behest of my Therapist (with whom I have what I would consider one of the most crucial relationships of my life. If that’s not you and your therapist, or you don’t have one, I can’t recommend taking the time to find someone like that highly enough. Therapy doesn’t mean something is wrong with you, it means that you’re invested in doing the work to find out who you really want to be in this life.), I spent the better part of most of the last Sunday mornings leading into 2020 journaling about what the last decade of my life looked like, and what I thought I might want to get out of the next one. The first portion of this exercise proved to be<strong> <em>immensely</em></strong> time consuming and actually as of right now I haven’t even started broaching what the next decade might look like, at least not on paper.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bqWLJOtQ5VLR_aNMoBXoRg.jpeg" /><figcaption>Me, overlooking Tokyo from the Sky Tree. One of the best moments of my life.</figcaption></figure><p>This could be due to the fact that the last decade, for me, encompassed ages 15–25. Which, I would argue, is probably the most critical developmental period of one’s life, second only to the time spent as a toddler. As I strolled down my own memory lane, it became clear to me <em>just how much shit has actually happened in my life</em>. And when I say shit I don’t only mean the dirty, brown, foul smelling chapters (though there were some of those, which I can now say were <strong>always</strong> working for my good), I also mean some of the most overwhelming highs I could ever imagine. For those of you who aren’t familiar with my story, here’s a not-at-all-brief overview of the last 10 years.</p><ul><li>I graduated highschool (big whoop, right? I actually almost didn’t, I was failing two classes with less than a month of school left. This coming from someone with a previous 4.14 GPA and a mid 30s ACT score)</li><li>I fell in love for the first time, and found it a few more times over the years.</li><li>I went to college, joined a frat, drank fucked and drugged my way into near oblivion with a healthy dose of suicidal ideation (To family who’s reading this, sorry to dredge up old wounds, but you also know all of this already)</li><li>I spent a super-happy-fun-time weekend in a mental institution as a result of the above</li><li>I played my first shows in a rock band. Though short lived, these are still two of the greatest nights of my life.</li><li>I dropped out of college after I woke up one morning only to find out I had verbally abused a woman I respect very deeply. If you’re out there reading this, and I know you know who are you, thank you. Had you not confronted me with just who I was becoming, I don’t think I would have left. I hope life is everything you could ever want it to be.</li><li>I started competing in Bodybuilding shortly after this at the age of 19, which consumed the better part of the latter half of the last decade</li><li>“Career” #1: I became a personal trainer</li><li>I met a girl named Afton (inspired by the song “Flow Gently, Sweet Afton”), who would eventually become my fiancé.</li><li>“Career” #2: I became a brand rep for Fitbit and moved to Seattle. Afton moved in with me after only dating for 6 months.</li><li>We adopted Haddie girl (one of the great lights in my life)</li><li>“Career” #3: Getting rained on all the time sucked ass and so did my job so we moved back to Colorado and I became a BMW Sales Advisor</li><li>I won arguably the biggest title in Colorado Bodybuilding and became the first ever Classic Mr. Rocky Mountain</li><li>Afton’s mom passed away</li><li>3 weeks after this, I almost died from a viral heart infection. This was attempt two on massive health failures as I had a brain tumor at 17 months old.</li><li>I attended Turing School of Software &amp; Design and met my mentor, who continues to show me a better way to live</li><li>Afton and I decided to get un-engaged</li><li><strong>Career #4</strong> <strong>(Real Career #1):</strong> I went from working part time in a supplement store making $12 an hour when I started Turing to the type of consistent income that has afforded me true freedom at a very young age as a Software Engineer.</li><li>I found Jiu Jitsu and yoga, quit bodybuilding, and began confronting my disordered eating habits/body dysmorphia with the help of my incredible aforementioned therapist</li><li>I bought my first house</li><li>I went to Japan and now if I’m not careful it’s literally all I will talk about</li></ul><p>If you stuck around to read all of this, gold star for you. That’s my decade in review. Along the way, I met some of the most incredible human beings I could possibly imagined. I’ve served as a best man, an officiant, and a groomsmen for 3 of the greatest relationships in my life. I’ve laughed, cried, and lots of other stereotypical cliches that come up when summarizing experiences. Most importantly, though, I’ve learned how to really live. That’s a funny thing to say, right? But it can’t be overstated. I truthfully did not know how to live until probably the last 2 or 3 years. I only understood the world as something I had to white knuckle my way through. Work harder. Do better. Be more. It was excruciatingly black and white and an excruciatingly painful to live. All of which was self induced.</p><p>In reflecting on all of this, I can only help but feel gratitude for all of it. I mean that genuinely. Every single ounce of suffering and joy that the last 10 years have brought, everything I’ve done to myself and to others (both positive and negative), it’s all been working for my good since day 1. I may not have had the wherewithal to recognize it at the time, but it couldn’t have possibly have happened any other way. I wouldn’t have wanted it to. I wouldn’t be who I am today without everything unfolding exactly as it did. And I think I’m pretty fucking fantastic. So, I wouldn’t change an inch.</p><p>When one looks back and that’s what the last 10 years have brought, it can be a little challenging to try to paint a picture of what the next 10 might bring. I don’t really believe in setting goals anymore, at least not in a traditional sense, because seeing what I have seen now, I would have undersold my potential every time. The belief around what I thought I could have was just too narrow in scope. My experience has shown me that the Universe is far better at coming up with incredible shit for my life than I could ever be, so I’ll just keep showing up as the guy I want to be. I’ll keep listening to my emotional guidance system, I’ll keep trying new things, and I’ll keep on finding ways to more deeply appreciate the world around me. I hope I never lose my sense of marvel at just how incredible it is to be alive. Along the way, I’m sure I’ll fuck up constantly. But you know what? The stakes just aren’t that high. No matter what happens, it’s all working for my good. And if it were easy, if we had all of the answers or a perfect plan, I genuinely don’t think existence would be all that entertaining.</p><p>If I were to be so bold as to try to ask for some things from the next decade, though, they might look something like this:</p><ul><li>I want to see as much of Japan as I possibly can.</li><li>I want to find my person to share this experience of life with.</li><li>I want to learn more languages (both of spoken and software varieties)</li><li>I want to be in a position where I could reasonably “retire” from a traditional 9–5 job.</li><li>I want to let go of any remaining presuppositions about who I thought I was supposed to be, so that I can just be <strong><em>me.</em></strong> Whatever that looks like.</li><li>I want to continue finding things that bring me joy and do them as often as possible, with the understanding that those things might shift and change at any given time.</li><li>I want to continue expanding my own sense of physical, emotional, and spiritual well being.</li></ul><p>Those first 4 are just about as specific as I will get nowadays as it pertains to goals. The next 3 are where the rubber really meets the road and are what I’ll be spending most of my efforts on. And with that, I’m going to finish up this cold brew and go about my Sunday with these ideas as my north star for the next 10 years. May you all be happy and may you all be free from suffering. No matter what, though, it’s working for your good. I promise that much.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfc808cf4bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I’m Done with Competitive Bodybuilding]]></title>
            <link>https://medium.com/@jpquinn605/why-im-done-with-competitive-bodybuilding-515205fbc95c?source=rss-e2313ed3d951------2</link>
            <guid isPermaLink="false">https://medium.com/p/515205fbc95c</guid>
            <category><![CDATA[life]]></category>
            <category><![CDATA[fitness]]></category>
            <category><![CDATA[bodybuilding]]></category>
            <category><![CDATA[body-image]]></category>
            <category><![CDATA[sports]]></category>
            <dc:creator><![CDATA[Jordan Quinn]]></dc:creator>
            <pubDate>Mon, 06 Aug 2018 13:18:44 GMT</pubDate>
            <atom:updated>2018-08-06T13:19:34.440Z</atom:updated>
            <content:encoded><![CDATA[<p>“But Jordan. You said you were gonna do the thing. Why aren’t you doing the thing? You sure like to flip flop. Clearly you don’t have anything figured out. You silly goose. It must just be too hard for you.”</p><p>Correct, I don’t have anything figured out. Incorrect, it isn’t too hard for me. Actually, choosing not to throw myself into the same destructive pattern over and over again is far more difficult than choosing to continue to compete.</p><p>I’m sharing this purely because I believe it might resonate with some people sifting through similar experiences.</p><p>Competitive bodybuilding, for me, became the place where my “enoughness” lives. If I could just win another show, if I could just get my pro card, if I could just diet hard enough or train hard enough or grow my social media following enough, then I’d finally be good enough. Good enough for what, exactly?</p><p>Good enough to meet the ephemeral and arbitrary standards I’ve unfairly placed upon myself.</p><p>There’s a fatal flaw in this logic, though. Every single one of us is “enough” exactly as we are. The only thing you actually ever truly have is right now. This moment. Period. Choosing to focus on some external thing outside of yourself that may or may not occur at some indeterminate point that doesn’t actually exist until you get to that moment is an inherently rocky and sandy foundation to build your life upon. Because it takes you out of living every moment you have up until that point. The focus is on somewhere else, some other thing, getting across the finish line. Meeting the goal. Getting the validation.</p><p>This can be extrapolated to any area of life. Buying the car, the clothes, the house, the dog, getting the promotion, dating a more attractive person, sleeping with more people, you name it. All of these things can send you down one of two paths.</p><p>Path one: The never ending cycle of not enoughness. You finally get the thing you think you wanted. And you’re still hollow. You’re still unfulfilled. So you set a loftier goal. Reach for a higher standard. Because clearly you just weren’t dreaming big enough. You buy a nicer car. Date your perfect 10 with a phD from Harvard. Get that 6 or 7 figure income. And yet at each level, it just rings more and more hollow. And you can’t figure it out. And if you don’t think this is a thing, look at the deaths of Anthony Bourdain, Kate Spade, Chris Cornell, Robin Williams, Kurt Cobain, etc.</p><p>Path two: You do these things simply because you want to. There are no strings attached to them. They do not influence your capacity to lead a fulfilled existence. You are enough as you are, and you realize that these things cannot enhance or detract from your enoughness. They can, however, provide fleeting moments of joy. And, again, this moment is all that we have. Appreciating these things as the here one moment and gone the next items that they are, and returning to your state of inner contentedness that you’ve fostered through doing the “deep” work, that can pan out quite well for you.</p><p>I don’t think competing universally causes endless suffering through this pursuit of trying to become enough. There are people it suits quite well. I do believe, though, that this condition is far more rampant than anyone likes to admit. In all areas of life. And I know that for me, it guarantees I’ll lock myself in my own personal version of hell. Where I can’t possibly be good enough. Ever.</p><p>And I’m a fucking delight. So I’m gonna go ahead and not allow myself to reside in that space of fear and resentment and sadness anymore.</p><p>Carry on.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=515205fbc95c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BodyBuilding Made Me a Better Software Engineer: Embracing the Things that Make You, You]]></title>
            <link>https://medium.com/@jpquinn605/bodybuilding-made-me-a-better-software-engineer-embracing-the-things-that-make-you-you-9d482fecb4a3?source=rss-e2313ed3d951------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d482fecb4a3</guid>
            <category><![CDATA[personal-development]]></category>
            <dc:creator><![CDATA[Jordan Quinn]]></dc:creator>
            <pubDate>Sat, 20 Jan 2018 16:17:48 GMT</pubDate>
            <atom:updated>2018-01-20T16:17:48.251Z</atom:updated>
            <content:encoded><![CDATA[<p>On the first day of <a href="https://www.turing.io/">Turing</a>, the founder, Jeff, made a fairly prolific statement:</p><p><strong>“This will be the hardest thing you ever do.”</strong></p><p>While I appreciated the sentiment and reasoning behind his statement, I cordially (and also very silently, mind you) disagreed with him. From the very first day. Turing, or any other credible coding bootcamp, is a full time job. I in no way want to disparage the level of work and sacrifice this takes. The work load is immense, the learning curve can be steep, and it is often times overwhelming. It is quite likely to be the hardest thing a person will do. Without my prior life experiences, I would be drowning in the proverbial ocean that is learning to become a Software Engineer.</p><p>That, however, is just it.</p><p>We all have prior life experiences that have formulated us to the point we find ourselves at in this very moment. Whether those experiences have been remarkable or plain, pleasant or horrid, simple or complicated, it doesn’t matter. You are who you are, and I am who I am, because of the decisions we made to get to this point. My decisions took me down a path that taught me to view suffering as a skill, motivation as a finite and fickle resource, and consistency as the only thing that really matters. My decisions turned me into a successful competitive bodybuilder and that, in turn, has made me a resilient and consistent human being. Being a resilient and consistent human being, then, has made me a better developer.</p><p>At first look, two things couldn’t seem to be on more polar opposite ends of the spectrum. Just look at the stereotypes that permeate both industries. The bodybuilder is nothing more than an arrogant meathead, screaming and grunting, eating their protein, taking their steroids, living in solitude and in anger. The coder is nothing more than a pale nerd, living solely off of energy drinks and doritos, introverted to the core and socially inept. Also living in solitude and in anger. I guess that much is the same from a societal view.</p><p>I, however, have become intimately entwined in both of these worlds. I see them for what they are. The bodybuilder is the embodiment of consistency. The embodiment of making the right choices day in and day out, and doing the hard stuff even when nobody is looking. The seasoned developer (which I am not yet, but am striving to become) is even more consistent still. Another lesson Jeff taught us was our ABCs, or, Always Be Coding. Even more universally, Always Be Consistent.</p><p>Being a developer and a bodybuilder both require a certain degree of self imposed suffering. Whether that suffering is raking your brain over the hot coals that is your steaming pile of hacky code for days on end or that suffering is giving up the feeling of a full stomach or knowing a day that isn’t fueled purely by caffeine and necessity (I guess that part isn’t so different between the two either): You are going to suffer. You are going to exit your comfort zone, and you are going to remain outside of that comfort zone for the foreseeable future.</p><p>The thing about suffering is that it really isn’t all that different than developing the muscles a bodybuilder strives for years to attain. The more you embrace it and throw yourself into it, the better you get at handling it. Just as the more often you train a muscle, the more it can grow. You can exercise your ability to suffer, and you can turn it into one of your greatest assets.</p><p>No matter how good you get at “embracing the suck”, as it is so often referred to, there are going to be times where the motivation just isn’t there. There are going to be days where the last thing you want to do is crawl out of bed and hit the gym or eat more chicken. That doesn’t change no matter what industry you are in. There are days where the last thing I want to do is write even a single line of code. Willpower, too, is somewhat of a muscle that can be exercised. They’ve done research on humans, exposing them to a situation where they were forced to use their willpower (or no willpower at all) for a certain amount of time. Following this period of time, they were given a task that was literally impossible to complete.</p><p>The group that was forced to utilize a large portion of their willpower resource prior to the impossible task almost universally became exasperated and ready to quit in a matter of minutes. Whereas the group that still had a full willpower reserve had no issue toiling away at the impossible task for almost any length of time. So how do we expand the reservoir?</p><p>Research has also found that people who regularly make the right choices (eating well, exercising often, quit smoking, etc) are exponentially more likely to have that ability to make the right choice bleed over into other areas of their life. They are more fulfilled, they perform better at work, they drink less, and do more. This, I believe, is why bodybuilding was such a transformative experience for me. You spend years developing your ability to make the right choices, no matter the circumstance. When you are able to transfer that capability to the other areas of your life, your willpower often becomes limitless in comparison to those around you.</p><p>However, no matter how often you utilize it, willpower is going to give out on you.</p><p>Your mental fortitude and ability to embrace the suck is going to disappear.</p><p>All you are going to be left with is <strong>consistency</strong>.</p><p>We are beings of habit. Doing the same things day in and day out will eventually turn that into your only frame of reference. Whether those things are getting home from work, grabbing a bowl of popcorn and plopping your butt in front of the tv or those things are getting home from work, running to the gym, crushing your workout, and then making the right food choices. Whatever you train your mind to expect is what you are going to find your body follows through with. When you can develop consistency in all aspects of life, everything else comes together.</p><p>When I was competing, I ate the exact same meal(s) 5–7 times a day. I lifted weights every single day. I did cardio every single day. I sacrificed my relationships and experiences with friends and family every single day. That, however, was one of the most successful periods of my life.</p><p>After leaving that behind, I was lost. Until I realized that all of those same skills (minus the whole giving up friends and family thing, I am happy to report we are closer than ever) could be translated to literally anything I wanted to do. That’s when I started writing code every single day. I (almost always) wake up at 5am to meditate, reflect, and prepare. I read self-improvement articles and books in droves. I still make the right food choices and exercise on a regular basis, which pays itself back into my willpower reservoir so that I can keep doing all of these same things day in and day out.</p><p>Now this may all seem a bit hardcore, and that’s fine. I don’t think everybody should go out and become a competitive bodybuilder just to try and further their other ventures in life. In fact, that’s probably the last thing I would ever recommend. What I would suggest, however, is the following:</p><p>Find the thing(s) that you can do on a daily basis that are going to force you to change your habits and your outlook. Don’t allow yourself to lose out to the easy choices. Do the hard stuff. Do the right stuff. Pursue that which, in the long run, sets your soul on fire. Even though in the short run, it often super sucks.</p><p>For a long time, I ran away from the ability to become more than average. I wanted a life of complacency, simplicity, and to leave behind a legacy of something relatively unremarkable. I wanted this because it was comfortable and because it was safe.</p><p>I came to find that by embracing the things that have made me into who I am, I could no longer settle for anything but growth and development and the pursuit of more.</p><p>The things that make you into who you are, are also the things that can catapult you to who you want to be. It’s just a matter of embracing them now, holding onto them no matter the circumstances, and striving for more of those things everyday.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d482fecb4a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Professional Story]]></title>
            <link>https://medium.com/turingschool/my-professional-story-fe58a757d640?source=rss-e2313ed3d951------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe58a757d640</guid>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[journal]]></category>
            <dc:creator><![CDATA[Jordan Quinn]]></dc:creator>
            <pubDate>Mon, 08 Jan 2018 14:46:13 GMT</pubDate>
            <atom:updated>2018-01-11T22:36:26.808Z</atom:updated>
            <content:encoded><![CDATA[<p>During my time at Turing School of Software &amp; Design, we were tasked with writing our professional story: a dive into where we’ve been, why we changed paths, and where we plan on going. I had a particularly tumultuous set of experiences that led me to where I am now (as most of us did at one point), and felt putting pen to paper to create this story for myself incredibly healing and beneficial. More than that, it strengthened my resolve. I firmly believe, now more than ever, I am going down the path for which I am meant. Below you will find my story. I am sharing it in hopes that it inspires someone to reflect on their own journey, write it down, and find this same strength of resolve I have now found within.</p><p>I’ve always loved being a resource for others. Collecting and processing information in a way that allows me to <strong>break high level thinking down</strong> into consumable chunks for those around me. Being a leader in someone’s development then comes as a natural extension of my propensity to collect information as a resource. After years of developing my own prowess in fitness, I turned that <strong>knowledge into a resource</strong>, working with dozens of clients to shed several hundred pounds. One client in particular was able to take the road map that I provided him and lose over 100 lbs in a year.</p><p>However, there came a point of stagnation in my ability to grow as an individual and in terms of knowledge. This led me to pursue a career as a BMW Client Advisor, again utilizing the aforementioned propensity to <strong>lead and guide through information</strong> in order to assist people making the 2nd largest purchase, besides their home, they would ever make. This afforded me the opportunity to excel in a new field, and I earned sales MVP over 38 other veteran advisors in my first month on the job. Throughout both of these chapters, I led another life as a competitive bodybuilder. This allowed me to apply my own knowledge towards bettering myself, but also come to love and respect the process behind any end result. This knowledge and <strong>love for the process</strong> led to me earning one of the most prestigious regional titles in the country: Mr. Rocky Mountain.</p><p>My turning point came when, in the span of three weeks, my now fiancee’s mother passed away, followed by myself nearly passing from a heart infection. I needed to break into an industry that afforded the balance I would need to care for myself and for her, while continually expanding my own knowledge in a process-driven, problem-solving environment. Beyond that, I refused to be beaten down by this. <strong>I was going to come back better</strong>. Enter software engineering. I knew there was no other field expanding at a more rapid rate, and few other fields that were more process-driven or full of opportunities to coach others towards an end solution. As I dove head first into this field, I discovered one thing rose above all of this: a passion for development.</p><p>This lead me to my time at Turing, where <strong>I harnessed this passion to propel myself to an entirely new level of skill and belief</strong>. Turing created the perfect vessel for my strengths to be emulated, and tested. Working with and assisting others, expanding my knowledge, and loving the process required to grow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*1IeC-YqXyRTAGOqPh5OeIw.png" /></figure><p><em>Jordan is a current Mod 2 (soon to be Mod 3!) student at Turing School of Software and Design.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe58a757d640" width="1" height="1" alt=""><hr><p><a href="https://medium.com/turingschool/my-professional-story-fe58a757d640">My Professional Story</a> was originally published in <a href="https://medium.com/turingschool">turingschool</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Diving Deep(er) into Objects — JS Fundamentals Part Two]]></title>
            <link>https://medium.com/@jpquinn605/diving-deep-er-into-objects-js-fundamentals-part-two-f8438bab838?source=rss-e2313ed3d951------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8438bab838</guid>
            <category><![CDATA[education]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[hackernoon]]></category>
            <category><![CDATA[computer-science]]></category>
            <dc:creator><![CDATA[Jordan Quinn]]></dc:creator>
            <pubDate>Sat, 06 Jan 2018 03:43:37 GMT</pubDate>
            <atom:updated>2018-01-06T03:43:37.817Z</atom:updated>
            <content:encoded><![CDATA[<p>Last time we spoke (well, I spoke, you read), the discussion centered around the very basics of interacting with objects in JavaScript. We worked through a series of meals with various key value pairs and we learned how to navigate through those objects and extract valuable pieces of information. At the end of that discussion, it was implied that objects would be a large part of your existence as a JS developer, and during the course of this particular fundamentals lesson, you’ll see why.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/605/1*lhHcoGpvs3U8RjN955F2Eg.png" /><figcaption>Just a Snippet of the Object We Are Working With</figcaption></figure><p>This object is representative of my hometown of Denver, Colorado. Over the years, this city has changed tremendously. And over those years, this object has changed tremendously as well. It has been expanded upon time and time again by those who have come before me, and will be expanded upon ever-more. To get started, let’s deconstruct some of the particular key value pairs of this object. Looking at the first block, it can be seen that our Denver object has the keys of elevation, mayor, neighborhoods(which is an array), buildings (and the various types of buildings), restaurants, breweries, and more. Inside of each of those keys, we occasionally find more keys with more values and it goes on and on and on. Rather than continuing to take a 10,000 foot overview of the object, though, let’s dive into some problems.</p><p>The first challenge we are going to tackle is to create an array of just the names of all of the restaurants. This one is fairly simple. Our restaurants are already stored in an array, so we can access each object iteratively. We want the name of every restaurant, so we know that this new array is going to be the same length as the original one; this points to the <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/map">Array Prototype method of map</a>. Map always returns to us an array that is the same length as the original array we are iterating over. This solution might look something like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/583/1*hled2Av0spMSNA9q-1um-g.png" /><figcaption>Output From the Map Method</figcaption></figure><p>Map returns us an array, but only if we store that array in a variable. So we declare restaurantNames and assign it to the array that map returns us. When we invoke map, it is iterating over our restaurants array, and for each restaurant it is pushing that restaurant’s name into the new restaurantNames array. The output is seen in the green above. Not too hairy, right? Good! That just means we can level up.</p><p>Next up, we are going to tackle creating an array with all of the buildings that were created before 1910. When we look at our buildings object that’s living inside of our Denver object, it can be seen that it is a series of arrays. Each of these arrays is contained within a key value pair, with the key being the building type and the value being the array of every building of that type. Each of the following images will be a step in how I would go about solving this, with the caption hopefully explaining the thought process:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/389/1*9E9nMfW6Gj7p06GyavzBmw.png" /></figure><p>We need a new array, but it isn’t going to be the same length as our original array as our original array is only the four building types inside of a new array. Since it isn’t going to be the same length as the original array, we can’t use map. So, reduce is a good choice. When setting up a reduce method, <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/Reduce">we know it takes two parameters</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*2uZqULb3k9YMNMB6HmG-XA.png" /></figure><p>Now that we have the building types as a string, we can iterate over that array using <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/forEach">forEach</a> ([‘commercial’, ‘historical’, ‘athletic’, ‘entertainment’, ‘medical’]) to get into each level, if you will, of our buildings object by passing in the type of building to our bracket notation. The JS compilier will interpret this as denver.buildings.commercial.forEach the first go around, followed by historical, etc etc. Each time it gets to a new type, it will look into each building of that type. But what do we need to find?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/449/1*7e19TLsiT2s7YxzT0LPyQA.png" /></figure><p>We know that we only want the buildings that have were constructed before 1910. This suggests we will need some sort of condition. So, we can tell JS that we only want to add to our accumulator buildings that are at least that old. This is the last step to the problem, and it will return:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/331/1*hFHJHa_FrzO91HRjmRoIyQ.png" /></figure><p>That particular problem was a bit more challenging. It involved a few steps, but we were able to get the job done. Feeling brave about objects? <a href="https://repl.it/@jpquinn605/Denver-Object-JS-Dojo-1">Take a stab at a few of these problems on your own,</a> let me know what you thought of the lesson, and stay tuned for more.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8438bab838" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Diving Deep into Objects — JS Fundamentals Part One]]></title>
            <link>https://medium.com/@jpquinn605/diving-deep-into-objects-js-fundamentals-part-one-c142a983208c?source=rss-e2313ed3d951------2</link>
            <guid isPermaLink="false">https://medium.com/p/c142a983208c</guid>
            <category><![CDATA[javascript-tips]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[oop]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Jordan Quinn]]></dc:creator>
            <pubDate>Thu, 04 Jan 2018 14:28:29 GMT</pubDate>
            <atom:updated>2018-01-06T02:56:39.028Z</atom:updated>
            <content:encoded><![CDATA[<p>As one progresses into the sea of possibility (and great sadness) that is JavaScript, it is inevitable that navigating through deeply nested objects will become a part of your daily existence. Said daily existence can be made much easier by understanding objects at a high level , followed by coming to understand them in great depth. To assist in this effort, we will be diving into an object of considerable mass, extracting some data, and discussing the potential applications of recovering that data. First and foremost, though, comes the 10,000 foot overview.</p><p>In a more practical sense and less theoretical sense, an Object in JavaScript is denoted by an opening and closing curly-brace {}. This creates a reference point in memory to whatever we decide that Object is going to contain, which can be strings, integers, arrays, or even more Objects. Inside of the aforementioned curly-braces, we will find a series of key-value pairs.</p><p>You can think of a key-value pair as akin to looking something up in the Dictionary. Our key is the word we are looking for, and our value is the definition that the dictionary returns to us. In JavaScript, your key is always going to be a string (even if you don’t write it as one when you instantiate the Object, thanks jurvuhscurpts).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LmT2q-rhQg2EVv6zahixCA.png" /><figcaption>No Google, You’re Wrong</figcaption></figure><p>Your value is going to be whatever you decide you want it to be. It can be an array, another Object, a string, you name it. In practice, this might look something like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*xYbW4DH12V-FHt_i-gnkeg.png" /><figcaption>I mean, am I wrong?</figcaption></figure><p>The myFavoriteMeal variable is an Object with a key of breakfast and a value tied to that key of eggs and bacon. In JS, we utilize the colon to assign our value to the key, not a standard assignment operator (=). If I want to access my eggs and bacon, there are two ways to do this: dot notation and bracket notation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/534/1*Wu8wGIkQvzyYGTahyxx1RA.png" /><figcaption>Accessing Eggs and Bacon Two Ways</figcaption></figure><p>Both of these options are going to return to us the string ‘eggs and bacon’. Note that if you want to directly access a key with bracket notation, you’ll have to do so by wrapping it in a string. There are exceptions to this, which we will cover. Now that we can access values in an Object, what happens when we have a really big object? Let’s say we turn our myFavoriteMeal object into myFavoriteMeals and it looks something like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*WLRNcenvgwh95c-YzC8bCg.png" /><figcaption>All Sorts of Nested Data-Types</figcaption></figure><p>We know how to get into our breakfast key, what about accessing the items in our lunch key? Those items have been stored in an array, which means we can access them by their index, or by utilizing any of the native Array prototype methods that JS gives us:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/1*8_KIqW_dxh2k1Qr4domeFw.png" /><figcaption>Accessing Each Item in our Lunch Array</figcaption></figure><p>Simple enough! If we move our attention to the dinner property of our myFavoriteMeals object, it can be seen that this is an object living inside of an object, otherwise known as objectiception (not really, but kind of). If we want to get into the values of this object, it’s no different. We can utilize either dot or bracket notation, chaining it onto our earlier my FavoriteMeal example. We will also utilize a variable to access something via bracket notation, so as to see the more practical application of that tool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*UE2BBZzAv_AUYpNhijiLSg.png" /></figure><p>As seen to the left, because dinner is just another object living inside of myFavoriteMeals, we can access its properties the exact same way we did with the initial myFavoriteMeal object. We can also store the key we are looking for in a variable, and pass that variable into our bracket notation. This is particularly useful, as most of the time with objects, you’ll be working with at least one dynamic piece of information (changing based on user interaction or which iteration of a function you’re on). This will allow you to dive into that object and extract the information you need. You’ll also notice that if you attempt to access bestMeal with dot notation, you’re going to get undefined. What is this witchcraft? Well, dot notation in JavaScript is going to explicitly search the object for a property with a key equal to ‘bestMeal’. Our dinner object doesn’t actually have that key anywhere (it’s only key is equal to ‘meal’), so it is going to return undefined. That said, if you were to give myFavoriteMeals.dinner.bestMeal a value by assigning it to ‘Salmon’, JS would automatically create that new key-value pair and attach it to your myFavoriteMeals.dinner object.</p><p>In this short lesson, we covered the ins and outs of basic object interaction. Understanding how to access various properties of objects via their key-value pairs, bracket and dot notation and when to use them, and adding properties to an already existing object. In the following article, we will get into the real-nitty gritty of object manipulation by solving a series of problems in a massive object for my home city of Denver, CO. Until then, start writing some of your own objects. Go into the docs, learn what you can learn, and start applying it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c142a983208c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>