<?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 Raoul George on Medium]]></title>
        <description><![CDATA[Stories by Raoul George on Medium]]></description>
        <link>https://medium.com/@raoulgeorge?source=rss-1546ada35a20------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ZW8n_kiJ2ATsk_Ucww0dyg.jpeg</url>
            <title>Stories by Raoul George on Medium</title>
            <link>https://medium.com/@raoulgeorge?source=rss-1546ada35a20------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:33:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@raoulgeorge/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[Anatomy of a frontend tech interview]]></title>
            <link>https://medium.com/@raoulgeorge/anatomy-of-a-frontend-tech-interview-3aa08a962225?source=rss-1546ada35a20------2</link>
            <guid isPermaLink="false">https://medium.com/p/3aa08a962225</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Raoul George]]></dc:creator>
            <pubDate>Thu, 06 Sep 2018 08:29:29 GMT</pubDate>
            <atom:updated>2018-09-06T08:29:29.542Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QcDLy9NvN7Z2EzkZFTF1zA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/xekxE_VR0Ec?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Markus Spiske</a> on <a href="https://unsplash.com/search/photos/javascript?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>There are a plethora of articles on what to expect in a frontend tech interview. But not too many opinions on how exactly to conduct a <em>great</em> interview.</p><p>Front end tech interviews these days are a mess. From asking potential candidates a slew of syntax oriented questions, to expecting them to implement Ukkonen’s algorithm in 15 minutes, most interviews don’t really focus on the right skills to test.</p><p>A typical frontend interview consists of questions that test Javascript, HTML and CSS.</p><p>These are the skills that I would usually test a frontend developer on-:</p><ul><li>A simple fizzbuzz problem to set the ball rolling.</li><li>A small algorithm/data-structure problem. Nothing too complex.</li><li>Ability to write object oriented JavaScript.</li><li>Questions pertaining to typical problems that a FED is bound to have experienced - asynchronous requests, change detection, DOM manipulation, inadvertent closures etc.</li><li>Design patterns and separation of concerns.</li><li>Writing structured, readable CSS.</li><li>understanding the importance of concise, semantic HTML.</li><li>Unit testing</li><li>Tooling IE. Webpack/grunt/gulp</li></ul><h3>Fizzbuzz</h3><p>I usually start with a simple <a href="https://en.m.wikipedia.org/wiki/Fizz_buzz">fizzbuzz</a> problem. This accomplishes two things -:</p><ul><li>Allows the candidate to relax a bit as 9/10 programmers will be able to solve this.</li><li>Acts as a gatekeeping question to weed out people who have atleast done some level of coding versus the pretenders</li></ul><blockquote>Getting that first question correct always provides a moment of relief to the candidate and eases nerves.</blockquote><h3>Object oriented javascript</h3><p>Most people underestimate the power of OOPS in front end development. In a world where we inherited codebases with 1000’s of lines of spaghetti jQuery strewn around, using basic object oriented concepts brings some method to this madness.</p><p>This is when I usually ask some basic questions about classes, objects, inheritance, encapsulation, polymorphism. A good way to test a candidate’s familiarity with these concepts is to ask him to build a class modelling a real world problem and then slowly deep-dive into how to go about implementing these concepts into the class definition and implementation.</p><h3>Structured CSS</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*6LnTOs8FtpwnDPi3k9Vo4Q.jpeg" /></figure><p>CSS skills are an other overlooked piece of the puzzle. Usual CSS questions revolve around concepts like the box-model, positioning etc. However, I see most value in understanding how the candidate has wrestled with the problem of writing maintainable css. Preprocessors like SASS/LESS are commonly (mis)used, but following certain coding guidelines make things a lot more organised. This is what I usually evaluate when it comes to CSS.</p><h3>System design</h3><p>This part is what I consider one of the most important skills that an experienced FED must possess. OOPS and CSS are skills that one can pick up by doing some amount of research. But designing a system from scratch is something that can only be learnt by experience. Understanding how to structure your codebase, conceptualize the different components that make up your application, deciding which one of the several JS frameworks to go with and why, taking care of messaging, routing, eventing, server side rendering, performance and the list goes on.</p><p>I like giving the candidate a problem statement and then sitting down with him as a peer and figuring out the best solution to it. This not only tests the hard skills above, but also serves as a great indicator of your prospective colleague’s attitude and interpersonal skills.</p><h3>Familiarity with atleast one JS framework</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1mT5axfsfECianccUmaa7g.png" /><figcaption>Too many choices(image credit: brewhouse.io)</figcaption></figure><p>The JS ecospace is flooded with frameworks and I don’t expect any developer to know all of them. Having said that, I would be hard pressed to call someone a modern front end developer if he has never worked with a framework or library before ( jQuery doesn’t count).</p><p>This is where I like to understand which framework he has worked on and the reasons why he chose that framework. Choosing the right framework for your application is an important decision — from valuing an opinionated framework like Angular which comes bundled with the everything and kitchen sink, to a more flexible library like react or vue which leaves a lot of the decision making to you, but also lacks in other areas like routing etc.</p><h3>ES6</h3><p>Surprisingly, a lot of very senior JS Dev’s ( &gt; 10 years of experience ) haven’t really adopted ES6 and the massive number of quality-of-life features it provides. Again, I don’t expect them to know about every single piece of syntax here, but concepts such as <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Spread_syntax">object spreading</a>, <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment">destructuring</a>, <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Arrow_functions">arrow functions</a> are a few things that a frontend developer must know about in 2018.</p><h3>Unit testing</h3><p>This can be a contentious point when it comes to front end development, but I always prefer a candidate who has worked on and believes in the value that good unit tests bring to the stability of an application, rather than someone who thinks its a waste of time.</p><p>I usually ask the candidate to write some unit tests for the fizzbuzz problem above and this gives me a chance to understand his opinion of unit testing.</p><h3>Conclusion</h3><p>So these are the usual topics I like to discuss with potential candidates.</p><p>At <a href="https://www.linkedin.com/company/sixt-research-development-india">Sixt R&amp;D</a>, we look at hiring the right people who can tell us what to do rather than wait to be told what to do.</p><p>Always remember, it is not just your potential candidate who is being judged, but opinions will be formed about you and the company you work for based on the quality of your interviews.</p><p><em>The views, thoughts, and opinions expressed in this article are my own, do not necessarily represent or reflect the views of Sixt</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3aa08a962225" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Binding this in React]]></title>
            <link>https://medium.com/@raoulgeorge/binding-this-in-react-65226aa0f223?source=rss-1546ada35a20------2</link>
            <guid isPermaLink="false">https://medium.com/p/65226aa0f223</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Raoul George]]></dc:creator>
            <pubDate>Fri, 31 Aug 2018 03:23:29 GMT</pubDate>
            <atom:updated>2018-08-31T03:23:29.094Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*3LG5LJj8_GhgI4HdE4NIYQ.jpeg" /></figure><p>React does not automatically bind this in ES6 classes.</p><p>From their docs:</p><blockquote>In React components declared as ES6 classes, methods follow the same semantics as regular ES6 classes. This means that they don’t automatically bind this to the instance.</blockquote><h3>Render Binding</h3><p>So in order to get around this, we learned to love <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_objects/Function/bind">bind</a>.</p><pre>class TestComponent extends React.Component {<br>  <br>  handleClick(event) {}<br><br>  render() {<br>    return (<br>      &lt;div&gt;<br>        &lt;input type=&quot;button&quot; onClick={this.handleClick.bind(this)} /&gt;<br>      &lt;/div&gt;<br>    );<br>  }<br>}</pre><p>The problem with this way of doing things is that a new function is called every time this component re-renders. It also looks a little clunky when we bind in the click handler.</p><h3>Arrow Functions in render</h3><p>A less verbose way to do this is by using arrow functions in your render method.</p><pre>class TestComponent extends React.Component {<br>  <br><br>  handleClick() { }<br><br>  render() {<br>    return (<br>      &lt;div&gt;<br>        &lt;input type=&quot;button&quot; onClick={() =&gt; this.handleClick()} /&gt;<br>      &lt;/div&gt;<br>    );<br>  }<br>}</pre><p>However, although the syntax is more succinct, we still suffer from the same problem that a new anonymous function is created every time the render method runs.</p><h3>Constructor Binding</h3><p>To get around the performance problems with directly binding in the handler, we can instead bind this to the handler in the constructor.</p><pre>class TestComponent extends React.Component {<br>  <br>  constructor(props) {<br>    super(props);<br>    this.handleClick.bind(this);<br>  }</pre><pre>  handleClick() { }<br><br>  render() {<br>    return (<br>      &lt;div&gt;<br>        &lt;input type=&quot;button&quot; onClick={this.handleClick} /&gt;<br>      &lt;/div&gt;<br>    );<br>  }<br>}</pre><p>We can avoid the performance issues using this method. But we will face issues with scalability. As we need a separate bind for each method, once our component becomes a little more complex, the constructor will be filled with a ton of bind statements.</p><h3>Arrow Functions in class</h3><p>To get around the scalability problems with the other methods, we can use arrow functions as class properties.</p><pre>class TestComponent extends React.Component {<br>  <br>  handleClick = () =&gt; { }<br><br>  render() {<br>    return (<br>      &lt;div&gt;<br>        &lt;input type=&quot;button&quot; onClick={this.handleClick} /&gt;<br>      &lt;/div&gt;<br>    );<br>  }<br>}</pre><p>This solves the performance issues with the first two methods and the scalability problems with the 3rd option.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65226aa0f223" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>