<?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 Oliver Leigh Coley on Medium]]></title>
        <description><![CDATA[Stories by Oliver Leigh Coley on Medium]]></description>
        <link>https://medium.com/@mxoliverleigh?source=rss-f2acfda7e0b5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*S4KjYn9SugFYiNPZIN08Gg.png</url>
            <title>Stories by Oliver Leigh Coley on Medium</title>
            <link>https://medium.com/@mxoliverleigh?source=rss-f2acfda7e0b5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:53:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mxoliverleigh/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[Redux and Full-Stack JavaScript]]></title>
            <link>https://medium.com/@mxoliverleigh/redux-and-full-stack-javascript-5007228770bf?source=rss-f2acfda7e0b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/5007228770bf</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[full-stack]]></category>
            <category><![CDATA[restful-api]]></category>
            <category><![CDATA[redux]]></category>
            <dc:creator><![CDATA[Oliver Leigh Coley]]></dc:creator>
            <pubDate>Thu, 16 May 2019 16:48:46 GMT</pubDate>
            <atom:updated>2019-05-16T16:48:46.940Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*esmQEASAUd6iDCUmdGq91A.png" /><figcaption>React with Redux … Better than a puppy in a cup?</figcaption></figure><p>About a month ago I started the first sprint of my first ever full-stack JavaScript application. Previously I had worked with React in single-page applications, and I had built server-side applications with Node.js and Express, using EJS Templates for the view, but aside from having a theoretical understanding of the process, I had never actually experienced how the client and server connect and communicate. Enter Pocket Therabuddy, a full-stack NERD (node, express, react, database) application and mental health tool built with the intention of putting better data in the hands of users and the awareness to take control of how their actions can effect their moods in both positive and negative ways.</p><p>Pocket Therabuddy began as the capstone project for my nine month long bootcamp. The only stipulations for our capstone were that we had to follow the agile methodology throughout our planning and building process, otherwise we had complete free range over our tech stack, what we wanted to build, and how we wanted to build it. It has been a few weeks since I officially graduated, but this project is something I plan to continue for a long time. In my time as a teacher and now as a developer I have always emphasized project-centric learning because it allows you to be exposed to problems and topics you would have never thought to learn about otherwise. Which brings me to the crux of this article, one of the things I learned in building this project was the role of Redux in a full-stack JavaScript application.</p><p>Redux is in short a state management tool, but in keeping track of the state it can take charge of quite a lot of important logically processes including communicating with the server.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/83407e887310656914d0ae0265f98b85/href">https://medium.com/media/83407e887310656914d0ae0265f98b85/href</a></iframe><p>This is a snippet of code with a GET request and POST request to the server. All in all pretty straight forward, the fun part is how redux handles making these requests.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/dc4e25fce71e2b24b5a09a949efe9f45/href">https://medium.com/media/dc4e25fce71e2b24b5a09a949efe9f45/href</a></iframe><p>This is the action creator for the GET request above, this action which can be called in any react component with habitActions.getHistory(id) will dispatch the request, then call the habitService.getHistory function which is the GET request from before. If the request is successful, it will pass the JSON response from the server into dispatch(success(habits)) which can be accessed in the component as this.props.habits . On failure, it will dispatch the error.</p><p>The last part in this process is how you access your redux action creators and responses within the component. Redux has both a mapStateToProps method and a dispatchState method, though I have found personally that mapStateToProps can be used for pretty much everything.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d77abab0a70ee59571bd7e68eba487da/href">https://medium.com/media/d77abab0a70ee59571bd7e68eba487da/href</a></iframe><p>This function here will get the currently logged in user (authentication, and fetchHabits are the names of the redux reducers that handle these states) and whichever habits are returned from the server request. This function should be located outside of your React class, either above or bellow.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d87f28b85e3ea15e35ef45d4d3c3e9c5/href">https://medium.com/media/d87f28b85e3ea15e35ef45d4d3c3e9c5/href</a></iframe><p>Here is the dispatch call that will trigger the action creator and service request we looked at above, which will set this.props.habits to the data returned from the server.</p><p>The last crucial but very simple part is the npm package react-redux which will give you access to the connect function</p><p>import { connect } from &#39;react-redux&#39;</p><p>Then at the bottom of your component connect your redux mapStateToProps function to the name of your class Component and export it as usual.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/640df88327ebc8eed5a2541a83371219/href">https://medium.com/media/640df88327ebc8eed5a2541a83371219/href</a></iframe><p>If you’d like to check out Pocket Therabuddy for yourself it is deployed <a href="https://pocket-therabuddy.herokuapp.com/">here</a> and you can find the GitHub repo <a href="https://github.com/MxOliver/Pocket-Therabuddy">here</a> with more information about running it on your local server and upcoming features. Stay tuned for an article about d3 and using data visualization with React (another key feature of Pocket Therabuddy).</p><p>— MxOliver</p><p><a href="https://github.com/reduxjs/react-redux">GitHub - reduxjs/react-redux: Official React bindings for Redux</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5007228770bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Role-based Authorization and the View]]></title>
            <link>https://medium.com/@mxoliverleigh/role-based-authorization-and-the-view-90c4f33a0fe8?source=rss-f2acfda7e0b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/90c4f33a0fe8</guid>
            <category><![CDATA[postgresql]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[sequelize]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[user-authentication]]></category>
            <dc:creator><![CDATA[Oliver Leigh Coley]]></dc:creator>
            <pubDate>Thu, 21 Mar 2019 14:26:57 GMT</pubDate>
            <atom:updated>2019-03-21T14:26:57.847Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*b9Kn0HgK5YWQkuM4ht97HA.jpeg" /></figure><p>Over the past few weeks I have been working on building a client-side wikipedia-esque web application using Node called Wikology. In Wikology, all standard members can create, edit, and read public wikis. Users can also upgrade to a premium account (using the Stripe API client for payment) and create private wikis which can only be read and edited by their collaborators.</p><p>In the past, when handling role based authorization and which CRUD (create, read, update, delete) functions user role’s are authorized for, all users, whether they were signed-in or not, had read access to everything. This meant that the majority of the authorization took place between the controllers and the model. I could easily pass in a policy class to my query files and check if a user was authorized before allowing them to continue with a CRUD action, and if they weren’t, I could flash an unauthorized notice and redirect them. With Wikology, the introduction of private wikis meant that read access was not a given for all users, and thus, role authorization had to be implemented not just between the model and controller, but also in the view.</p><p>So how does one implement role based authorization for CRUD methods in the view part of an application? If you are a seasoned developer this may seem like an obvious answer, but this was my second ever client-side application and I was about to reacquaint myself with the MVC framework on a whole other level.</p><p>The key to working with the View side of the Model-View-Controller framework is to think about how you are passing information to the view.</p><pre>show(req, res, next){ <br>   <br>   wikiQueries.getWiki(req.params.id, (err, wiki) =&gt; {    <br>            <br>      if(err || wiki == null){ <br>               <br>         res.redirect(404, &quot;/wikis&quot;);  <br>          <br>      } else if(wiki.private === false || (wiki.private == true &amp;&amp; <br>  wiki.userId == req.user.id)){    <br>                <br>        wiki.body = markdown.toHTML(wiki.body);                        <br>        wiki.title = markdown.toHTML(wiki.title);                        <br>        res.render(&quot;wikis/show&quot;, <strong>{wiki: wiki, collaborator: null}</strong>); <br>              <br>      } else if (wiki.private == true) {     <br>            <br>          collaboratorQueries.collaboratorAccess(wiki.id,    <br>          req.user.id, (err, collaborator) =&gt; { <br>                   <br>                if(err || collaborator == null) {   <br>                     <br>                    req.flash(&quot;notice&quot;, &quot;You do not have permission    <br>                    to view this wiki.&quot;);                        <br>                    res.redirect(&#39;/wikis&#39;);   <br>                 <br>                } else {         <br>               <br>                     wiki.body = markdown.toHTML(wiki.body);                           <br>                     wiki.title = markdown.toHTML(wiki.title);                          <br>                     res.render(&quot;wikis/show&quot;, <strong>{wiki: wiki,     <br>                     collaborator: collaborator}</strong>);                    <br>               }                <br>          })             <br>     }        <br>  })    <br>},</pre><p>This is the show method which handles the view for each individual wiki. Let’s break this down:</p><ol><li>Get the wiki — in order to do anything we need to retrieve the specific instance that matches the given wikiId.</li><li>Check if the wiki is private and if so, check if we are the owner — if the wiki is public, or if we wrote the wiki, we have guaranteed read access and can go ahead and render the view. Here we are passing the wiki from step 1 in as {wiki: wiki } and the collaborators as null because they aren’t relevant to the show method if we are the owner or if the wiki is public.</li><li>If it is private and we are not the owner, we need to retrieve the collaborators for this wiki — each Collaborator instance has a one-to-one relationship with User, and a one-to-many relationship with Wiki (eg. each collaborator instance only has one user and one wiki, but a wiki can have many collaborator instances). The specific query here is happening on my collaboratorQuery file (shown below) but the concept is fairly straightforward. I pass in the wikiId from step 1, as well as req.user.id which is the id of the user making the request. Notice I’m not trying to retrieve all of the collaborators for this wiki, I only need to know if the current user is a collaborator in order to determine their read access.</li></ol><pre>collaboratorAccess(wikiId, userId, callback){   <br>     Collaborator.findOne({where: {wikiId: wikiId, userId: userId}})           <br>     .then((collaborator) =&gt; {            <br>           callback(null, collaborator);        <br>    }).catch((err) =&gt; {            <br>           callback(err);        <br>    })    <br>}</pre><p>If there is an error, or if a collaborator instance doesn’t exist between the current user and the wiki, the user is redirected and sent a message letting them know that they are not authorized to view that wiki. However, if everything succeeds we can go ahead and call on the view to render the wiki. This time, we pass in {wiki: wiki, collaborator: collaborator} which not only passes the wiki to the view, but passes the collaborator instance that links the current user as a collaborator with the wiki. By passing the collaborator instance to the view I can make sure the current user has access to view the private wiki before it renders. Ideally the user would be redirected before they even reach the view, but if they were to enter the route manually (eg. a former collaborator who no longer has read access but knows the url route) this would double-check their authorization before rendering.</p><p>This same strategy can be used for the rest of the CRUD methods, passing in authorized users as collaborator instances in order to determine what should be rendered in the view. Other examples include, determining whether the edit and delete buttons should be visible to a given user, or which private wiki titles should appear on a user’s index page (eg. the ones that they own or collaborate on).</p><p>Whenever I am stuck on a problem, the most effective question I can ask myself is “Who knows what and how?” Essentially — Does this component have the information it needs to do what I am asking it to do? Where is that information coming from and how is it accessing that knowledge?</p><p>and remember if you’ve been staring at the same problem and getting nowhere — take a step back so you can see the forest for it’s trees.</p><p>— MxOliver</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90c4f33a0fe8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Really, It Should Not Be This Complicated]]></title>
            <link>https://medium.com/@mxoliverleigh/really-it-should-not-be-this-complicated-fd8a13056747?source=rss-f2acfda7e0b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd8a13056747</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[code-newbie]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[programming-tips]]></category>
            <dc:creator><![CDATA[Oliver Leigh Coley]]></dc:creator>
            <pubDate>Wed, 14 Nov 2018 18:51:50 GMT</pubDate>
            <atom:updated>2018-11-14T18:54:40.545Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*Dko9PLjqgjzAgnlRWm0i8w.jpeg" /><figcaption>The immortal words of Avril Lavigne in meme format: “Why do you have to go and make things so complicated?”</figcaption></figure><p>If you’ve done any amount of programming you probably know the acronym DRY (Do Not Repeat Yourself), a mnemonic device to remind you that each parcel of knowledge or logic should only be spelled out once. Any time you need to access that knowledge in the future, instead of writing it out again you should just call back to that first declaration. There are a lot of articles out there about DRY, this is not going to be one of them. Instead, I want to talk about another mnemonic that I wish I had known about when I began programming a few short months ago; KISS (Keep it Simple, Stupid). In other words, don’t make things more complicated than they need to be, the path of least resistance is actually a great path to take when writing code.</p><p>I started to really think about this about a week ago as I was working on creating a chat room application for my bootcamp at Bloc. I was in the process of adding in a User component that, when logged in would display the username at the top of the page as well as attached to any sent messages, when I ran into a problem. When no one was logged in the user object would be null, so every time I tried to run my app while signed out it would throw an error because it can’t render the property username of a null object. I knew I would need to write some kind of conditional, telling my application to first check if there was a user, then either render the username or print “Guest” in it’s place. Sounds perfectly simple, and yet somehow a few hours later I ended up with three separate functions and a new state property for my User component all trying to handle this one issue but not actually doing much at all. I had made things way too complicated, and nothing was working.</p><p>This is not the first time I’ve done something similar, in an effort to embody the DRY principle of reusable code I had ended up making thing’s way more convoluted and messy than they needed to be. I had three functions all trying to handle what could have been done in one or two lines. I spent the second day on Slack working with the Bloc tech assistants in an effort to untangle my mess, but I was still going about it the wrong way. That night I decided something had to change. When I woke up the next morning I created a new GitHub branch and started over. Next I broke it down into the three necessary tasks:</p><ol><li>Check if User is null</li><li>If yes, print “Guest”</li><li>If no, print username</li></ol><p>Then, I thought about location. Who needs to this knowledge, and where is the ideal place for it to live so that they can access it? I also made sure to set aside places that needed to know about the user as a whole, from places that just needed the username. In doing so I realized that the only two relevant places were the render section of my User component, and the handleSubmit method of my MessageList component. I decided to ditch the DRY principle for a moment; these were both child components they didn’t have access to each other’s information, and furthermore I was already working with a reusable user object and all I needed was a simple conditional. This is what I came up with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/606/1*8Q41DtM_Werlbq25Q16hgQ.png" /><figcaption>Current User: {this.props.user ? this.props.user.displayName : “Guest” }</figcaption></figure><p>One single line of code after three days of frustration. I’ve always considered myself a maximalist in life; I love busy patterns and collecting weird knick knacks, I take comfort in surrounding myself with the things I love and the idea of having a capsule closet that can fit in a single backpack gives me nightmares. Nevertheless, this week I learned that programming is one place my maximalism should not be allowed to roam free. Hopefully you can learn from my mistakes and remember to KISS (Keep it Simple, Stupid), because honestly, it does not have to be that complicated.</p><p>— MxOliver</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd8a13056747" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reacting to React]]></title>
            <link>https://medium.datadriveninvestor.com/reacting-to-react-daa5ae30c9a8?source=rss-f2acfda7e0b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/daa5ae30c9a8</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Oliver Leigh Coley]]></dc:creator>
            <pubDate>Wed, 24 Oct 2018 20:55:23 GMT</pubDate>
            <atom:updated>2018-10-24T20:55:23.699Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j-OZBduxOo9SCWPB3mIXUA.jpeg" /></figure><p>I started learning JavaScript about a month ago, three weeks later I dove into React with the mission of creating a simple To Do list application. Before starting I had read up on all the pros and cons of using React; it’s fast, the unidirectional data flow makes debugging more efficient, and the VirtualDOM allows for quicker more responsive updates, but the biggest drawback seemed to be that it has a steep learning curve. Because I am fairly new to programming and this is the first framework/library that I have tried, I don’t feel that I can accurately estimate if React is more or less difficult to pick up on than other frameworks, but I can say that it was probably the most frustrating endeavor I have attempted so far.</p><p>To clarify, I think that React has the potential to be a really useful tool, I just need to get the hang of it first. For now I won’t be writing about my opinion of React, but I did want to talk about why I the first few weeks of React were so frustrating for me (and likely many others). React, for all intents and purposes, is the fancy fluff on top of a cake. It can make building and using your program more appealing, faster, and be ultimately a great asset, but at the same time, it can look really intricate and intimidating, even though at the end of it all it’s all built on concepts you already know. This was where most of my problems learning React initiated. I got caught up in the fluff and forgot that underneath it all I was essentially still doing JavaScript.</p><p>I only came to this realization late last night. I was working on adding a delete button to my app that would allow the user to remove individual To Do list items. I had been working with a tech agent on the Bloc Front-End Slack channel for quite some time when I finally said “I think I’m missing something fundamental because I don’t understand what any of this is doing.” The agent wrote back saying to forget React for a moment and focus on JavaScript, what would you do in JavaScript? This is what I came up with.</p><blockquote>deleteTodo(index) {<br> const todoDelete = this.state.todos.filter((todos, i) =&gt; i !== index); this.setState( { todos: todoDelete } ); <br>}</blockquote><p>In order to delete selected To Do items, I needed to create a filter that would compare my array of of ‘todos’ with the selected ‘todo’ and return everything that did not match the selected item. A filter passes certain parameters and constructs a new array of the elements that returned true. Once I looked at it in these terms, it was no longer a scary React thing that I assumed I didn’t understand, it was just a simple filter method that I had done hundreds of times before. Then all I had to do was set the State so that React would update the UI with our new array. The syntax for this particular case looks something like this:</p><blockquote>this.setState( {the state as originally set in the component: the new filtered list});</blockquote><p>I still have a lot more to learn about React, but it’s good to remember that feeling intimidated can often be more of a barrier than the actual difficulty of the concepts themselves.</p><p>— MxOliver</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=daa5ae30c9a8" width="1" height="1" alt=""><hr><p><a href="https://medium.datadriveninvestor.com/reacting-to-react-daa5ae30c9a8">Reacting to React</a> was originally published in <a href="https://medium.datadriveninvestor.com/">DataDrivenInvestor</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Millennial Life Hacks]]></title>
            <link>https://medium.com/@mxoliverleigh/millennial-life-hacks-7874aac00ab1?source=rss-f2acfda7e0b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/7874aac00ab1</guid>
            <category><![CDATA[queer]]></category>
            <category><![CDATA[lifehacks]]></category>
            <category><![CDATA[millennials]]></category>
            <category><![CDATA[humor]]></category>
            <category><![CDATA[poetry]]></category>
            <dc:creator><![CDATA[Oliver Leigh Coley]]></dc:creator>
            <pubDate>Fri, 12 Oct 2018 21:51:04 GMT</pubDate>
            <atom:updated>2018-10-12T21:51:04.832Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qkSgiIbLal7Gs7I-7ib20g.jpeg" /><figcaption>Flickr Source: Ronnie Pitman</figcaption></figure><p>Sew pennies into the pockets of your clothes.</p><p>Wear invisible platform boots so you look like you are floating.</p><p>Replace your wardrobe with a large sheet of canvas that you use as a dream journal.</p><p>Use a wedding veil as a casual accessory.</p><p>Carry a bundle of firewood at all times.</p><p>Grow moss on an old pair of overalls.</p><p>Submit your resume as a series of niche memes.</p><p>Swap out your under eye concealer for craft glitter.</p><p>Speak of nothing but the oncoming apocalypse.</p><p>Hang wind chimes from your belt so you won’t get lost.</p><p>Burn everything that doesn’t bring you joy.</p><p>Move to the Woods.</p><p>Start a coven of queer witches.</p><p>Never look back.</p><p>— MxOliver</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7874aac00ab1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Maybe she’s born with it, Maybe it’s Repl.it]]></title>
            <link>https://medium.com/@mxoliverleigh/maybe-shes-born-with-it-maybe-it-s-repl-it-f719e516d461?source=rss-f2acfda7e0b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/f719e516d461</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[programming-languages]]></category>
            <category><![CDATA[text-editor]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Oliver Leigh Coley]]></dc:creator>
            <pubDate>Fri, 12 Oct 2018 18:38:40 GMT</pubDate>
            <atom:updated>2018-10-12T18:38:40.308Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WEohxt-PlFmaqz1rMX6_Nw.jpeg" /><figcaption>Photo credit: instagram — @gabrielapalai</figcaption></figure><p>Repl.it stands for ‘Read-Eval-Print Loop” and is essentially an online coding platform that works like a text editor but with access to basically every programming language you could ever need. I was first exposed to Repl.it when I was working with one of Bloc’s tech assistant agents on Slack because I was hopelessly confused about closures. I had copy-pasted my code into Slack but in order to work with it and see exactly what errors were being logged by the console, the agent asked me to send it in a Repl.it link. At the time my head immediately went to “WHAT IS REPL.IT AND WHY CAN’T YOU JUST HELP ME HERE” but I shook off my impatience and did what was asked. Thus began my ever-blossoming relationship with a coding platform.</p><p>So, why is it that I am so enamored with Repl.it? In the few short months that I have been learning programming, I have tried several text editors and online platforms. I worked with TextMate, and Atom, I tried JS Bin which is another online platform, but they all left something to be desired. Offline text editors such as TextMate and Atom lacked the easy sharable quality of their online counterparts. Where as JS Bin had trouble with ES6 syntax, had a bit of a clunky interface in terms of changing between languages, and made it difficult to save and share code in a way that I could edit it later.</p><p>Repl.it on the other hand, not only has a much nicer interface (no offense to JS Bin but it looks like it came from the era of Windows 2000), it is easy to switch between languages or work with multiple at the same time. You can save your Repls in your account and edit them later, as well as share them as a URL that is both simple and SEO-friendly (aka. easy for humans to read). The console errors are also a bit more nuanced, though that might just be a formatting preference, but I have trouble matching other platform’s errors to specific line numbers. Lastly, the automatic titles that Repl.it ascribes to your new Repls are like something out of a dada-esque poetry generator. Which doesn’t really pertain to it’s usability as a programming platform, but it adds a nice touch of whimsy which is always appreciated.</p><p>In short — Use Repl.it, because you’re worth it.</p><p>— MxOliver</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f719e516d461" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Artist to Programmer]]></title>
            <link>https://medium.com/@mxoliverleigh/from-artist-to-programmer-5a963f963fc8?source=rss-f2acfda7e0b5------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a963f963fc8</guid>
            <category><![CDATA[codingbootcamp]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-developer]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[bloc]]></category>
            <dc:creator><![CDATA[Oliver Leigh Coley]]></dc:creator>
            <pubDate>Fri, 12 Oct 2018 17:40:24 GMT</pubDate>
            <atom:updated>2018-10-12T18:44:06.009Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*yUZRu_jZXasau0u0M0awgw.png" /></figure><p>Today marks the end of my first month of coding bootcamp at Bloc, and I have never been more thrilled about my future. Don’t get me wrong, I love making art; but I’ve realized that programming is what gets me excited about waking up in the morning where as art is something I want to come home to after a long day.</p><p>I began this journey towards becoming a web developer roughly six months ago. I had been feeling stuck in my life, design is something I have always loved but it was also something that had been a consistent source of solace for me and in turning that into a career I had lost sight of why I enjoyed creating in the first place. I decided to take an online class on hacking Wordpress child-themes as an introduction to HTML and CSS. I hadn’t worked in HTML since I was in 5th grade and obsessed with making offline websites about how to care for a pet skunk, but although so much had changed since 2002, my fervor for learning code had not waned in the slightest.</p><p>I love building things. This is such a quintessentially nerdy opinion, but there is nothing more satisfying than learning how something operates, and figuring out how I can move building blocks to make something entirely new or to trouble shoot existing problems. Programming allows me to be constantly working towards building something that not only functions but that serves a specific purpose, whether it’s a simple sorting function, or a program that connects people across the globe. I get to piece things together and see how they fit, and there is no feeling better than when you finally fix that error and everything falls into place. I think I actually enjoy being frustrated, which I suppose is a good thing as a programmer, since even experienced developers spend a lot of time debugging and fixing errors. With out frustration not only would life be kind of boring, but every time I make a mistake I end up learning at least two or three new things on my quest to figure out what went wrong.</p><p>I don’t know exactly where I am going to be in seven months when I finish this program, but I do know that I am already a developer and that I am eager to see where this takes me.</p><p>— MxOliver</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a963f963fc8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>