<?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 Marie-Laure Thuret on Medium]]></title>
        <description><![CDATA[Stories by Marie-Laure Thuret on Medium]]></description>
        <link>https://medium.com/@mlthuret?source=rss-c6b74d331d2e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*awY-pjz0YTeeg13J9mgyBA.png</url>
            <title>Stories by Marie-Laure Thuret on Medium</title>
            <link>https://medium.com/@mlthuret?source=rss-c6b74d331d2e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:26:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mlthuret/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[From Paris to the Silicon Valley: Speaking at React Conf 2017]]></title>
            <link>https://medium.com/algolia-stories/from-paris-to-the-silicon-valley-speaking-at-react-conf-2017-6d2b3fc72223?source=rss-c6b74d331d2e------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d2b3fc72223</guid>
            <category><![CDATA[algolia]]></category>
            <category><![CDATA[team-stories]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[Marie-Laure Thuret]]></dc:creator>
            <pubDate>Tue, 16 May 2017 09:06:21 GMT</pubDate>
            <atom:updated>2017-05-16T14:50:46.020Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oks8eEMA_sSErqa89j5KCw.png" /></figure><p><em>My name is Marie-Laure Thuret and I’m a front-end developer working at Algolia. 2016 was the year when I started to get involved into the open source community. 2017 was the one when I was able to share some of this work with the React Community.</em></p><p>In the middle of the night I received an email entitled “Speaking at React Conf 2017”. The email confirmed that my talk had been chosen, and that I would be speaking at the pinnacle conference for React developers. It wasn’t my first speaking opportunity, but it was definitely a jump from the conferences I’ve spoken at in France. I couldn’t sleep anymore. As I thought about the prospect of speaking in front of the entire react community, I started to feel pressure — a good kind of pressure, but pressure nonetheless.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FPF0Vi-iIyoo%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DPF0Vi-iIyoo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FPF0Vi-iIyoo%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/92eb38334a7ccf00c4153210578bc40c/href">https://medium.com/media/92eb38334a7ccf00c4153210578bc40c/href</a></iframe><p>The talk I gave at React Conf earlier this year was about React Storybook, a tool that lets you develop your React UI components in complete isolation. Arunoda Susiripala created it in 2016, and I developed an add-on for it: the <a href="https://github.com/mthuret/storybook-addon-specifications">specifications add-on</a>. For this talk I didn’t wanted to just speak about it. I wanted to present how it can affect the developer journey when creating UI components. Our team relied a lot on this tool when developing our new <a href="https://community.algolia.com/react-instantsearch/">React InstantSearch library</a>, and I knew that live coding and examples would make the talk more engaging.</p><h3>Empowerment in your Environment</h3><p>If I hadn’t joined Algolia last fall, I doubt I would have submitted a talk for React Conf.</p><p>Algolia has a strong culture and <a href="https://stories.algolia.com/how-algolia-built-a-culture-first-company-around-ownership-eee6623b1b6">values ownership</a> — If you want to do something, do it. This doesn’t mean that you will be alone in the process — here, everyone helps their teammates.</p><p>While I’m based in Paris, Algolia’s headquarters are in San Francisco, where we’re encouraged to travel to meet our American colleagues. Additionally, Algolia encourages &amp; supports any Algolian who would like to speak at a conference, whether about Algolia or not.</p><p>Even in our French office, we have employees coming from a dozen different countries, meaning that we never speak French in the office. When I applied for React Conf, I was speaking English daily for four months, and even though my English is not perfect, it helped me a lot with my confidence.</p><h3>Continuously Improving</h3><p>I received help from a lot of people inside the company. I did a couple of public rehearsals of my talk during work hours — several Algolians attended. It help me refine certain parts and improve the message I wanted to deliver.</p><p>I also had the chance to receive public speaking training a couple of weeks before the conference, which everyone at Algolia is encouraged to do no matter their position. It has proved to be very helpful — I learned how to get rid off those unwanted “mmmmh” words that polluted my talks in the past, and I also learned what real eye contact with the audience actually looks like.</p><p>Our creative designer Sebastien dedicated a full hour to review and improve the design of my slides. I learned many useful tricks which I can reuse in the future.</p><p>My goal at the beginning was to share things I’ve learned with the react community, but I learned so many other things myself on various topics. Before I even gave the presentation, I was happy with the journey it took me on — it was a real team effort!</p><h3>And we’re going to San Francisco</h3><p>React Conf takes place in Santa Clara, but I arrived a few days in advance to spend some time in our SF office and take some time to meet with my Silicon Valley-based colleagues — also, I needed time to recover from jet-lag. Those few days in SF were amazing because I got the chance to discover a new city and a new culture.</p><h3>First stop: Menlo Park</h3><p>The React core team at Facebook invited all the speakers to do a test-run with them before the actual conference, which gave me the opportunity to make a small trip into the Silicon Valley, where I met Tom Occhino and Ben Alpert. Their advice and ideas were helpful in making some last-minute modifications, which gave me the feeling that the presentation was (finally) finished. The content was solid and could bring some value to developers.</p><p>Proposing a rehearsal for speakers is an awesome idea. It guarantees to the organizers a quality conference, and it helps those of us who aren’t professional speakers to avoid feeling like we’re being thrown in the deep-end. It certainly helped me feel confident about my presentation.</p><h3>D-Day: React Conf</h3><p>On Sunday March 12th it was finally time to leave for the Santa Clara Mariott — it was a shame that Great America was still closed at the time — enjoying some rides to relax a bit before the show would have been nice. But It was 27°C outside with a perfect blue sky — there’s worse ways to relax.</p><p>I attended the speaker dinner that first night. I met and chatted with speakers coming from so many cities and backgrounds; We were also joined by some developers from the React core team.</p><p>But, this was just the beginning.</p><p>During the conference, it was impressive to see so many developers coming from everywhere: famous tech companies to non tech companies switching to React. From the Silicon Valley to Europe, South America… It was also the first tech event I participated in where so many women developers were attending.</p><blockquote>“Diversity is a gift that makes all of us better and I really experienced it there. “</blockquote><p>I enjoyed having the chance to chat with some of them during the various networking moments at the conference. And there were plenty of them. Long breaks between talks, happy hour after the first day and the closing party that even featured karaoke.</p><p>React Conf was the best-organized conference I’ve ever attended, let alone spoken at. The Facebook team did an amazing job on logistics and production; the whole event was livestreamed and, trust me, the backstage were impressive.</p><p>This conference was single-tracked, and all along Tom Occhino was playing the host. This helped keep the conference dynamic and he did a great job introducing each of the speakers.</p><h3>On stage</h3><p>I was presenting on the second day of the conference. I actually didn’t follow any of the talks that morning as I was rehearsing in the parking lot and trying to relax a bit. But like Tom Occhino said to me: don’t stress, go there and have some fun.</p><p>I definitely had a fun time doing this talk. React Storybook is a tool I love. Sharing my workflow with it with others couldn’t have been anything other than fun.</p><p>In a nutshell the talk went well. The live coding went over great and I was particularly glad I made a summary slide. One of the attendees used it on his own notes and tweeted about it.</p><h3>Michael Chan on Twitter</h3><p>Notes from @mlthuret&#39;s #reactconf talk on React Storybook</p><p>Except for the morning of the second day, I was able to follow most of the conference. The subjects were really diverse — from React Fiber to React VR, including a lot of talks about React Native, but also state management, prettier, jest, ES.next, type systems — and there were a lot of announcements during the conference.</p><p><a href="https://www.youtube.com/watch?v=7HSd1sk07uU&amp;list=PLb0IAmt7-GS3fZ46IGFirdqKTIxlws7e0">All the talks were recorded and I encourage you to check them out on youtube if you have any interest in React.</a></p><h3>Sharing is Caring</h3><p>I often heard people say that they can’t present something because they have nothing to say, or they have no chance to be accepted somewhere simply because nobody knows them. That’s not true. If you work on something, you have something to share with others. If you don’t feel confident enough to dare propose something, find a safe environment that will empower you to do it.</p><p>I guarantee you that sharing with others will bring you a lot. You’ll start amazing discussions that will open you to new perspectives.</p><p>Travelling to California, participating at React Conf, meeting many new people — it was really a strong moment for me that I’m won’t forget anytime soon.</p><p>I had the chance to connect with an awesome community and I hope it will not be the last time.</p><p>A huge thanks to all the people that organized this event and to this amazing community for the memorable moment there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d2b3fc72223" width="1" height="1" alt=""><hr><p><a href="https://medium.com/algolia-stories/from-paris-to-the-silicon-valley-speaking-at-react-conf-2017-6d2b3fc72223">From Paris to the Silicon Valley: Speaking at React Conf 2017</a> was originally published in <a href="https://medium.com/algolia-stories">Algolia Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a React Components Living Documentation using React-Storybook.]]></title>
            <link>https://medium.com/@mlthuret/building-a-react-components-living-documentation-using-react-storybook-5f11f0e7d23e?source=rss-c6b74d331d2e------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f11f0e7d23e</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Marie-Laure Thuret]]></dc:creator>
            <pubDate>Wed, 10 Aug 2016 19:03:55 GMT</pubDate>
            <atom:updated>2016-08-20T09:22:53.376Z</atom:updated>
            <content:encoded><![CDATA[<p>The first time I heard the term <em>“living documentation”</em> was when I discovered Behavior Driven Development (also known as BDD). If you don’t know what BDD is you can still read <a href="https://dannorth.net/introducing-bdd/">this introduction by Dan North</a>. But to give you a quick idea, it’s when developers, Q&amp;A and business people collaborate to write specifications. Those specifications are focused on examples.</p><p>Now, who never read a documentation that were out of date ?</p><blockquote>Code is often the only thing we can really trust; most written documentation is outdated before the project is delivered.</blockquote><blockquote>Gojko Adzic</blockquote><p>One of the benefit of practicing BDD besides that you’re going to develop the right software (which is the most important thing actually), is that you can also <strong>build a functional documentation that can’t be outdated</strong>. The only thing you need to do is to use scenarios as tests. They will end up instrumenting your application and verify that outputs are correct. That’s it, you’ve just created a living documentation.</p><p>By using those scenarios as tests, you’re making <strong>a strong connection between the code version and the specifications</strong>.</p><p>But using BDD scenarios is not the only way to create a living documentation.</p><blockquote>Living documentation is a source of information about system functionality that’s as reliable as programming language code but much easier to access and understand.<br>Gojko Adzic</blockquote><h4>Bringing a living documentation for front-end components</h4><p>A year ago, I’ll join a project where for the first time I needed to make front-end development. We were using Ember and we did have some components to avoid duplication. But we’ve got a problem with new comers : it was hard to know what components were already there, what they were doing, and how to use them.</p><p>One day, a colleague got the idea to add a showcase to display all the components we have, with every possible behaviors. Of course, this showcase needed to be a living documentation, so we used the showcase to test our components.</p><p>We end up having a specific url in our dev environment to display our components. It was perfect when somebody needed to see a component in action. But the associated tests were also an important part of it because they helped to understand how to use the component and why they were used for. <strong>Indeed, the test code was the component specification.</strong></p><h4>And then comes React-Storybook</h4><p>Those last months, I discovered React and Redux. I was working on a presentation about how to test a React and Redux application when I discovered React-Storybook. Almost immediately I made the parallel with what we’ve done on my previous project.</p><p>If you have no idea of the purpose of <a href="https://voice.kadira.io/introducing-react-storybook-ec27f28de1e2#.rs193je6w">react-storybook, you can read this article.</a> Basically, it creates an isolated application where you can :</p><ul><li>Display your components inside storybook by declaring stories.</li><li>Taking advantage of storybook to develop in isolation your components by using quick iteration</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KrICpak6ZrbEjAank0Vhmg.png" /><figcaption>React-Storybook Interface</figcaption></figure><p>Adding more and more stories of your components to react-storybook will allow you to build a strong documentation. Every time a developer will want to know what does a component and how to use it, he will either be able to saw it live in storybook or look at its declaration. <strong>That’s good but is this documentation live ?</strong></p><p>Well, no if we rely only on the declared stories. Maybe our components will change in the future and if there is no tests related to the stories, how can we be sure that the displayed component in react-storybook is still correct ? We surely ain’t gonna watch them all manually.</p><p>Maybe we do have some tests for those components. That’s a great thing, but there’s a big chance that we’re re-declaring the components that we’re testing in our test files. If so why not used directly the one made for the story and write tests on it ?</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1399b0c2be7c97ee8a9cb286dc1dd3d8/href">https://medium.com/media/1399b0c2be7c97ee8a9cb286dc1dd3d8/href</a></iframe><p>In example above, we’re just exporting the component declaration used for the story to be reused inside our tests files.</p><p>To make the test runner works we’ll also need to be able to redefine storybook functions. We can also take advantage of that redefinition by replacing action and linkTo functions by spies.</p><p>For example, I use the following file in my storybook config. It’s those functions I import inside my stories files :</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/08a57eff714b480856b40e72102c6d16/href">https://medium.com/media/08a57eff714b480856b40e72102c6d16/href</a></iframe><p>And I use this as a mock for the facade :</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/74d197452424025dfe6a0af1f4f4adf7/href">https://medium.com/media/74d197452424025dfe6a0af1f4f4adf7/href</a></iframe><p>All our stories are now verified by tests that<strong> share the same component declaration</strong>. It’s a good thing because when the component will evolved, only one piece of code will be modified.</p><p>But we can do better…</p><h4>Executable specifications directly inside Storybook</h4><p>As I said earlier, tests are specifications. Wouldn’t it be nice to have those specifications directly displayed inside react-storybook ? And wouldn’t it be nice to also have both tests and stories declaration side by side ?</p><p>To do that, I had the idea to create a new addon : <a href="https://github.com/mthuret/storybook-addon-specifications">react-storybook-specifications</a>.</p><p>The idea behind this addon is to <strong>write tests directly inside stories and still be able to use them with the CI.</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/25ab6316a57745e629cac7b6022ef6da/href">https://medium.com/media/25ab6316a57745e629cac7b6022ef6da/href</a></iframe><p>It will create a new panel inside storybook that looks like this :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/973/1*Z8y3xmlwq85wHNLi2yBfmw.png" /><figcaption>when everything is ok</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/971/1*osW3QQn33hEy67URP7xG8Q.png" /><figcaption>when failure happen</figcaption></figure><p>Of course, to use tests written inside stories with the CI you’ll need to use the same kind of strategy with the facade that I showed you before. You’ll also need more configuration. More on that can be found <a href="https://github.com/mthuret/storybook-addon-specifications/blob/master/README.md">on the addon documentation</a>.</p><p>So this is how I would build a living documentation for react components based on the great <a href="https://github.com/kadirahq/react-storybook">React-Storybook</a> project. Feel free to share your thoughts about it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f11f0e7d23e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>