<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dave Berner on Medium]]></title>
        <description><![CDATA[Stories by Dave Berner on Medium]]></description>
        <link>https://medium.com/@daveordead?source=rss-cddbbd21a977------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*apt_4JgxykeKbQNUNCM5Xw.jpeg</url>
            <title>Stories by Dave Berner on Medium</title>
            <link>https://medium.com/@daveordead?source=rss-cddbbd21a977------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:28:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@daveordead/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Handling SCSS variables at scale]]></title>
            <link>https://medium.com/fed-or-dead/handing-scss-variables-at-scale-78e14652175c?source=rss-cddbbd21a977------2</link>
            <guid isPermaLink="false">https://medium.com/p/78e14652175c</guid>
            <category><![CDATA[scss]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[frontend]]></category>
            <dc:creator><![CDATA[Dave Berner]]></dc:creator>
            <pubDate>Sun, 03 Sep 2017 08:27:38 GMT</pubDate>
            <atom:updated>2017-09-03T16:22:06.037Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x2gUD6BhNjkF7ac4UEwg5Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/5mZ_M06Fc9g?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Roman Mager</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Variables in SCSS are a wonderful thing but they can quickly get out of hand, trying to maintain them across several files without accidentally reassigning them or keeping track of where they originated or what their scope is supposed to be.</p><p>The problem fundamentally is that SCSS has no concept of locally scoped variables, much like CSS itself, everything is in the global namespace.</p><p>I’ve adopted a pattern that I’ve used in my projects for the last couple of years where scoping is emulated using a simple naming convention.</p><p>I have a single _variables.scss file which contains all my “global” variables. These are all prefixed g- to easily identify them across the app.</p><p>For example:</p><pre>// _variables.scss</pre><pre>// Colours</pre><pre>$g-color-blue: #509cf6;</pre><pre>$g-color-green: #1bb362;</pre><pre>$g-color-brand: $g-color-green;</pre><pre><br>// Font scale</pre><pre>$g-font-size: 16;</pre><pre>$g-font-size-large: 20;</pre><p>The g- flag indicates they are intended to be used across multiple files.</p><p>Then in my component files I have a set of variables declared at the top of the file. For example if I had an accordion component I would set out the file along the following lines:</p><pre>// _accordion.scss</pre><pre>// Variables</pre><pre>$c-accordion-background-color: $g-color-blue;</pre><pre>$c-accordion-font-size: $g-font-size-large;</pre><pre><br>// Base</pre><pre>.c-accordion { <br>    background-color: $accordion-background-color;<br>    font-size: rem($g-font-size-large);<br>}</pre><p>This is obviously a contrived example, but I have found this pattern to be hugely beneficial on huge projects with large numbers of components and app-wide variables to keep track of.</p><p>It is important to note that local component / module variables should exclusively be used in their component files in order to emulate local scope.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78e14652175c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fed-or-dead/handing-scss-variables-at-scale-78e14652175c">Handling SCSS variables at scale</a> was originally published in <a href="https://medium.com/fed-or-dead">FED || Dead</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 reasons you should be hiring more junior developers]]></title>
            <link>https://medium.com/fed-or-dead/7-reasons-you-should-be-hiring-more-junior-developers-49f8d4a32fd0?source=rss-cddbbd21a977------2</link>
            <guid isPermaLink="false">https://medium.com/p/49f8d4a32fd0</guid>
            <category><![CDATA[junior-developer]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Dave Berner]]></dc:creator>
            <pubDate>Tue, 05 Jan 2016 08:33:01 GMT</pubDate>
            <atom:updated>2016-01-05T08:40:59.059Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PDspC41iJ_id8CTogim4TQ.jpeg" /></figure><p>I know it’s tempting, you’ve finally been given extra headcount for your team or you’re about to start a new project and your first thought is, “I want senior <em>rockstar</em> developers who really know their stuff”. I want a team of elite experienced individuals who are going to knock this out of the park.</p><p>I’m urging you to consider another option.</p><p>There are a number of advantages to growing or seeding your team with juniors rather than having it comprised of just mid-weight and senior developers.</p><h4>1. Mentoring is rewarding for everyone</h4><p>Having some junior developers mentored by your seniors keeps both sets on their toes. It encourages pair programming and joint problem solving where juniors will ask questions resulting in the seniors reinforcing their own knowledge.</p><p>It demonstrates to your seniors that you have confidence in them and their abilities whilst simultaneously developing their leadership skills.</p><p>Senior developers won’t always seek help or ask questions of their peers for fear of coming across as not understanding something they feel they should know — which in the long run, is holding them back from improving. You can alleviate this by introducing the mentoring model which brings about a culture where asking questions is not only acceptable but encouraged.</p><h4>2. Finding good people is hard, so breed great people in house</h4><p>This one speaks for itself really. At all my previous companies we spent a lot of time interviewing unsuitable candidates. It’s very tough to find people that have exactly the right combination of skills and character traits.</p><p>If you hire junior developers with the right attitude they will learn from your experienced team members and become the seniors you wished you were able to find.</p><h4>3. Passion is infectious</h4><p>Do you remember when you first got into web development, using tables for layout and spacer gifs? That pride when you could add a <a href="http://www.w3.org/QA/Tools/Icons">W3 validation badge</a> to the footer of your fresh new website! Remember how stoked you were to have landed your first professional development job?</p><p>The juniors of today have that passion and drive you had then, they can’t wait to get started! It’s infectious, adding new fresh, enthusiastic people will increase the motivation of your existing team.</p><h4>4. Generate new ideas</h4><p>It’s easy to get stuck in set ways of solving certain problems. I myself have been guilty of not going back to check whether some of my old CSS hacks or workarounds are still needed with modern browsers.</p><p>Junior developers won’t have solved all these problems before and don’t have preconceived ideas about how things should work, so will be looking at them with fresh eyes.</p><h4>5. Avoids butting heads</h4><p>One of the main problems with having a company built of people at the same level, is everyone thinking they know best. If a problem crops up there is no hierarchy for difficult decision making. It is common for egos to get in the way of coming to the right solution.</p><p>Having a team comprised of varied weights means there is always someone to defer to when this situation arises.</p><h4>6. Creates progression opportunities</h4><p>As compelling as the day to day work and salary can make a role, a lot of developers want to be able to progress. Creating mentor and leadership roles for seniors to aspire to and mid-weight positions for juniors to work towards, means good developers will remain working for you for longer.</p><h4>7. How are they ever going to move past junior level if we don’t give them a shot?</h4><p>This is a big one for me.</p><p>Years ago when I took that first step into an established company it didn’t just improve my coding skills but also gave me exposure to processes like version control, deployment, agile workflow, development cycles and a whole host of other things that contribute to becoming a well rounded developer. I wanted to learn these things but often wasn’t hired because of my lack of experience in these areas. A Catch 22 situation.</p><p>There are currently more developer jobs than people to fill them, myself and my colleagues are endlessly harassed on sites like LinkedIn by recruiters trying to pry us away with promises of amazing roles whilst I’m seeing a large number of junior developers on Twitter looking for a single opportunity to shine. This is crazy to me - let’s give these juniors a chance!</p><h4>In conclusion</h4><p>I think these are all compelling reasons to add junior developers to your team make up. With that said, you need a balance! Don’t have the majority of your developers be juniors when starting on a new large project or start-up, you’ll need the experience that comes with having seniors on board as well.</p><p>I believe a well balanced team is the cornerstone of a successful tech business and hope this post inspires you to make some junior hires this year.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49f8d4a32fd0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fed-or-dead/7-reasons-you-should-be-hiring-more-junior-developers-49f8d4a32fd0">7 reasons you should be hiring more junior developers</a> was originally published in <a href="https://medium.com/fed-or-dead">FED || Dead</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Battling BEM – 5 common problems and how to avoid them]]></title>
            <link>https://medium.com/fed-or-dead/battling-bem-5-common-problems-and-how-to-avoid-them-5bbd23dee319?source=rss-cddbbd21a977------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bbd23dee319</guid>
            <category><![CDATA[bem]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[css]]></category>
            <dc:creator><![CDATA[Dave Berner]]></dc:creator>
            <pubDate>Tue, 08 Dec 2015 09:51:16 GMT</pubDate>
            <atom:updated>2016-06-02T21:39:06.146Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YiNzs1FIlS1SNVlOYYuK9g.jpeg" /></figure><p>*** PLEASE NOTE: This article has been extended as of 01/06/2016 with an additional 5 problems. The latest version (which includes all the below points also), can be found here: <a href="https://www.smashingmagazine.com/2016/06/battling-bem-extended-edition-common-problems-and-how-to-avoid-them/">https://www.smashingmagazine.com/2016/06/battling-bem-extended-edition-common-problems-and-how-to-avoid-them/</a> ***</p><p>Whether you’ve just discovered BEM or are an old hand (in Web terms anyway!) and have been using it for the past few years, you can probably already appreciate what a useful methodology it is.</p><p>If you don’t know what BEM is I suggest you <a href="https://en.bem.info/">read about it here</a> before continuing with the post.</p><p>Now, I’m under no illusion that this is a beautiful way of naming things. It’s absolutely not. One of things that put me off adopting it for such a long time was how eye-gougingly ugly the syntax is. The designer in me didn’t want my sexy markup cluttered with dirty double underscores and foul double hyphens.</p><p>The developer in me looked at it pragmatically and eventually the logical, modular way of building UI outweighed the right-side of my brain complaining “but it’s not pretty enough”.</p><p>I certainly don’t recommend picking living room centre-piece this way, but when you need a life jacket (as you do in a sea of CSS) I’d take function over form any day.</p><p>Anyway – onto the dilemmas:</p><h4>1. Grandchildren selectors</h4><p>These bad boys are the bane of my life — and I’m sure their misuse is one of the reasons people have an immediate aversion to BEM. I’ll give you an example:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8c3438fd0825f57136e05a088fbff675/href">https://medium.com/media/8c3438fd0825f57136e05a088fbff675/href</a></iframe><p>As you can imagine, this can quickly get out of hand and the more nested your component is, the more hideous and unreadable the classnames become. I’ve used short words like card, body, text and link but you can imagine how out of control it becomes when your block element is called something like drop-down-menu.</p><p>My belief is the double underscore pattern should only appear once in a selector name. You should never end up with anything like: parent__child__grandchild__greatgrandchild. If you’re getting to great great great grandchild levels you might want to revisit your component structure anyway.</p><p>BEM naming isn’t strictly tied to the DOM so it doesn’t matter how many nested levels deep a descendent element is. The naming convention is there to help you identify relationships with the top level component block — in this case, card.</p><p>This is how I would treat the same card component:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1728549a2566ab28f41bb5f8de34ab29/href">https://medium.com/media/1728549a2566ab28f41bb5f8de34ab29/href</a></iframe><p>This means all the descendent elements are only affected by the card block. So, we would be able to move the text and images into card__header or a new card__footer element without breaking anything.</p><h4>2. Cross component… components</h4><p>Another issue commonly faced is if a component’s styling or positioning is affected by it’s parent container. This specific problem is covered in a lot <a href="http://simurai.com/blog/2015/05/11/nesting-components/">more detail here</a> and <a href="https://en.bem.info/forum/4/">here</a>. I’m just going to fill you in on my preferred approach.</p><p>To summarise, let’s assume we want to add a button into the card body of our previous example. Button is already it’s own component. It looks like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a39d6a1e1d84923287308c7715fb6c27/href">https://medium.com/media/a39d6a1e1d84923287308c7715fb6c27/href</a></iframe><p>If there are no styling differences to the regular button component, then there is no problem, we just drop it in like so:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4404dd9a4da3ffa07986d7213a345951/href">https://medium.com/media/4404dd9a4da3ffa07986d7213a345951/href</a></iframe><p>However, what happens if there are a few subtle styling differences, e.g we want to make it a bit smaller, have rounded corners, and add a drop shadow but it’s specifically only when part of a card component? I find a cross component class to be the most robust solution i.e:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bd2c9b9c662946883d2425f0236e0901/href">https://medium.com/media/bd2c9b9c662946883d2425f0236e0901/href</a></iframe><p>The unique styling attributes are applied to card__button which lives in the with the rest of the CSS for card. This means if you decide to remove the card component, the unique button styles are removed with it, without you having to remember to do so. It’s worth putting a comment in your CSS to indicate that it is a cross component style.</p><p>Of course, the other option is to go back to your designer and tell them the button should be consistent with the rest of the buttons on the site and avoid this issue altogether… but that’s one for another day ;)</p><p>I would also apply the rule of 3 here. This means, if later on in development this same button styling crops up a further two times, then abstract it to it’s own modifier.</p><h4>3. Modifiers or a new component?</h4><p>One of the biggest problems is deciding where a component ends and a new one begins. In our card example, you might later create another component called panel with very similar styling attributes but a few noticeable differences.</p><p>But what determines whether there should be two components panel and card or whether you simply create a modifier for card that applies the unique styles.</p><p>It’s very easy to over modularise and make everything a component. I recommend starting with modifiers but if you’re finding your specific component CSS file is getting difficult to manage then it’s probably time to break a few of those modifiers out. A good indicator is when you find you’re having to reset all the “Block” CSS to be able to style your new modifier, this to me suggests new component time.</p><p>The best way if you work with other developers or designers is to ask them for an opinion. Grab them for a couple of minutes and discuss it. I know it’s a bit of a cop-out answer but on a large application its vital that you all understand what modules are available and agree on exactly what constitutes a component.</p><h4>4. What should I name wrappers / containers?</h4><p>Some components require a parent wrapper or container that dictates the layout of the children. In these cases I always try to abstract the layout away into a grid and the component is simply the contents of each grid cell. In our card example, if we wanted to layout a list of 4 cards, I would use the following markup:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/70c124cc44d467a2a383609b38a928a8/href">https://medium.com/media/70c124cc44d467a2a383609b38a928a8/href</a></iframe><p>Don’t be afraid to use a little extra markup to save yourself a massive headache. No-one is going to pat you on the back for shaving off a couple of &lt;div&gt; tags!</p><p>In some instances this isn’t possible, for example your grid isn’t going to give you the result you want or you simply want something semantic to name the parent element. In this case I tend to opt for the word container or list depending on the scenario. Sticking with our cards example, I might use &lt;div class=“cards-container”&gt;[…]&lt;/div&gt; or &lt;ul class=“cards-list”&gt;[...]&lt;/ul&gt; depending on the specific use case. The key is to be consistent with your naming convention.</p><h4>5. How to handle states?</h4><p>This is a common problem, particularly when styling a component in an active or open state. Let’s say for example our cards have an active state, so when they’re clicked on they get a nice border styling treatment to make them stand out. How do you go about naming that class?</p><p>The way I see it you have two options really, either a standalone state hook or BEM like naming as a modifier:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a18aa740f143831ad774a952a39cfc47/href">https://medium.com/media/a18aa740f143831ad774a952a39cfc47/href</a></iframe><p>Whilst I like the idea of keeping the BEM like naming for consistency, the advantage of the standalone class is that it makes it easy to use javascript to apply generic classes to any component. This proves to be more problematic when you have to apply specific state classes for each component. Possible, but it means writing a lot more JS.</p><p>It makes sense to stick to a standard set of state hooks, <a href="https://medium.com/u/5a285923fa03">Chris Pearce</a> has <a href="https://github.com/chris-pearce/css-guidelines#state-hooks">compiled a good list</a> so I recommend you just pinch those :)</p><h4>Conclusion</h4><p>BEM has been an absolute life saver for me in terms of creating applications in a modular, component driven way. I’ve been using it for around 2 years now and these were the few stumbling blocks I’ve hit along the way. I hope you’ve found this article useful, and if you’ve not given BEM a go yet, I highly encourage you to do so.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bbd23dee319" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fed-or-dead/battling-bem-5-common-problems-and-how-to-avoid-them-5bbd23dee319">Battling BEM – 5 common problems and how to avoid them</a> was originally published in <a href="https://medium.com/fed-or-dead">FED || Dead</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transitioning to working with a Designer]]></title>
            <link>https://medium.com/fed-or-dead/transitioning-to-working-with-a-designer-576f16d9b330?source=rss-cddbbd21a977------2</link>
            <guid isPermaLink="false">https://medium.com/p/576f16d9b330</guid>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Dave Berner]]></dc:creator>
            <pubDate>Fri, 06 Nov 2015 00:17:58 GMT</pubDate>
            <atom:updated>2015-11-06T00:17:58.155Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_ASVxMQ2WFospoTZ22MDnw.jpeg" /></figure><p>If you’re a Front-end Developer like me, odds are that you have (or believe you have) a few creative bones in your body. Since I started down the webby path many years ago my role has included both design and front-end extensively. I would typically be responsible for user journeys, wireframes, mock ups in Fireworks (Sketch more recently) and then bringing the creation to life in the browser with HTML, CSS and JavaScript.</p><p>I’ve read all the articles titled ‘should designers learn code’, (off topic, but in a nutshell I believe they should at least understand browser / code limitations) which had never really been an issue for me as I had always done both.</p><p>A few months ago I started working for Campaign Monitor, where they have a great set up. There are three main product teams comprised of a product manager, a designer, a front-end and 5 back-end developers. This makes for a mini-startup type feel which is a cool way of doing things.</p><h4>My fears</h4><p>I was initially a little bit worried as this spelled the end for my time putting mockups together – I felt like my job had been cut in half! I had a bunch of questions looping through my head:</p><ul><li>what if I didn’t like the designer’s work?</li><li>what if they don’t understand limitations of code?</li><li>what if I forget how to use Sketch?</li><li>what if they just like to create beautiful images with no thought to the end user? I see examples of this on Dribbble all the time.</li><li>and what if we hate each other?</li></ul><p>Turns out, all my fears were unfounded. The designer I’ve been paired with is extremely talented and the product manager has made sure we’ve both been involved with putting together the user stories. Whilst the designer is without a doubt a pixel perfectionist, in many ways it takes the pressure off me as it means I have my own quality assurance before anything gets shipped. Things that I might previously have let slip under the radar now get picked up ensuring we have a better quality end product.</p><p>He also recognises that I had a design background and gets me involved early, asking for opinions and feedback, checking feasibility of different approaches. It has removed the rush factor from my work and stops me being a bottleneck that’s needed to both design and build a piece of UI.</p><p>We get on really well which is imperative when you’re working with someone so closely day to day. We’ve developed a solid working relationship and friendship, which makes it easy to discuss design decisions and be empathetic to each others point of view. Enabling these type of relationships to flourish is something that is at the heart of Campaign Monitor and we definitely benefit from ensuring all hires are a good culture fit.</p><p>Perhaps most importantly, this transition has allowed me to focus more on Front-end honing my skills specific to that area - with Service Worker, ES6 and React all on my learning list I think detailed visual design on top would be an overload.</p><h3>Conclusion</h3><p>It was definitely hard to let go of that part of my skill-set but I still do design on some of my side projects so I haven’t completely abandoned it.</p><p>As our Head of Engineering said in response to my ‘<a href="https://medium.com/fed-or-dead/is-full-stack-a-thing-e9730c99c9a9">Is full stack a thing</a>’ article, we want people with a T-shaped skill-set, and I’m now happy for design to form part of my top bar rather than my stem.</p><p>We’re currently looking for Front-end Developers in the San Francisco area so if it sounds like the sort of set up you’d be interested in, reach out :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=576f16d9b330" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fed-or-dead/transitioning-to-working-with-a-designer-576f16d9b330">Transitioning to working with a Designer</a> was originally published in <a href="https://medium.com/fed-or-dead">FED || Dead</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Giving back – an hour of code]]></title>
            <link>https://medium.com/fed-or-dead/giving-back-an-hour-of-code-b26ea5c7656f?source=rss-cddbbd21a977------2</link>
            <guid isPermaLink="false">https://medium.com/p/b26ea5c7656f</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Dave Berner]]></dc:creator>
            <pubDate>Sun, 18 Oct 2015 21:42:03 GMT</pubDate>
            <atom:updated>2015-10-18T21:42:03.900Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*lMmUF-lZGzdlmdGSq7sgPw.png" /></figure><p>At <a href="https://www.campaignmonitor.com/">Campaign Monitor</a> we recently took part in the Hour of Code programme.</p><p>Essentially this involved us taking 18 school kids from year 8 (aged 12–13) for the morning, and exposing them to computer science in the workplace.</p><p>Working with code can appear a daunting (and geeky) profession that is inaccessible to most people, whereas the reality is anyone can pick up the basics. The main ingredients required to be a good programmer are problem-solving skills, asking questions, logic and creativity – which kids seem to naturally have in abundance.</p><h4>A bit of background</h4><p>In the US only around half the states allow students to count computer science courses toward high school graduation and there is a massive shortage of people studying computing.</p><p>Here are some stats from <a href="https://code.org/">code.org</a> about the state of computing in the USA:</p><blockquote>There are currently 592,067 open computing jobs nationwide.</blockquote><blockquote>Last year, only 38,175 computer science students graduated into the workforce.</blockquote><p>The below chart kindly provided by <a href="https://www.nicta.com.au/">Nicta.com.au</a> shows that in Australia there is a massive drop in the number of university applications for Information and Communication Technologies (ICT) courses whilst the number of ICT jobs is growing at a tremendous rate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5owRawWg4bMcP1BT0dLxWA.png" /></figure><p>It’s also becoming an important part of more traditional job roles and the hope is that by getting exposure early these kids will be heading in the right direction whichever career path they choose to follow.</p><h3>The event</h3><p>It was actually quite daunting having our reception area packed with 18 school children. It’s been a long time since I had to interact with a 12 year old, (probably not since I was 12 myself…) so even just trying to think of appropriate language / ways of phrasing things was a challenge.</p><p>We started off by showing them around the office, the various workspaces and giving them a taste of developer life at Campaign Monitor.</p><p>It was probably predictable that the main thing they initially latched onto were the breakfast and lunches supplied for our staff plus the ping pong tables and xboxes. A dream for most teenagers!</p><p>That said, they also seemed to grasp the advantages of working in small teams to solve problems and the benefits of the collaboration spaces we have set up. I’m not sure they appreciated the value of the optional standing desks – but I’ve yet to give them a go myself to be honest!</p><p>One of our more experienced team members then gave a brief talk on his journey through high school, university and the Campaign Monitor internship programme to his current role. I thought this was really important as it gave the kids an opportunity to see what the whole path could look like.</p><h4>The hour of code</h4><p>It was finally time for the hour of code itself. We had them work in twos – research shows students learn best with pair programming, sharing a computer and working together.</p><p>No question about it, these are smart kids. They absolutely smashed through the logic puzzles in the guise of birds both flappy and angry. If you’re interested the challenges can be found here: <a href="https://code.org/learn">https://code.org/learn</a>.</p><p>It was great to see them discussing the problems and high-fiving when they figured out the correct solutions.</p><p>To clarify these weren’t children who particularly wanted to learn coding, most of them preferred PE to IT but they had the skills required in droves.</p><h4>The Panel</h4><p>To finish the morning off myself and three of the other CM team were sat up as a panel to be asked questions by the kids. I was definitely out of my comfort zone at this point as I’d not done anything like this before. They were being rewarded with sweets for asking questions so as you can imagine it started out with, “what’s your favourite colour?”, “is it going to rain today?”, “what’s your favourite food” etc – fair play to them, they got their rewards. As I said before, smart kids.</p><p>It did then get on to more serious questions like “what was your first job?” – we had collectively done paper rounds, worked at KFC and even collected golf balls from a driving range.</p><p>“What did you score at uni?” All the guys I work with are super smart and smashed university with outstanding grades, I had to profess that I had dropped out. I wasn’t sure if that was what the teachers wanted to hear, but I hoped it showed the kids that there is more than one route into the field. A lot of developers are self taught and in my opinion having a real passion for the subject can count for far more than a degree.</p><p>At the end of the session they got a taste of the awesome lunches we have here and were let loose on the ping pong tables — I’m pretty sure they’d been eyeing them up the whole time!</p><h3>Conclusion</h3><p>I hope they got something out of it – I know I did. It was great being out of my comfort zone. It’s very different talking in front of kids than your peers. There were definitely times that you could see they had switched off and were unengaged – I wouldn’t have the skills to be a teacher these days – but then they’d surprise you with thought provoking questions.</p><p>The giving back initiative is one of the many things I love about working here. I would encourage others to get involved, ask your employer see if you can run an hour of code at your workplace. Details on signing up can be found here: <a href="https://hourofcode.com/us#join">https://hourofcode.com/us#join</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b26ea5c7656f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fed-or-dead/giving-back-an-hour-of-code-b26ea5c7656f">Giving back – an hour of code</a> was originally published in <a href="https://medium.com/fed-or-dead">FED || Dead</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why ‘I don’t have time’ is a bullshit excuse for not learning]]></title>
            <link>https://medium.com/fed-or-dead/why-i-don-t-have-time-is-a-bullshit-excuse-for-not-learning-de5eb3e780ae?source=rss-cddbbd21a977------2</link>
            <guid isPermaLink="false">https://medium.com/p/de5eb3e780ae</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Dave Berner]]></dc:creator>
            <pubDate>Mon, 12 Oct 2015 19:36:40 GMT</pubDate>
            <atom:updated>2015-10-12T22:28:42.580Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cNCgCvoRt3Y39MmWOpKNTg.jpeg" /></figure><h3>Why ‘I don’t have time’ is a bullshit excuse for not learning — a<strong>nd how to stop using it</strong></h3><p><em>I’m going to be using the terminology “things” throughout this article, because the items that interest you could be a new language (programming or otherwise), a framework, a tool, software, a skill… the list is endless. So it’s just easier to label them ‘things’.</em></p><p>I started trying to create more time because I found myself saying over and over again “I’d love to learn [that new thing] <strong>but I don’t have time</strong>”.</p><h4><em>(…Here come the excuses!)</em></h4><p>But having said that, I’d often find myself watching trash TV, or looking at Facebook or browsing some arbitrary website – essentially just wasting away the hours. <strong>It wasn’t that I didn’t have the time, it was that I wasn’t making use of it</strong>.</p><p>Although I thought I really wanted to learn all these new and exciting things, it seemed that subconsciously it was quite low on my agenda.</p><p>Sometimes the weight of all the new things would <a href="https://medium.com/fed-or-dead/help-there-s-too-much-to-learn-ea6696651457">overwhelm me</a> and I’d feel defeated before I started. If you’re like me you probably follow a whole host of blogs, a bunch of mailing list subscriptions and social outlets to boot. Each one packed with new things to learn, tools to add to your arsenal and techniques to stay on top of. So it’s natural that you’d feel like you’re drowning in a sea of tech.</p><p>It’s easy to think “this [ thing ] doesn’t apply to the role I’m in” and assume you could get by day to day without it. You’re probably right, but if we’re not learning we grow stale, bored and uninspired.</p><h3>Get organised</h3><p>I’ve found that making a list of the new things (and even old things) that specifically interest me has been enormously beneficial. This enables you to filter out all the noise and really focus on the things relevant to you. I add a short description of the item as well if the name is ambiguous.</p><p>Keep your list in a Google doc or somewhere that is easy to access, evaluate and add to. I prefer to keep mine in a rough priority order too. When I finally find the time I just grab whatever is top of the list.</p><p>“That’s great”, you’re thinking, “but finding the time is the problem in the first place!”</p><p>Touché. I’m going to cover that now…</p><h3>Finding the time</h3><p>Whilst it’s tempting to try everything out at once, it’s unlikely to stick. Your best bet is to try these approaches independently and stick to the ones that work for you.</p><h4>1. Ask your boss!</h4><p>We’re not all blessed with working at a company that allocates training / learning time each week. But after asking one of my previous employers for it we were granted that luxury and it made a huge difference. Each team member was granted a half day each week to dedicate to learning. All email, Slack, Hipchat etc shut down and time blocked off in the calendar as busy. We’d physically hide ourselves away for the half day if we had to.</p><p>It’s worth asking the question of your manager. The worst they can say is “no”. And even if they do, it still shows them that you’re keen to develop and love what you do which can only reflect positively. If they say “yes”, you’ll be benefiting not only yourself but the rest of your team and even the business as a whole.</p><h4>2. The journey</h4><p>My bus ride to work is populated by people glued to their smart phones scrolling through baby photos on Facebook or flicking through other social sites.</p><p>This is prime prep time. Try to do your blog catch ups and subscription pruning now. As I said earlier a lot of the things you hear about probably won’t apply to you so this is an ideal time to collate the list of ones that do.</p><p>For a longer commute use a Kindle or e-reader and do some road learning on your way to the office. You can pick them up for as low as $100 which is a small price to pay for your personal development.</p><h4>3. Fight the snooze button</h4><p>It sounds easier than it is, but try getting up a little earlier at the weekend and get a couple of hours of learning in. I personally find this one to be the most useful. My wife has a tendency to sleep later than me, so I make a point of getting up extra early (quietly…) on one of the days to play with something new.</p><p>If weekends aren’t an option, get up a bit earlier on a week day and learn at home or go to the office and use their facilities before anyone is there to distract you…</p><h4>4. The calendar is your friend</h4><p>The calendar on my phone has been a huge help. I’ve set a recurring calendar reminder for Wednesday saying ‘learn something new this week’. That way I can feel smug if I already have, but I know to get my ass in gear if I haven’t. I usually set it for a few minutes after my bus is due so it pops up on my commute.</p><p>Block some time off in your calendar, start small, even if it’s just one lunch time or evening per week set aside to learn something new. At least that way it’s there as a constant reminder.</p><h4>5. Experiment on your new projects</h4><p>When you start a new project refer back to the list you wrote earlier and just try adding one or two tools or techniques from it into the project. You’ll know pretty quickly whether this is a something that’s going to help or hinder your development.</p><h3>Conclusion</h3><p>I’ll admit that none of these suggestions are ground breaking, (I’m still trying to figure out how to alter time and physically create more hours…) but if you’re reading this looking for ways to make more time, then I assume you’re not trying them yet ;) They are all simple things that you could implement right now and you’re on the right track.</p><p>So, no more excuses — get out there and happy learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de5eb3e780ae" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fed-or-dead/why-i-don-t-have-time-is-a-bullshit-excuse-for-not-learning-de5eb3e780ae">Why ‘I don’t have time’ is a bullshit excuse for not learning</a> was originally published in <a href="https://medium.com/fed-or-dead">FED || Dead</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is full-stack a thing?]]></title>
            <link>https://medium.com/fed-or-dead/is-full-stack-a-thing-e9730c99c9a9?source=rss-cddbbd21a977------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9730c99c9a9</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[full-stack]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Dave Berner]]></dc:creator>
            <pubDate>Tue, 29 Sep 2015 12:08:59 GMT</pubDate>
            <atom:updated>2015-09-29T12:10:27.840Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pwvPcOIXceKESbzvRxNMkA.jpeg" /></figure><p>There have been a lot of arguments on this topic but as someone who has worked for the last year and a half as a “full-stack” developer I thought I would throw my 2 cents in.</p><p>So what did I do in my last role?</p><ul><li>I wire-framed our core product and marketing site</li><li>I put together lo-fi mockups</li><li>I wrote the HTML, SCSS and JS and was fully responsible for that domain</li><li>I was responsible for making the product accessible, performant and usable from a front end perspective.</li><li>I set the architecture, standards, best practices for the front end.</li></ul><p>At this stage you’re thinking ‘fair enough, he’s a front-end with a design background, nothing unique here’. Whilst we had a backend architect who put together the database schema and set the standards for writing backend code but I also:</p><ul><li>Wrote queries in pgSQL</li><li>Added / removed / updated database tables</li><li>Contributed to application architectural discussions</li><li>Day to day I would be writing both front and back end code</li></ul><h3>So, am I full-stack?</h3><p>I guess it depends where you draw the line in the sand.</p><p>If being full-stack means you are a master in all areas, then I definitely don’t fall into this category. Design, front-end and back-end are made of so many unique components, I think it would be impossible to claim mastery in all.</p><p>Design can be made up of wire-framing, UI design, UX, knowledge of the tools themselves (Photoshop, Sketch etc), prototyping, usability testing and so on.</p><p>Front-end can cover accessibility, usability, semantic markup, scalable CSS, JavaScript (potentially some of its frameworks too), performance etc. Again the list is endless.</p><p>Back-end could include knowing any number of server-side languages, databases, hosting environments, data management, security and much more.</p><p>Many of the items I mentioned above are now speciality jobs in their own right let alone the split between the overall parent groupings.</p><h3>Other disciplines</h3><p>To put this all into perspective it may be easier to look at other jobs and make a comparison. My landlord is a carpenter by trade (and a very good one) who because of the nature of his job has dabbled in electrics, brick laying and plumbing. Whilst he knows enough to get by in those other trades and has been known to fix up our pipes, lighting problems - his business card reads carpenter, not “full-stack tradesman”.</p><h3>Could I get a job as a full-stack?</h3><p>Honestly, I think it depends who’s hiring. A start-up company making a small product that only has budget for one developer to come and piece together the application may well be willing to take me on as a full-stack. I could put together a reasonable database and have it talk to the front-end which would be fine for a proof of concept.</p><p>However, a bigger company with an existing team of front and back-end developers would never hire me as a back-end, I wouldn’t even pass the entry test!</p><h3>So, finally, am I full-stack?</h3><p>I would say no. I’m not convinced it’s a thing. There are a few extremely talented people who are masters in all fields but the majority of us have our specialisation and can get by in others if we need to. The long and most accurate title: I’m a front-end developer with a background in design who can dabble in the back-end - but that’s never going to fit on my business card! The short title: I’m a front-end developer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9730c99c9a9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fed-or-dead/is-full-stack-a-thing-e9730c99c9a9">Is full-stack a thing?</a> was originally published in <a href="https://medium.com/fed-or-dead">FED || Dead</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bored of Flat Design]]></title>
            <link>https://medium.com/fed-or-dead/bored-of-flat-design-518f15d28331?source=rss-cddbbd21a977------2</link>
            <guid isPermaLink="false">https://medium.com/p/518f15d28331</guid>
            <category><![CDATA[flat-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[web-design]]></category>
            <dc:creator><![CDATA[Dave Berner]]></dc:creator>
            <pubDate>Sat, 19 Sep 2015 09:48:23 GMT</pubDate>
            <atom:updated>2015-09-19T09:48:23.141Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5J3P1dQW4eqkPKfraw7mDg.png" /></figure><p>Is anyone else bored of flat design yet? I’m tired of seeing the same uninspired, generic, template-style sites that are being churned out.</p><p>In all honesty there are elements of flat design that I love:</p><ul><li>the simplicity</li><li>the lack of images required / being able to style flat sites almost totally with CSS</li><li>the use of white space</li></ul><p>Things I hate about it</p><ul><li>lack of usability around form controls</li><li>lack of depth</li><li>lots of new sites looking identical / templated</li></ul><p>When flat first started making waves in the design community and on sites like Dribbble I believed it would be a short loved fad. A necessary step, as skeuomorphic design had gone too far (although I’m still jealous of the Photoshop skills of the designers that we’re able to create that type of work). My assumption was everything would be stripped back and then gradually designers would add little touches and flair to evolve it.</p><p>It does seem that with Google’s Material Design there is a some sense coming back, starting to see subtle shadows indicating depth and buttons beginning to look “clickable” again, which is great. But, it’s definitely not solving the issue with sites looking like they were produced as part of a regurgitated factory process.</p><p>I’m interested to see what the next phase is. My wife is a graphic designer and she’s finding a nice balance between flat design and the shabby chic style which has become popular in interior design. I like the combination and wonder if there are other areas of design that can be drawn from to create more inspired and unique sites.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=518f15d28331" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fed-or-dead/bored-of-flat-design-518f15d28331">Bored of Flat Design</a> was originally published in <a href="https://medium.com/fed-or-dead">FED || Dead</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tips and tools for collaborating remotely]]></title>
            <link>https://medium.com/fed-or-dead/tips-and-tools-for-collaborating-remotely-795d53b9a307?source=rss-cddbbd21a977------2</link>
            <guid isPermaLink="false">https://medium.com/p/795d53b9a307</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[remote-team]]></category>
            <category><![CDATA[collaboration]]></category>
            <dc:creator><![CDATA[Dave Berner]]></dc:creator>
            <pubDate>Fri, 11 Sep 2015 13:49:42 GMT</pubDate>
            <atom:updated>2015-09-11T13:49:42.154Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8UjqeV4pmh3S1g82Au33Ww.jpeg" /></figure><p>Maybe you’re considering emigrating. Perhaps the person you enjoy working alongside the most is moving away. Maybe you’re just interested in collaborating with someone you met online but they live hundreds of miles away. The good news is working remotely with other developers is easier today than it ever has been before.</p><p>I live and work in Australia but the majority of my side projects are carried out with a handful of people in the UK. When we first moved over here I was worried about whether it would be sustainable to continue working with them, but it turns out with a bit of effort and organisation, it can actually be great. In fact potentially you can have round the clock development going on!</p><p>The time difference for us is significant (~10 hours) and there is never a convenient time to talk. On weekdays one of us will be on the bus on their way to work as the other is getting ready to have dinner — but it does mean twice a day we have the opportunity to exchange instant messages. Our tool of choice for this has been <a href="https://slack.com/">Slack </a>and I can’t fault it.</p><p>We use <a href="https://trello.com/">Trello</a> for our workload management — another clean and simple tool that we use to track and assign tasks to each other. We set up a board for each project and pull status updates through into a Slack channel.</p><p>For those of you that haven’t used version control before, I strongly recommend you use <a href="https://git-scm.com/">Git</a>. We use private repositories in <a href="http://bitbucket.org/">Bitbucket</a> and have found that pull requests have become increasingly important now we are not in the same room. Our git strategy is fairly basic but it works for us. To summarise, we have the ‘master’ branch which is always production ready and the dev branch containing work in progress. Each developer then has their own version of the dev branch prefixed with their initials. When we complete work we issue a pull request to the main dev branch to ensure our code is up to standard before merging it. I may do another post soon in more detail on git workflows.</p><p>Finally, the most important thing you can do is have video face to face time. We catch up over Google hangouts every couple of weeks to check in, share ideas and see how it’s going. It’s vital that it’s not all about work and that you still talk about fun stuff — I mean that’s probably why you enjoyed working together in the first place!</p><p>We’ve produced some of our best projects whilst collaborating remotely, so don’t be downhearted if your closest dev mate is moving overseas — with modern tools and planning you can make it work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=795d53b9a307" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fed-or-dead/tips-and-tools-for-collaborating-remotely-795d53b9a307">Tips and tools for collaborating remotely</a> was originally published in <a href="https://medium.com/fed-or-dead">FED || Dead</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Help, there’s too much to learn!]]></title>
            <link>https://medium.com/fed-or-dead/help-there-s-too-much-to-learn-ea6696651457?source=rss-cddbbd21a977------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea6696651457</guid>
            <category><![CDATA[framework]]></category>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Dave Berner]]></dc:creator>
            <pubDate>Sat, 20 Jun 2015 01:05:52 GMT</pubDate>
            <atom:updated>2015-09-19T09:27:21.374Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vojbQQLePIICpEwgo9Q1sQ.jpeg" /></figure><p>No doubt you’ve felt this too. As a front-end developer it seems there is a never ending list of tools / frameworks / methodologies that keep popping up. All of them hailed as things that must be in our toolkit. When you’re starting out it’s easy to get swept away in a sea of Grunt, Gulp, Bower, Node, Backbone, React, Meteor, Angular, Scss, Sass, Less, Stylus, Git, BEM, Coffee-script, Yeoman, Atomic design, etc etc and feel like the shoreline is nowhere in sight.</p><p>You go online and read blog after blog and article after article by really smart people teaching amazing tips and tricks on a whole array of topics that all relate to front-end development. You start to feel insignificant because it seems like everyone else is light years ahead and all over these ground breaking technologies.</p><p>The fact is, that’s total bollocks. The Chris Coyiers, Pauls Irishs, Harry Roberts’, Nicole Sullivans and [insert your favourite awesome dev here] of the world are the minority. They are brilliant and they are pushing our field forward but 95% of front-end devs aren’t in their position.</p><p>I know people who are worried about applying for roles because they’re convinced all the other applicants are going to be the same caliber as these gurus.</p><p>Again total bollocks.</p><p>I must admit I was under the same disillusion for a while. Until I decided to quit my old job a few years ago and my boss and I started looking for my replacement.</p><p>We saw loads of CVs and interviewed tons of people. Most weren’t experts in all the latest technologies and there was plenty of people saying ‘Oh, I’ve been meaning to get round to looking at [insert tech here]’.</p><p>If you’re reading this post or indeed any front-end development post and are worried about being behind with the latest web tools / frameworks, odds are you’re already more on the ball than the majority of people that will be going for the same role as you.</p><p>Don’t worry about not having time to learn every tool that pops up, just read about a few and pick up the ones that will actually be useful to your workflow. A company isn’t realistically expecting you to have experience with them all, and most are a lot easier to learn on the job anyway as you can see them being used in context.</p><p>My other advice would be don’t jump in and start learning a tool straight away — especially frameworks, let it sit in the market for a while and get established so you can get a handle on whether or not it will stand the test of time.</p><p>Happy coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea6696651457" width="1" height="1" alt=""><hr><p><a href="https://medium.com/fed-or-dead/help-there-s-too-much-to-learn-ea6696651457">Help, there’s too much to learn!</a> was originally published in <a href="https://medium.com/fed-or-dead">FED || Dead</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>