<?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 Colin Recko on Medium]]></title>
        <description><![CDATA[Stories by Colin Recko on Medium]]></description>
        <link>https://medium.com/@cpr1988?source=rss-4228f25cb548------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ohNDVHFA_9Tt77TL.</url>
            <title>Stories by Colin Recko on Medium</title>
            <link>https://medium.com/@cpr1988?source=rss-4228f25cb548------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:17:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cpr1988/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[The Future of Coding]]></title>
            <link>https://medium.com/@cpr1988/the-future-of-coding-768bc3305e8c?source=rss-4228f25cb548------2</link>
            <guid isPermaLink="false">https://medium.com/p/768bc3305e8c</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Colin Recko]]></dc:creator>
            <pubDate>Mon, 18 Apr 2016 23:15:33 GMT</pubDate>
            <atom:updated>2016-04-18T23:15:33.903Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s world of immediate gratification and continuous evolution, the computer world is developing and growing faster than anyone could have dreamt in past years. Change comes swiftly, and soon after, it’s hard to remember what it was ever like before your touchscreen smartphone or your Apple Watch. As we look into the future of coding, it’s hard to say what will change. One thing that I think will certainly have an effect on the world of coding is the emergence of coding bootcamps. Thousands of new developers have entered the workforce after a few months learning some code at bootcamps, but what does this mean for the future of computer programming?</p><p>First, as bootcamps are a relatively recent phenomenon, bootcamp alums are still working their way up the ladder. I think very few, if any, have yet to really reach the top. I think it will be interesting to see how these new techies from a non-traditional background will be in management positions in the future. They’re coming into the industry without formal education in computer science, and may have had years of experience in other fields. This will surely give them a unique view of the coding world compared to their counterparts from more traditional CS backgrounds. I’m not sure the exact effect this will have on the industry, but I do think that it will result in a deviation from standard practices that have existed in the past.</p><p>Another interesting thing I’ve noticed about coding schools is that many of them focus on Ruby on Rails. This is supposed to be a language that CAN be quite easy to learn in comparison to other languages. It’s quite logical, and the syntax is very similar to that of English. This has led to many schools devoting a lot of time and energy into teaching Rails to students. While Rails and Ruby are quite popular languages, they are ranked #9, behind other languages like JavaScript and Python. Will these new Ruby devs force the growth of Rails? That would be nice for someone like me who has spent a lot of time learning about it.</p><p>Lastly, one thing that I can predict is that something new and incredible will surface that no one knows of right now, and it will become a major part of coding. That’s the only thing that I really can predict at this point. Once I’m in the workforce, I will have a better idea of what the expect from the world of coding.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=768bc3305e8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[jQuery: You Might Not Need It (But You Probably Will)]]></title>
            <link>https://medium.com/@cpr1988/jquery-you-might-not-need-it-but-you-probably-will-14b7cc2ed713?source=rss-4228f25cb548------2</link>
            <guid isPermaLink="false">https://medium.com/p/14b7cc2ed713</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Colin Recko]]></dc:creator>
            <pubDate>Mon, 18 Apr 2016 22:15:36 GMT</pubDate>
            <atom:updated>2016-04-18T22:15:36.018Z</atom:updated>
            <content:encoded><![CDATA[<p>Upon first hearing of jQuery, I immediately took to the great expanses of the Internet to find answers to some of those initial questions a person may have about something new they’re learning. As I scrolled through Google, I found page after page gloating of the benefits of jQuery.</p><blockquote>The purpose of jQuery is to make it much easier to use JavaScript on your website.</blockquote><p>Hmm.. Sounds good to me.</p><blockquote><strong>jQuery</strong> is a fast and concise JavaScript Library created by John Resig in 2006 with a nice motto − Write less, do more</blockquote><p>Go on…</p><blockquote>There seems to be a commonly held belief that jQuery users are ignorant.</blockquote><p>Huh?</p><p>The more I dug, the more I read of jQuery’s current controversial status. It seems many people don’t appreciate how “simple” jQuery can make developing a website, among many other reasons. Regardless, I dove into my assignment for class. I completed a jQuery tutorial over the course of a few hours, and while it seemed quite easy as I went through the course, actually applying what I learned into a real piece of code has proven to be quite difficult. As a complete newbie, here are some things I have taken away from my time with jQuery so far.</p><p>First, naming things on your HTML page is so important. I have not personally done a crazy amount of styling on much of anything I’ve made so far. While I have done some minor changes, while also utilizing tools such as Materialize and Bootstrap, I rarely need to go in and give an ID of class to my objects on the page. However, I quickly realized that this is not an option while using jQuery. A lot of jQuery is based around finding certain tags within your code that has a specific ID or class. If you mislabel something or don’t give something a tag, jQuery won’t work for you. This has proven to be a bit of an adjustment for me. Thinking of of dozens of tag names can be a bit difficult at times as a lot of stuff tends to overlap, or serve a similar purpose.</p><p>This will lead us into the DOM. It seems a lot of people online don’t really like interacting with this DOM. DOM stands for Document Object Model. You can basically think of it like a tree with branches that holds all of your HTML elements. You connect with the DOM to manipulate an object on your website. This is where tags come in handy. Once you know where you want to go, you will need to do a lot of climbing up and down this tree to access the part of your website you need. While it seemed quite simple on the tutorial, I’ve since tried a simple hide and reveal query on a project I am working on now to no avail. I’m hoping to have that worked out by tonight. We will see.</p><p>Lastly, jQuery does let you do a lot of really cool stuff. A lot of the cool functions you’ll see different websites do, like hiding and revealing things, adjusting stuff as you move or click your mouse as well as updating bits of information depending on input the user gives. This is stuff that really takes your project to the next stage. Of course, this seems to be the most difficult aspect. One thing jQuery lets you do is animate things. For example, if I click a link, maybe a piece of text with fade in and fade out when I click it again. Adding fun features like this will really help improve the impression your webpage leaves on users.</p><p>For now, jQuery is still bouncing around in my brain. Like everything, this will surely require lots of time and practice before it becomes easy, despite what people say online. My hope is that with jQuery, I’ll really be able to do some of the cool things I’ve been hoping for at last!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14b7cc2ed713" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Approaching JavaScript as a Rails Developer]]></title>
            <link>https://medium.com/@cpr1988/approaching-javascript-as-a-rails-developer-cb587d3e5fd3?source=rss-4228f25cb548------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb587d3e5fd3</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Colin Recko]]></dc:creator>
            <pubDate>Tue, 12 Apr 2016 13:40:59 GMT</pubDate>
            <atom:updated>2016-04-12T13:40:59.958Z</atom:updated>
            <content:encoded><![CDATA[<p>I still remember being in middle school, and sitting in my first Spanish class. The teacher immediately began to speak to us in Spanish, and I was initially taken aback by these new sounds that filtered into my ears. I couldn’t understand anything she was saying, and I wasn’t sure if I would ever get to the point where I could begin to make sense of what was going on. Eventually, I began to realize that English and Spanish have a lot of similarities. Even though they look a bit different and there are few weird quirks that separate them, a lot of the basics are the same. Spanish and English even have a lot of similar words.</p><p>In a way, you could say that its similar with Ruby and JavaScript. After spending a few months absorbing Ruby in all of its awesomeness, approaching JavaScript seemed like a daunting task. However, I’ve come to find that there are a lot of similarities between the two languages. Like in Ruby, I can fined numbers, strings, Booleans, objections and functions. A lot the same basic rules of logic apply between the two. However, it’s obvious that Ruby was written with a lot more thought and consideration for the programmers who have to work with these languages.</p><p>One aspect of JavaScript that I find to be quite frustrating are the numerous exceptions to rules. As I read through “Eloquent JavaScript”, the author mentions so many errors that written into the code. This can be quite difficult for a new programmer to remember. Ruby is not a perfect language and has its quirks, but compared to JavaScript, it is a language of logic. I wish that JavaScript would correct some of its weirdness, instead of adding on more layers of weirdness (=== ????? WHY?!)</p><p>In closing, JavaScript may seem quite familiar to a Ruby developer due to a lot of the basics being the same. However, the way JavaScript is written is a bit different. Regardless, you should be able to work with VERY basic JavaScript if you just spend a few minutes reading the rules of syntax. For example, I created a Fizzbuzz function in JavaScript, which seemed like a miracle to me at the time. If you put in some time, you too can tackle JavaScript.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb587d3e5fd3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simplicity and Coding]]></title>
            <link>https://medium.com/@cpr1988/simplicity-and-coding-980582cfeb61?source=rss-4228f25cb548------2</link>
            <guid isPermaLink="false">https://medium.com/p/980582cfeb61</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Colin Recko]]></dc:creator>
            <pubDate>Fri, 25 Mar 2016 14:42:46 GMT</pubDate>
            <atom:updated>2016-03-25T14:42:46.982Z</atom:updated>
            <content:encoded><![CDATA[<p>For a person new to coding, like myself, creating that code that can be succinct and function can be quite a daunting task. I’ve found myself writing programs that are extraordinarily long in order to meet my needs. I’ve then seen that same program written in a fraction of lines. How can we get from a program with line after line of code to a program that can accomplish all of those tasks with half the amount of code? Simplicity is the key, but is easier said than done, and surely comes with time and experience. After watching a talk done by Rich Hickey called “Simple Made Easy”, I’m not sure I’m any closer to understanding than before. Regardless, I did pick up a few useful tips that I will try to incorporate into future projects.</p><p>First, what does simple actually mean? “Simplicity is a prerequisite for reliability.” This quote resonates for me. Simple, is it’s most archaic and basic definition, means one fold or braid. If you think of pieces of string, a former member of the Navy may be able to create a complex entanglement that could surely hold the weight of several men, but he may struggle to actually articulate what each string is doing as he moves down the line. It’s quite similar to coding. You don’t want to entangle those strings more than are necessary. You can do this by trying to remember the number 1 while you are coding. Your individual pieces of code should have one role, task, concept or dimension. Having just one of something is key to writing good code. This does not mean that a function needs to only do one thing, or appear only once within your code. Going through your code, and counting how many times a piece of code appears is not beneficial to your program. Instead, enhancing functionality by combining different aspects together when necessary will result in stronger code.</p><p>Second, what is easy? This can be quite a dangerous word for someone writing a program. Sticking with something because it is easy for you may actually be quite detrimental to your program. The word easy actually means near or at hand. In that sense, something that is easy in program means something that is readily available for us on our hard drive, within our already acquired toolset, or just some place that is accessible for us without much thought. The problem with this approach is that easy is relative. What may be easy for you may not be for another. Limiting yourself to conventions that you already know limits you from growth in the future, and can be quite damaging to the functionality of your program.</p><p>An important step to creating good code that can be simple and efficient is planning. Taking the time to think about the paths your code will take before actually typing anything out allows your brain to process and analyze how your code will look. Mr. Hickey recommended the classic who, what, where, when, why and how approach. This tried and true method has worked for countless people in many different areas forever. It can work in coding, too. Remembering that anything that doesn’t fit within those parameters is probably something you should not focus on for the time being is also important. It’s ok for you to say you don’t know and that you don’t want or need to know. I have personally found that writing our requirements for my coding assignments allows my brain a second and different way of processing what has been given to me. Drawing diagrams with details regarding functions helps me to begin to understand the complexities of my code in a more simplified manor.</p><p>Writing code that is truly simplified is something that requires repeated practice. While I am still working on writing programs that have been completely refactored and edited, I am slowly getting to the point where I feel completely comfortable going to simple route. Remember that always doing something that is easy prevents you from learning because you always do things that are near to your capabilities, and remember that cardinality does not result in simplicity or increased functionality.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=980582cfeb61" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Today, we read a very interesting blog post regarding some principles that will help us to create…]]></title>
            <link>https://medium.com/@cpr1988/today-we-read-a-very-interesting-blog-post-regarding-some-principles-that-will-help-us-to-create-75f92fddc1e7?source=rss-4228f25cb548------2</link>
            <guid isPermaLink="false">https://medium.com/p/75f92fddc1e7</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Colin Recko]]></dc:creator>
            <pubDate>Mon, 21 Mar 2016 13:38:04 GMT</pubDate>
            <atom:updated>2016-03-21T13:38:04.343Z</atom:updated>
            <content:encoded><![CDATA[<p>Today, we read a very interesting blog post regarding some principles that will help us to create better code. These five key principles, known by the acronym SOLID, were first created by two gentlemen named Bob Martin and Michael Feathers, and have become the five most important rules that guide engineers today to write code that is maintainable and efficient.</p><p>The first of these five is known as the Single Responsibility Principle. For me personally, this is the principle that I feel I most need to implement into my own code. It’s essentially the most basic, but also can be quite difficult to wrap your head around. Basically, this principle states that classes and methods should be simple enough that they only have one true responsibility. This is easy enough to understand, but can be quite difficult to put into motion. According to the article, anything that gives a class or method a reason to change can be viewed as a responsibility. They provided an example that used a program that processes deals for maybe a car dealership, and then calculated the commission that they salesperson would receive for that sale. Due to the fact that methods that maintain the deal probably would not change, but the commission could easily change due to differing amount of commission percentage, it makes sense to make the method that maintains the commission into a different class to separate it from the other methods.</p><p>The second of these principles is known as the Open/Closed Principle. This principle states that classes or methods should be open for extension, but closed for modification. This means we should be able to easy amend a program without having to do major overhaul on a class. They used an example that parses some information. The problem is that the code is too strict, and needs to be changed for different inputs. The goal of this principle is to used different techniques, such as the strategy pattern, to have code that keeps us in line with the Single Responsibility Principle, and to create more specific classes.</p><p>The third of these principles is known as the Leskov Substitution Principle. For me personally, this was the one that I had to read up about a bit more to understand. To actual definition states that objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program. But what does this mean? Basically, when we create a function in Ruby, it should be able to operate on all objects that are a certain type. That means that even objects that inherit from another object should be able to receive a function, and respond to it the same way that their parent would. The best example they gave was regarding the classic square/rectangle conundrum. A square is a type of rectangle, but it is not the same as a rectangle. A square should be able to receive the functions as a rectangle, and have them work. However, a rectangle may not receive a function in the same way as a square.</p><p>The fourth principle is known as the Interface Segregation Principle. To understand this principle, you must first understand duck typing. Duck typing is when within coding, we continue using methods that work for certain objects. We don’t need to continue to make new methods just because we have a new object. This refers to the classic “if it looks like a duck, and quacks like a duck, it’s a duck.” Basically, if an object can receive a method, and responds well to it, we don’t need to continue making more. Back to Interface Segregation Principle, with this new information in mind, we need to stop trying to label objects when we can make it easily do what we want through manipulation by method. Avoid using methods that are unnecessary, and can be a burden for engineers and users.</p><p>Lastly, we have the dependency inversion principle. This has to do with avoiding duplication and unnecessary coding. This principle basically states that low-level objects should be able to respond to high-level functions. Basically, having low-level objects that are amenable to code they inherit from higher level objects streamlines the coding process, and allows for clearer code.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75f92fddc1e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Impostor Syndrome]]></title>
            <link>https://medium.com/@cpr1988/impostor-syndrome-dd709c39ba32?source=rss-4228f25cb548------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd709c39ba32</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[impostor-syndrome]]></category>
            <dc:creator><![CDATA[Colin Recko]]></dc:creator>
            <pubDate>Mon, 14 Mar 2016 22:03:30 GMT</pubDate>
            <atom:updated>2016-03-16T13:14:28.554Z</atom:updated>
            <content:encoded><![CDATA[<p>My first day at the Iron Yard was one of complete panic. Before I came that day, I had naively thought that I had a decent level of understanding of HTML and CSS. I showed up, and listened to the morning lecture, and felt prepared to start that day’s assignment. Upon reading the directions, my heart fell deep into my stomach. I had no idea how to do the assignment. I didn’t even know where to start. I looked around the room, and noticed that seemingly everyone knew what to do, and how to do it. They feverishly typed away on their laptops, while I began to Google different topics hoping for some direction. I didn’t know anyone yet, so I was afraid to turn to my neighbors for help for fear of looking stupid. Little did I know, I was not the only one who was lost and confused. I also didn’t know that I actually did have some idea of how to do the assignment. I just needed to learn how to approach HTML/CSS projects.</p><p>This is classic case Impostor Syndrome. Impostor Syndrome is a psychological phenomenon in which people are unable to internalize their accomplishments. Basically, this means that people with this disorder are unable to recognize their own abilities, and have difficulty celebrating their successes because they focus more on their failures. In the coding world, having Impostor Syndrome is quite common. There are so many languages, and within each language, there are so many concepts that it would be nearly impossible to know everything. Often times, coders with this problem won’t share knowledge they have, collaborate, help with open source projects or apply for jobs that they may be qualified for. I can relate to this in a way. It’s scary to put yourself out there in a world where you don’t feel entirely sure of yourself. No one wants to seem ill-prepared or unintelligent. This poor internal barometer of your own skill set can be a huge detriment to your life.</p><p>On the other hand of the spectrum, there are people who overly inflate their abilities, and can often be a huge problem for someone to work with or be around. This is called the Dunning-Kruger Effect. The Dunning-Kruger Effect is a cognitive bias in which unskilled individuals suffer from illusory superiority, mistakenly rating their ability much higher than average. We all know that person who thinks they know everything, and in reality, knows nothing.</p><p>If you’re dealing with Impostor Syndrome, there are a couple of things you should remember in order to overcome and succeed. First, remember to surround yourself with people who will support you when you’re down, but also be real with you and provide with constructive criticism. Second, try to measure your success with realistic goals. Next, look for positives. You can find something positive in everything you do. Remember the small victories, and acknowledge the success of others. Fourth, keep the negativity away. Avoid negative people and negative thoughts, as they can only bring you down. Always help others. Also, remember that the people who are widely respected in the coding community started from zero, just like you. We have a tendency to build our heroes up into infallible mythological creatures, when in reality, they make mistakes and can write bad code as well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd709c39ba32" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Ask a Good Technical Question]]></title>
            <link>https://medium.com/@cpr1988/how-to-ask-a-good-technical-question-805fab858baa?source=rss-4228f25cb548------2</link>
            <guid isPermaLink="false">https://medium.com/p/805fab858baa</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Colin Recko]]></dc:creator>
            <pubDate>Wed, 09 Mar 2016 07:06:06 GMT</pubDate>
            <atom:updated>2016-03-09T07:06:06.755Z</atom:updated>
            <content:encoded><![CDATA[<p>In the event you haven’t seen Sasha Laundy’s speech Pycon 2015, click play on the video below. It’s actually a great presentation on how to be an effective employee and employer in the tech industry. In this video, she goes over a lot of different things about how to give and receive technical help. I want to focus on how you, as a newbie to the tech industry, should approach asking a technical question. Below, I will go over the five techniques Ms. Laundy explained during her presentation.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FhY14Er6JX2s%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DhY14Er6JX2s&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FhY14Er6JX2s%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/cc2d36ed0a46ac7431139624bf4bbcb9/href">https://medium.com/media/cc2d36ed0a46ac7431139624bf4bbcb9/href</a></iframe><p>First, she suggests choosing your place of employment carefully. Working in a negative environment is not conducive to learning or growth. This one is really quite simple. In order to be in a place where you will be ok to explore ideas and ask questions, make sure the people you surround yourself with are open to these possibilities.</p><p>Second, she suggests you ask questions early. It’s easy for you to try to weather a storm on your own, but putting off going for help will only hurt you in the long run. She gave an interesting anecdote about her own experience with delaying asking questions, and the negative impact it had have on her team as a whole.</p><p>Third, Mr. Laundy wants you to be competent. Experts like to help people who show that they have the drive and desire to learn, and also care enough to follow-up with them afterwards. Auditing the way that you present your question is a part of displaying competence. Instead of fumbling around your question, get straight to the point and don’t censor your feelings.</p><p>Fourth, she states that telling people what you need is so important. She gave a technique that she had great success with. She suggests telling people that you are 30% done with a project when going for feedback. By stating you’re farther along, they may just skim through your project without really analyzing it. Going for help with a lesser percentage of work done could result in your whole project being picked apart.</p><p>Fifth, you need to say what you’ve already done. By explaining what steps you’ve already taken, you help people understand what has or hasn’t worked for you. This will help them steer in the proper direction.</p><p>By following these five rules of thumb, you’ll be able to ask more effective technical questions, and grow as a developer and person.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=805fab858baa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ruby]]></title>
            <link>https://medium.com/@cpr1988/ruby-516d2c1f9c28?source=rss-4228f25cb548------2</link>
            <guid isPermaLink="false">https://medium.com/p/516d2c1f9c28</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ruby]]></category>
            <dc:creator><![CDATA[Colin Recko]]></dc:creator>
            <pubDate>Tue, 08 Mar 2016 14:50:35 GMT</pubDate>
            <atom:updated>2016-03-08T14:50:35.750Z</atom:updated>
            <content:encoded><![CDATA[<p>My first introduction to Ruby was back in January. I remember doing loads of research considering which coding language would be the best fit. Ultimately, what sold me on Ruby was a mentor I had from Thinkful. He told me, “Colin, if you want to code, why not have fun while doing so?” I thought this was an interesting statement to make on something that many people consider to be extremely difficult and overly complicated. The more I read about Ruby and its history, the more I began to understand that Ruby is designed in a very user-friendly way. Due to this, I never really felt overwhelmed during my initial introduction to Ruby. The basics are quite simple, and Why’s Poignant Guide does a great job of equating Ruby syntax to the English language.</p><p>Last week, I felt completely overwhelmed by HTML. I’ve spent the majority of my time spent coding so far focusing on Ruby basics to prepare for a code school. This week so far has been nice as I have a better idea of what I’m doing, and I don’t feel so lost in the fray. Why’s Poignant Guide does a great job of explaining why Ruby is more user-friendly than HTML/CSS. Most things in Ruby can be explained in a way that makes sense from the standpoint of an English speaker. It was designed in a way that makes it easy for us to understand.</p><p>I know in the coming weeks, Ruby won’t seem some simple and logical. I’m ready for the challenge. Bring it on, Ruby!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=516d2c1f9c28" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CSS Resets]]></title>
            <link>https://medium.com/@cpr1988/css-resets-c0ab81d0e56e?source=rss-4228f25cb548------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0ab81d0e56e</guid>
            <category><![CDATA[css]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[html-css]]></category>
            <dc:creator><![CDATA[Colin Recko]]></dc:creator>
            <pubDate>Fri, 04 Mar 2016 15:29:58 GMT</pubDate>
            <atom:updated>2016-03-04T15:29:58.481Z</atom:updated>
            <content:encoded><![CDATA[<p>When creating a website using HTML and CSS, the most difficult part is often styling. Getting the perfect font or perfectly placing an item within your layout can be extremely difficult, and part that can be due to the default stylings that your browser creates for you. Fortunately, there is a tool we can all use that allows us to essentially wipe the slate clean, and change the default CSS settings. This tool is called a CSS reset. A CSS reset is a line of code that you place at the top of your CSS styling sheet that allows you to change those default settings. This is beneficial because it allows website designers to create a website that will look the same across the border, no matter what browser is being used. One example of a default setting your browser sets is the color of hyperlinks. Most times, you will see hyperlinks colored blue. This is because blue is the default color. With a CSS reset, you would be able to change the color of all hyperlinks on your page simply by creating a line of CSS code instructing your browser to do so. CSS resets can get a bit tricky because we often will reset our default, only to change just one of those elements later. Due to this resetting , and then later resetting again, some people suggest not using CSS resets as it can get a bit confusing. As for me, I will probably avoid CSS resets for the time being. Until I am completely comfortable with my CSS abilities, it may be better for me to just avoid causing unintended interruptions as much as possible. :P</p><p>One week at the Iron Yard down! So many more to go!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0ab81d0e56e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>