<?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 Alec Bridge on Medium]]></title>
        <description><![CDATA[Stories by Alec Bridge on Medium]]></description>
        <link>https://medium.com/@AlecBridge?source=rss-19188e6cdb83------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*_57a9PQsT0iECtMR.jpeg</url>
            <title>Stories by Alec Bridge on Medium</title>
            <link>https://medium.com/@AlecBridge?source=rss-19188e6cdb83------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:10:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@AlecBridge/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[Learning A to Z CSS:]]></title>
            <link>https://medium.com/@AlecBridge/learning-a-to-z-css-608af850cdfa?source=rss-19188e6cdb83------2</link>
            <guid isPermaLink="false">https://medium.com/p/608af850cdfa</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Alec Bridge]]></dc:creator>
            <pubDate>Wed, 15 Jun 2016 03:31:14 GMT</pubDate>
            <atom:updated>2016-06-15T03:31:14.772Z</atom:updated>
            <content:encoded><![CDATA[<p>Upon reviewing the A to Z CSS series (<a href="http://atozcss.com/start-here/">atozcss.com</a> for class) at The Iron Yard, I don’t feel like the terms and the uses stuck with me as much as I thought they would’ve. Though I am a visual learner, I also need the hands on experience to make the ideas stick. Along the great series though, I did notice a couple recurring themes and bigger picture ideas that were oddly refreshing. A few of which I will discuss briefly below.</p><p>(As a disclaimer I don’t consider myself a “coder” yet, though that is an ultimate goal- everything here to be taken with a grain of salt!)</p><h4>1.) Get Particular</h4><p>Style is a little bit unique to each individual when it comes to fashion. The same could be said about coding to some extent, though I noticed the theme of “keeping the code lean” vs messy. Which makes perfect sense in the greater picture, less confusing and easier to read for all should be the norm. There was another part where he even mentioned how he tries to avoid styling id’s if he can exclusively use classes he will. That is because they override less, letting you get more particular in what you are trying to accomplish anywhere in the CSS. From what I can tell this seems to be a recurring trend from some of the limited code i’ve seen so far.</p><h4>2.)User Knows Best</h4><p>Though it is great knowing all the fancy things you can do to make an extravagant site, it isn’t always the best idea to go for all of the bells and whistles. Unless of course thats the specific goal, then by all means fire away. A bad user experience is somewhere you don’t want to find yourself, because that in turn means there was a breakdown of what you wanted from your code and what the goal was. Throughout life I have always followed the good old “K.I.S.S” principle, or Keep It Simple, Stupid. If your objects/page doesn’t flow easily through itself, you may want to consider changing something up a bit.</p><h4>3.)Find A Way</h4><p>The last major idea I noticed throughout the series was that code though going through a computer (binary) can seem a bit fluid. Possibly a better word from fluid would be free, as in there are multiple ways to get the same result. It is up to you to figure out what works best for you and your user experience so that there are no holes in your code and site breaking bugs. Though I currently am not well versed, I am sure there are certain exceptions to this rule as well, an un-written law of coding that I currently do not know.<br> — And thats what excites me, the fact that I don’t know. That leaves room to learn and figure it out along the way, and after the course and maybe even a few years down the line to take a look back and see if I still agree 100% with what I came up with here from learning my A,B,C’s.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=608af850cdfa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning to Code: Day 0]]></title>
            <link>https://medium.com/@AlecBridge/learning-to-code-day-0-3ae49958a98a?source=rss-19188e6cdb83------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ae49958a98a</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Alec Bridge]]></dc:creator>
            <pubDate>Wed, 08 Jun 2016 20:07:52 GMT</pubDate>
            <atom:updated>2016-06-08T20:07:52.980Z</atom:updated>
            <content:encoded><![CDATA[<p>To say that this is “Day 0” of learning to code is a bit of a lie. It is a lie because technically I have spent quite a few man hours over the course of a couple months practicing the very basics of HTML and JS. Doing so to help rekindle the love of coding I had back in High School and in preparation for enrolling at The Iron Yard starting next week here in MN. Upon reviewing the materials and prerequisite work I’ve already learned more about the field and the idea of learning than I had anticipated. With that being said, here is a quick list of what I’ve already taken to heart and helped me most in learning not only to code but also to grow.</p><h4>1.) It is Okay to be Wrong:</h4><p>It is hard for me to admit, but I have been known to be a bit of a perfectionist. I don’t know where it comes from whether it is something ingrained from society, my upbringing, or just my personality in general but I can’t help it. I am used to treating everything black and white, where being right = good and being wrong = bad. Learning to admit a fault is a good character trait to have and in coding as I’ve picked up from Sasha Laundy’s “<a href="https://www.youtube.com/watch?v=hY14Er6JX2s"><em>Your Brain’s API</em></a>” it has helped me stop from feeling down about a failed section of code and look at it as a chance to learn instead of a chance to be frustrated. To say that and to think someone will magically stop being frustrated trying to work out a problem isn’t accurate but it has definitely helped me take all my mistakes with a grain of salt and not be as hard on myself and even others in the past.</p><h4>1.5) No One is Perfect:</h4><p>In addition to it being fine for me to make mistakes but it is for others as well, including instructors and “experts” in the field and who already code for a living. Starting this journey in my mind’s eye for some reason I pictured it as one universal way of solving <em>X</em> and once it is learned it is no different than typing this very article. I couldn’t have been more wrong, and that was made apparent when I went on a job shadow with my brother <a href="https://medium.com/u/4981c1cec4af">Ryan Bridge</a> to his work at Software For Good. That’s where I was first introduced to Git and the idea of taking on part of a project then bouncing it off of someone else for review. Where your idea may have done the job just fine (or not) but there is an alternative and cleaner way of doing the exact same thing that you didn’t think of before. Needless to say this field is a big example of working as a team which I look forward to.</p><h4>2.) It Takes Time:</h4><p>Sounds a bit self-explanatory I know, but it may be bigger than you think. To think that maybe you could take a course online, or a 3 month long coding bootcamp would make you into an expert know-it-all doesn’t do this field of work any justice. Beside the fact it takes time to learn any of the coding languages, the fact that they are always evolving and changing ends up making this a commitment to learning. For all we know what we are learning or have learned may even become obsolete in either the near or distant future is both exciting and a bit frightening. As the saying goes, “nothing great happens overnight” which couldn’t be more true here. Which was made very clear to me after watching the series “<a href="https://vimeo.com/84022735"><em>The Long Game</em></a>” about DaVinci and how there were plenty of years where the Art History seems to not mention too much, of how there are times when even the greats were considered not so greats.</p><p>In the end, most of this is probably either painfully obvious or just simply cheesy..regardless I feel like it is important to put into words and put thought into action. Keeping these things in mind has already improved my experience working through some of Codecademy’s courses too. I say improved because at times it would become unclear what they are looking for in the lesson, and ended up as just trying to find a work-around for the problem at hand. Which ends up not teaching the proper way of coding but helped teach me to learn in general. If I leave you with one thing from all of this I hope that it is to — Never Stop Learning.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ae49958a98a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>