<?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[Fear and Coding - Medium]]></title>
        <description><![CDATA[Thoughts, Rants and Discussions about Code - Medium]]></description>
        <link>https://medium.com/fear-and-coding?source=rss----39e7bbfe62ab---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*V6fV_nTPxkLuJvPn.jpeg</url>
            <title>Fear and Coding - Medium</title>
            <link>https://medium.com/fear-and-coding?source=rss----39e7bbfe62ab---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 06:31:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/fear-and-coding" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[!Library Junkie]]></title>
            <link>https://medium.com/fear-and-coding/library-junkie-144057ab6ca9?source=rss----39e7bbfe62ab---4</link>
            <guid isPermaLink="false">https://medium.com/p/144057ab6ca9</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[angularjs]]></category>
            <category><![CDATA[libraries]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Shaun D]]></dc:creator>
            <pubDate>Tue, 22 Aug 2017 09:23:14 GMT</pubDate>
            <atom:updated>2017-08-22T09:23:13.580Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the last few weeks I’ve had the task of attending interviews at a whole wide range of companies, from the small start-ups setting out to disrupt an industry, to the big</p><p>corporations who have 100s of developers on board churning out a wide range of applications. I will admit that it’s not my favourite thing to do, interview that is, but it is always interesting to see what companies are doing.</p><p>One thing that is probably pretty obvious to most people by now, especially if you’ve been a developer in the market any time in the last few years, React dominates. I’ve got an expansive spreadsheet where I have kept a log of every role I have been put forward for or applied for and React takes up a good 80% of it. Its not a comprehensive overview of every job that is out there, but it is one that I think very well represents the developer job market in the UK, especially in London.</p><p>In the past 10 years I have seen frameworks and libraries come and go. Like many developers I know, I got my start with jQuery and to be a front end developer a few years ago, this was about all you needed to land a job in an ad-agency or equivalent circa 2009. That might not be true for 100% of places, but thats what I recognised back then. If you could write you’re own jQuery plugins or a very small library that had a dependency on jQuery, you were in. There were, of course, much larger libraries at the time, ones that were more like frameworks, but very few people dove into them.</p><h3><strong>Library Junkie</strong></h3><p>I consider myself a pretty generalist developer. I’ve used at some point most of the popular libraries and frameworks in both personal and client projects. I have bits that I like about them all — I like the opinionated and standards based approach of Ember, I like using Typescript by default on Angular and I like the simplicity of React — and I think in some places they all have their drawbacks, but the one thing that I don’t do is attach myself to a library. Im not a {React, Angular, Ember} Developer, Im just a developer who happens to have worked with all these tools. A blacksmith doesn’t specialise in just using a single hammer or a technique — they might be better with the power hammer than they are with the grinder, but they never <em>*just*</em> use the single tool — I might drag this analogy on for a fair bit, but I think you get the point.</p><p>Its become clear that many companies ( and the developers within ) have become so attached to a particular library or framework, so much so that they have the blinders on when it comes to hiring new people. Don’t mistake this criticism for being sour about not getting a particular role, on the contrary, I don’t think I would get on too well inside that company. One of the questions I always ask in either a telephone interview or a face-to-face one is “Why did you pick [Framework/Library]”. Usually the answer is “Because it was the best one suited to what we needed to deliver” but without much supporting evidence to back that statement up. I usually follow that up with “What have been the challenges using [Framework/Library]?” and more times than none met with silence. Nobody wants to point out their weakness’, I get that, but I find it hard to believe that anything is perfect in a project.</p><p>On many occasions I didn’t get the role because I was too much of a generalist, this was genuine feedback from at least 6 roles ( another 2 sort-of gave that feedback, but danced around the wording ). Im OK with that, in fact after getting that same feedback from 2 interviews, I began to start interviews like that, just to make it clear. I also went into a bit of a talk as to why I think its important not to be. I’ve seen far too many developers get stuck with a particular framework, programming language etc and then find themselves ‘feeling’ behind when a new hotness comes along. Its literally a running-joke within Web Development that not a day goes past without some new framework being the one to rule them all, that I wonder what happens when everyone eventually and inevitably moves away from React. Tying myself to a single library just isn’t in my nature and whilst there was a fair few jobs that I didn’t get because I wasn’t a library junkie, I don’t intend on changing that.</p><h3><strong>Fully stacked</strong></h3><p>Its been a fair few years since I started regarding myself as a Full Stack developer, despite most of my actual ‘paid’ work being as a Front End developer. Full stack seems to mean a lot of different things to people. For some it just means that I can write server-side code as well as client side. For a few it simply meant that I could write the Full Stack for the client side (HTML. CSS, JS) along with some build tools. Full Stack, to me means all of these things in addition to some dev ops. I strongly believe that for any half-decent sized project, a devops is required purely to take care of everything they can do — they can whip around AWS CLI much fast than I can navigate endless menus in the browser — but I have always found that a project can move faster if there are some developers who are able to easily articulate to the devops person what is required, the smoother the project will run, also if the devops person isn’t available, all hell wont break loose.</p><p>I don’t use the term Full Stack developer in order to demand a higher salary, I use it so that someone who might be interested in hiring me knows exactly what they are getting. They don’t have to hire me for a full stack role, I am more than happy to work on either the client or the server, but they will have the knowledge that I am able to work across the stack and potentially help in any of those areas.</p><p>However, it appears that recently this has held me back from getting roles. Some additional feedback I had received had been that the employer worried that I might be bored just doing Front End development and not have the opportunity to work on the server side. This has been the feedback on more than one occasion, so much so that I have actually considered removing it from my CV, either that or having a few variations of my CV to be used.</p><h3><strong>Future developer</strong></h3><p>All this has got me thinking about what it might be like for developers getting jobs in the future and what we should be prepared for. What advice should I offer to those developers who ask me “Should I learn X?”. My answer up until now has been to build upon core JavaScript skills ( or other programming languages ), Libraries and Frameworks are simply using different approaches to get the same thing done. Learn about declarative and imperative programming, learn more about functional programming, learn the newest features of your chosen language, then when it comes to using a framework, you are much better armed to understand what it is doing and will learn its nuances much faster.</p><p>From my collected data on the past month (UK/Europe Only), looking at Job sites and speaking with recruiters, my conclusion is that there are significantly more jobs for React developers, this includes React Native, however, an Angular developer appears to be getting initial higher salary, on average around £10k more for permanent and £50 more per-day for contract. React roles tend to be more prevalent in Ad-Agencies and StartUps and Angular roles are in giant corporations and financial institutes.</p><p>For now, I’m going to stick to not being a library junkie.</p><p><em>I posted this originally on my own blog </em><a href="http://www.kodacell.com/post/library-junkie/"><em>http://www.kodacell.com/post/library-junkie/</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=144057ab6ca9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fear-and-coding/library-junkie-144057ab6ca9">!Library Junkie</a> was originally published in <a href="https://medium.com/fear-and-coding">Fear and Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Speaker Notes : This is for everyone]]></title>
            <link>https://medium.com/fear-and-coding/speaker-notes-this-is-for-everyone-b9d0ee58e4d4?source=rss----39e7bbfe62ab---4</link>
            <guid isPermaLink="false">https://medium.com/p/b9d0ee58e4d4</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[speaking]]></category>
            <dc:creator><![CDATA[Shaun D]]></dc:creator>
            <pubDate>Wed, 06 May 2015 12:23:11 GMT</pubDate>
            <atom:updated>2015-05-06T12:23:11.416Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p4hjOKW6pU2m6b9WeYlxJw.jpeg" /></figure><p>Front-Trends, 2015</p><p>These are my raw notes that I made for the talk Im about to give at Front-Trends conference in Warsaw, Poland.</p><p>This isn’t a blog post so little care has been taken with spelling and grammar, its more of a brain-dump and should be treated as such.</p><p>The slides are here :</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fspeakerdeck.com%2Fplayer%2F7e1f2c6b309a4c91b88d69406b93d02e&amp;url=https%3A%2F%2Fspeakerdeck.com%2Fshaundunne%2Fthis-is-for-everyone&amp;image=https%3A%2F%2Fspeakerd.s3.amazonaws.com%2Fpresentations%2F7e1f2c6b309a4c91b88d69406b93d02e%2Fslide_0.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=speakerdeck" width="710" height="463" frameborder="0" scrolling="no"><a href="https://medium.com/media/ea3c83aa9bd054b5fdc9df1d201d4e27/href">https://medium.com/media/ea3c83aa9bd054b5fdc9df1d201d4e27/href</a></iframe><blockquote><em>When sites are correctly designed, developed and edited, all users have equal access to information and functionality.</em></blockquote><p>I think the most important part of this is the ALL Users should have equal access.</p><p>When Sir Tim Berners Lee tweeted from the opening ceremony at the London 2012 olympics “This is for Everyone” he was talking of course about the Internet. XX years before his tweet he, as we are all aware of, ‘Invented’ the internet. It was in the early days a way to share knowledge and at its core, no matter how many GIFs we upload, still is that. Not only that, but sometimes the things we build, the social networks, the forums — they connect us and become part of our lifestyle.</p><p>The social networks, the newspaper sites, online education, tutorials and workshops. The world wide web that Sir Tim Berners Lee gave us, is for everybody and we can do our part as developers, designers and UX’rs to ensure that everybody has as easy access as possible to that wealth of knowledge.</p><p>The current state of accessibility kind of feels like a little bit of a job half done. I think there’s some of us who sort of half do it, maybe there’s a gap in education about making the web more accessible and then sometimes is just that people flat out think its a difficult thing to do.</p><p>I’ve found that when a lot of people think about accessibility on the web, they immediately think about people with visual impairments. The key things that I’ve personally found people jumping to whoever accessibility is mentioned is either tabbing through the page or the use of a screenreader. Whilst both of these do have something to do with accessibility, they’re not the only conditions that might affect someones use or interactivity with the things we build.</p><h3>VISUAL</h3><p>Users with low vision, obstructed vision or colour blindness. Users with low vision might use a screen magnifier so you might want to make sure that click areas are large enough with enough spacing apart. User with colour blindness to certain colours might have trouble separating something that is red for example, so if all your links are only discussable by being red in colour you might want to consider having an underline too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/741/1*G49wlFb4TAj3dkQ2nyimcg.png" /></figure><h4>Picard Quick Tip.</h4><p>Try not to use</p><pre>maximum-scale=1.0</pre><p>in your viewport meta tag because this disables the users ability to pinch and zoom. I know the designer thinks that they have the perfect type setting, font-size and line height down and in that case want the user to not be able to zoom — but its important that they realise they’re wrong and someone wants to zoom and they should be able to.</p><h3>AUDITORY</h3><p>All too often I have found myself embedding videos on the web and anytime I have asked for a suitable subtitle file, its always been a pain to get some sort of transcript. Fight for it if you’re in this position, its not a hard thing to implement as a developer as the html5 track element has pretty good support now and most video players have fallbacks. Its also worth saying that if you have a podcast, it’s bee great to see more transcripts out there.</p><h3>MOTOR</h3><p>Motor is a pretty big one because it can cover a whole range of assistive technologies, from someone who suffers with RSI and primarily uses a keyboard to navigate, to someone who might use an assistive joystick or eye tracking to move the mouse around. We’ll dive in a bit deeper to keyboard navigation in a bit, but for the other assistive technologies it can be as simple ensuring that hit targets on buttons and links are well defined and have some space between them if they are bunched up together.</p><p>So today, I want to go through 10 things that we can do as developers that are super easy, can become part of you workflow and together we can begin to make the things we build a little bit more accessible to as many people as possible. So, in no particular order of importance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*L5UzFiuCagQPKXC7lPW1UA.jpeg" /></figure><p>Im not here to make you feel bad. I am by no means an authority on accessibility, just a programmer who finds the subject interesting and wants to share some of the things that I’ve learnt.</p><h3>10 — Accessibility First.</h3><p>You’ve heard of Mobile-First right? Big thing, maybe sometime used as a buzzword by sales people and recruiters, but really it was pretty good advice. But if you have a Mobile First approach to you’re code you’re thinking about small screens, low powered devices and slow connections first and by building your pages in a way that makes them fast, snappy and responsive in that environment you get a much better user experience for everyone, no matter the screen size or connection speed. Also, if you’re building a responsive website, its a lot easier to go mobile-first that trying to bake in the mobile layouts after, using progressive enhancement (another dangerous word).</p><p>Its the same with accessibility. Its something thats a lot easier to do from the beginning rather than try to bake in the last 2 days or when your PM comes along with a WCAG report that has a bunch of accessibility failures that you have to fix y the end of the day. Thinking about accessibility upfront can also influence UX and make the site or application simply a little bit more usable.</p><h3>9 — Keyboard Navigation.</h3><p>I know what you’re thinking, Who doesn’t use a mouse, right?</p><p>People on the Enterprise don’t use a mouse.</p><p>Vim Users don’t use a mouse.</p><p>From personal experience I just find it a lot easier to navigate my most-visited sites using just a keyboard. Reddit, Gmail and other sites I use on a daily basis have good keyboard-only support and whilst I can use a mouse when necessary, there are a lot of people who cannot. Adding basic Keyboard support isn’t difficult either, you just have to remember that wherever you add a click, you might need to consider adding a keyboard input event such as hitting the enter button or using the arrow keys to navigate a carousel. The BBC’s main site has a carousel on it’s homepage and it’s really nice to use with just a keyboard.</p><p>Tab ordering is also important when it comes to Keyboard navigation, some native HTML elements are inserted into the tab order of the page such as Headings, Form fields and links, but there are also these ‘semantically neutral’ elements that don’t get inserted into the tabbing order that we might want to be able to navigate to AND through with the keyboard. Thats where we get onto</p><pre>tabindex</pre><p>If the tabindex isn’t used on an element then it will follow the convention of the element. If its a control element such as a form field, button or link it will be in the tabbing order of the page, but if its a span or a div, it will not.</p><pre>tabindex=”-1&quot;</pre><p>will allow an element be programatically focusable. This means that you can respond to keypresses and send focus to an element that has this tabindex using</p><pre>.focus()</pre><p>in JS. This is good for when you are creating those custom selects and wants someone to be able to use arrow buttons to be able to make a selection. This is also good for when you open a modal on a screen.</p><pre>tabindex=”0&quot;</pre><p>will put the element into the natural order of the document. So if you are using divs or spans as buttons, or even using HTML Web Components, you will likely need to add tabindex=0 in order for a user to be able to access that element.</p><pre>tabindex=”[1…99]”</pre><p>any positive integer will put the tabbing order, in the order that you declare. If you think you need to control the tabbing order, beware, its not easy to maintain the natural tabbing order.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*KMU5PYL23xqGMP8C9sY9BQ.gif" /></figure><pre>:focus{<br>  outline:none;<br>}</pre><p>Don’t disable the `:outline`. Designers hate it, that blue outline you get on focus, but its really important for people using keyboard navigation are able to tell where they are on the screen. It does’t have to be that blue outline, but elements that receive focus should always have some sort of visual key. If its a button or a link, give `:focus` the same treatment as hover and if its a form field, heading or navigation element, give it some sort of outline or visual state that makes it obvious when we are on the page.</p><h3>8. Skip Navigation Links</h3><p>Sort of comes into the keyboard navigation area of things, but I believe its important enough to be in and of itself. Its something thats possible for everyone to go away today and implement into any project that you might be working on.</p><pre>&lt;body&gt;<br>&lt;a href=”#main”&gt;Skip Navigation&lt;/a&gt;<br>&lt;nav&gt;<br>  &lt;ul&gt;<br>    &lt;li&gt;&lt;a href=”#”&gt;Home&lt;/a&gt;&lt;/li&gt;<br>    &lt;li&gt;&lt;a href=”#”&gt;About&lt;/a&gt;&lt;/li&gt;<br>    &lt;li&gt;&lt;a href=”#”&gt;Blog&lt;/a&gt;&lt;/li&gt;<br>   &lt;li&gt;&lt;a href=”#”&gt;Contact&lt;/a&gt;&lt;/li&gt;<br>  &lt;/ul&gt;<br>&lt;/nav&gt;<br>  &lt;div role=’main’ id=’main’&gt;<br>    &lt;! — Main body of content →<br>  &lt;/div&gt;<br>&lt;/body&gt;</pre><p>Someone who uses a keyboard for navigation, visual or not, can often find it fatiguing to continue tapping through repeating content across pages, this commonly being navigation — so it’s a common pattern to make a link that sends focus to the main content of the page the first element in the page, so that the first tab allows a user to just skip to the content.</p><h3>7. Alt tags</h3><p>ALT tags is something you’re told about right at the beginning of your career as a web developer and then it seems that you just one day, stop adding them. Has anyone ever had one of those WCAG2.0 Reports done on something they built? Everytime they come back there is always something about Alt tags.</p><p>The alt text is meant to help the user not miss any content, Its not only something thats used by assistive technologies, but maybe also used when people switch off images in their mobile browser to save on data.</p><p>If your image is part of the content, then it should have some relative text in the alt tag.</p><p>If you’re having to use an image for purely decorative reasons and its not relative to the content, then still use an alt tag, but just have it as an empty string, that way assistive technology knows to just skip over it and ignore it. You might also use this technique if you have an image for a graph and descriptive text underneath.</p><h3>6. Forms</h3><p>Forms by default are pretty good for accessibility. The few things you can do as a developer is make sure that the forms tabbing order makes senses. Labels are a massively important part of forms, on a UX side of things, labels tell the user about the expectation of that field. For someone using assistive technology might also need something like a screen reader or Braile output, they need a label associated with the field and no, placeholder text does not suffice. Of course, maybe you don’t need labels to be show to people who can see a form, thats where we can use a little CSS magic.</p><pre>.sr-only {<br>   position: absolute;<br>   width: 1px;<br>   height: 1px;<br>   padding: 0;<br>   margin: -1px;<br>   overflow: hidden;<br>   clip: rect(0,0,0,0);<br>   border: 0;<br> }</pre><p>Many popular UI frameworks have a helper class a little bit like this. This allows you to keep elements that assistive technology use in the natural flow of the document, but hide it for visual users. So you can use this on labels if you don’t need them for visual users.</p><p>And before anyone asks, no, I’ve not found a way and I don’t think that there is a reliable way of detecting someone using a screenreader in JS and Im not too sure about how I feel about the idea of that being a good thing. I don’t think you should be thinking about a layout for assistive technology.</p><h3>5. ARIA</h3><p>ARIA allows us to extend HTML. We can add additional attributes to elements to allow us to communicate to assistive technology.</p><p>We can assign roles to let assistive technology know its purpose.</p><p>We can use aria-states and properties to communicate the state of an element. On Friday Leonie Watson is doing a talk on ARIA, so make sure you catch that to dive into ARIA and how to use it.</p><h3>4. Landmarks</h3><p>Landmarks are specific roles assigned to elements to allow AT to navigate directly between them. Someone using AT can navigate between these landmarks. Again, be sure to attend Leonie talk on Friday to no doubt find out a bit more about Landmarks.</p><h3>3. Media</h3><p>I mentioned before that if we are using media on a page, we should also provide subtitles for video and transcripts for any audio content. Its also important to not have video or audio auto-play when the page loads. We all know how annoying auto-playing video is, imagine if sound were your only means of navigating the web and you suddenly have this. Video controls are more than apt and I am yet to come across a requirement of auto-playing video that can’t just be put behind user controls.</p><h3>2. Testing</h3><p>Doing all of these things are fine, but testing is an important part of that. Not just testing our code, but I think its important that we test our tools too. Spend some time with a screen-reader, or learn about keyboard only navigation on pages. The next time you finish up a feature or a page, put its through its paces. If you’re code reviewing a peers work, educate them on how they can ensure their work is accessible by AT.</p><h3>1. Lets talk about it</h3><p>The last thing that I really think will help is that we start talking more accessibility. Talk about it with our peers, talk about it more at conferences and share the things we’ve learnt. Im not talking about calling each other out on twitter, but working together to help one another fill in the gaps we see in our work.</p><p>There are some things that you can’t fix as a developer. Design and UX might be something thats totally out of your hands, but that doesn’t mean that you can help educate. Colour and contrast are interesting things because its something that certainly gets looked over in a lot of cases, and then there are a lot of interesting things around typography such as the types of fonts used that help people with cognitive problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/741/1*G49wlFb4TAj3dkQ2nyimcg.png" /></figure><h4><strong>Picard Quick Tip</strong></h4><p>jQuery UI is a great learning resource, they have an excellent standard for ensuring that the widgets they make are as accessible as possible. If you ever wonder how to make tabs or carousels more accessible, have a look at how those components are implemented in jQuery UI, how they’re structured and how they use ARIA and how they use JavaScript to handle focus and keyboard input.</p><h3>Tooling</h3><p>So what tools are out there that can help us?</p><h4>Accessibility Developer Toolbar</h4><p>Chrome ADT is a great place to start. It allows you to run an audit on a page much like you would a performance audit. It feeds back with information on form inputs with missing labels, or maybe an element that is focusable, but obscured by another element. It also has a tab in the inspect element view where you can select your DOM element and see the accessibility properties of that element. There are also some equivalent tools for other browsers.</p><h4>Chrome://accessibility</h4><p>On the subject of chrome, if you want to see the accessibility tree — this is the rendered tree that AT uses as apposed to the DOM tree that you might be used to. You can use this if you need to investigate what affects certain ARIA states or properties might have.</p><h4>Tenon.io</h4><p>You can use Tenon to run an audi via it’s API, it will then respond back using JSON. This can be useful for QAs running automated testing and be run in your CI workflow or something similar.</p><h4>Screen Readers.</h4><p>So beyond these other tools that can test our code, you might want to actually test something with a screenreader, thankfully they’re available on all platforms, including the ones we have in our pockets and generally are free to use and the paid ones usually come with a free trial. It can take some getting used to when using a screenreader, but I think that if you are serious about understanding how a lot of people will access the things that you build, its time thats worth investing.</p><h3>Resources</h3><p>Youtube playlist</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fvideoseries%3Flist%3DPLOFw4-G3iCCzvqK9O_YrViUCcN9Esk4O2&amp;url=https%3A%2F%2Fwww.youtube.com%2Fplaylist%3Flist%3DPLOFw4-G3iCCzvqK9O_YrViUCcN9Esk4O2&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FDqVsoDbh9U8%2Fmqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="853" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/cec6fc844dac4939d14eb632e3aeb105/href">https://medium.com/media/cec6fc844dac4939d14eb632e3aeb105/href</a></iframe><p><a href="http://www.w3.org/TR/wai-aria/">http://www.w3.org/TR/wai-aria/</a></p><p><a href="http://a11yproject.com/">http://a11yproject.com/</a></p><p><a href="https://code.facebook.com/accessibility">https://code.facebook.com/accessibility</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l4G0D9vnhFU7l7G7Ey6Cxg.png" /></figure><p>So lets go from boring beardless Riker, to awesome bearded Riker. Lets make the web more accessible.</p><p>My name is Shaun, Im a developer based in London in the UK. I’ll be around for the rest of the conference if you want to talk about anything I’ve spoken about or if there are any questions, or you can find me online usually under the moniker of @shaundunne.</p><p>Thanks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/333/1*RCqpcX23izeo6b8mBrrhgg.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9d0ee58e4d4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fear-and-coding/speaker-notes-this-is-for-everyone-b9d0ee58e4d4">Speaker Notes : This is for everyone</a> was originally published in <a href="https://medium.com/fear-and-coding">Fear and Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Some Documentaries]]></title>
            <link>https://medium.com/fear-and-coding/some-documentaries-f5a34d0b68b0?source=rss----39e7bbfe62ab---4</link>
            <guid isPermaLink="false">https://medium.com/p/f5a34d0b68b0</guid>
            <category><![CDATA[documentary]]></category>
            <category><![CDATA[film]]></category>
            <category><![CDATA[code]]></category>
            <dc:creator><![CDATA[Shaun D]]></dc:creator>
            <pubDate>Wed, 04 Mar 2015 02:12:14 GMT</pubDate>
            <atom:updated>2015-03-04T02:13:31.551Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mEU6MqKShvZ5b3ACVUEFUQ.png" /></figure><p>Documentary might just have to be one of my favourite forms of film. Its not just because its real (most of the time), its something more than that. My favourite documentaries are ones that I watch on repeat, they’re the ones that I find truely immersive, the ones that refuse to let go and shift your perception of everything that you know. Those aren’t the films im going to be sharing here…or maybe some of them are ☺.</p><p>Being someone who tinkers with code most of the day (and night), its great when there is a documentary that in some way I relate to, so below is a list/links to some well-worth watching documentaries about programming/programmers/code-tinkerers.</p><h4>Moon Machines : Navigation Computer {Full}</h4><p>Part of the Moon Machines series, this look at the navigation computer is fascinating. Rope Memory anyone? (the other parts are worth watching)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fvideoseries%3Flist%3DPLTu8nanTJo7GvulBxz9JT9JcXeXimM1Vr&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D9YA7X5we8ng%26list%3DPLTu8nanTJo7GvulBxz9JT9JcXeXimM1Vr%26index%3D3&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2F9YA7X5we8ng%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/41f9accb268dfca28d985c33054f321d/href">https://medium.com/media/41f9accb268dfca28d985c33054f321d/href</a></iframe><h4>Project Code Rush {Full Movie}</h4><p>A documentary about Netscape and the birth of Mozilla. All footage was also released openly for people to mix their own version of the film.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F4Q7FTjhvZ7Y%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D4Q7FTjhvZ7Y&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F4Q7FTjhvZ7Y%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/ced07c77cce6a813196a319f0e9ff97f/href">https://medium.com/media/ced07c77cce6a813196a319f0e9ff97f/href</a></iframe><h4>TPB AFK {Full Movie}</h4><p>A film following the trials of The Pirate Bay founders.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FM_T03p1cCVM%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DM_T03p1cCVM&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FM_T03p1cCVM%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/5574094c92963c6d9bb15b12a9632597/href">https://medium.com/media/5574094c92963c6d9bb15b12a9632597/href</a></iframe><h4>DEFCON {Full Movie}</h4><p>A insight into the worlds largest Hacker conference.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F3ctQOmjQyYg%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D3ctQOmjQyYg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F3ctQOmjQyYg%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/a05c462570ee99a013bb33411a8662c1/href">https://medium.com/media/a05c462570ee99a013bb33411a8662c1/href</a></iframe><h4>The Internets Own Boy {Full movie}</h4><p>The Story of Aaron Schwartz, programming prodigy and activist.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FvXr-2hwTk58%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DvXr-2hwTk58&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FvXr-2hwTk58%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/3a7d6fed479c38575c9d46a046850295/href">https://medium.com/media/3a7d6fed479c38575c9d46a046850295/href</a></iframe><h4>Revolution OS {Full movie}</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fjw8K460vx1c%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Djw8K460vx1c&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fjw8K460vx1c%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1f7d4f5ec9ada762e454713c3986ff37/href">https://medium.com/media/1f7d4f5ec9ada762e454713c3986ff37/href</a></iframe><h4>Indie Game {Trailer}</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FdINgx0y4GqM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DdINgx0y4GqM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FdINgx0y4GqM%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/9f5fabf005cc4e482d2ab0eea2768487/href">https://medium.com/media/9f5fabf005cc4e482d2ab0eea2768487/href</a></iframe><p>Enjoy ;)</p><p><a href="http://www.twitter.com/shaundunne">Shaun</a> can usually be found not fixing bugs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5a34d0b68b0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fear-and-coding/some-documentaries-f5a34d0b68b0">Some Documentaries</a> was originally published in <a href="https://medium.com/fear-and-coding">Fear and Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learn all the things!]]></title>
            <link>https://medium.com/fear-and-coding/learn-all-the-things-5772eb2fb41d?source=rss----39e7bbfe62ab---4</link>
            <guid isPermaLink="false">https://medium.com/p/5772eb2fb41d</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Shaun D]]></dc:creator>
            <pubDate>Mon, 02 Mar 2015 14:14:51 GMT</pubDate>
            <atom:updated>2015-03-03T15:53:55.765Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TXJpmTcIdY6kbQQllNZ9aA.jpeg" /></figure><p>Ember, Angular, React or that other thing?</p><blockquote>“What should I learn next?”</blockquote><p>Its something that I get asked so often that I’ve sort of come up with a stock answer. A lot of the time the stock answer is sort of tailored to the personality of the person asking if I know them well enough, but the core of the answer is generally the same. Having worked in a few agencies over the past 7 years of so, I’ve run into my fair share of developer arch-types. The old school developer who doesn’t see the benefit in changing, the young gun who is always onto the new-shit. The mid-weight developer who is super astute, but always feels like they are a little bit behind the curve and the newbie who has just got their first serious job and looks like they are about to drown in the sea of choices.</p><p>In November 2011 I would say that I was definitely the newbie. I was working for a major Agency in London as a junior developer and I felt like I was not only drowning, but I had no real idea how to swim. It was pretty scary, before this job I felt like I knew enough, but upon landed on my first project, I realised that I really knew so little. At this time I made the pilgrimage to Brighton and to the Full Frontal Conference where I heard some amazing talks, but the one that stuck with me was the the talk from <a href="https://twitter.com/jashkenas">Jeremy Ashkenas</a>. He talked about the design decisions in CoffeeScript and within that talk he spoke a bit about Backbone.js. Another talk that day was from <a href="https://twitter.com/slicknet">Nicholas Zakas</a> about modular JavaScript. Both of these talks combined led me down a deep rabbit hole, of which Im still very much crawling through, of learning and iterating myself and my skills. I read a lot. I studied as if I were going to be tested every single day and I wrote code like a maniac. In December of 2011 I wrote a small framework inspired by both Backbone and the idea of modularity in code. It was a very small backbone-ish like framework where the DOM library could be swapped out at any time. Why? Well, if you’ve every worked with banks you will know that they might not be able to use a certain version of jQuery or they might only be able to use MooTools or a million other reasons you might need to swap out a part. It didn’t go anywhere really, I got the basics down, but as the work pilled on I never really moved the framework forward.</p><p>So over the past few years we have had a barrage of tools thrown at our faces and we’ve been lead to believe that we have to choose our Poison. Backbone, Angular, Ember, React, Knockout with Require or Browserify built with Make, Gulp, Grunt, Broccoli or Webpack. (I know — there’s a lot more). For some, the choice might be easy, one or more of them might tie up with your personal philosophy on how things on the web should be built. Maybe you think that Embers conventions lead to better and more maintainable code. Maybe the testability of Angular is something you prefer. Maybe AMD syntax is easier to read for yourself and your team or maybe you’ve just adopted some decent knowledge of Gulp on a previous project and are now using because it just works. But, if you’re new to JavaScript and are having trouble working out what you should learn because you are yet to work on a project that might or might not require some sort of modern front end framework — how do you choose to invest your time when it comes to learning? You’re being told left and right on twitter that Ember is the future or that on <a href="http://www.reddit.com/r/javascript">/r/javascript</a> that there are 10 Angular jobs for every Backbone job (unconfirmed) or that you should learn all of them. I’ve spoken to a lot of developers who are fairly new and they all say the same thing. It’s daunting to know where to focus their time.</p><p>So, whilst I have my own personal preferences of what tools I like to use and what I want to focus on at the moment, let me offer my two cents on what you might want to learn if you’re finding yourself a little lost amongst the options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AiutBToQ0z_IGhHvez4EpA.png" /></figure><h3>ES6 and the future of JavaScript</h3><p>If I were a relative newcomer to JavaScript, once I felt like I was ready to move on past the basics and wanted to start looking at more complex applications, design patterns, reading ‘The Good Parts…again’ and feeling like I needed to definitely learn something new in order to make myself ready for the onslaught of everything that is to come, I would start learning more about ES6 and the ongoing evolution of JavaScript. New syntax, new features and more are all becoming available to JavaScript. Block scoped variables, Fat arrow syntax, Class Syntax, Module system. All of these things and more are available for you to use now (by using Transipilers to convert from ES6 to ES5) and by learning about all the new features that are coming you are definitely preparing yourself for the foreseeable future of JavaScript development and not tying yourself to a framework that may or may-not be around in a few years (or just completely change everything about the way you build apps with their framework). Some frameworks are already using tooling to help them use some of the upcoming features in ES6 and beyond, so if you do find yourself on a project using it, you shouldn’t find yourself to overwhelmed with new syntax.</p><p>There are a lot of good talks on ES6 that will get you rolling a lot quicker than I can in this (or many) posts. The three I can recommend are:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F0VUjM-jJf2U%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D0VUjM-jJf2U&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F0VUjM-jJf2U%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/143f7d14624c281ca6312b8d331dce41/href">https://medium.com/media/143f7d14624c281ca6312b8d331dce41/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F9WJ8pQHhOm8%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D9WJ8pQHhOm8&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2F9WJ8pQHhOm8%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/fe1aac27dd75a7c8b673bff1cca1200d/href">https://medium.com/media/fe1aac27dd75a7c8b673bff1cca1200d/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Frwm5JLqCpdk%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Drwm5JLqCpdk&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2Frwm5JLqCpdk%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/bed923c0da2f4c0bd66aabb161640589/href">https://medium.com/media/bed923c0da2f4c0bd66aabb161640589/href</a></iframe><p>You might find similar ground covered, but it’s well worth the time to just everything hammered home.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AiutBToQ0z_IGhHvez4EpA.png" /></figure><h3>Accessibility (A11Y)</h3><p>So many developers I have worked with and spoken to have little experience with A11Y, yet I strongly believe that its one of the most important skills to hone. Understand that most of the things that we build can be seen by almost anyone with a computer and an internet connection. There’s something really powerful in that thought that maybe we don’t think about too much. Im a big keyboard navigator — not because of some disability, but because I find it a lot quicker and easier most of the time to just use keyboard navigation. I love it when a site is optimised for it, when I can tab-and-space through forms, when I can go through items using <strong>HJKL</strong> keybindings, but most of the sites I use just aren’t built with this in mind. I know that there probably isn’t any decent data on keyboard-only users and even if they were it would probably be a ‘nice to have’, but I really don’t think that understanding tabbing order or adding some nice navigation via the keyboard is really all that difficult. On top of that we could throw in some nice Aria-tags to enable assistive technologies aid people through our site. We might only be making a brochureware website for some Mayonnaise, but do hard-of-sight people not like condiments? Do people with motor disabilities not want to read about the new [insert car name here]. Whilst we might not be able to test everything, we can at least give some people a chance.</p><p>We should be thinking about ‘<strong>A11Y-First</strong>’ just as much as ‘<strong>Mobile-First</strong>’ and if you add a little bit of knowledge, you will find yourself a pretty valuable member of any team and will be help make the web just that little bit more accessible for everyone.</p><p>A good place to start will be the <a href="http://a11yproject.com/resources.html">A11Y Project Resource Page</a> and then check out some of Marcy Suttons talks.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F04DOp1F9Od4%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D04DOp1F9Od4&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2F04DOp1F9Od4%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/7f2feb35970f170b5dac86218355c599/href">https://medium.com/media/7f2feb35970f170b5dac86218355c599/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AiutBToQ0z_IGhHvez4EpA.png" /></figure><p>So those are two things that I would (and am) investing some time in. Sure, you’re gonna maybe want to look at every shiny new thing that comes along and of course, sometimes that will be beneficial, but if you don’t know what to spend time looking at right now, right this moment, then take a shot at spending some time on these things. I don’t think that the upfront investment is a lot and I certainly believe that it will be a better payout for yourself in the future.</p><p>Shaun Dunne spends far too much time on Reddit and can be found snapchatting at : fearandcoding</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5772eb2fb41d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fear-and-coding/learn-all-the-things-5772eb2fb41d">Learn all the things!</a> was originally published in <a href="https://medium.com/fear-and-coding">Fear and Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vim.]]></title>
            <link>https://medium.com/fear-and-coding/vim-cee4a97787e2?source=rss----39e7bbfe62ab---4</link>
            <guid isPermaLink="false">https://medium.com/p/cee4a97787e2</guid>
            <dc:creator><![CDATA[Shaun D]]></dc:creator>
            <pubDate>Sat, 27 Dec 2014 02:08:01 GMT</pubDate>
            <atom:updated>2014-12-27T02:07:43.569Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*WGl9lISqXzcwqOXsZwCSdQ.jpeg" /></figure><h3>I guess you can say things are getting a little serious now.</h3><blockquote>“How do you know someone is a Vim user?”</blockquote><blockquote>“They’ll tell you”</blockquote><p>There something so elitist about Vim that I just couldn’t see past. Anyone who used it just had to mention they used it and for the longest time I never really understood why. I’m still somewhat convinced that some use it because it comes with a status. A Vim user is a real hardcore coder or something to that effect.</p><p>The truth is, I’ve tried several times to make the switch to Vim, just to see if it really is as good as people make it out to be. At least twice a year for the past four years I have tried to make the switch and it really just hasn’t struck gold for me.</p><p>Now I’m at it again.</p><h3>A little history.</h3><p>My first IDE/editor was Macromedia Homesite. I lived off a pirated serial number for a good while. I probably only used 20% of its overall functionality, but it stuck around for a while.</p><p>I then moved onto Dreamweaver and got to know a little more about IDEs and what they could offer. Dreamweaver caught a lot of slack for it’s WYSIWYG functionality, but I never really ever used it. Autocomplete was my friend, as was the built in FTP functionality allowing me to just jockey right on the live server (I didn’t really use version control at this point). When I was forced into using SVN, there was built in stuff for that too.</p><p>When I joined SapientNitro in 2010 I got my first Mac and was introduced to textmate. It didn’t have as many windows as Dreamweaver, and didn’t appear to have as many built-in features, but after a week, I dug it’s simplicity. Over about a year I used Textmate and got into the whole mantra of small sharp tools. I got used to the large editor area, the darker color scheme that was a whole bunch easier on my eyes and there was a whole bunch of third party plugins that made my development workflow smoother.</p><p>I think I first heard about Sublime text on some tutorial site, it was like net-tuts, codeschool or something like that, but it was / still is compared to Textmate but with an ever growing eco-system for plugins and a momentum for the core software that Textmate just didn’t have. I tried it, liked it and have owned it ever since.</p><p>Along the way I have tried other editors.</p><p>I tried Webstorm and was put off by all the setup for a project. The built-in tools sounded nice, but they really didn’t seem to compensate for the fact that I had to deal with just so much going on in my direct vision.</p><p>I tried Githubs Atom editor and found it slow and clunky. I couldn’t care less about it’s ‘Hackability’, when scrolling through a few hundred lines of code was sketchy like one of those infinite scrolling sites. I’ve not tried it in its recent releases and see many people using it, but it’s really not tearing me away from Sublime yet.</p><p>I tried Visual Studio for a bit. I liked the idea of giving a fully featured IDE another try, but much like Webstorm there was just too much going on. Yeah, built in Node tools, Build tasks and Phonegap / Cordova compilation was a plus, but I’d have to work on a Windows system and I just don’t do that anymore unless I want to play some games. Sorry. Strictly on a Mac most of the time or I jump to a Arch box occasionally at home.</p><h3>Coming back</h3><p>So here we are. I am still very much a lover of Sublime, have been a happy customer for years. I have a color scheme I like, I have a bunch of snippets and I have memory muscle for my most used shortcuts. So why the change.</p><p>About 4 months ago I started getting this shooting pain running from the palm of my hand down my arm to my elbow. I didn’t even consider that this might be RSI, because it felt way more painful that I imagined that RSI was, but after talking about it with people whom had suffered with it before, all the signs pointed to RSI. I had tried various ergonomic mice before but I decided that maybe it was best that I not try to use the mouse as much.</p><p>Keyboard navigation on some websites suck — there’s probably an entire set of blog posts on how maybe we should start trying to fix this — but I manage to get by with the help of some Chrome extensions and general A11Y methods.</p><p>General OS stuff is sorted with the Aid of Spectacle window manager and Alfred.</p><p>Now time for one of the places where I spend a good majority of my time, Sublime. There is Vintage mode and there is a plugin called Vintageous, but after trying these I just couldn’t get the hang of them and always found myself drifting back to using a mouse. So I decided that I should give Vim a good hard look and real effort to get along with it.</p><p>So that’s why I’m trying Vim. Not because its cool or hip or makes me a l337Hax0rz, but because my fucking hand hurts. A lot. I guess I am hoping that with minimal movement of my hands daily that they will get better. I’ll get myself a nicer keyboard rather than writing on something flat and I’ll be able to do everything with just as much ease without needing a mouse.</p><p>So far I have Vim up and running with Pathogen and Nerdtree. I went through various of the top posts in /r/vim in order to gather the best starting out guide, plenty of opinions on Vundle or Pathogen, and I just went with Pathogen because that seemed to get more positive votes. I know that Vim has a built in file explorer but every guide I look at seems to recommend Nerdtree, so Im going with it.</p><p>So here I am. Ready to dive into life with Vim. By the time I get back to work on the 5th I am either going to hate it or love it … or be totally indifferent. What I do know is that I really need to figure out how to change the color scheme.</p><p>EDIT : Aha! <a href="http://vimawesome.com/plugin/vim-tomorrow-theme-all-too-well">http://vimawesome.com/plugin/vim-tomorrow-theme-all-too-well</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cee4a97787e2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fear-and-coding/vim-cee4a97787e2">Vim.</a> was originally published in <a href="https://medium.com/fear-and-coding">Fear and Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Code Live: Railsbricks App]]></title>
            <link>https://medium.com/fear-and-coding/code-live-railsbricks-app-bdbc43518003?source=rss----39e7bbfe62ab---4</link>
            <guid isPermaLink="false">https://medium.com/p/bdbc43518003</guid>
            <dc:creator><![CDATA[Shaun D]]></dc:creator>
            <pubDate>Tue, 09 Dec 2014 20:27:26 GMT</pubDate>
            <atom:updated>2014-12-08T02:45:11.428Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/457/1*KGWnLDf2gR-Tmcq7ApGZsA.png" /></figure><p>Building Rails apps even faster</p><h4>Monday 8th December — 1:11am</h4><p><a href="http://railsbricks.net/">Railsbricks</a> is an app generator for getting off to a flying start with a rails application. Now I already love the workflow for Rails, I think that it’s one of the more matured workflows for web application development that exists. Say what you want about Rails as a framework or Ruby as a language, it makes me feel productive and that makes me a happier developer.</p><p>On a daily basis I don’t get to work much with Ruby or Rails for that matter, but in my own time I have built a few applications using Rails and really enjoy using the framework and the tools around it. I already think that the standard Rails workflow is awesome and allows me to move fast with ideas, but Railsbricks takes care of a lot of general boilerplate stuff that you might do on most apps. It goes ahead and adds Bootstrap for UI, Devise for User Authentication, Layouts for headers and footers, Secret values for config stuff, email setup, contact forms etc etc. There’s a whole lot of options for it.</p><p>So, whilst I’ve now run out of Newsroom episodes, and Reddit seems to be having load issues</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*80Rk76hxN0xV0mP4Jk5mwA.png" /></figure><p>I thought to myself <strong>“Maybe I’ll download that Elvis movie where Kurt Russell plays Elvis”. </strong>Turns out there’s only like 5 seeds for the film so thats gonna take a while.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i7rIekHcwe6Hkwffe9Svvg.png" /></figure><p>So, whilst I wait to get my Elvis on, I might as well get this device library thing up and running again.</p><h4>What device library thing?</h4><p>Well at NiceAgency (my current employer) I had built this small CRUD app that allowed the test devices to be tracked. It was originally built using <a href="https://www.meteor.com/">Meteor</a> and deployed on Heroku, but some idiot (me) dropped the MongoDB that it was using and rendered it useless. Now, I could have very well just brought it back up with a fresh DB — I had no backup — but I also wanted to add a couple of features to it, make it a bit less … prototypy (It was built in about 3 hours) and also put in some sort of backup routine. I could do all this in Meteor, but I wanted an excuse to use Rails and try out Railsbricks, so I chose to update it.</p><p>The device library just has the ability to add devices, edit them, assign them to a user and thats about it really. Its real simple way of tracking whom has what.</p><h4>1:20am</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*0HN8ZO8hxsa4xguRTSuo5Q.gif" /></figure><p>I start out by installing Railsbricks, easily done by following their <a href="http://railsbricks.net/get-started">guide</a>, tis just a simple gem install. I use RVM as my Ruby version manager. I know a lot of people prefer rbenv, but I’ve always used RVM and never really had any problems with it. I know that Railsbricks uses Ruby 2.1.5 so I go ahead and <em>rmv install</em> that version and im good to go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ICiJBbIFduU5P9DK5C_2uw.png" /></figure><p>I then kick off with the rbricks commands.</p><p>After about 45 seconds of questions to set up your app, all of which are easy to answer even if you’ve never really written a rails application before, Railsbricks goes off and starts creating the boilerplate for your app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nhbamTdFaiT8pAABR395GA.png" /></figure><p>It goes off and sets up a <a href="http://unicorn.bogomips.org/">Unicorn</a> config for production (Unicorn is a HTTP server for Rack applications), sets up some dummy users, routes, paths, models and views. Sets up a default admin user and some templates to get going.</p><p>I <strong><em>cd</em></strong> into my app folder and run <strong><em>rails s </em></strong>and badaboom ….</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FiUPQ8vp82xwDM30gI7vFg.png" /></figure><p>Love it. That really is fast.</p><p>I open the project up in Sublime and it looks like a regular rails project, just with tons of stuff already set up.</p><h4>1:35am</h4><p>Had a play around for a couple of minutes, editing users, changing passwords etc — all works as expected. I now realise that maybe adding the ability to add posts isn’t quiet what I need, so going to have to change that.</p><p>So from here on in Railsbricks is kind of done, its back to straight-up Rails development, but its saved a lot of time getting our boilerplate app set up.</p><h4><strong>1:50am</strong></h4><p>Used rails scaffolding to scaffold out the device stuff.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dSeJ_oSsyDbANMHr-9nBFw.png" /></figure><p>Im really just going by what I used before in the meteor app. I then run a db:migrate to create the database table.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iUfbA8cacZAIEZJR4KQtFA.png" /></figure><p>Whilst adding some seeds to the DB seed file I realise that I should have set the available field to a boolean, oh well I can change that when I need too.</p><p>I set up some dummy data in the seeds file for creating some devices by passing an array to the create method.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VHBeoSkiXszG01rC1GX5Nw.png" /></figure><h4>2:25am</h4><p>Whoopsie, I used the field <strong><em>type </em></strong>for device and thats a reserved word so I got a fail when trying run my seeds. Im sure that best practices dictate say that you should just run another migration to fix the field in the schema, but all I did was just edit the Device migration file to have a <strong><em>device_type </em></strong>field and then run <strong><em>rake db:drop db:create db:migrate </em></strong>then I can run <strong><em>rake db:seed </em></strong>and get everything I need.</p><p>Sweet!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IVkVEoWoUw6Sryz7J4qNqw.png" /></figure><p>Needs a bit of style work, but all is good in the hood. Elvis has now finished downloading so I’m going to indulge in that now. I’ll come back to this tomorrow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdbc43518003" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fear-and-coding/code-live-railsbricks-app-bdbc43518003">Code Live: Railsbricks App</a> was originally published in <a href="https://medium.com/fear-and-coding">Fear and Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ICA : The GitShots]]></title>
            <link>https://medium.com/fear-and-coding/ica-the-gitshots-840ca4a3011a?source=rss----39e7bbfe62ab---4</link>
            <guid isPermaLink="false">https://medium.com/p/840ca4a3011a</guid>
            <dc:creator><![CDATA[Shaun D]]></dc:creator>
            <pubDate>Sat, 06 Dec 2014 01:53:11 GMT</pubDate>
            <atom:updated>2014-12-06T01:53:02.685Z</atom:updated>
            <content:encoded><![CDATA[<p>One of my last projects at SapientNitro was to build this social CRUD site to define the rules of Art. It was a responsive site, buit with Ruby on Rails on the backend and a Box2D on the front end. Why the need for a physics on the front end? Bubbles, thats why.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BzWZ6hIAQyQCmnTMw50xMw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ghnvp_Vi0kQE9nVaRrZCOg.png" /></figure><p>You can still see the site live at artrules.ica.org.uk. I’d love to dive into the code, but it’s been well over a year since I left Sapient and can barely remember any of it. What I do remember was that there was a lot of work involved and I started using this thing called Gitshots to take a photo on each git commit I made. See below as I went through a good few weeks of hell to deliver the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*88AEGzzobAE_w_KpHVTDfA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K2OSwPlBvskOLIXG1Sc6KQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8me444O8wdi-uJQqq7b6SQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iqTLuTPFIqWFMCyug1VyRg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BKwi0O3RxIG0lnyGzTTB7w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dkp4uliFCGrV0qDVcBqIWQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aVCXWbivi9-Kd5475SY0wQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GgkR632eqDNAmgL8ud_fvg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7NAZFNLpaZt_etHARJ4nhg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7NAZFNLpaZt_etHARJ4nhg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*prwXEUBPZioyjnGjNa04NQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fXLNnQmBA8JcvghkbXtUCQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jewb_KJJacPfD_ZWs9sm6w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*swmXyLuJZRtWWqamfYN8NQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AmmkAm5_Em9t_kw0PhEtrw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Brw8wi7VG9gM1tJBFqL7JA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QpharjfyQTu2YySVAL8eWg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LAHrcg1jIbyWXj_9Y2XWTw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L7Pa9HWxp_qSNYdZ7B2Z_Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v8V7-eOAsYKhG7IeG4CdXA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pV71I-ZPfFLbKMSyVJWWRQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-zlYrXVTURuobi1csFJ4-g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bT6l4XDu-djd1zmzSbr3hg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bxwG1bAuiWdFk_HsRNn2Ow.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n2ZZwJBpwIhq6hj7utGGjA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s4-pookxwwBEiuvZbB0MIg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L31aL_vZ8XdNlg0FxYlCOg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N_O9gZ0oCyZh9fGNCIvXmw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tl2LJwgjT38_GgY7wmU5BQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X3jHD1uBYXQHvT6shapUnA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*auuaI32LOtwbRAh07vvAWA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HtS-ngnGkCsP6Juk5iS2ig.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bzQkcuGUp5mNa5PUo4fZhg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N6tBhLtP7QnWTSarnpJY4g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gFQr_zJ0xWDwJco_P77BOw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f4WYyDyuruq8qhvu-tSVdw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OJacGXVeIjwX3e88Oa9L9w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lvlAXAOAmdHWQ4L18Rp8mA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xa-p4Q4ZwD-eWarhj30emw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pmRfZjTq3oH5ysjUkh5KIA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TY48ETwy7_a-TPl-jOBQxA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v4g9pOIY93_C9McT2BWsIw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ejvmJZj5roOVtkawi8hzrw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rCGJjAnLBdWpg4MChfTaqQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fw84C8MmjXfKwQj2W9uklA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JpWMnlQYcsvG2CqDaPR4Dg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zwRjCQ14dcqjPapD8QBZAQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ch-CpJaq2xEL_uWxvrYriQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uj5BnGux6sdL8YhrM1hJXw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vRYnca5E5wvYX9pQWb8jfg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HAnqXbUFQbO8n21wPcMrKA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dwwaurRnQ1KLLPyGkVB5Zg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jVStjek26c2bVpGWlZp2Sw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p89E67rq8SMLeYS-9IWmIg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2J_FP-xpY4ZL9kWnts8RAg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*egIYUJgXoKeWzf9QoUrqDg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nM0GN5skwzJDx1O8qcGKhQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t-8abDCQ9XAOJtt_GvlA3g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*62PhZHehzDqKlWCPLgttCg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XyRO5x3Tgmr3-xoJHUQ71g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TM2s7HR_eu9cB1BxYS-Cww.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8PEUk4Vq1RQywmqqdqGvdw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YtuRYIw2jpXOrodWaXXzvg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-eydqmbKq5WKUOlmQileSg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jNFjjLDTLbJXL5LyclRdEQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RuvrLeolRjxyrhO2ct0gXQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PJ1Hda0ut6ev_4wjoSd-pA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nPE0B_RJIo-3Uk4NBf_enQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GavPXcDV14hSsyMeOP2Krg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D-XJ_7u6P4xUhbci81mkpA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LiRieKgs94-g16uBIRWuEg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y7jmh8FmGbTdhrAxiKA1EQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2H-CDYs_zotDGaUrKdB2kg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*75Y-q6kkLyOOEK9xirR4uA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qfpIBhK4j_YEg1quBHKYIw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jXmpLLrMtQdgLzIoy8_GlQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_QUzjRgPJU5EED10Qgdbbg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oJ7zmL5FlhkZeaZHFRIf_g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UudssVvYdWbDHIs2QnCvog.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yI2xJ0Q9UtB0ZgGZWZELow.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rrx4_zz4ire-scv2_M1KYQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*88oVB7ydgYT35fNc6TbIJg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9ELwtyb7Vez3N7B5gXTQVQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ptStGCSJBJuBgwhGuFNeTA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5EM9IwT6S8k3kf0fDyDAbg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4G24SGyLeIB4naSw12kmKA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N52ZGEfQBFo51qpV4ChskQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qYpc4EvvEgLPCDFcbW_auw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CmaBUQMSnwiUbEJBLDC_xA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xL2gzAV3THaOmfl9Ek5MUQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1QgaWsUmvUv9qZ2PYI1ZLg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hL6cOhZ8Y2cF5LZl1L0raw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GwYQJ759J95pqs1MN9cX6g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cQ5mF3u2OIhMgW5BMVWPaA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C4ZpRaipZ1KOSgQoT2rYTg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hwqITptsruDQw5fPeugKkQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hwqITptsruDQw5fPeugKkQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MUCZyWesnMP8y4RE1TJ0hw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YDoO40-YlHbzjN9VQlj-oQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R1ViyTZlxumunzOLpHKGWw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kb8HkWIKZDPUaKJneCs_CQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W4xSkxZjPAomlFRVFAlzdQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CCTIh_sNOK0A952uRmjL9Q.jpeg" /></figure><p>Its interesting for myself to look back at these pictures, I don’t know why, I just find it interesting.</p><p>I’m now using <a href="https://github.com/mroth/lolcommits">Lolcommits</a> and will make a new post once the project I’m working on is Live.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=840ca4a3011a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fear-and-coding/ica-the-gitshots-840ca4a3011a">ICA : The GitShots</a> was originally published in <a href="https://medium.com/fear-and-coding">Fear and Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I Wish I knew]]></title>
            <link>https://medium.com/fear-and-coding/what-i-wish-i-knew-dd4a50e5237b?source=rss----39e7bbfe62ab---4</link>
            <guid isPermaLink="false">https://medium.com/p/dd4a50e5237b</guid>
            <dc:creator><![CDATA[Shaun D]]></dc:creator>
            <pubDate>Sat, 06 Dec 2014 01:27:36 GMT</pubDate>
            <atom:updated>2014-12-09T20:23:30.458Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*GECVVluN5z13c7m01vr_Wg.jpeg" /></figure><p>I, Coder.</p><blockquote>This is a republished post from a deleted blog.</blockquote><p>I’m a massive Adam Savage fan. It’s not just Mythbusters, it’s almost everything that he does that I’m inspired by. He’s certainly one of the top 10 most influential people that I hold in high regard. He’s a maker, a storyteller, a high functioning hoarder and someone who loves pop culture. When he speaks, he speaks from the heart and always about the things that he loves with such passion, that it leaves me hooked</p><p>There’s a big maker movement going on at the moment in our world, it can’t really be ignored. Etsy, Kickstarter, Thingyverse and a bunch of other platforms have enabled makers to turn their hobbies and passions into small business and have their projects reach hundreds. I’ve always seen common traits in the maker movement and the programming community, we seem to share a lot of similar traits and our paths tend to cross a lot.</p><p>So, with that, I have decided to riff off of <a href="http://www.tested.com/art/makers/461291-maker-faire-2014-adam-savages-10-commandments-making/">Adam’s 10 commandments of making</a> speech that he gave at this years Makerfaire and make a list of things that I wish I could go back in time and tell myself as a younger, thinner programmer. I’ve outright stolen some of his ideas, but tried to make them a little more relevant for programming, but I also think they can be relevant to almost any profession.</p><h2>Make something, anything.</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/306/1*YMo1H7Mo1kSNlepb073syw.gif" /></figure><blockquote>“How should I get started with X”.</blockquote><p>Just do it. If you want to get started with Python, build something with it. JavaScript? Build something. It might seem hard at first, it might seem impossible, but I promise that there is no better exercise that trying. We live in a time where people write detailed tutorials, step by step instructions and getting started guides every single day for different things and these are published on a platform that we can access at almost any time day and night. Screencasts, conference talks and podcasts are available mostly for free. You can see new code on github on a daily basis, you can see they achieved something and you can learn from that. The access to source code, to articles and tutorials is only growing and the things you can learn just from having internet access is nothing short of incredible.</p><p>If you can’t think of something to make, ask someone, Check out the barrage of ideas on <a href="http://www.reddit.com/r/SomebodyMakeThis/">/r/SomebodyMakeThis</a> or find a problem that needs to be solved in your workplace. Seriously, making anything at all is better than sitting around and doing nothing.</p><h2>Make stuff that improves your life</h2><p>There is nothing more satisfying than surrounding yourself with things you have made. Make your own todo list, twitter-bot, something that can improve your workflow or life. There might be something out there that does 80% of what you want it to do — grab it, rip it apart and learn how it works, you can then begin putting it back together and start adding the other 20% you need to make it the thing you want.</p><h2>Don’t wait</h2><p>Do it now. Begin. You can forever be saying to yourself ‘Let’s put it off till tomorrow’, ‘Let’s wait until tomorrow’ and there will come a point to which you say ‘How many more tomorrows have I got?’. Tomorrows eventually stack up and just become a pile of Yesterdays.</p><h2>Use a project to learn a skill</h2><p>I love reading and listening to people talk about programming, but the way I learn best is by just digging in. If you want to learn backbone.js, then find the right project to use it. You might feel that you don’t know if its the right tool for the job, but that comes with experience. I will hold back on using something new until I think I have the right project to use it on. I find that I just learn something at a level of detail that no book can dive into when I have a deadline fast approaching.</p><p>Use the ‘Make something’ attitude to test drive languages, frameworks and utilities and never be afraid to step out of your comfort zone.</p><p>Make a list of all the things you want to learn and anytime you see a resource for learning that thing, add it to the list. On a quiet Saturday night or Sunday morning, pick something from that list, learn a bit and make something. I can’t tell you how many times I’ve gotten up early on a Sunday for the early morning F1 races, everyone in the home still asleep, and just started hacking away at something for a couple of hours. No commitment to the project (yet) just having fun with code.</p><h2>ASK.</h2><figure><img alt="" src="https://cdn-images-1.medium.com/max/432/1*dTqUM4JfB2htNS9Dvaszbw.gif" /></figure><p>Ask for help. We are so lucky that we now live in an age where we are at most a single tweet, stack overflow question or IRC chat away from getting help with something. Ask your co-workers for help, people at meet-ups and conferences. If you’re stuck with using a tool that somebody else built, find out a way to contact them and ask for help. There are very few things more satisfying than helping someone, extending their knowledge and then sitting back and watching them do some great things with that knowledge now at hand. Don’t wait to ask because you think you’re going to feel like an idiot for not knowing, ask now.</p><p>Ask for feedback. Meetups are a great place to unveil a project you’ve been working on and you can get almost immediate feedback. Reddit has several programming subreddits that have people consistently positing their projects and asking for feedback. Ask the people you work with and respect the opinions of. Ask friends and family. Feedback, however critical, is always of value.</p><h2>Share your methods and knowledge, don’t make it a secret</h2><p>Only you have a monopoly on being you.</p><p>If you think that your technique or the little utility you’ve made is the thing thats makes you special, you’re an idiot, because it’s not. It’s the things that you do with that knowledge and skill that make it special. Im not saying that you have to give your code away for free, I’m not saying that you can’t sell an app, but you can share anything you learnt or did to make that app or You might be able to share a utility or framework that you made to help out.</p><p>You likely learnt some of the things you know from someone sharing with you, so try to pay it forward where you can.</p><h2>Discouragement and failure are intrinsic to the process</h2><p>Things are going to break. Something won’t work and it’s all going to be your fault.</p><p>One of the hardest things that you will have to deal with as a programmer is the fact that you’re going to be wrong, a lot.</p><p>Sometimes your going to fuck everything up. Sometimes you’re not going how to fix it or how long it might take to fix and you’ll have multitudes people telling you that it has to be done today, tomorrow or ASAP. Come to terms with the feelings of not being good enough, don’t try to hide from it. We all know that we learn from our mistakes and sometimes the best way to learn from them is to share them with others. How, Why and When did it all go so wrong?</p><p>You will usually have to work under pressure and time will always be a factor of that pressure. The mistakes that are always worse are the ones made under pressure and it always takes twice as long to go back and fix them. You need to learn where your tipping points are and understand the signs that begin to appear right before you’re about to go over the edge and where things are going to go wrong.</p><p>Share your failures with others. Telling stories is part of what makes us human and we can use those stories to help prevent from failing the same way twice.</p><p>“Failure is a bruise, not a tattoo.”</p><h2>Measure carefully</h2><p>“The difference between knowing what tools to use is everything that separates the craftsman from the novice”</p><p>Anyone who takes enough time can make it perfect. Time is usually the only limiting factor even if you have no skill, you can slowly work through everything and figure it all out. Tools, technique and knowledge will reduce that time.</p><p>Talent is something you have naturally, Skill is something that is built after you’ve put in the hours.</p><h2>Make things for other people</h2><p>Just like making something for yourself, making things for other people is just as satisfying. It doesn’t have to be thousands of other people, it might be just a few, but knowing that those few people use the thing you made, is an awesome feeling. Make something as a gift or just a kind gesture. Make something to make someone smile and laugh. Make a tool that people can use or learn from. Its gratifying and when you are trying to think of something to make, consider this as an option.</p><h2>Don’t be a dick</h2><p>Not a week goes by where something doesn’t appear in my general reading stream where someone is being a dick. Its either someone has been a dick and people are one a rant, or someone has disagreed with something someone else has done and then a group have people have banded together to socially execute that person, and it usually ends up with someone loosing their job.</p><p>I try to stick to <a href="http://www.urbandictionary.com/define.php?term=Wheaton%27s%20Law">Wheaton’s Law</a> . I can’t say that I haven’t occasionally been a dick on Social media, hell, I once got a firm verbal spanking at a job when I <a href="https://twitter.com/shaundunne/status/242625920660299776">tweeted</a> that a clients developer had 288 occurrences of !important in a single CSS file. Sure, it was bad and I was venting because I had to now work around this, but I was being kind of a dick about it.</p><p>Also when you’re at conferences, try not to be a dick, to anyone.</p><p>Be excellent to each other. And … party on dudes!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd4a50e5237b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fear-and-coding/what-i-wish-i-knew-dd4a50e5237b">What I Wish I knew</a> was originally published in <a href="https://medium.com/fear-and-coding">Fear and Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Code Live : LFW Twitter Wall]]></title>
            <link>https://medium.com/fear-and-coding/code-live-lfw-twitter-wall-5d3fa260c5f9?source=rss----39e7bbfe62ab---4</link>
            <guid isPermaLink="false">https://medium.com/p/5d3fa260c5f9</guid>
            <dc:creator><![CDATA[Shaun D]]></dc:creator>
            <pubDate>Sat, 06 Dec 2014 01:04:53 GMT</pubDate>
            <atom:updated>2014-12-06T01:04:14.526Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been tasked with building a twitter wall for London Fashion Week. This is to only pull pictures in and I thought it’d be fun to sort of blog my thought process. I’ve got until Next week to do it, but I want to get something up and running by tomorrow.</p><p><strong><em>4th Sept : 12pm</em></strong></p><p>I started with the Node <a href="https://github.com/sahat/hackathon-starter">Hackathon Starter</a> . I’ve had it in the back of my head for when I needed to do something reasonably fast — now seems to be the best time to break it out and give it a try.</p><p>Gotta think of a name….A wall.</p><p>Jericho.</p><p>I clone it down — remove the .git file and run a fresh git-init in the repo. Added my bitbucket repo as remote. Added all the initial files, commit, push.</p><p>I go through the starter kit code and see what it has to offer me — a lot. There’s potential to use FourSquare and maybe also Instagram — but getting pictures from twitter is the main focus.</p><p>I’ve got some information on the screen size and screen resolution that the wall will be on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DWS4uqR-6_WRnq8ijiwDog.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NTiK7IBoAUAC88524iZJBQ.jpeg" /></figure><blockquote>LED Screen actual resolution is 512pixels by 320pixels. We feed this though a video matrix that takes a 1080 signal and down samples, scales/crops to 512 x 320</blockquote><blockquote>Screen Size 4.48m Wide by 2.8m Tall</blockquote><blockquote>Pixel Pitch is 8.75mm</blockquote><p>Okies. Im not going to worry about that right now — after some quick calculations — it’s a 16:10 aspect ratio I think. Front end doesn’t matter too much right now.</p><p><strong><em>2pm</em></strong></p><p>Post meetings, post lunch. I get cracking back on with the boilerplate, start taking a few things out that I know I definitely don’t need, other bits that I probably don’t need can wait until I’ve got this working. It already comes equipped and ready with the Twit node module, so I create a new route, a new controller and get those working.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SmXyK4rESvMpmXK6jQRCuA.png" /></figure><p>Cool, that works, I can display some tweets with a search attached.</p><p>Time to look at the Twit module and see if I can get streaming working.</p><p><strong><em>3pm</em></strong></p><p>I’ve had a look through the docs of the Twit module and can definitely get the stream working. I’ve got to jump in a meeting in a bit though.</p><p><strong><em>5:30pm</em></strong></p><p>After a meeting and helping out some other people with some bits I finally get the chance to sit down and have another look at this fetching the twitter Stream.</p><p>All good. Now I have an event that happens when a new tweet comes in that matches. At the moment it’s just showing in the log, but it’s working.</p><p>Now, time to head home, I can think about it more there.</p><p><strong><em>00:00am</em></strong></p><p>Glitch Mob goes on, and time to figure out the best way to do this.</p><p>Im thinking about using Socket.IO?? Maybe push all the tweets into a buffer and then when I have enough (it’s a waste of a call maybe to shoot 1 at a time down the pipe) I can pipe them through Socket.io and add them to the DOM??</p><p><strong><em>01:00am</em></strong></p><p>Socket.io seems to be working as expected. Now on to getting it to render — will probably need to get some help from a lib here. Ember? React maybe?</p><p><strong><em>2:00am</em></strong></p><p>I was going to be brave and do it with React — but after a quick re-fuel and fiddling with Socket.io, I settled on potentially doing the front end rendering with Angular.</p><p>Have I ever mentioned how much I dislike Jade templates?</p><p>Ronald Jenkees is on to get me through getting Angular set up.</p><p><strong><em>5th Sept : 10:50am</em></strong></p><p>At some point last night I fell asleep. Woke up pretty late and had to get to work. Got in, did a few things and back to this. Last night I left it at writing the html (or jade) for displaying the tweets.</p><p><strong><em>12:36pm</em></strong></p><p>Can’t get this bloody socket.io thing working now.</p><p><strong><em>4:00pm</em></strong></p><p>Asked to stop working on the project….</p><p><strong>Update : 6th December 2014</strong></p><p>Our version of the twitter wall never went further than this. I don’t know the reasons why. Its always a shame to never actually finish something that you really want to, but I found this in my ‘Drafts’ and thought that it was something worth publishing.</p><p>For those of you who are working in agencies or who want to work for them, I hope this gives you something, even if that something is a word of warning. Sometimes you will be asked to do things at short notice and sometimes you will want to do them bad enough that you will work the hours necessary only for the opportunity to disintegrate pretty quickly. You won’t always get to finish everything and that is just one of those things you have to live with.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d3fa260c5f9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fear-and-coding/code-live-lfw-twitter-wall-5d3fa260c5f9">Code Live : LFW Twitter Wall</a> was originally published in <a href="https://medium.com/fear-and-coding">Fear and Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s actually wrong with Angular.js?]]></title>
            <link>https://medium.com/fear-and-coding/whats-actually-wrong-with-angular-js-149f40539d11?source=rss----39e7bbfe62ab---4</link>
            <guid isPermaLink="false">https://medium.com/p/149f40539d11</guid>
            <dc:creator><![CDATA[Shaun D]]></dc:creator>
            <pubDate>Tue, 07 Oct 2014 14:30:15 GMT</pubDate>
            <atom:updated>2014-10-07T14:30:15.529Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Tc-mFPUs0XSYQjDkNzNoQ.jpeg" /></figure><p>Nothing.</p><p>Now go build things.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=149f40539d11" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fear-and-coding/whats-actually-wrong-with-angular-js-149f40539d11">What’s actually wrong with Angular.js?</a> was originally published in <a href="https://medium.com/fear-and-coding">Fear and Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>