<?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 John Daugherty on Medium]]></title>
        <description><![CDATA[Stories by John Daugherty on Medium]]></description>
        <link>https://medium.com/@JohnDaugherty?source=rss-f556cce65990------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*RBWCq623FFGFRPYS.jpeg</url>
            <title>Stories by John Daugherty on Medium</title>
            <link>https://medium.com/@JohnDaugherty?source=rss-f556cce65990------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:09:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@JohnDaugherty/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 necessary evil]]></title>
            <link>https://medium.com/@JohnDaugherty/a-necessary-evil-e55b90cbee9c?source=rss-f556cce65990------2</link>
            <guid isPermaLink="false">https://medium.com/p/e55b90cbee9c</guid>
            <dc:creator><![CDATA[John Daugherty]]></dc:creator>
            <pubDate>Wed, 17 Jun 2015 13:56:08 GMT</pubDate>
            <atom:updated>2015-06-17T13:56:08.416Z</atom:updated>
            <content:encoded><![CDATA[<p>Javascript is everywhere. It’s embedded into the internet so deeply that even people that have no idea about coding have probably heard of it. It’s everywhere you go online. It’s pretty much inescapable at this point.</p><p>This means it’s something any person who wants to communicate with machines needs to learn to do so. If coding is how we talk to computers Javascript is the best way to talk to web pages. Unfortunately Javascript is an entirely different beast than our beloved Ruby.</p><p>I’ve spent a lot of time gushing on Ruby and Rails because, why not? They are great communication tools. Javascript is also a great tool but it’s not nearly as intuitive as lots of either of those two.</p><p>Or is it?</p><p>While Ruby seems easy to read that’s more so due to the fact that someone purposely designed it that way. A lot of thought went into making Ruby a really readable form of code. Any time someone sits down with the express function of designing a really easy to read and useful langauge they are going to labor over it until it meets the vision they have. That’s how Matz wrote Ruby. That’s how Hickey came up with Clojure. So why is Javascript any different?</p><p>Javascript was developed by Brendon Elch at Netscape in 1995 to be a middleman between users and the internet. As the internet was taking off he took it upon himself to built “the assembly language of the web”. I really doubt that in 1996 Mr. Elch thought he was going to make the foundation for virtually all web pages that would exist after that but, hey, that’s software right?</p><p>So Brendon coded JavaScript in a mere 10 days. Not a lot of time to sit and think about the future of coding or what is going to happen down the road. However it was the perfect amount of time to make a language that works and works well. If that wasn’t the case we wouldn’t be talking about it right now.</p><p>As a result of these things Javascript is radically different than Ruby. For one Ruby is object oriented, which is moreso a way of thought and organization, as opposed to JS’ Dynamic programming, which means breaking things down to smaller sub problems and going through them one at a time. One isn’t better than the other per se but going from one language to another takes some getting used to.</p><p>In JS classes aren’t a thing. The way things get their properties is much more direct. Each function is a self contained world that is on it’s own. So no classes. Also no methods. JS has functions and functions are our “verbs” but they are really self contained and work different than methods do.</p><p>They will either sound confusing or make sense to you depending upon your background in computer programming.</p><p>Also no ends. Or we have endings but not actual “end”s and now they are semicolons. So yes. Semicolons everywhere!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FM94ii6MVilw%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DM94ii6MVilw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FM94ii6MVilw%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/98a2d01bf5bdd294fa8021bd708bd959/href">https://medium.com/media/98a2d01bf5bdd294fa8021bd708bd959/href</a></iframe><p>I could go on and on about the differences and pick apart all the things that challenge my thoughts but I don’t really gain much from that. I’d rather focus on similarities. For a very funny take on programming language quirks I suggest this talk <a href="https://www.destroyallsoftware.com/talks/wat">https://www.destroyallsoftware.com/talks/wat</a>. It brings up a lot of JavaScript’s “features”.</p><p>Let’s talk about Abstraction. Good code should rely on it. The language you choose shouldn’t make a huge difference as long as it gives you the tools to use abstraction and JS does a good job of insuring you can.</p><p>That brings me to the actual words in the language. JS has a really similar set of words it uses to solve the same problems all other languages face. It maps, reduces, it does all kinds of stuff.</p><p>So in the end there are some differences but there’s also a lot of similarities. So conceptually they have similar end games it’s just the routes they take to get there that are different.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e55b90cbee9c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Surrender to the Flow]]></title>
            <link>https://medium.com/@JohnDaugherty/rails-fd43bed48ad1?source=rss-f556cce65990------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd43bed48ad1</guid>
            <dc:creator><![CDATA[John Daugherty]]></dc:creator>
            <pubDate>Mon, 01 Jun 2015 18:28:53 GMT</pubDate>
            <atom:updated>2015-06-01T18:58:23.156Z</atom:updated>
            <content:encoded><![CDATA[<p>Simple, pain free, no fuss. Ruby is a lot of things that make a developer’s life easier. Making a coding language readable by the average person is incredible accomplishment. Every language has advantages over other languages so Ruby isn’t the best language; it’s just great for easy communication.</p><p>Other languages have their advantages as well. PHP, .NET, and many others all have their place in the ecosystem. They have their quirks as well.</p><p>When <a href="http://en.wikipedia.org/wiki/David_Heinemeier_Hansson">David Heinemeier Hansson</a> was building <a href="https://basecamp.com/">basecamp</a> in 2004 he needed a way to deploy a web application simply and effectively. He had used PHP but felt like it was too repetitive and bogged down by unneccessary details. In Ruby he found the language that he needed. In addition to being readable, uncluttered, and capable of extraction, Ruby had the added plus of Gems. With a vibrant culture and large amount of resources already available Ruby seemed like the perfect language for this project.</p><p>As he created Basecamp, Hansson began building a framework and library of tools that would make deploying web apps with Ruby more simple. These came to be known as Rails.</p><p>Ruby on Rails has since grown to become one of the more popular ways to write web applications available today. In the span of ten years Hansson’s project has changed the shape of the development realm.</p><p>This is because Rails follows the same rules of thought that Ruby does. It makes things easier to get off the ground and it’s an excellent way to quickly deploy seemingly complex applications. For the developer that values his time and enjoys a huge array of resources it’s an excellent language to learn.</p><p>Ruby’s built in framework standardizes the approach to things like email and html writing and a number of other things. This is great because other coding languages had not taken the effort to standardize them yet. If you’re a good developer, of course you can read and modify code how you see fit but by having everyone on the same page has it’s advantages as well.</p><p>Realizing that what the world needed was a uniform and less cluttered approach to web application development, Hannson set to work on establishing a set of Rails standards and guiding principles. Soon developers everywhere were seeing the benefits as the language blossomed.</p><p>By having a uniform layout it makes communicating with other developers much easier. The only caveat that happens when having something uniform is we give up things that make us stick out. Yes, Rails still allows for programmers to let their personalities to shine through but, unlike other languages, Rails has things to say.</p><p>Chances are if you know any rednecks or sadistic feline haters the phrase “there’s more than one way to skin a cat” has popped up. This means there’s several ways to get the same outcome. It also means that poor cat is dead.</p><p>A moment of silence for Mr. Whiskers</p><p>Many other languages are pretty blase about how to get from A to B. That’s one of th great things about coding is that the possibilities are pretty much endless when it comes to the actual code we write to get the results we want. The disadvantage of that is that it’s hard to get everyone on the same page if we can’t just nail down some basics.</p><p>Rails has preferences when it comes to certain things. It has opinions. It has wants and needs. It has an idea of what’s best.</p><p>Best might be subjective but Rails is a language that knows what’s best for you and for the software. It’s like the overbearing mother of the programming world. You can not listen to it and still do fine but you will probably wind up wishing you had gone with what it said the whole time.</p><p>Hannson famously declared Rails as Omakase. A Japanese phrase meaning “I’ll leave it to you.” Omakase means trust in the person who developed it that they have your interests at heart. He expounded on this thought by say</p><p>“A team of chefs picked out the ingredients, designed the APIs, and arranged the order of consumption on your behalf according to their idea of what would make for a tasty full-stack framework…. When we, or in some cases I — as the head chef of the omakase experience that is Rails — decide to include a dish, it’s usually based on our distilled tastes and preferences. I’ve worked in this establishment for a decade. I’ve poured well in the excess of ten thousand hours into Rails. This doesn’t make my tastes right for you, but it certainly means that they’re well formed.”</p><p>These ideas are at the heart of Rails. You have to surrender to the flow if you choose Rails as the language for you. It will make things go a lot faster and make your job a lot easier.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd43bed48ad1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A solid foundation]]></title>
            <link>https://medium.com/@JohnDaugherty/a-solid-foundation-16aa8df55f1e?source=rss-f556cce65990------2</link>
            <guid isPermaLink="false">https://medium.com/p/16aa8df55f1e</guid>
            <dc:creator><![CDATA[John Daugherty]]></dc:creator>
            <pubDate>Mon, 25 May 2015 19:21:35 GMT</pubDate>
            <atom:updated>2015-05-25T20:31:49.269Z</atom:updated>
            <content:encoded><![CDATA[<p>Now that I’ve established the importance of communication and how coding is just man interacting with computer, I’d like to address standards. Standards are much more important in the coding world than in the traditional world. Most of us grew up speaking English or whatever our native tongue is so the it’s a lot easier to play fast and loose with the first langauge we learned. We can use slang in English.</p><p><a href="http://www.urbandictionary.com/define.php?term=nah+mean&amp;defid=16983">Nah mean?</a></p><p>Chances are if you are a native English speaker that “nah mean” had some significance for you. If not, no big deal, sometimes when we communicate with other people we run into issues. The same thing happens when we communicate with computers.</p><p>Computers just know what we tell them to know. They operate based on guidelines we set. When we are working with an Object Oriented Programming language like ruby we need to adjust accordingly</p><p>I hope I’m not jumping to conclusions by saying there is a 100% chance you didn’t come out of the womb speaking Ruby. Chances are, like everyone else, you learned to code after your learned to speak.</p><p>That’s why standards are important.</p><p>Adhering to a set of guidelines when coding is going to eliminate a lot of potential confusion. A current approach to eliminating any possible confusion and making sure everyone is on the same page is SOLID.</p><p>SOLID is five different principles that really nail the benifits of OOP. It’s a set of guidelines developed by <a href="http://en.wikipedia.org/wiki/Robert_Cecil_Martin">Bob Martin</a> and <a href="https://twitter.com/mfeathers">Michael Feathers</a> that help engineers write maintainable code. A lot of the names sound kind of intimidating but conceptually they all just establish that we don’t waste time and write the most practical code possible.</p><p>Solid stands for the following:</p><ul><li>S — <a href="http://en.wikipedia.org/wiki/Single_responsibility_principle">Single Responsibility Principle</a></li><li>O — <a href="http://en.wikipedia.org/wiki/Open/closed_principle">Open/Closed Principle</a></li><li>L — <a href="http://en.wikipedia.org/wiki/Liskov_substitution_principle">Liskov Substitution Principle</a></li><li>I — <a href="http://en.wikipedia.org/wiki/Interface_segregation_principle">Interface Segregation Principle</a></li><li>D — <a href="http://en.wikipedia.org/wiki/Dependency_inversion_principle">Dependency Inversion Principle</a></li></ul><p>Although that might seem like a somewhat intimidating list of words it’s not nearly as bad as it sounds. All of this stuff just boils down to really simple ways to write usable code. While I admit that I was pretty intimidated by SOLID at first, I realize that, as of this current moment, it’s the best approach to writing OOP. It gets everyone on the same page. It might seem like a it’s a pretty big undertaking and not immediately beneficial but it insures everyone that practices it is writing readable, practicle code that others can dive into without having to fudge around with it too much.</p><p>So now that we’ve established a solid, pun intended, way to approach OOP let’s go over each of the methods shall we?</p><p>Single responsibility is an idea that means we don’t want to make our classes and methods highly specified right out of the gate. They should be focusing on a single thing.</p><p>We want our code to be able to be as functional as possible and by writing really specific methods and classes it degrades the codes ability to scale up.</p><p>We have to look at the big picture.</p><p>Our code should be scalable. We shouldn’t have to refactor the entire code because we change a small element.</p><p>We are making things easier for ourselves in the long run.</p><p>The open/close principle means our classes or methods should be open for extension but closed for modification.</p><p>This, again, is just another way of emphasizing that our code should be modular and not really specified. Making your code capable of doing more things without making it unnecessarily complex is the name of the game.</p><p>This brings us to the Liskov/Substitution principle. If that name sounds as intimidating to you as it did to me then we’re on the same page. If not, congrats on your familiarity with naming principles. The “Liskov” refers to Barbara Liskov, who introduced the concept in the late 80&#39;s. Substitutability means:</p><p><em>Let Φ(x) be a property provable about objects x of type T. Then Φ(y) should be true for objects y of type S where S is a subtype of T.</em></p><p>or:</p><p>“if <em>S</em> is a subtype of <em>T</em>, then objects of type <em>T</em> in a program may be replaced with objects of type <em>S</em> without altering any of the desirable properties of that program.”</p><p>This approach to coding is going to save us a lot of headache in the long run. By not making things highly specified we are able to use them more liberally if need be. We don’t want to go and write new code all the time. We want the original code we write to be able to be used again and again for different purposes.</p><p>It is indeed a pretty intense concept. I really struggled with it originally but after reading a lot more about it really came to appreciate the genius of it. It’s just a way of streamlining the language and optimizing our means of communication.</p><p>for a much more detailed take on the Liskov/Substitution principle, including a very nice breakdown with several code examples I suggest <a href="http://www.objectmentor.com/resources/articles/lsp.pdf">http://www.objectmentor.com/resources/articles/lsp.pdf</a>. If anyone has a better resouce on the subject feel free to comment.</p><p>The interface-segregation principle states that no client should be forced to depend on methods it does not use. By adhering to this principle we are assuring that our code will be as usable as possible. we don’t want to go writing new code over and over again. We want a solid foundation of code that we can use as much as possible. If our code depended on methods it didn’t use we’d be wasting time writing more code each time we wanted to deploy another idea that used the same concepts.</p><p>The dependency inversion principle touches on the same ideas as the rest but has a more apparent and immediate use. It states:</p><p><em>A. High-level modules should not depend on low-level modules. Both should depend on </em><a href="http://en.wikipedia.org/wiki/Abstraction_(computer_science)"><em>abstractions</em></a><em>.</em></p><p><em>B. Abstractions should not depend on details. Details should depend on abstractions.</em></p><p>This is just another way of dictating that our code won’t become useless as we build upon it. By not depending on details and instead depending on abstractions we insure that this is the case.</p><p>As software developers we should strive to make our interactions with other developers and computers as easy as possible. Adhering to the SOLID principles insures this. If we follow these rules it insures that we don’t write extraneous code and that others who use our code can do so without having to rewrite the basic functionality of it. Coding itself is already a lot to take on, why make it any more difficult?</p><p>If you visit <a href="http://manifesto.softwarecraftsmanship.org/">http://manifesto.softwarecraftsmanship.org/</a> you can see these thoughts layed out more directly.</p><p><em>5/25/2015: This post will be edited as new information is added.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16aa8df55f1e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moving Forward]]></title>
            <link>https://medium.com/@JohnDaugherty/moving-forward-b081c8126961?source=rss-f556cce65990------2</link>
            <guid isPermaLink="false">https://medium.com/p/b081c8126961</guid>
            <dc:creator><![CDATA[John Daugherty]]></dc:creator>
            <pubDate>Thu, 21 May 2015 12:44:29 GMT</pubDate>
            <atom:updated>2015-05-21T12:44:29.148Z</atom:updated>
            <content:encoded><![CDATA[<p>One thing I love about coding is the culture. It is a culture that is typically focused on improving and moving forward. “How can we make this make more sense?”, “how can we streamline this?” and “how can I improve” are common thoughts among coders. A lot of people get stuck doing what is comfortable and don’t think about doing things differently once they have learned how to do them. If coders stuck to their guns we would still be using punch cards or writing in COBOL. If we didn’t have the desire to improve I’d still be mucking around with visual basic and html. Our beloved Ruby wouldn’t exist.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/355/1*LXyFjTQiOR3AbSs0NCgL_w.jpeg" /><figcaption>Imagine if we just settled for this instead of trying to improve things.</figcaption></figure><p>Fortunately that’s not the culture of coding and we have brilliant people that push us forward. It’s a theme of my life and it’s a theme among certain coders that I strongly identify with.</p><p>in 2011 Rich Hickey gave a talk about his language, Clojure, that went into the ideas behind why we want to create new languages. While the talk was primarily about Clojure, the ideas were practical and universal and can be applied to a lot of other aspects of life. In case you haven’t noticed I really enjoy relating coding to more universal themes. Coding is a way of life and an approach to problem solving. Once one begins to think like a coder a lot of the issues we face in day to day life seem easier to manage.</p><p>More in part 2.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b081c8126961" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Overcoming Imposter Syndrome]]></title>
            <link>https://medium.com/@JohnDaugherty/overcoming-imposter-syndrome-838708d2095e?source=rss-f556cce65990------2</link>
            <guid isPermaLink="false">https://medium.com/p/838708d2095e</guid>
            <dc:creator><![CDATA[John Daugherty]]></dc:creator>
            <pubDate>Wed, 20 May 2015 02:18:03 GMT</pubDate>
            <atom:updated>2015-05-20T23:42:00.962Z</atom:updated>
            <content:encoded><![CDATA[<p>Imposter syndrome in any career field is just like the imposter syndrome a lot of people feel when becoming an adult. As a child I would look up to people like my father, my principle, my friend’s cool older brother, and Atlanta Braves pitcher John Smoltz and think “man, they really have it together. I can’t wait til I’m an adult!” only to realize the truth. My dad had no idea what he was doing, my principle was faking it, and my friend’s older brother was still living with his parents at 25. John Smoltz probably kind of knew what he was doing but I’m sure he had feelings of self doubt as well.</p><p>That’s the thing about life. You will always not know a lot more than you know. It’s pretty much impossible to know everything. The greatest thing a person can do as an adult is realize that they don’t know everything and be fine with that.</p><p>Once most junior developers start out they get overwhelmed with the realization that there is loads that they don’t know. This leads to the previously mentioned imposter syndrome.</p><p>Yes, most junior developers don’t know everything. No, that doesn’t mean they are terrible or not developers; it just means they are starting off.</p><p>Everyone starts somewhere.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FDN43sCyEanA%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DDN43sCyEanA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FDN43sCyEanA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/fe8d50365cea8684066d296c682b2518/href">https://medium.com/media/fe8d50365cea8684066d296c682b2518/href</a></iframe><p>The key is to not sabotage the mind with negative thoughts. Nobody is saying overcompensate by acting like a knowitall but instead be comfortable with the learning process and open to taking in as much as possible. Never get bogged down by feelings of self doubt or other toxic behaviors.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=838708d2095e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Celebrate Communication Cont.]]></title>
            <link>https://medium.com/@JohnDaugherty/celebrate-communication-cont-4de79b5d9a69?source=rss-f556cce65990------2</link>
            <guid isPermaLink="false">https://medium.com/p/4de79b5d9a69</guid>
            <dc:creator><![CDATA[John Daugherty]]></dc:creator>
            <pubDate>Wed, 20 May 2015 01:55:57 GMT</pubDate>
            <atom:updated>2015-05-20T23:55:10.038Z</atom:updated>
            <content:encoded><![CDATA[<p>After addressing a lot of the social misdeeds people commit Sasha Laundey went on to address several ways to ask better questions. She brought up a list of several simple ways to better communicate that should help anyone seeking to learn.</p><p>While everyone doesn’t have the liberty to just quit where they work they hopefully do have the opportunity to surround themselves with more positive influences. It’s no secret that being around negativity has it’s downsides, but it’s actual toxicity is a much bigger issue than simple annoyance.</p><p>A group with poor culture isn’t going to bolster anyone’s creativity or desire for improvement. Poor attitudes begit poor attitudes, so it’s best to surround oneself with others that encourage learning and growing. Whether it’s taking a class, attending a meetup, or just finding others to spend time with, having a good team on your side makes all the difference in the world.</p><p>The next way to overcome obstacles is to ask early. The longer one spends time on something with no breakthroughs the more of a challenge it becomes. It’s very easy to spend far too much time on something and end up exasperated. You can tread water for as long as you’d like, but eventually your arms will get tired.</p><p>People can go for their entire lives without realizing how poorly they are doing conveying their desires to other people. When someone has trouble efficiently asking basic questions it creates more work for both the person asking the question and the person being asked.</p><p>I have grown up with parents that suffered from this type of behavior to a frustrating degree. In fact pretty much every member of my family tends to do things that make communicating more challenging.</p><p>I remember my father asking me for a rake when I was a child and him being disappointed when I brought back the wrong rake. He told me to get the other rake and was once again disappointed when I returned with another, also wrong, rake.</p><p>In my father’s eyes’ I was a wiseass who was doing everything in my power to keep our lawn covered in leaves but in reality I was just a confused seven year old who didn’t understand my dad’s proclivity for maximum rake efficiency.</p><p>The best way to get results is to be specific about your needs. Nobody knowledgeable is going to be able to help you with a“syntax error” just like no seven year old is going to know which rake you are talking about. My family had around six rakes; there’s an unlimited number of possible syntax errors.</p><p>In addition to being specific about one’s desires, another way to maximize the benefit of your potential answers is to say what you’ve done already. Establishing where you stand, what you’ve tried, and how you believe you should continue is a great way to insure that anyone helping you is on the same page.</p><p>Simply saying “what should I do?” is not a great way to get help. Communicating the exact nature of the problem you’re facing and how you got there is. Coding, like life, is about context. Doctors need to give you an examination. The bartender needs to know if you like IPA’s or Pilsners. Duane Johnson needs to know if you can smell what the rock is cooking.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FMr8glaM4ruM%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DMr8glaM4ruM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FMr8glaM4ruM%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4cf70854b194e4bcf2fc44f6d274f517/href">https://medium.com/media/4cf70854b194e4bcf2fc44f6d274f517/href</a></iframe><p>Learning to ask questions effectively is going to save all parties involved a lot of unnecessary time. Turning good questions into a habit is one way to insure you&#39;re getting the information you need to improve.</p><p>Life is going to be filled with interactions that can be much smoother if we follow some basic principles. Not being a jerk, articulating oneself as best as possible, and asking good questions are just some of a few steps we should all take in order to communicate effectively.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4de79b5d9a69" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Celebrate Communication]]></title>
            <link>https://medium.com/@JohnDaugherty/celebrate-communication-515159a30e51?source=rss-f556cce65990------2</link>
            <guid isPermaLink="false">https://medium.com/p/515159a30e51</guid>
            <dc:creator><![CDATA[John Daugherty]]></dc:creator>
            <pubDate>Tue, 19 May 2015 02:53:43 GMT</pubDate>
            <atom:updated>2015-05-19T03:07:08.057Z</atom:updated>
            <content:encoded><![CDATA[<p>Learning coding is basically rewiring your brain. When one begins learning a new language one must fundamentally alter how he perceives the text in front of him. As one opens up these new neural pathways and begins to exercise that part of the mind it’s important to let our thought patterns change to reflect our new knowledge.</p><p>Before getting into coding I know I had a lot of problems with adequately conveying my thoughts to other people. I also had some habits that were not conducive to a positive learning environment. As I’ve made the journey towards learning more and more I’ve come to learn the error of my ways and I’m working on doing my best to communicate the best way possible.</p><p>Sasha’s lecture resonated with me because it echoes a lot of the things I already believe and made me realize some things I hadn’t yet thought of. Her stance on not being a jerk is something I’ve tried to stick to once I became aware of how much jerklike behavior irritated me. A lot of these behaviors aren’t intentional because we as a society have fostered this type of behavior for generations but they are nonetheless very real and very very off putting. I cannot reiterate how not helpful and annoying it is for someone to say “oh you didn’t know that?” or a “well actually,”. That behavior is childish and entirely inappropriate for a learning environment. Nobody likes a knowitall and nobody likes smug people.</p><p>I don’t really blame the people that do these things because most people aren’t aware how detrimental these expressions can be. Most people aren’t aware “oh you didn’t know _____” is pointless until you respond, “yes, that’s why I asked.”</p><p>But aside from the irritating social faux paus that bog down our interactions the other ways Sasha brought up improving our communication were great as well.</p><p>I will be implementing her advice from here on out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=515159a30e51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ruby is a language for the people]]></title>
            <link>https://medium.com/@JohnDaugherty/ruby-is-a-language-for-the-people-c59fb8237164?source=rss-f556cce65990------2</link>
            <guid isPermaLink="false">https://medium.com/p/c59fb8237164</guid>
            <dc:creator><![CDATA[John Daugherty]]></dc:creator>
            <pubDate>Sat, 16 May 2015 17:50:31 GMT</pubDate>
            <atom:updated>2015-05-16T23:27:08.016Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the things that make it difficult to break into coding is the fact that coding languages can feel almost impenetrable. Many languages seem cryptic upon first glance and the idea of having to decode them seems daunting.</p><p>Ruby is not one of those.</p><p>In it’s essence ruby is a language that is built for convenience and ease of use. It’s practical. It reads well. It eschews bulk and unnecessary details in favor of making a coding language that feels almost human. In our effort to speak with computers humans have consistently been bent at the force of these machines only to spit out language that is lost to the average reader.</p><p>Fortunately Ruby is not that way.</p><p>Upon first inspection simple lines of Ruby are fairly straightforward. Sure the syntax is different from traditional English and it’s obviously code but the essence of communication is definitely there.</p><p>Ruby is favorable compared to a lot of other languages for these reasons. The fact that Ruby is so user friendly makes it a great language to explore the possibilities of programming. It’s not often we encounter languages that seem to welcome those not already engaged in the programming nomenclature but Ruby does exactly that.</p><p>Ruby is a straightforward language that I look forward to using.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c59fb8237164" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week one]]></title>
            <link>https://medium.com/@JohnDaugherty/week-one-106fb6a49576?source=rss-f556cce65990------2</link>
            <guid isPermaLink="false">https://medium.com/p/106fb6a49576</guid>
            <dc:creator><![CDATA[John Daugherty]]></dc:creator>
            <pubDate>Mon, 11 May 2015 00:58:51 GMT</pubDate>
            <atom:updated>2015-05-11T00:58:51.096Z</atom:updated>
            <content:encoded><![CDATA[<p>I have just completed the first week at The Iron Yard. It was extremely fun and I learned a lot not only about coding but about myself as well.</p><p>I am looking forward to the challenges I will be facing next week.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=106fb6a49576" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>