<?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 Umberto Babini on Medium]]></title>
        <description><![CDATA[Stories by Umberto Babini on Medium]]></description>
        <link>https://medium.com/@umbobabo?source=rss-b1cfe52241b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*1bCLoT09vRF_6216.jpg</url>
            <title>Stories by Umberto Babini on Medium</title>
            <link>https://medium.com/@umbobabo?source=rss-b1cfe52241b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:00:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@umbobabo/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[Reflection on ReactFest 2018]]></title>
            <link>https://medium.com/@umbobabo/reflection-on-reactfest-2018-2d5ec6ec6520?source=rss-b1cfe52241b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d5ec6ec6520</guid>
            <category><![CDATA[the-economist]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[reactfest]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Umberto Babini]]></dc:creator>
            <pubDate>Wed, 14 Mar 2018 10:45:59 GMT</pubDate>
            <atom:updated>2018-03-14T10:45:59.950Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rc1DuNPJs1vMMownsF0xGg.jpeg" /></figure><h4>The good, the bad and the ugly</h4><p><em>The Economist</em>’s front-end development team (yes, we have a team of dedicated devs!) recently attended <a href="https://reactfest.uk/">ReactFest</a> in London.</p><p>If you’re looking for a general review of ReactFest or for some of the specific talks, this is not the blog post you are looking for.</p><p>Rather, this post contains some of my impressions of the conference within the context of <em>The Economist</em>’s digital development team. I also get into what I thought went well and what could be improved.</p><p>If you’re a tech geek, just jump to my reflections of the individual ‘Talks’ below.</p><h3>What went well</h3><h4>Diversity</h4><p><a href="https://medium.com/u/bea61c20259e"><em>The Economist</em></a> was a proudly ‘Diversity Sponsor’ and from what I saw in term of diversity, ReactFest was a success.</p><p>I was pleased to see that software development — at least at ReactFest — was no longer a ‘male-only’ hangout. In fact, it was a major improvement to other software development conferences I’ve been to in the past.</p><p>Kudos to the organisers and to other Diversity Sponsors — <a href="https://medium.com/u/4c541d683027">YLD</a>, <a href="https://medium.com/u/900ee8ad3db9">Formidable</a>, <a href="https://medium.com/u/6ea7ad0f4fa5">Trainline</a> and J.P. Morgan — for ensuring that most of the panels contained brilliant females software engineers and developers.</p><h4>Location and size</h4><p>One Embankment was a superb location for ReactFest. About 200 people showed up, which I think is the appropriate size for intimate chats. It also made it easier to dare I say it: “network” with strangers!</p><h4>Talks</h4><p>Here are some reflections on my favourite talks from ReactFest, which include highlights that are relevant to<em> The Economist’s </em>digital and development experience.</p><p>FYI —our current technology stack (React, GraphQL, Node.js®, Docker, Redux, Relay …).</p><p><a href="https://twitter.com/peggyrayzis">PEGGY RAYZIS</a></p><h3>Umberto Babini on Twitter</h3><p>😍 Really love this approach: https://t.co/PbnTfo4A4s</p><p>I was immediately sold by the direction Apollo is going with the usage of state management to resolve external and local data with a single source of truth.</p><p>We use Apollo technologies like <a href="https://github.com/apollographql/graphql-tools">GraphQL-Tools</a> to create a mockup server for visual tests, but we are not currently using Apollo Client.</p><p>We will soon start an exploration to evaluate it in a secondary product with a simpler codebase than our <a href="https://www.economist.com/">mothership</a>.</p><p>With Apollo we hope to be able to simplify our codebase potentially removing Relay, some related dependencies like isomorphic-relay and isomorphic-relay-router, and Redux.</p><p><a href="https://twitter.com/dan_abramov">DAN ABRAMOV</a></p><p>When Dan Abramov talks you definitely know he has something good to say.<br>If you haven’t seen it, you definitely should watch his talk at <a href="https://2018.jsconf.is/">JSConf Iceland 2018</a> .</p><p>His talk at ReactFest was good as usual. However, I was more impressed by the first part of the <a href="https://2018.jsconf.is/">JSConf Iceland 2018</a>:</p><h3>Umberto Babini on Twitter</h3><p>About the CPU demo: In 2013 I was working with Ext.js and D3 struggling in performances for huge DOM in data visualization. If I could have seen this demo I would have said: &#39;Are you kidding me mate?...This is just sci-fi&#39;...finally, it seems we are there. https://t.co/h9N3yF7dyn</p><p>The performances you see in the demo are something that we are not used to seeing so often in the JS world.</p><p>Evan Hensleigh, a developer on the data team, represented <em>The Economist</em> at ReactFest. He uses React to build <a href="https://www.economist.com/blogs/graphicdetail/2018/02/daily-chart">infographics</a> which in some cases can be very complex, with huge DOMs that can be mutated. This is why I think the first part of the Dan’s Iceland talk is more impressive than the second bit.</p><p><a href="https://twitter.com/marcelcutts">MARCEL CUTTS</a></p><p>Marcel was fun and also right in saying that type checking is hard.</p><p>Our FrontEnd Team has a wide spectrum of seniorities. We have devs with 15+ years of experience and multiple languages backgrounds working with fresh and smart chaps and gals that just recently started loving JS and no knowledge of other languages.</p><p><strong>Type checking</strong> for junior dev <strong>is tough</strong>. Not because they struggle with understanding it, but because they are challenged everyday with other things that our standards imply like writing good quality code, writing tests (unit, contract, integration, end-to-end, visual) and linting. Only then everything needs to be reviewed by a peer-reviewer and a core-reviewer, and also pass a human QA. So for them it is something more to worry about.</p><p><strong>Type checking</strong> <strong>is good</strong>. In my opinion as the Tech Lead, regardless of the advantages in term of bugs detection and self documentation of the APIs, it’s very useful to push less experienced developers into thinking deeper into their implementation and in a cleaner functional programming way.</p><p><a href="https://twitter.com/nicol4s_c">NICOLAS COUVRAT</a></p><p>I had a good chat with Nicolas before his presentation and it was interesting for me to meet him.</p><p>We will soon release our first React Native application (currently iOS only) and I personally hope that the team could have time to experiment a little bit with something like <a href="https://github.com/necolas/react-native-web">https://github.com/necolas/react-native-web</a> which caught my attention.</p><p><a href="https://twitter.com/NikkitaFTW">SARA VIEIRA</a></p><p>Sara is right: ‘BEM sucks’ … now.</p><p>There are definitely better solutions today. When we started building the new <a href="http://www.economist.com/">www.economist.com</a> (First commit 17th September 2015) and earlier our o<a href="https://github.com/economist-components/">pen source component library</a>, BEM was the best approach especially considering that we had web developers/designers in the team that were used to work with CSS only but not with JS.</p><p>BEM was the natural solution to have designers writing styles while developers where writing the functional component.</p><p>Suggested solutions like inline styles weren’t good for us because we wanted make the styles importable on demand and keep them separated from the functional component.</p><p>Today we are evaluating abandoning it because we need better encapsulation of components and styles due to the usage across more products. We want anyway keep styles as an option and we can do it via an Higher Order Styled Component.</p><p>We are currently evaluating <a href="https://github.com/emotion-js/emotion">Emotion</a> as CSS-in-JS solution.</p><p><a href="https://twitter.com/siddharthkp">SIDDHARTH KSHETRAPAL</a></p><p>We are implementing Auth-0 as authentication service for our users, but this is another story.</p><p>When we started the revamp of our website in 2015, we faced the same problems and in the end, the similar solutions that Siddharth mentioned during his talk.</p><p>The idea was (and still is) simply great: designers and developers communicate together with a common language that simplify interaction and creating a faster pace because we <em>all </em>want to deliver features to our users as quickly as possible, without affecting the quality of the products.</p><p><strong>BE SURE THE DESIGNERS ARE FULLY ON-BOARDED WITH THIS!</strong></p><p>We were lucky because we were working with <a href="https://www.edenspiekermann.com/">Edenspiekermann</a>, a consultancy company from Berlin, and their amazing designers.</p><p>They suggested this approach, and for me it was a revelation.</p><p>Siddharth during his talk clearly explained how the concept works.<br>Their team abstracted units and values using t-shirts sizes and for colour they created a colour object easy to use with the dot syntax (e.g. colour.green.light).</p><p>We abstracted a little bit more, with 3 presets (that erroneously at the time we called component).</p><ul><li>Colours</li></ul><p><a href="https://github.com/economist-components/component-palette">economist-components/component-palette</a></p><pre>:root {<br>  --color-economist: #e3120b;<br>  --color-beijing: #121212;<br>  --color-kiev: #383e42;<br>  ...<br>}</pre><p>Apart from our branded Red, the rest of the palette have city names.<br>We wanted designers to work prototyping quickly with developers to avoid the following situation:</p><p>Designer: “Can you change that in a slightly light blue, please?”<br>Developer: “Define ‘slightly’ and try again”<br>Designer: “…you know what? light blue would be sufficient…”<br>Developer: “Define ‘light’ and try again”<br>…</p><p>This is what we have now:</p><p>Designer: “That border should be ‘London’”<br>Developer: “… border: var( — color-london) … done”</p><p>It’s up to the designers and not to the developers, to keep the palette contained in order to not loose their mental sanity.</p><ul><li>Typography</li></ul><p><a href="https://github.com/economist-components/component-typography/blob/94be16fef22be7613a2bcfe78ea10c6e8778a30b/src/typography.css#L11">economist-components/component-typography</a></p><p>We created a starting value defined with the number “0” thus developers can easily go up and down for decreasing or increasing a font-size for example.</p><pre>.post {<br>   font-family: var(--fontfamily-sans);<br>   font-size: var(--text-size-step-0, 1rem):<br>   line-height: var(--text-line-height-sans-on-step-0, 1rem);<br>}</pre><p>If a designer asks you to increase the font size you replace ‘0’ with ‘1’ and when you have to decrease the values you change it to ‘-1’ (e.g. from ‘ — text-size-step-0’ to ‘ — text-size-step — 1’).</p><ul><li>Grids</li></ul><p><a href="https://github.com/economist-components/component-grid">economist-components/component-grid</a></p><p>When we started coding, the design was just one page because we were applying a very incremental process for deliverables, so it was clear to everyone that nothing was written in stone.</p><p>This is why we ended up using animals-sizes for spacing instead t-shirt sizes (that we used for the gutters). Gutters (vertical dividers) were well defined due to the way the vertical divisions work in our responsive design, while spacing (we mean horizontal spacing in this case) were still in evaluation.</p><p>If we used t-shirt sizes, what would happen if a designer asked you to add a value between X and XL?</p><p>While there is always an animal that can fit between a hedgehog and a rabbit!</p><pre>--grid-spacing-mouse: 0.1em;<br>--grid-spacing-hedgehog: 0.35em;<br>                                &lt;&lt;&lt; Add your guinea-pig here<br>--grid-spacing-rabbit: 0.714em;<br>--grid-spacing-fox: 1em;<br>--grid-spacing-sloth:</pre><h3>What could be better</h3><p>ReactFest was clearly a positive experience. The location also helped with socialising because after the talks you could walk around and ask your questions directly to the speaker which was great.</p><p>Anyway, I would have personally preferred <em>fewer</em> talks and used that time to have all the speakers on stage together answering questions from the audience.</p><p>I know there were channels like Slack for instance where you can ask questions but I think the panel is a much more interesting and effective way in this kind of context.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5z1M_L8STnPCtiqpMIaDEA.jpeg" /><figcaption>Angelo Repole, Evan Hensleigh (Data Team), Ellis Taylor, Elisabeth Hard, Elisabeth Harris, Yasmin Green…I’m not there, I was late.</figcaption></figure><p>As a Sponsor looking for new talents to hire, the balcony on the path to the bar, was a great position to have a chat with a lot of interesting people.</p><p>A lot of them already work in great companies with most of them using the same technologies we use: GraphQL, Node.js®, Docker, Redux, Relay, Jest, Flow…and obviously React.</p><p>They were particularly interested in the way we use GraphQL to communicate with them multitude of micro-services we have, some of them for legacy reasons and a lot of them newly rewritten in Golang.</p><p>A special thanks to all the organisers, the speakers, to <a href="http://ygdev19/">Yasmin Green</a> and <a href="http://thepragmaticdev/">Ellis Taylor</a> for the work done on our booth, to <a href="http://lizziehard1/">Elisabeth Hard</a> for the work done on the video for the conference, and to Elisabeth Harris (HR) for being there with us to find new talents.</p><p>Oh, by the way, <a href="https://globalcareers-economist.icims.com/jobs/">we are hiring</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d5ec6ec6520" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>