<?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 Maxence Dalmais on Medium]]></title>
        <description><![CDATA[Stories by Maxence Dalmais on Medium]]></description>
        <link>https://medium.com/@maxired?source=rss-958052064161------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*yV3hLbPKnWrnSui9.jpeg</url>
            <title>Stories by Maxence Dalmais on Medium</title>
            <link>https://medium.com/@maxired?source=rss-958052064161------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 08:26:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@maxired/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[How to get the best from Jitsi?]]></title>
            <link>https://medium.com/@maxired/how-to-get-the-best-from-jitsi-7a30f4cb9817?source=rss-958052064161------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a30f4cb9817</guid>
            <category><![CDATA[jitsi-meet]]></category>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[videoconference]]></category>
            <category><![CDATA[zoom]]></category>
            <category><![CDATA[jitsi]]></category>
            <dc:creator><![CDATA[Maxence Dalmais]]></dc:creator>
            <pubDate>Tue, 09 Jun 2020 10:01:58 GMT</pubDate>
            <atom:updated>2020-06-09T10:01:58.900Z</atom:updated>
            <content:encoded><![CDATA[<p>Jitsi is a very popular and versatile video conferencing solution. It is both available as open-source software on <a href="https://github.com/jitsi/jitsi-meet">Github</a>, or as a hosted services on <a href="https://meet.jit.si/">https://meet.jit.si/</a>. In this article, we will browse solutions to improve your Jitsi meeting.</p><h3>Turn the camera on</h3><p>Ok, this one is obvious and not dedicated to Jitsi, but seriously, please turn the camera on. A video conference without video is really really boring. People will lose their focus within minutes. You can be sure than people with a camera turned off will do something else during the meetings: sending chat messages, Internet browsing, or even cooking, who knows.</p><p>Also having the camera on will help to have more reactions. Most of your meetings are not webinar: You want people to be active and participate. having the video on will help them.</p><h3>Use Snap camera</h3><p>You are convinced that video is a must, but Jitsi is missing a good and efficient blur my background features. Or people have bad lighting condition and video quality is not great? Install <a href="https://snapcamera.snapchat.com/">Snap Camera</a> or another virtual webcam system such as <a href="https://obsproject.com/fr">OBS</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MsYUs8tbS1aTwA8YY6Mg5Q.png" /><figcaption>Me, using a <a href="https://www.snapchat.com/unlock/?type=SNAPCODE&amp;uuid=e85ea1aacc3949cc9ea2b1f4e980b845&amp;metadata=01">Beach Background</a> on Snap Camera</figcaption></figure><p>Using a lens, you will be able to change your background, lightening, or if your meeting allows it, turn yourself into a potato</p><h3>Push to Talk</h3><p>Video conference with lots of people tens to be noisy. I often advise people to mute themself when they don’t speak. But this a drawback of reducing people’s reactions. You will probably lose 1 second unmuting yourself before speaking, which will slow down things and make them less natural.</p><p>In order to mute yourself to prevent undesirable background noise but keep the conversation natural, one good option is to use the ‘Push to talk’ features.</p><p>So, how does that works? Easy as it sounds: just press the space bar whenever you want to talk. The first time you press the bar, your mic will go on mute when you release it. After that, it will be active only when pressing the bar.</p><p>Of course, you can always go back to the previous behavior by clicking on the mic icon.</p><h3>Add Party Button</h3><p>So far, we spoke about the video and sound features of Jitsi, which is about mimicking what you would get in real life. But using software means you can do more than in real life: new features can be added.</p><p>One that people loves is the party button: it allows to add another kind of reaction during your meeting, and make them fun again</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*rT3R3s3O28s2_ZePJbkjyQ.jpeg" /></figure><p>In order to use the party button and depending on your context you have two solutions :</p><ul><li>If using the official Jitsi instance, you can install the <a href="https://chrome.google.com/webstore/detail/jitsi-meet-party-button/pbdkaccnkglbocobgnkcggipeeakfppg?hl=en">Jitsi meet party button extension</a>. Be aware that all participants will need to install the extension to see the reaction</li><li>If using your own Jitsi server, install the plugin <a href="https://gumroad.com/retrolution#LnVyo">https://gumroad.com/retrolution#LnVyo</a> directly on your server. No need to change anything on the clients</li></ul><h3>Try others Jitsi Provider</h3><p>Finally, because Jitsi is open source and as a great API, some people are running their own custom Jitsi server with custom features.</p><p>One of them is <a href="https://www.retrolution.co/">Retrolution</a>, a Jitsi based solution dedicated to agile teams and facilitators. Currently free during beta, it includes a private room, reactions, and a new layout called ‘FishBowl’ which allows you to add some rules during your meeting, prevent everybody to speak simultaneously and so improve the quality fo the discussion</p><h3>What else?</h3><p>You probably already have your own tricks that I did not mention. If so, please share as comments. I’ll update this article based on your suggestions!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a30f4cb9817" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nobody’s in the office? Here is how to handle your first remote retrospective. meeting]]></title>
            <link>https://medium.com/@maxired/nobodys-in-the-office-here-is-how-to-handle-your-first-remote-retrospective-meeting-53d70a2e49d?source=rss-958052064161------2</link>
            <guid isPermaLink="false">https://medium.com/p/53d70a2e49d</guid>
            <category><![CDATA[retrospectives]]></category>
            <category><![CDATA[coronavirus]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Maxence Dalmais]]></dc:creator>
            <pubDate>Fri, 13 Mar 2020 09:41:54 GMT</pubDate>
            <atom:updated>2020-03-13T09:41:54.182Z</atom:updated>
            <content:encoded><![CDATA[<h3>Nobody’s in the office? Here is how to handle your first remote retrospective meeting</h3><blockquote>Disclaimer: I am <a href="https://www.linkedin.com/in/maxencedalmais/">Max</a>, a software developer who used to work remotely while working for <a href="https://medium.com/u/4d2ed76cb5eb">NearForm</a>, a distributed first JavaScript agency. I am now working on <a href="http://retrolution.co/">Retrolution</a>, a suite of tools dedicated to retrospective facilitators. This post is not about Retrolution, but list some general advice based on my experience</blockquote><p>As an experienced facilitator or not, handling a remote retrospective will for sure be a new challenging experience. Once again, you will be required to adapt yourself and your plans to match that new context. I will in this blog post give you easy-to-apply advice for your first remote retrospectives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ygVf3svWeywv8loFs2NJgw.jpeg" /></figure><h3>Turn the webcam on</h3><p>Ok, this one might be very obvious, but you should use a reliable video conference system, and turn the video on. Without the video, it is really easy to be distracted during an online meeting. Having the video signal will force everyone to be focused. On top of that, the video signal provides visual feedback that conveys a lot of information. Finally, this will allow for nonverbal communication. More on that later.</p><h3>Keep it simple</h3><p>If this is one of your first remote retrospectives, keep it simple. Don’t overuse technology, especially if you did not use it before. If your team is suddenly distributed, keep in mind that people might not have the perfect working condition. Maybe some people will be in a noisy environment. If so, it’s ok to use chat or simple poll tools. But don’t introduce overly complicated tools that you don’t master.</p><p>For example, if as an icebreaker you want people to draw a smiley face to represent their iteration mood, you can use online drawing tool, maybe the one bundled with your video conference system, but if you don’t have one, just ask people to draw on regular post-its and showing them on the webcam.</p><h3>Keep the energy level high</h3><p>As you are aware, a retrospective is about getting everyone’s opinion and aligning people with their perception. It is very easy in our daily job to be so focused on a task that we don’t interact enough with each other. Bad news, things get worse people working distributed. That’s one more reason to do a retrospective.</p><p>If you want everybody to be engaged during the remote retrospective, ask them regularly their opinion using gestures, such as roman voting, Five-Finger-Voting, or simple head nodding.</p><h3>Use Slides</h3><p>Because getting everyone’s attention might be harsh and drawing online might be harder than with a pen, I would suggest you use slides or another presentation support. When doing a physical retrospective, you probably use a paperboard, posters and or post-it. Don’t rely solely on the video chat. Lot’s of people are using a premade column-based solution for their retrospective. I don’t advocate for such a platform, because of the lack of flexibility. One good option is to use a collaborative slide software such a <a href="https://docs.google.com/presentation/u/0/">Google Slides</a>, or a free collaborative board solution, such as the one from my friend of <a href="https://agoora.fr/?utm_source=medium&amp;utm_medium=retrolution">Agoora</a>.</p><h3>Use sub-chats</h3><p>Last piece of advice of this article: use sub-chats. If you are using liberating structure — and you should-or any form a collaborative process including group reflection, you will have so ask people to connect to different chat rooms. You might not want to do that for your very first remote retrospective, but that is a very good way to mimic what you would do if present all physically in the same room.</p><h3><strong>What about you?</strong></h3><p>Ok, I am done with my piece of advice, but I will be happy to know more about your tricks when handling remote retrospective, and more generally remote meeting. So please comment and share ;-)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53d70a2e49d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing JSON-Explorer, a free open-source web JSON visualizer]]></title>
            <link>https://medium.com/@maxired/introducing-json-explorer-a-free-open-source-web-json-visualizer-227849c0f4e9?source=rss-958052064161------2</link>
            <guid isPermaLink="false">https://medium.com/p/227849c0f4e9</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[retrospectives]]></category>
            <category><![CDATA[json]]></category>
            <dc:creator><![CDATA[Maxence Dalmais]]></dc:creator>
            <pubDate>Wed, 11 Mar 2020 15:00:23 GMT</pubDate>
            <atom:updated>2020-03-11T15:00:23.346Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><a href="https://fr.wiktionary.org/wiki/tl;dr">tl;dr</a>: You can visit <a href="https://maxired.github.io/json-explorer/">https://maxired.github.io/json-explorer/</a> and upload a JSON to explore and filter it. This is mainly useful for tabular data.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*pWw5UBJpxQEEKjY0Lwnw3w.png" /><figcaption>The landing screen of JSON-Explorer — import a file, see it</figcaption></figure><p>While working on <a href="https://www.retrolution.co/">Retrolution</a>, I recently faced a situation where I wanted to provide a new web interface on top of data that I don’t own. For those interested in retrospectives meetings, I am speaking about the very famous <a href="https://retromat.org/en/">Retromat</a>. While the code of Retromat is available on Github, there is currently no license attached. Moreover, even if the project was open-source, the data is not available on the repository.</p><p>I very recently contacted <a href="https://twitter.com/findingmarbles"><strong>Corinna Baldauf</strong></a>, Retromat founder, for permission to use the data. She basically refused me the right to use freely Retromat data, which I totally respect. This could be the end of the story but at the same time she that reassures me that “For your own personal use you can do whatever you want.”</p><blockquote>For your own personal use you can do whatever you want.</blockquote><p>Because my initial goal was to create a useful web interface and share it with people, I tried to find an alternative. One of them would be to manually recreate the data by myself, asking permission to differents authors and so on. Quite possible actually, but looks to me more like a tedious job than a quick win.</p><p>For legal reasons, I don’t want to host any data that I don’t own. But it is easy for everyone with limited computed skills to download a file, save it locally, and use it on another webpage.</p><p>Before going further, I decided to do a very quick research about currently available solutions that would to the job. Such tools probably exist, but I haven’t been able to find them. So I decided to build one. You can find it <a href="https://maxired.github.io/json-explorer/">here</a> and the sources on G<a href="https://github.com/maxired/json-explorer">ithub</a>.</p><p>Because I want my tool to be useful for everyone, I made it so it works with any JSON, not just Retromat one.</p><p>For example, you can use the file <a href="https://data.senat.fr/data/senateurs/ODSEN_GENERAL.json">https://data.senat.fr/data/senateurs/ODSEN_GENERAL.json</a> found on the french government open data platform and discover that ‘Michel’ is the all-time most popular name for french Senator.</p><p>Or you can use <a href="https://retromat.org/activities.json?locale=en">https://retromat.org/activities.json?locale=en</a> and filter Retromat activities ;-)</p><p>Everything is still pretty rough. I just spend for now a few hours on it, but please let me know it is useful or how can it be improved.</p><blockquote>Ps: I want to publicly thanks Corrina and all Retromat contributors for their amazing work, and hope they will succeed in their quest <a href="https://retromat.org/blog/help-make-retromat-sustainable/">to make Retromat sustainable</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=227849c0f4e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to write a native iOS app without owning a Mac]]></title>
            <link>https://medium.com/@maxired/how-to-write-a-native-ios-app-without-owning-a-mac-93c2776f3bf5?source=rss-958052064161------2</link>
            <guid isPermaLink="false">https://medium.com/p/93c2776f3bf5</guid>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[Maxence Dalmais]]></dc:creator>
            <pubDate>Mon, 09 Mar 2020 08:26:21 GMT</pubDate>
            <atom:updated>2020-03-09T08:26:21.975Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Hi, I am <a href="https://www.linkedin.com/in/maxencedalmais/">Max</a>, Javascript Developer and this post is about how I write IOS apps without owning any Apple hardware, nor running a Hackintosh. BTW, I am not affiliated with any of the tools presented here.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OOQ-mteN6qdrQITQgu3Law.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@thomasw?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Thomas William</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Do you even need a native App?</h3><p>Before going further, it might be worth asking yourself whether you even need an app. Progressive Web Apps, PWA, have done a long way and are now ready for prime time. The current iOS 13 did introduce better support for PWA, and for a low-cost budget, it is one option to consider. But be aware that for now, iOS PWA can’t handle push notification or background activities. They are an option but there are lots of cases where you would need a native app.</p><p>In case you are developing a PWA, or even just a responsive website and don’t have a mac, there is plenty of options online to test your application on an iOS simulator, or even on a real phone. Such options include <a href="https://www.browserstack.com/">https://www.browserstack.com/</a> or <a href="https://app.lambdatest.com/">https://app.lambdatest.com/</a>. Of course, you can just test the responsive layout of your website by reducing your browser and using included mobile development tools, but by the end, you will need to test on a real device.</p><h3>Use a remote macOS</h3><p>If you are developing an Objective-C/Swift based iOS app chances you are owning a mac. if you don’t, there is still a solution for you: use a remote macOS. You will find online several companies providing Mac computer accessible remotely, via RDP, VNC, or even directly in your browser. I don’t have huge experience with that solution, but I did use <a href="https://www.macincloud.com/">macinacloud</a> and have been happy about it. If you plan to use it as your main development platform, I would suggest you go for 16GB of RAM, especially if you plan to use the simulator.</p><p>If you don’t have a mac but does have an iOS device that you want to use to debug your app, you will get two options:</p><ul><li>Use TestFlight so you can build in on your mac and share it with your device. This is the easiest to setup up</li><li>Use a remote USB connection. The idea here is to use a software that will forward your USB connection from your local computer to your remote mac. I am not sure about other providers, but when using macinacloud, you will need to use an external tool, as <a href="https://support.macincloud.com/support/solutions/articles/8000007775-how-do-i-connect-my-physical-iphone-or-usb-device-to-the-server-">described in their documentation</a>.</li></ul><h3>Use Expo App</h3><p>So you want to develop a Mobile Application with offline support, notification or maybe just want to be visible on the Apple Store? There is another solution in which you won’t have to have a Mac or use Xcode. I named it: <a href="https://expo.io/">Expo</a>.</p><p>I am Javascript Developer for 10 years and started to code in React in 2015, so I am definitely biased, but this is the setup up I am currently using, and I love it.</p><p>Expo is a suite of tools based on React-Native and aiming to help you create React-native apps without the hassle. The tools are improving very fast, so if you tried them a few months ago and hit some bugs or issues, you should give them another chance.</p><p>Since Expo 33, released June 2019, you can now render your React-Native application on iOS and Android devices, but also as a web page. This is a good option when developing.</p><p>Moreover, Expo comes with the Expo Client. Though the expo client, you can distribute your React-Native code to your iOS device. You will have a joyful development experience, with live-reload and remote debugging.</p><p>Don’t own an iOS device? Expo has also a service side part, that can build your application bundle ;-) Still, you will probably want to test it before delivering it to your users and submitting it to the AppStore. I am currently using <a href="https://appetize.io/">Appetize</a>, which allows you to run the build provided by Expo on an iOS simulator.</p><p>Need to run on a real device? BrowserStack also provides this option.</p><h3>Ask somebody else ;-)</h3><p>Thanks for reading so far. I tried to keep it short but at the same time to be very concrete. If you have more questions or maybe realize that developing yourself your next mobile app might be a not so great idea, be aware that there are lots for people out there that could help you design and develop your apps, beyond what you imagined. As for me, you can find me on <a href="https://www.linkedin.com/in/maxencedalmais/">Linkedin</a> or <a href="https://www.codementor.io/@maxired">Codementor</a>.</p><p>PS: Sorry Flutter developers, I don’t know much about solutions that you would use. Don’t be shy and share it in commentary ;-)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93c2776f3bf5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 conseils pour améliorer vos Rétrospectives agiles]]></title>
            <link>https://medium.com/retrolution-fr/10-conseils-pour-am%C3%A9liorer-vos-r%C3%A9trospectives-agiles-b4a1d48138b4?source=rss-958052064161------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4a1d48138b4</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[retrospectives]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Maxence Dalmais]]></dc:creator>
            <pubDate>Fri, 17 Jan 2020 11:28:46 GMT</pubDate>
            <atom:updated>2020-01-24T17:03:01.172Z</atom:updated>
            <content:encoded><![CDATA[<p>Animer une réunion de rétrospective n’est pas une chose facile. Comment répondre à vos attentes et à celles des participants ? Comment éviter l’ennui et la répétition ? Tout simplement, comment faire en sorte que les gens ressortent en se disant : “Nous faisons en sorte que la situation s’améliore”. Voici une liste de 10 conseils facile à mettre en oeuvre qui devrait vous aider lors de votre prochaine rétrospective.</p><blockquote>A Propos de l’Auteur: Maxence est avant tout un passionné de technologie qui aime mettre ses compétences au service de l’équipe, pour construire des produits fortement valorisés par les utilisateurs. Il a récemment décidé de lancer <a href="https://www.retrolution.co/utm_source=medium&amp;utm_medium=10-conseils">Retrolution</a> une suite d’outils afin d’aider les facilitateurs de rétrospectives dans leur mission</blockquote><h3>1: Préparez et planifiez</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*amKKspOLA_p9ZcAfdt9MLw.png" /></figure><p>Un premier conseil qui peut paraître évident, mais qu’il est toujours utile de rappeler : La planification est l’étape principale vous permettant d’assurer une rétrospective utile et efficace. C’est lors de celle-ci que vous vous poserez les questions telle que “Qu’est ce que j’attend de cette rétrospective”. Évidemment, en fonction du type de rétrospective — d’itération, de release, de projet, … — , des personnes présentent et du temps alloué, le déroulement de votre rétrospective ne sera pas le même.</p><p>Une bonne structure de rétrospective suivra la structure en 5 phases décrites dans “<a href="https://www.amazon.fr/Agile-Retrospectives-Making-Teams-Great/dp/0977616649">Agile Retrospectives: Making Good Teams Great</a>” de <strong>Esther Derby et Diana Larsen.</strong> Prenez-le temps de comprendre cette structure, elle vous accompagnera dans la durée.</p><p>En plus d’une bonne préparation votre rétrospective, par exemple en sondant en avance les participants, gardez bien en tête qu’il sera possible de modifier votre plan de rétrospective durant celle-ci en fonction du contexte. De plus essayez de réfléchir à l’avance à comment adapter vos activités afin de maîtriser votre timing.</p><p>Bonne nouvelle, avec le temps et l’expérience, ainsi qu’en utilisant les conseils suivants, la préparation prendra moins de temps.</p><h3><strong>2: Expliquez la démarche</strong></h3><p>Tout comme tout autre réunion, une réunion de rétrospective où les participants manquent d’implication et s’ennuient, aura un impact négatif sur la productivité et le moral des participants.</p><p>Pour éviter cela, une astuce est de bien faire comprendre aux participants que la rétrospective est le meilleur moment pour discuter et améliorer le travail quotidien. En d’autres terme on cherche à <strong>Optimiser</strong> le fonctionnement de l’équipe.</p><blockquote>La rétrospective est le meilleur moment pour discuter et améliorer le travail quotidien</blockquote><p>La rétrospective se place dans un cycle itératif d’amélioration continue. C’est le moment de faire le point sur la situation donnée et décider de modifications dans le fonctionnement de l’équipe. On peut alors décider de continuer certains point, ce qui constitue généralement la majorité implicite, d’encourager certains comportements présents, de décourager certains comportements présents, mais également d’en introduire de nouveaux.</p><p>En faisant une analogie avec l’Intelligence Artificielle et les mathématiques, nous comprenons bien la notion d’optimisation de l’équipe en jouant sur différents critères, ou neurones.</p><p>Evidemment, et ce n’est pas toujours chose facile, il faudra faire adhérer l’équipe à cette volonté de changement dans l’idée d’amélioration.</p><h3>3: Définissez un objectif</h3><p>Nous l’avons vu précédemment, la démarche derrière la réunion de rétrospective est l’amélioration du fonctionnement de l’équipe. Dans un cadre Scrum, tel que décrit dans le <a href="https://www.scrumguides.org/docs/scrumguide/v2017/2017-Scrum-Guide-French.pdf">Guide Scrum</a> :</p><blockquote>Le Scrum Master encourage l’équipe Scrum à améliorer, dans le cadre de travail Scrum, son processus de développement et ses pratiques afin de les rendre plus efficaces et agréables pour le prochain Sprint</blockquote><p>Pour ma part, je considère que si dans un premier temps ou dans une position de facilitateur non intégré à l’équipe, il faille garder un objectif flou tel que décris dans le Scrum Guide, il est intéressant par la suite de faire des rétrospectives avec un objectif précis et définis à l’avance.</p><p>Ainsi, après une deadline manquée, il sera intéressant d’organiser une rétrospective spécifique afin de comprendre toutes les raisons de ce retards, faire réfléchir l’équipe sur ce qu’elle aurait pu faire pour mieux prévenir celui-ci, et décider d’actions afin d’éviter que la situation ne se reproduise.</p><p>Sans allez dans cette exemple extrême et lié à une longue période, vous pourrez décider de cibler la rétrospective sur un ou deux éléments marquant de la période. D’une manière générale, si vous sentez en amont que les discussions de la rétrospective risquent de converger vers un sujet central, il peut être préférable de définir en amont ce sujet comme thème de la rétrospective. Parce que vous l’aurez préparé, cela vous évitera de vous sentir débordé.e et permettra d’avoir une discussion plus constructive.</p><h3>4: Adoptez une posture basse</h3><p>Même si vous proposez un agenda, organisez les discussions et éventuellement définissez le thème des discussions, attention, ce n’est pas vous la star de la réunion; bien au contraire. Plus que d’animateur, votre rôle est bien celui de facilitateur. Vous donnez les consignes, écoutez, aidez à reformuler et regrouper les idées, mais en aucun cas ne jugez, décidez et très rarement proposez.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NAuHajRNTXnW7UH7orx1kQ.jpeg" /><figcaption>En tant que facilitateur de rétrospectives, vous écoutez plus que ce que vous ne parlez</figcaption></figure><p>On appelle ceci avoir une posture basse. Vous n’êtes pas ici dans cette réunion le sachant, mais bel et bien celui qui crée le cadre permettant l’auto-organisation de l’équipe.</p><p>C’est pour cette raison qu’il est souvent très difficile en tant que Manager, chef d’équipe ou encore chef de produit d’animer de bonnes rétrospectives: Vous êtes à la fois juge et partie. Hormis les structures avec une véritable bienveillance et forte confiance entre les membres, et où le travail et donc le cadre de la rétrospective est clairement segmenté, je déconseillerais cette double position.</p><h3>5: Prenez le temps nécessaire</h3><p>Une erreur classique de l’organisation des rétrospectives est de ne pas prendre suffisamment de temps. Si vous souhaitez que vos réunions soit qualitatives, ne rognez pas là dessus. <strong>C’est peut-être le conseil Numéro 1</strong>.</p><p>Actuellement la plupart des équipes ne prennent pas suffisamment de temps pour leur rétrospective. En faites-vous parties ? C’est simple, si vous utilisez une seul activité, du type <a href="https://retromat.org/fr/?id=49">Starfish</a> ou similaire, c’est le cas. Mais heureusement, vous lisez cet article ;-)</p><p>Le guide Scrum propose des rétrospectives de 3H pour des itérations d’un mois. Pour des itérations de deux semaines, tels que j’observe régulièrement, prévoyez 90 ou 120 minutes. Il est utopique d’espérez faire un bonne rétrospective en 1H avec 10 participants. Croyez moi, j’ai essayé.</p><p>Evidemment, adaptez le temps de la rétrospective en fonction de la période d’itération et du nombre de personnes impliquées.</p><h3>6: Utilisez des Liberating Structures</h3><p>La plupart des guides des rétrospectives vous parleront d’activités à utiliser pour vos rétrospectives. Les activités ont l’avantage d’être ludiques, prêtes à l’emploi, et pour certaines, visuelles. Au delà des activités, souvenez-vous que le but de la rétrospective est d’écouter tout le monde, d’aligner les membres de l’équipe et de les amener collectivement à mener des actions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/302/1*ml-K9lltgzzmj46guE0_qQ.png" /><figcaption>Le logo des Liberating Strucutres</figcaption></figure><p>Pour cela, utilisez lors de chaque rétrospectives des <a href="https://www.liberatingstructures.fr/">Liberating Structures</a>. Derrière ce terme se cache des formats d’exercices et ateliers permettant à chacun de s’exprimer et d’itérer sur les idées émises.</p><p>Lorsque vous utilisez, adaptez ou même concevez une activités essayer d’utilisez et mixer ces structures libératrices. Elles vous permettront d’impliquer tout le monde, même lors de rétrospectives avec plus de 8 personnes.</p><h3>7: Effectuez une méta-rétro</h3><p>Un conseil présent dans “Agile Retrospectives: Making Good Teams Great”, et que j’ai déjà abordé dans l’article “<a href="https://medium.com/@maxired/alimenter-la-boucle-de-r%C3%A9troaction-une-phase-suppl%C3%A9mentaire-pour-rendre-votre-r%C3%A9trospective-7abdbd5e7c5d?source=friends_link&amp;sk=398bd222d4cfe98f7f4d6faae6d13754">Alimenter la boucle de rétroaction</a>” : à la fin de la rétrospective, prenez le temps de recueillir du feedback sur la rétrospective qui vient de se dérouler.</p><p>Cette simple action vous aidera à vous améliorer, ajuster vos rétrospectives à l’équipe, et aidera à ancrer la culture du feedback et de l’amélioration continue.</p><h3>8: Décidez d’actions SMARTs</h3><p>Généralisable en dehors de la rétrospective, la prise d’action <a href="https://fr.wikipedia.org/wiki/Objectifs_et_indicateurs_SMART">SMART</a>s — pour Spécifiques, Mesurables, Atteignables, Réalistes et Temporellement définies — est une solution qui <strong>augmentera durablement l’utilité de vos réunions</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*EWZmwLpiajH9q__KOIE60Q.jpeg" /><figcaption>Credit: <a href="https://retromat.org/en/?id=13"><strong>Manuel Küblböck</strong></a><strong> sur Retromat</strong></figcaption></figure><p>Ce cadre de pensé vous permettra d’éviter de sortir de réunions avec des actions floues ou pire encore, le sentiment que la seule utilité de celle-ci a été de planifier la prochaine.</p><p>Il s’agit véritablement d’un fondement important, sur lequel les deux prochains points de cet article reposent.</p><p>Une autre astuce : <strong>limitez le nombre d’actions</strong> prise lors de chaque rétrospective. Le but est bien d’itérer et d’apporter les changements au bon rythme, pas de perturber votre organisation toutes les 2 semaines.</p><h3>9: Planifiez et donnez de la visibilité à vos actions</h3><p>Les actions décidées en rétrospectives seront à effectuer lors de la prochaine itération. Celle-ci peuvent être spécifiques à un moment donnée. Par exemple, l’équipe peut décider d’aborder un sujet précis lors de la prochaine rétrospective. Il faudra dès lors modifier l’agenda de celle-ci, ou par exemple définir un rappel lors de celle-ci afin de ne pas oubliez ce point.</p><p>Si l’on ne peut pas définir en avance à quel moment précis l’action devra être effectué, une solution efficace consiste à intégrer ces actions sous la forme de tâches dans la prochaine itération.</p><p>Enfin, le changement demandant du temps et de la répétition, il peut-être utile d’afficher dans l’espace de travail les actions de la période, ou encore de les rappeler avant chaque rituel. Ce sont les mêmes solutions que certaines équipes utilisent pour ancrer et garantir de respect des valeurs et accords de travail propres à l’équipe.</p><h3>10: Assurez le suivi de vos actions</h3><p>C’est l’ultime conseil de cet article, mais surtout le conseil ultime pour garantir la pérennité des changements et de votre équipe; C’est également le point principal de l’article <a href="https://medium.com/@maxired/alimenter-la-boucle-de-r%C3%A9troaction-une-phase-suppl%C3%A9mentaire-pour-rendre-votre-r%C3%A9trospective-7abdbd5e7c5d?source=friends_link&amp;sk=398bd222d4cfe98f7f4d6faae6d13754">Alimenter la bouche de rétroaction</a> : <strong>Assurez le suivi de vos actions</strong>.</p><p>La rétrospective sert à prendre des décisions permettant d’essayer d’améliorer le cadre de travail, dans un environnement qui plus est changeant. Il est alors fondamentale d’évaluer le résultat de ces actions et de décider de la suite à y donner. Nous en revenons ici au point numéro 2, celui de la démarche d’amélioration continue.</p><p>Pendant la rétrospective, après l’introduction mais avant d’entamer des discussions plus globales, faites un les actions prises précédemment. Il faudra parfois revenir sur des actions prises plusieurs itération précédentes, et ne pas se contenter de ne parler que de l’itération courante. Cela vous aidera à projet l’équipe dans le long terme, et rappeler le chemin parcouru.</p><blockquote>Vous souhaitez aller plus loin ? Abonnez-vous sur Medium, rendez-vous sur <a href="https://www.retrolution.co/">Retrolution</a> ou retrouvez-moi sur <a href="https://www.linkedin.com/in/maxencedalmais/">Linkedin</a>. Vous souhaitez discutez de vos besoins concernant les rétrospectives ? Suivez <a href="https://calendly.com/maxence-retrolution/30min">ce lien</a>, et prenons le temps de discuter.</blockquote><h3>Bonus: Détendez-vous</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EzSU5zA1HApuUaUrE_k3kQ.jpeg" /></figure><p>Parce que tout bon classement contient un bonus, en voici un, rien que pour vous: <strong>Détendez-vous.</strong></p><p>Suivre tout ces conseils peut paraître lourd. Vous comprenez l’intérêt mais n’avez pas le temps de creuser chaque sujet ? C’est normal, ne vous inquiétez pas. Si c’est votre cas, n’essayez pas de faire parfait dès vos premières rétrospectives. Concentrez-vous sur les 5 premiers points de cet article, et faites-vous confiance. C’est cette même confiance qu’il faut construire au sein de l’équipe pour que ses membres aient envie d’avancer ensemble.</p><p>Ne cherchez pas dès les premières rétrospectives à trouver des solutions miracles. Expérimenter d’abord avec des petits changements. Et enfin, n’oubliez pas que vous êtes également amené à vous améliorer. Comme chaque membre de l’équipe, vous avez le droit à l’erreur.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4a1d48138b4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/retrolution-fr/10-conseils-pour-am%C3%A9liorer-vos-r%C3%A9trospectives-agiles-b4a1d48138b4">10 conseils pour améliorer vos Rétrospectives agiles</a> was originally published in <a href="https://medium.com/retrolution-fr">Retrolution — fr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Alimenter la boucle de rétroaction : Une phase supplémentaire pour rendre votre rétrospective…]]></title>
            <link>https://medium.com/retrolution-fr/alimenter-la-boucle-de-r%C3%A9troaction-une-phase-suppl%C3%A9mentaire-pour-rendre-votre-r%C3%A9trospective-7abdbd5e7c5d?source=rss-958052064161------2</link>
            <guid isPermaLink="false">https://medium.com/p/7abdbd5e7c5d</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[retrospectives]]></category>
            <dc:creator><![CDATA[Maxence Dalmais]]></dc:creator>
            <pubDate>Mon, 13 Jan 2020 09:16:54 GMT</pubDate>
            <atom:updated>2020-01-24T17:04:47.845Z</atom:updated>
            <content:encoded><![CDATA[<h3>Alimenter la boucle de rétroaction : Une phase supplémentaire pour rendre votre rétrospective d’itération plus productive</h3><blockquote>Je travaille comme développeur dans des environnements dits agiles depuis une dizaine d’années et suis le fondateur de <a href="https://www.retrolution.co/?utm_source=medium&amp;utm_medium=feedback-loop">Retrolution</a>, un outil d’aide aux facilitateurs de rétrospectives. J’ai l’expérience d’organisations qui appliquent Scrum mots par mots et d’organisations beaucoup moins structurées. J’en suis venu à la conclusion que <strong>la réunion la plus importante pour une équipe orientée produit est la réunion rétrospective</strong>. Je suis récemment devenu facilitateur de rétrospective et j’utilise dans mes rétrospective d’itération une phase supplémentaire par rapport au format classique en 5 phases. Je l’appelle ‘Feed the feedback loop’ ou en francais ‘Alimenter la boucle de rétroaction’. Voici ce que c’est, et pourquoi vous pouvez l’utiliser.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U5nRNsgxshJvHz2qOhRR8A.jpeg" /><figcaption>Recueillir des retours et itérer peut semble effrayant, mais souvenez-vous que vous êtes en sécurité ;-) — Photo by <a href="https://unsplash.com/@she_sees?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Charlotte Coneybeer</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>RetroQuoi ?</h3><p>Si vous n’êtes pas familiers avec les réunions rétrospectives, je vais expliquer brievement le concept.</p><p>Une réunion rétrospective est une <strong>réunion collaborative</strong> dont le but final est d’<strong>améliorer les conditions de travail et le résultat du travail</strong> d’un groupe de personnes travaillant plus ou moins ensemble et orientées vers les mêmes objectifs.</p><p>Cette réunion peut avoir lieu sur une base régulière pour les équipes suivant un processus itératif, mais aussi après un événement important tel qu’une fin de projet, une itération plus longue comme une fin de trimestre, ou une échéance manquée.</p><p>Le but de la réunion est de <strong>tirer des leçons de la période passée</strong> (d’où le terme Rétro), et pour l’équipe <strong>de décider et de s’engager à une liste d’actions </strong>à effectuer<strong> </strong>dans la prochaine itération. Les actions sont décidées par l’équipe afin de réduire ou de résoudre un problème, un point douloureux ou d’encourager un comportement.</p><p>Pour être utiles, il est communément admis que les actions doivent être <a href="https://fr.wikipedia.org/wiki/Objectifs_et_indicateurs_SMART">SMART</a>, ce qui signifie Spécifiques, Mesurables, Atteignables, Réalistes et Temporellement définies. Pour être précis, la signification des acronymes change quelque peu avec le temps et le contexte. Pour les réunions classiques, j’aurais tendance à garder le mot original derrière le A, qui signifie <em>Assignable</em>. Pour les réunions rétrospectives, il pourrait être plus difficile d’assigner une action à une personne spécifique, car nous pourrions décider d’un changement collectif.</p><h3><strong>Les rétros sont métas</strong></h3><p>Les réunions de rétrospective, telles que présentées dans le livre <a href="https://www.oreilly.com/library/view/agile-retrospectives/9781680500295/">Agile Retrospective: Making Good Teams Great</a> d’<strong>Esther Derby</strong> et <strong>Diana Larsen</strong> suivent une structure en cinq phases. Les cinq phases sont :</p><ol><li>Préparer le terrain</li><li>Rassembler des données</li><li>Générer des idées</li><li>Décider de ce qu’il faut faire</li><li>Clore la rétrospective</li></ol><p>Dans la dernière phase, “ Clore la rétrospective “, nous faisons souvent <strong>la rétrospective de la réunion rétrospective</strong> elle-même.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FRJSomfGCxHBwb0GpEQ%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FRJSomfGCxHBwb0GpEQ%2Fgiphy.mp4&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FRJSomfGCxHBwb0GpEQ%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/a9419f53549c705a3f79ef58d058afd6/href">https://medium.com/media/a9419f53549c705a3f79ef58d058afd6/href</a></iframe><p>L’idée est de recueillir les réactions des participants afin d’améliorer les rétrospectives suivantes. Cela sert à la fois un objectif pratique — car cela aidera l’animateur à mieux adapter les prochaines rétrospectives à l’équipe — et un objectif pédagogique — car cela montre aux participants que le <strong>format des rétrospectives peut être adapté à d’autres sujets</strong> et que <strong>tout peut être amélioré.</strong></p><h3>Les Rétrospectives d’Itérations concernent le fait d’itérer et l’Amélioration Continue</h3><p>Une idée fausse et courante au sujet de la réunion rétrospective concerne son objectif principal. Le but de la rétrospective n’est pas de se concentrer sur le passé, mais d’apprendre du passé afin d’améliorer l’avenir.</p><p>Comme Aristote l’a écrit dans son livre “<em>Éthique à Nicomaque”</em> datant de 350 avant J.C :</p><blockquote>Personne ne pense au passé, mais à ce qui est futur et peut être différent</blockquote><p>Nous savons déjà que nos actions doivent être <em>SMARTs</em> et que tout peut être amélioré. De plus, les actions sont décidées sur la base d’un objectif.</p><p>En travaillant avec des itérations courtes, (entre 1 jour et 1 mois), il est clair que :</p><ul><li>chaque itération ne doit pas apporter de changements spectaculaires</li><li>la courte période d’itération facilite l’apprentissage</li></ul><p>De plus, lorsqu’on s’engage dans des activités rétrospectives, il doit être clair que le<strong> processus d’itération ne concerne pas seulement le produit, mais aussi le processus et les personnes</strong>.</p><p>Pour compléter ces concepts, il est bon de <strong>considérer certaines actions comme des expériences</strong>. Lors de la prochaine itération, l’équipe tentera de mettre en œuvre l’expérimentation. Parce qu’une expérimentation n’est rien de plus que ce qu’elle dit, une expérimentation, <strong>elle doit être évaluée</strong>. Ensuite, les résultats seront contrôlés, et l’expérimentation pourra être prolongée, adaptée ou arrêtée.</p><p><strong>C’est exactement ce qu’est cet ajout à la structure traditionnelle en 5 phases : vérifier l’état et le résultat des actions précédentes afin d’avoir une décision d’équipe concernant un éventuel suivi.</strong></p><p>J’appelle cette étape “Feed the feedback loop” ou “<strong>Alimenter la boucle de rétroaction</strong>”, car c’est vraiment de cela qu’il s’agit. Elle vous permet de commencer la discussion avec des choses qui ont été planifiées et mises en œuvre précédemment, et vous donne l’occasion de vérifier comment elles ont fonctionné dans la pratique et de les adapter.</p><p>Ne vous méprenez pas : cette idée n’est pas nouvelle et a été discutée par d’autres personnes sous des noms différents tels que <a href="https://scrumcrazy.wordpress.com/2011/10/19/best-practice-review-the-action-items-from-the-previous-retro-in-the-current-retro/">Suivi rétrospectif</a>, <a href="https://blogs.aca-it.be/10-tips-more-effective-retro-actions/#10">Évaluation des résultats des actions</a>, ou décrite dans <a href="https://www.kbp.media/action-focused-retrospectives/">Rétrospectives axées sur l’action</a>. Malgré ces articles, je pense qu’elle mérite plus de visibilité et d’être intégrée dans toutes les rétrospectives d’itérations.</p><h3>Phase ou activités ?</h3><p>Nous avons introduit le concept d’“<strong>Alimenter la boucle de rétroaction</strong>“ pour les rétrospectives d’itérations, mais nous ne l’avons pas encore vraiment decris.</p><p>Une des questions se pose est de savoir s’il s’agit d’une phase de la rétrospective ou d’une activité. Je dirais qu’il ne peut pas vraiment s’agir d’une activité parce que sa portée est en quelque sorte limitée et qu’elle ne se marie pas bien avec d’autres activités.</p><p>Cependant, il est assez difficile de théoriser une nouvelle phase dans le processus rétrospectif et il peut sembler effrayant d’échapper à la structure bien connue en 5 phases.</p><p>Certaines personnes aiment l’imaginer et l’intégrer dans la phase initiale de “préparation du terrain“. D’autres animateurs pensent qu’elle appartient à la quatrième phase “ Décider quoi faire “, puisque l’équipe décidera à la fin de la phase de décider quoi faire avec les expériences.</p><p>Enfin, considerent qu’il est inutile de faire un point sur le suivi des actions. Leurs arguments sont que les questions importantes émergeront d’elles-mêmes, ou plus précisément seront rappelées par les participants et que ce n’est pas le rôle de l’animateur de soulever des questions. Je ne peux qu’être en désaccord avec eux.</p><blockquote>Le rôle du facilitateur est de s’assurer que l’équipe apprend le plus possible, qu’elle s’adapte au fil du temps, et aussi de faire le meilleur usage du temps alloué pour la rétrospective .</blockquote><p>Le fait de disposer de 5 à 15 minutes (soit environ 10 %) consacrées à “alimenter la boucle de rétroaction“ vous permettra de parcourir rapidement les sujets importants et libérera généralement du temps pour d’autres sujets au cours des autres phases de la rétrospective.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgfycat.com%2Fifr%2Ffluffyinstructiveafricanclawedfrog&amp;url=https%3A%2F%2Fgfycat.com%2Ffluffyinstructiveafricanclawedfrog&amp;image=https%3A%2F%2Fthumbs.gfycat.com%2FFluffyInstructiveAfricanclawedfrog-size_restricted.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=gfycat" width="900" height="380" frameborder="0" scrolling="no"><a href="https://medium.com/media/d66ded1f16aee3a30f775c6be08b4778/href">https://medium.com/media/d66ded1f16aee3a30f775c6be08b4778/href</a></iframe><p>Dans un deuxième article, j’expliquerai comment je prépare et anime cette nouvelle étape de la rétrospective, mais laissez-moi ici vous expliquer deux aspects essentiels.</p><p>Tout d’abord,<strong> vous voulez l’imaginer comme une phase rétrospective</strong>. Je le fais entre les phases “Préparer le terrain” et “Recueillir des données”. Le fait de la considérer comme une phase vous aidera à <strong>prendre le temps qu’elle mérite,</strong> et aussi à la considérer non pas comme une activité définie, mais comme une phase avec un but. En fonction de l’équipe et du contexte, vous <strong>adapterez le contenu et l’activité</strong> de la phase. Et comme il s’agit d’une phase, vous n’avez pas besoin de vous concentrer exclusivement sur les actions précédentes. Vous pouvez par exemple rajouter comme sujet des changements récents ou des événements qui se sont produits.</p><p>Secondement, vous voulez considérer chaque point discuté comme une mini-rétrospective : vous voulez que tout le monde soit au fait des points discutés, recueillir des données sur les résultats, génèrer des idées à leurs sujets et enfin décider de la suite éventuelle.</p><p>Bien sûr, de temps en temps, un point nécessiterait une discussion plus longue et il ne serait donc pas possible de se tenir au calendrier initial. C’est votre rôle de facilitateur de détecter et de décider si vous voulez vous en tenir à votre plan initial ou changer complètement votre rétro et vous concentrer sur cet élément. En fonction des activités que vous avez prévues pour les autres parties de la rétrospective, vous pouvez écrire l’élément sur un paperboard et l’ajouter aux éléments discutés plus tard dans la phase “ Générer un aperçu “.</p><h3>Conclusion</h3><p>En tant quie facilitateur de rétrospective, votre travail consiste à faire en sorte que la réunion rétrospective soit la plus utile possible pour les participants. En ajoutant à votre rétrospective la phase supplémentaire “alimenter la boucle de rétroaction“, vous aiderez l’équipe à garder une trace de ses expériences antérieures et à décider de ce qu’elle doit en faire. Vous élèverez le processus d’itération à un nouveau niveau. Comme toujours avec la rétrospective, prenez le temps d’y réfléchir et de l’adapter à ce que vous pensez être le mieux pour l’équipe, le contexte et vos connaissances.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7abdbd5e7c5d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/retrolution-fr/alimenter-la-boucle-de-r%C3%A9troaction-une-phase-suppl%C3%A9mentaire-pour-rendre-votre-r%C3%A9trospective-7abdbd5e7c5d">Alimenter la boucle de rétroaction : Une phase supplémentaire pour rendre votre rétrospective…</a> was originally published in <a href="https://medium.com/retrolution-fr">Retrolution — fr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Feed the feedback loop : An additional phase to make your iteration retrospective more productive]]></title>
            <link>https://medium.com/hackernoon/feed-the-feedback-loop-an-additional-phase-to-make-your-iteration-retrospective-more-productive-3d7e3ea612f6?source=rss-958052064161------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d7e3ea612f6</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[retrospectives]]></category>
            <category><![CDATA[meetings]]></category>
            <dc:creator><![CDATA[Maxence Dalmais]]></dc:creator>
            <pubDate>Fri, 10 Jan 2020 09:35:21 GMT</pubDate>
            <atom:updated>2020-01-30T12:59:42.693Z</atom:updated>
            <content:encoded><![CDATA[<h3>Feed the feedback loop: An additional phase to make your iteration retrospective more productive</h3><blockquote>I’ve been working as a software developer in so-called agile environments for the last 10 years or so, and am the founder of <a href="https://www.retrolution.co/?utm_source=medium&amp;utm_medium=feedback-loop">Retrolution</a> a tool to help retrospective facilitators. I’ve experienced organization applying <em>scrum by the book</em> and some much less structured process. I came to the conclusion that the <strong>single most important meeting for a product oriented team is the retrospective meeting</strong>. I recently became retrospective facilitator and use in iteration retrospective an <strong>additional phase to the classical 5 phases retrospective format</strong>. I call it ‘<strong>Feed the feedback loop<em>’</em></strong><em>. </em>Here what it is, and why you may want use it.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TDZupXNPZlGj3JtFuPA-HQ.jpeg" /><figcaption>Getting Feedback and looping may seem scary, but remember that you are safe ;-) — Photo by <a href="https://unsplash.com/@she_sees?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Charlotte Coneybeer</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>RetroWhat?</h3><p>If you are not familiar with retrospective meetings, let me try to explain the concept behind them.</p><p>A retrospective meeting is a <strong>collaborative meeting</strong> whose ultimate goal is to <strong>improve working conditions and delivery</strong> of a group of people working more or less together and aligned toward the same objectives.</p><p>This meeting can take place regularly for teams following an iterative process, but also after an important event such as a project release, longer iteration such as a quarter-end, or a missed deadline.</p><p>The goal of the meeting is to <strong>learn from the past period</strong> (Hence the term Retro), and for the team to <strong>decide and commit</strong> to a <strong>list of actions</strong> in the next iteration. The actions are decided by the team to reduce or solve an issue, pain point or encourage a behavior.</p><p>To be useful, it is commonly accepted that actions have to be <a href="https://en.wikipedia.org/wiki/SMART_criteria">SMART</a>, which stands for Specific, Measurable, Attainable, Relevant, and Timely. To be accurate, the meaning of acronyms changes somewhat over time and context. For classical meetings, I would tend to keep the original word behind the A, which stands for <em>Assignable. </em>For retrospective meetings, it might be harder to assign an action to a specific person, as we might decide on a collective change.</p><h3>Retros are meta</h3><p>Retrospective meetings, as presented in the <a href="https://www.oreilly.com/library/view/agile-retrospectives/9781680500295/">Agile Retrospective: Making Good Teams Great</a> by <strong>Esther Derby </strong>and<strong> Diana Larsen </strong>follow a five phases structure. The fives phases are :</p><ol><li>Set the stage</li><li>Gather data</li><li>Generate insight</li><li>Decide what to do</li><li>Close the retrospective</li></ol><p>In the last phase, ‘Close the retrospective’ we often do the <strong>retrospection of the retrospective meeting</strong> itself.</p><p>Retro of the retro? pretty Meta, right?</p><p>The idea is to gather feedback from participants to improve following retrospectives. This serves both a practical purpose — as it will help the facilitator to better adapt the next retrospectives to the team — and an educational purpose — as it shows the participants that the <strong>retrospective format can be adapted to other topics</strong> and that <strong>everything can be improved</strong>.</p><h3>Iterations Retrospectives are about iteration and continuous Improvement</h3><p>One common misconception about the retrospective meeting is its main focus. The goal of the retrospective is not to focus on the past, but to learn from the past to improve the future.</p><p>As Aristotle wrote in his 350 B.C.E book <em>“Nicomachean Ethics” :</em></p><blockquote>No one deliberates about the past, but about what is future and capable of being otherwise.</blockquote><p>We already know that our actions must be <em>SMARTs</em> and that everything can be improved. Moreover, actions are decided based on a goal.</p><p>When working with short iterations, (anything between 1 day to 1 month), it is clear that :</p><ul><li>every iteration should not bring dramatic changes</li><li>the short iteration period make it easy to learn</li></ul><p>Also, when engaging in retrospective activities, it should be clear that the <strong>iteration process is not only about the product but also the process and the people.</strong></p><p>To build on top of these considerations, it is good to <strong>consider certain actions as experiments</strong>. During the next iteration, the team will try to implement the experimentation. By definition, one experiment <strong>has to be evaluated</strong>. Then the results will be controlled, and the experimentation may be extended, adapted or stopped.</p><p><strong>This is what this addition to the traditional 5 phases structure is all about: checking the status and outcome of previous actions in order to have a team decision regarding a potential follow-up.</strong></p><p>I call this step ‘<strong><em>Feed the feedback loop</em></strong>’ because this is really what is it all about. It allows you to start the discussion with things that have been planned and implemented previously and allows you to check how they have worked in practice and adapt them.</p><p>Don’t get me wrong: this is not a novel idea and has been discussed by others with different names such as <a href="https://scrumcrazy.wordpress.com/2011/10/19/best-practice-review-the-action-items-from-the-previous-retro-in-the-current-retro/">Retrospective Follow Up</a>, <a href="https://blogs.aca-it.be/10-tips-more-effective-retro-actions/#10">Evaluate action outcomes</a>, or described in <a href="https://www.kbp.media/action-focused-retrospectives/">Action Focused Retrospectives</a>. Despite these articles, I think it deserves more visibility and to be integrated into all iterations retrospectives.</p><h3>Phase or activity?</h3><p>We introduced the<strong> ‘Feed the feedback loop’</strong> concept for iteration retrospective but haven’t yet been descriptive about it.</p><p>One of the questions that deserved to be asked is whether this is a retrospective phase or an activity. I would say it can’t be defined as an activity because it’s is kind of limited in scope and does not play well with other activities.</p><p>On the other end, it is kind of a big deal to theorize a new phase in the retrospective process and may seem frightening to escape the well-known 5-phases structure.</p><p>Some people like to imagine it and integrate it in the initial<em> ‘Set the stage’ </em>phase. Other facilitators think it belongs to the fourth <em>‘Decide what to do’</em> phase since the team will decide at the end decide what to do with the experiments.</p><p>Finally, some will say that there is no point in making a follow-up point on actions. Their arguments could be that important issues will emerge on their own, or more accurately will be recalled by participants: it is not the facilitator’s job to bring up issues. I can only disagree with them.</p><blockquote>The facilitator job is to make sure the team learns as much as they can, that they adapt over time, and also to make the better usage of the time allocated for the retrospective .</blockquote><p>Having 5 to 15 minutes (or around 10%) dedicated to ‘Feed the feedback loop’ will allow you to quickly browse through important topics and will usually free up time for other topics during other phases of the retrospective.</p><p>Feeds the loops to make sure it starts and never end</p><p>In a second article, I will explain how I prepare and animate this new stage of the retrospective, but let me explain two essential aspects.</p><p>First of all, <strong>you want to think of it as a retrospective phase</strong>. I do it between the ‘Set the stage’ and ‘Gather data’ phase. Thinking of it as a phase will help you <strong>take the time it deserves</strong>, and also to think of it not as a defined activity, but as a phase with a goal. Depending on the team and the context, you will <strong>adapt the content and activity</strong> of the phase. And because this is a phase, you don’t have to stick to focus exclusively on the previous actions. You can, for example, bring as a subject recent changes or events that occurred.</p><p>Secondly, you want to consider each point discussed as a mini-retrospective: you want everybody to be knowledgeable of the discussed items, gather data on the results, generate insight on them, and finally decide what to do with them.</p><p>Of course, from time to time, the item would require a longer discussion and we cannot stick to the original schedule. It is your role as a facilitator to detect and decide whether you want to stick to your original plan or change your retro completely and focus on that item. Depending on the activities you’ve planned for the other parts of the retro, an option is to write the item on a paperboard, and add it to the items later discussed in the ‘Generate Insight’ phase.</p><h3>Conclusion</h3><p>As a retrospective facilitator, your job is to make the retrospective meeting the most useful for the participants. By adding the extra ‘Feed the feedback loop’ phase to your retrospective, you will help the team keep track of their previous experimentation and decide what to do with them. You will bring the iteration process to a new level. As always with retrospectives, take some time to reflect on it and adapt it to what you think is best for the team, the context and your knowledge.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d7e3ea612f6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/feed-the-feedback-loop-an-additional-phase-to-make-your-iteration-retrospective-more-productive-3d7e3ea612f6">Feed the feedback loop : An additional phase to make your iteration retrospective more productive</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Native Performance: Do and Don't]]></title>
            <link>https://medium.com/hackernoon/react-native-performance-do-and-dont-1198e97b730a?source=rss-958052064161------2</link>
            <guid isPermaLink="false">https://medium.com/p/1198e97b730a</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[hackernoon-top-story]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Maxence Dalmais]]></dc:creator>
            <pubDate>Fri, 31 May 2019 09:47:33 GMT</pubDate>
            <atom:updated>2019-06-04T07:29:29.145Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>TL;DR — Do read the docs of React, React Native and every libraries you are using Using remote Images can be painful: use a library. Some patterns can be harmful, be careful with PureComponents and HOCS. Keep your libraries up to date. Give some love to your app and you users.</blockquote><p>This article is based on two years of experience building <a href="https://nelio.io/">Nelio</a> React Native Mobile Apps, available on <a href="https://itunes.apple.com/fr/app/nelio/id1057392527?mt=8">iOS</a> and <a href="https://play.google.com/store/apps/details?id=io.nelio.hello&amp;hl=en">Android</a>. It assumes you already have some experiences with React and or React Native. It is not strictly speaking dedicated to React Native, as some of the advices you will find below apply for a regular React application. It is also not an exhaustive guide to performance: you can apply all advices found here but still have a laggy app. Don&#39;t blame us ;-)</p><p>Nelio is a food delivery startup focusing on Craft Food, currently operating in Paris. When delivering quality good is your business, it impacts all aspects of your company. From the marketing message to your codebase. Basically, everybody here is focused to deliver the best User eXperience.</p><p>Performance is one of the topic which can change the overall perception of the service you deliver. To be honest, we have sometimes a hard time matching our and our customers expectation on that topic. This articles is based on what we learned so far during this journey. Mistakes that we did, and will not reproduce, or stuff that we learnt and actions that we took in responses.</p><h3>React and React-Native Performance</h3><p>Being a React developer for the last 4 years, all I can say is that I love it. I was more than happy when joining this React Native project and it matched what I expected in terms of learning curve: Having the same framework make it really easy to start developing your first components, but later on you will need to get a deeper understanding of React Native. Just as being an advanced React Web developer requires you to have an understanding of what is going on in the browser ;-)</p><p>Regarding, performance in React Native, this is the same:</p><blockquote>Everything you know about React performance will apply in a React Native application</blockquote><p>That being said, probably the first next step is to jump to <a href="https://reactjs.org/docs/optimizing-performance.html">React performance doc</a> and later on <a href="https://facebook.github.io/react-native/docs/performance">React Native performance doc</a>. These are great resources that I will not spend anytime copy-paste or rewrite here ;-) I will rather focus on specific patterns that we put in places or decided to avoid in order to improve performances.</p><p>I will also not spend any time arguing whether React Native is fast enough or not, whether you should move to flutter or go fully native. There are some great React Native Apps out-there. Here is how we try to be one of them.</p><h3>Do provide UI Feedback</h3><p>Performance is mainly about perception rather than measuring precisely how long a function take time to complete. More important that <em>how long ?</em>, you should ask yourself <em>why ?</em> and <em>when ?.</em></p><p>It is commonly accepted that after a user interaction you should give feedback in 100ms. Keep in mind that this threshold is a barrier that you should not cross. Keep also in mind that<strong> it is never too early to give feedback</strong>.</p><p>There are different ways to give feedback to the user. In React Native, a great and simple solution is to use the <a href="https://facebook.github.io/react-native/docs/touchableopacity">TouchableOpacity</a> component on all component which accept user interactions. This will give feedback to the user during the interaction and is a great way to indicate that something will occur after the interaction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/356/1*VyQsZkHhMwtASBU8guUfxA.png" /><figcaption>A skeleton product card in Nelio App</figcaption></figure><p>If the click lead to opening a new screen, then you should <strong>spend some time thinking about your data loading</strong>. Usually a good approach is to open your new screen as soon as possible, render the content that you already have, and display a loader and/or some placeholder component while the content is loading. This is a technic also called <a href="https://uxdesign.cc/what-you-should-know-about-skeleton-screens-a820c45a571a"><em>Skeleton Screens</em></a><em>.</em></p><p>If your click lead to something else, such as adding an item to your cart, to favorites, or post a chat message , this very often will include a remote API call. In that case, you should when possible — which is most of the time — <strong>act as if the endpoint did already respond successfully</strong>. This pattern is called <a href="https://uxplanet.org/optimistic-1000-34d9eefe4c05">Optimistic UI</a> and is also wide spread across the industry.</p><p>At Nelio we are using GraphQL with ReactApollo. ReactApollo with the <a href="https://www.apollographql.com/docs/react/features/optimistic-ui">optimisticResponse</a> parameter has a great solution to implement this pattern. This can also be done in different manners when using redux.</p><h3>Images</h3><p>A big topic regarding performance and usability of your React Native apps is image. Coming from a web background, it was for me a bit of a surprise. When you think about it, the browser are doing a huge job dealing with images, speaking of downloading, caching, decoding, scaling and displaying them: all that happening in a streamed way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*7aPSypInSHdfEUpqW045Ig.gif" /></figure><h4>Do use an Image Caching solution</h4><p>React Native code offers an <a href="https://facebook.github.io/react-native/docs/image">Image</a> component, which does a great job at displaying a single image, but has some issues when dealing with a lots of them. Specifically, we had some flickering issues, and also when too many images are loaded in our apps, at some points, they just stop loading.</p><p>We switch to <a href="https://github.com/DylanVann/react-native-fast-image">react-native-fast-image</a>, and it seems we are not the only one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kW8vh_xG5phNxpE_8ucJ_g.png" /><figcaption>Recently react-native-fast-image was downloaded 12% as often a react-native on NPM registry which is almost as Expo</figcaption></figure><h4>Do load images the size you need them</h4><p>React-native-fast-image solved lots of issues we had, but we still had some random crashes in our app that we noticed was linked to some images. After a quick check, we noticed that we asked our app to download, cache, and scale tens of Images, each weighing several hundred KiloBytes. We tried initially to solve this problem by putting some hard limit to images upload, but we were not happy with this solution. In any case, <strong>be careful about the amount and size of the images your are loading</strong>, as this put lots of pressure on the device. A good solution is to do a big part of the job not on the device but before.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*qp4sp_nxFk3uyAnU2Q9W8Q.jpeg" /><figcaption>An image resized to specific dimensions with cloudImg with the following URL <a href="https://acoigzuuen.cloudimg.io/crop/640x360/q95/_s3_nelio_/kaviari-3384d944c6f8418679baee23-1523374450958.jpeg">https://acoigzuuen.cloudimg.io/crop/640x360/q95/_s3_nelio_/kaviari-3384d944c6f8418679baee23-1523374450958.jpeg</a></figcaption></figure><p>Even if you don&#39;t have memory issues with images, it is still a good idea to size your image in the exact dimension you will display them. This will put less pressure on your user device.</p><p>We recently switch to use an Images Scaling CDN solution which would allows us to download images scaled precisely at the size we would display it. For the record we opted for <a href="https://www.cloudimage.io/">CloudImage</a>, and are currently very happy with it. It allow us to request an image on the fly with specific dimension. For a quick implementation with opted-in for a change of our GraphQL resolvers to translate to images URL to the cloudImage one. This change can also be done client side. CloudImage is the solution we went for, for could have used <a href="https://cloudinary.com/">Cloudinary</a> or hosting an open source solution such as <a href="https://github.com/imgproxy/imgproxy">imgProxy</a> or <a href="https://github.com/thumbor/thumbor">Thumbor</a>.</p><h3>Do use Pure Components wisely</h3><p>As said previously, React Native apps are before and after all React apps. Most advices which are good for React apps are good for React Native apps.</p><p>Probably the most popular advices around React performances concerns the use or not of PureComponent (and/or <a href="https://reactjs.org/docs/react-api.html#reactmemo">React.memo()</a>). Long story short, useless re-render in React is usually not an issue but can become one on complex application. PureComponent is a way to prevent a component to re-render when his props did not changed. More precisely it implements it implements <a href="https://reactjs.org/docs/react-component.html#shouldcomponentupdate">shouldComponentUpdate</a> by doing a shallow comparison of props.</p><p>Some people think it is a good pattern to use PureComponent by default when implementing a new Component. My advice is to always keep in mind that it can be more harmful than helpful. This is really good example <a href="http://wiki.c2.com/?PrematureOptimization">of Evil Premature Optimization</a>.</p><p>If you need/really want to reduce re-render keep in mind, in that case, when instancing a component, you should <strong>not create any props of that PureComponent in your parent render method</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mna5onBl0ntyQau3ngybLg.png" /><figcaption>Don&#39;t create any new props at render time when using a pure component</figcaption></figure><p>The two main uses cases when giving props are providing new objects and new functions. The upper example also show providing a child Component as Children Props, but if you go beyond JSX, at the end, it it just a regular JS object.</p><p>Regarding objects, also keep in mind that arrays are objects. When switching your component to a more functional style, be always aware that most functional function, which are in themselves pure, create new references. Once again, don&#39;t call theses functions at render time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ptTNNQnBwm7JTRtZ8hzmUQ.png" /><figcaption>Also avoid pitfalls when going functional</figcaption></figure><p>Another pattern that you might use a lot when using React-Native are <a href="https://reactjs.org/docs/render-props.html">renderProps</a>: providing as props a function that return a component. From a props point of view, a render props is just a regular function provided as props, and so the general advice apply: Don&#39;t create renderProps at runtime.</p><p>Here at Nelio we don&#39;t use yet React Hooks which you will need to check if you haven&#39;t. Hooks shipped in React Native 0.59, and there will be a dedicated section about it below. What we use instead is <a href="https://github.com/acdlite/recompose">recompose</a>, from whose hooks have been greatly inspired.</p><p>Recompose, thanks to Pure , withHandlers and withPropsOnChange has proven for us to be a great utility at helping keeping our code base clean and improve performance.</p><h3>Don&#39;t use HOCs on the fly</h3><p>When you application becomes complex and you want share some common pattern across your component, it is not rare to use <a href="https://reactjs.org/docs/higher-order-components.html">High Order Components</a>.</p><p>Using High Order Component is rather a good practice even if this sometimes can be arguable as it increase indirection. It can though increases the complexity of your code comprehension.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qT0AJGIrNJjRslfNe719bg.png" /><figcaption>Don&#39;t instance HOC at render</figcaption></figure><p>What you should really be careful is <strong>not instance any High Order Component on the fly, specifically </strong><a href="https://reactjs.org/docs/higher-order-components.html#dont-use-hocs-inside-the-render-method"><strong>during a render method</strong></a>. The reason why you don&#39;t want to do that is that you are effectively creating a new component. React can&#39;t know that this is effectively the same component as before (as this is indeed not). This put lots of pressure on the reconciliation algorithm. More than that, it also force React to run all <a href="https://reactjs.org/docs/react-component.html#the-component-lifecycle">lifecycle method</a>, on the whole tree.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2YnM4jOczsFVVhRygSzTWw.png" /></figure><p>I can remember one case where we had this bad pattern, noticed it and solved it. Basically this happened when we mixed the used of <em>RenderProps</em> and <em>High Order Components</em>. As Apollo user, we use in most places <a href="https://www.apollographql.com/docs/react/essentials/queries/#basic">Apollo Query Component</a> to fetch data from our endpoint. Because our code style is to use recompose when possible, the initial implementation was wrapping the Apollo Query component in a <em>fromRenderProps</em> HOC. This works great for all query where you don&#39;t need dynamic variables, but failed otherwise, as there is <a href="https://github.com/acdlite/recompose/issues/702">no way to give specific props to your render props component</a>. The way we implemented this originally was wrong. We later identifier two ways to improve that. The first one was to accept to not use Recompose HOC here, and just do a regular Component using a more classical implementation. The second one, that we choose, was to switch to <a href="https://www.apollographql.com/docs/react/api/react-apollo#graphql">Apollo graphQL HOC</a>, which is <a href="https://www.apollographql.com/docs/react/recipes/recompose">documented</a> to match our usage.</p><p>Another usage that I can imagine is if you need to instance a High Order Component based on props that you received. I created a<a href="https://repl.it/repls/VividOrangePipeline"> small example</a> that show such case. We had in our codebase something that was close from this pattern. After some thinking, we get rid of it by either by not using HOC in those places, and replace it by renderProps or directly providing the Component as props.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WmtKK-YxJxxbRTViDnX08A.png" /><figcaption>Do use another pattern such as Children, renderProps, or Component as Props</figcaption></figure><h3>Don&#39;t implement bulk reducers</h3><p>If you are not using GraphQL, chances are you are using <a href="https://redux.js.org/">redux</a>. Here we are using both, but I don&#39;t recommend it for most cases.</p><p>If you are not using redux with <a href="https://github.com/paularmstrong/normalizr">normalizr</a> and/or <a href="https://rematch.gitbooks.io/rematch/#getting-started">rematch</a>, or at some point writing yourself your reducers, please be careful to <strong>always mutate only the objects that you need to</strong>. If you followed attentively <a href="https://redux.js.org/basics/reducers#designing-the-state-shape">Redux basic tutorial</a> you are already aware of this point, but if you are not, then read it again ;-)</p><p>If you are like us and sometime too eager to code, then maybe when refetching a list of item from the network, and saving it to your reducer — even in a normalized way — you naïvely do :</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcarbon.now.sh%2Fembed%3Fbg%3Drgba%2838%252C87%252C125%252C1%29%26t%3Dlucario%26wt%3Dnone%26l%3Djsx%26ds%3Dtrue%26dsyoff%3D20px%26dsblur%3D68px%26wc%3Dtrue%26wa%3Dtrue%26pv%3D56px%26ph%3D56px%26ln%3Dfalse%26fm%3DHack%26fs%3D14px%26lh%3D133%2525%26si%3Dfalse%26es%3D2x%26wm%3Dfalse%26code%3Dfunction%252520itemsReducer%252520%28state%252520%25253D%252520%25257B%25257D%25252C%252520action%29%252520%25257B%25250A%252520%252520switch%252520%28action.type%29%252520%25257B%25250A%252520%252520%252520%252520case%252520UPDATE_ITEMS_DOCS%25253A%25250A%252520%252520%252520%252520%252520%252520return%252520%25257B%252520...state%25252C%252520...action.docs%252520%25257D%25250A%252520%252520%252520%252520%25257D%25250A%252520%252520%25257D%25250A%252520%252520return%252520state%25250A%25257D&amp;url=https%3A%2F%2Fcarbon.now.sh%2F%3Fbg%3Drgba%2838%25252C87%25252C125%25252C1%29%26t%3Dlucario%26wt%3Dnone%26l%3Djsx%26ds%3Dtrue%26dsyoff%3D20px%26dsblur%3D68px%26wc%3Dtrue%26wa%3Dtrue%26pv%3D56px%26ph%3D56px%26ln%3Dfalse%26fm%3DHack%26fs%3D14px%26lh%3D133%252525%26si%3Dfalse%26es%3D2x%26wm%3Dfalse%26code%3Dfunction%25252520itemsReducer%25252520%28state%25252520%2525253D%25252520%2525257B%2525257D%2525252C%25252520action%29%25252520%2525257B%2525250A%25252520%25252520switch%25252520%28action.type%29%25252520%2525257B%2525250A%25252520%25252520%25252520%25252520case%25252520UPDATE_ITEMS_DOCS%2525253A%2525250A%25252520%25252520%25252520%25252520%25252520%25252520return%25252520%2525257B%25252520...state%2525252C%25252520...action.docs%25252520%2525257D%2525250A%25252520%25252520%25252520%25252520%2525257D%2525250A%25252520%25252520%2525257D%2525250A%25252520%25252520return%25252520state%2525250A%2525257D&amp;image=https%3A%2F%2Fcarbon.now.sh%2Fstatic%2Fbanner.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=now" width="1024" height="473" frameborder="0" scrolling="no"><a href="https://medium.com/media/3d898468db6f5adc84804d660cd84d87/href">https://medium.com/media/3d898468db6f5adc84804d660cd84d87/href</a></iframe><p>If doing so and having some performances issues while rendering a list of items which can be refreshed in the background, then what you will want to do is update your store only when needed. More precisely <strong>only update references which need to be</strong>: if an items as the same value as before, then you probably don&#39;t need to save a new reference for it in redux. Updating reference in your store, will create useless render which by the end will produce the same components.</p><h3>Don&#39;t naively share Selectors</h3><p>If using redux, you are using mapStateToProps functions in your connect() call.</p><p>As your application grow, and your mapStateToProps complexity increase, then you might notice that some of the computation that you do in your mapStateToProps become heavy. You might also notice that you are sometimes re-rendering too much, which might seems counter intuitive as connect implements his <a href="https://redux.js.org/faq/react-redux#why-isn-t-my-component-re-rendering-or-my-mapstatetoprops-running">own props shallow comparison</a>.</p><p>The issue here is basically the same than with pureComponent. If every time you render your parent component you give new props to a pureComponent, it will need to re-render. <strong>What you want do here is keep the prevProps if the behavior of your component will be the same.</strong></p><p>Once this is correctly understood, then <a href="https://github.com/reduxjs/reselect">reselect</a> is a great solution to overcome this issue. This once again introduce a little boilerplate but this is definitely worth-it.</p><p>But be careful, <strong>a bad use of reselect can also introduce new performance issue</strong>. This is specially the case when you share your reducers in different places of you app, or shared across different instances of the same component. The problem here is that reselect selectors are basically memoized method whose cache has with limit of one. Reselect documentation has a dedicated section concerning <a href="https://github.com/reduxjs/reselect#sharing-selectors-with-props-across-multiple-component-instances">shared selectors</a> and provide a pattern to overcome it. Basically it consists of creating new selectors for each instance of the component. Others library such as <a href="https://github.com/toomuchdesign/re-reselect">re-reselect</a> solves this issue differently.</p><p>In any case, you should be really careful about this when you start to share you selector across Components or different instances of the same component.</p><h3>Going further</h3><p>Delivering a lag free experience on all smartphones is not a one time tasks, but as often with Software Development, a continuous quest. You will find below some improvements that we are currently considering.</p><h4>Use React Native 0.59</h4><p>As said previously, RN0.59 bring React hooks to React Native. Using hooks should allow us to switch away from recompose, which is not developed anymore.</p><p>Moreover, React Native 0.59 bring to Android devices an upgraded version of <a href="https://facebook.github.io/react-native/blog/2019/03/12/releasing-react-native-059#updated-jsc-means-performance-gains-and-64-bit-support-on-android">JavaScriptCore</a>, which have not been updated in a while. This update bring a performance gain of about 25% and <a href="https://developer.android.com/distribute/best-practices/develop/64-bit"><strong>64 bits supports which will be mandatory on Google Play store starting August 1, 2019</strong></a><strong>.</strong></p><h4>Experiment with FlatList Options</h4><p>When rendering a list of elements, you should always use a component based on a <a href="https://facebook.github.io/react-native/docs/virtualizedlist">VirtualizedList</a>, such as a <a href="https://facebook.github.io/react-native/docs/flatlist">FlatList</a> or a <a href="https://facebook.github.io/react-native/docs/sectionlist">SectionList</a>. Depending of the number of items of your list, the complexity of your component and their dimensions, you probably want spend some time tweaking their props, as lots of them will have a direct impact on Performance.</p><h4>Use Tool to detect your performance issue</h4><p>When trying to understand performance issues, you want try to understand how much time a component isMounting or rendering. <a href="https://reactjs.org/blog/2018/09/10/introducing-the-react-profiler.html">React Profiler</a> has been a great help at understanding sources of lags.</p><p>Something that we haven&#39;t used yet but can be useful when trying to find sources of responsiveness in your app, is <a href="https://github.com/facebook/react-native/blob/0ee5f68929610106ee6864baa04ea90be0fc5160/Libraries/BatchedBridge/MessageQueue.js#L88">spying the queue</a>, as explained <a href="https://blog.callstack.io/reactnative-how-to-check-what-passes-through-your-bridge-e435571ffd85">here</a>. The Queue is the communication proxy channel between the JS part of you app and the Native Part.</p><p>Your interface might be something half reactive : For example the scroll view or the touchable opacity work, but then the JS handler that you wrote are not triggered. In that case it means that the native code is executed, but not the JS. Spying if the queue is super busy is probably a good step to understand what is the source of your issue.</p><h3>Thanks</h3><p>Woo, congrats for reading until there. Any personal tips to share ? Don&#39;t be shy and comment ;-) Any question you still have ? Please put it there, and I&#39;ll do my best to answer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1198e97b730a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/react-native-performance-do-and-dont-1198e97b730a">React Native Performance: Do and Don&#39;t</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A small trick to write clean reducers]]></title>
            <link>https://medium.com/hackernoon/a-small-trick-to-write-clean-reducers-a0b1b1eff3d2?source=rss-958052064161------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0b1b1eff3d2</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[immutablejs]]></category>
            <category><![CDATA[react-redux]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[lodash]]></category>
            <dc:creator><![CDATA[Maxence Dalmais]]></dc:creator>
            <pubDate>Thu, 10 Aug 2017 06:24:44 GMT</pubDate>
            <atom:updated>2017-08-10T07:48:03.417Z</atom:updated>
            <content:encoded><![CDATA[<p>Writing react-redux reducers might be sometimes painful. Specifically, you might have to write lots of boilerplate code just to change one value or flag in a nested object. We will see how a small trick can help us reduce this code.</p><blockquote>TLDR: you can use lodash/fp/set to modify a deep attribute in your store in an immutable way. for example with import set from &#39;lodash/fp/set&#39; and then use set(path,<em>value</em>, state) such as with <em>s</em>et(`manufacturers.${manufacturer}.models.${model}.options.colors.${color}`, true)(state)</blockquote><h3>Current Situation</h3><p>When you are writing react-redux reducers, you must be careful about not mutating objects in the store. This is not 100% true in a simple react application, but since you are probably using some shallow comparison of props somewhere in your apps, this is true. This is the case if you use come kind of <a href="https://facebook.github.io/react/docs/react-api.html#react.purecomponent"><em>PureComponent</em></a>, or using <em>react-redux</em> connect with <a href="https://github.com/reactjs/react-redux/blob/master/docs/api.md#connectmapstatetoprops-mapdispatchtoprops-mergeprops-options"><em>mapStateToProps</em></a> functions, or any other way where you could use <a href="https://github.com/reactjs/reselect"><em>reselect</em></a> plugged to your store. If your are not, you probably should.</p><p>Some people love to use <a href="https://github.com/facebook/immutable-js"><em>Immutable.js</em></a> object in their store. If that’s your case and are happy with it, then you don’t really need to go further in the article. Personally, I prefer to deal with regular JS object in my store. I indeed found doing conversion between plan object JS object and Immutable to be cumbersome.</p><p>So, in order to write my reducers so they won’t mutate object in the store, and using regular JS object, here how I used to write my reducers.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/eb3eac810a39da52f6050fbf78519a24/href">https://medium.com/media/eb3eac810a39da52f6050fbf78519a24/href</a></iframe><p>You can probably find other ways to write this in a way you like better, or even argue that the shape of my <em>redux</em> store could be changed to better suit this operation, but still, there is time when you have to modify a deep attribute in your store.</p><p>I guess at this point you understand why I wanted to get a better solution. I will present one, but if you have other options, I will be happy to see it in comments ;)</p><h3>Finding a solution</h3><p>Now that our problem is correctly stated, as a good lazy programmer that you probably are, you must be wondering if there is a solution to this specific need. There is none as far I know. Again, feel free to correct me, or create one based on this article. Actually, the last section should be also interesting for you in that case.</p><p>Long story short, I’ve been looking for a solution to this problem, and since people I work with are terrible fans of <em>l</em><a href="https://github.com/lodash/lodash"><em>odash</em></a>, I thought there might be a solution here. I already knew the <a href="https://lodash.com/docs/4.17.4#set"><em>set</em></a> method, which is useful to set the value of attributes in nested objects. The problem with the regular version of the set method, is that it will mutate the object on which we set the attribute. As we said in introduction, this is not something that we want here. Basically what I was looking for was an immutable version of set.</p><p>I am glad I was not the only one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/1*yO4DORNgqM-CHftmb7t2Og.png" /><figcaption>The first result of this quick search was the trace to follow</figcaption></figure><p>As you can see on the above screenshot, my now hero <a href="https://medium.com/u/ff5ebab653a9">Rico Sta. Cruz</a>, asked <a href="https://github.com/lodash/lodash/issues/1696">this question</a> as a <em>lodash</em> issue two years ago. <a href="https://medium.com/u/c9acea0bae6e">John-David Dalton</a> answered immediately that it will come in <em>l</em><a href="https://github.com/lodash/lodash/wiki/FP-Guide"><em>odash/</em></a><em>fp</em>, and <a href="https://medium.com/u/783da0379221">Kyle Kelley</a> confirmed that more recently, even giving the syntax that we could use for “<em>Redux style state setting”</em></p><p>After that, I wanted to check if this solution was used and recommended in the react community. I did a very quick check, but did not found much reference to it. Nevertheless, I found one example, written by the now famous <a href="https://medium.com/u/a3a8af6addc1">Dan Abramov</a> in<a href="https://stackoverflow.com/a/37266130"> this stackoverflow post</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*hJKTbeu8NXlwfY-VNQRbSA.png" /><figcaption>Extract from <a href="https://stackoverflow.com/a/37266130">Dan Abramov post on stackoverflow</a>, available as gist <a href="https://gist.github.com/maxired/53c18a9796bd3b0ec61441a171895f00">here</a></figcaption></figure><p>I think that we now have our answer: you can use <em>lodash/fp/set</em> function as an helper in a <em>react-redux</em> reducer in order to avoid useless code. This is even done by someone from the community whose talent is recognized by lots.</p><h3>Going further ?</h3><p>I won’t detail much here how you can use set to modify an object inside an array. In fact, it is already done in the previous sample. If you want modify several properties in the same time, I believe you can also use <em>lodash/fp/merge</em> or <em>lodash/fp/defaultsDeep</em> to do so.</p><p>Also, I told you previously that <em>lodash/fp/set</em> was able to modify object in an immutable way. This the case. What you also want be sure, is that it will copy only objects that are needed, but will keep references for objects which are not impacted. This is also the case: you are safe, using <em>lodash/fp/set</em> will not lead to useless rendering.</p><p>Another topic which is useful to highlight here is performance. Overall, <em>lodash</em> has great performances. Nevertheless, If this is a really important matter to you, I believe there are way to be faster that <em>lodash</em> here. The immutability around <em>lodash/fp</em> is done as a layer around the initial implementation of <em>lodash</em> methods, here <em>lodash set</em>.This lead to the object traversal being done more than one time: the run-time complexity is bigger than it needs to be. Actually, I created a minimalist implementation of such an immutable set function that will work with only one iteration</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/76d286d69a5e7bbd64ea2a906ded8321/href">https://medium.com/media/76d286d69a5e7bbd64ea2a906ded8321/href</a></iframe><p>I compared this implementation to <em>lodash/fp/set</em>, and despite being very naive, it seems to outperform it, if I believe <a href="https://jsperf.com/lodash-fp-set-vs-custom">this jsPerf test</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*LEoQfGhLvukbAGlYAe3C2Q.png" /><figcaption>jsPerf results of lodash/fp/set vs the naive implementation shown previously, transpiled with babel</figcaption></figure><p>This make me think that there is a room for creating a library dedicated to this use case and more. The closest I found so far is <a href="https://github.com/nosovsh/reduceless"><em>reduceless</em></a>, which is more a wrapper around the store so you don’t have to write reducer, but for different reasons, I would not recommend it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0b1b1eff3d2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/a-small-trick-to-write-clean-reducers-a0b1b1eff3d2">A small trick to write clean reducers</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to map a Map]]></title>
            <link>https://medium.com/hackernoon/how-to-map-a-map-12c6ef1c5b2e?source=rss-958052064161------2</link>
            <guid isPermaLink="false">https://medium.com/p/12c6ef1c5b2e</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[es6]]></category>
            <category><![CDATA[arrays]]></category>
            <category><![CDATA[maps]]></category>
            <dc:creator><![CDATA[Maxence Dalmais]]></dc:creator>
            <pubDate>Mon, 19 Dec 2016 14:08:30 GMT</pubDate>
            <atom:updated>2017-07-30T11:06:41.904Z</atom:updated>
            <content:encoded><![CDATA[<p>2016 comes to an end, and ES6 is everywhere. But with ES6, came some new syntax and APIs. This article aims to answer to a very specific question : How to map a Map into an array ?</p><blockquote><em>tl;dr</em>: Just use Array.from(map, ([key, value]) =&gt; value)</blockquote><p>If you are reading this, it means that you are interested in a more complete answer. To be clear, we are talking here about the JavaScript <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map">Map</a> type. Instances of Map don’t provide a map methods. This article is about ways to implement one.</p><p>Still interested ? If so, we will first discuss about the need to do so, and mainly why you might prefer using a Map instead of a regular Object.</p><p>Then, we will discuss about different ways to do this mapping.</p><h3>Map vs Object</h3><blockquote>Before going further, let’s try to answer a simple question : Why would anyone use Map in JavaScript ?</blockquote><p>Coming from another language, such as say <em>Java,</em> using <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map">Map</a> seems pretty obvious. But what if you come from a pre-ES6 world ? Any reason to use Map over Object ?</p><p>To be clear, I am not advocating in using Map everywhere. As always, it is the developer choice to decide what match best the current situation. To help you decide, I will list here few points for which you might prefer use Map instead of a plain Object.</p><h4>Typed keys</h4><blockquote>Short Version : You can use any type as key for Map. You shall not use Object or Array, or any complex type properties of Other Object. Probably a better idea to use only string.</blockquote><p>A regular JavaScript object, simply created with{} , is very flexible. For each keys, you can assign it any of other JavaScript types :</p><pre>const obj = {}; <br>obj.first = ‘myvalue’;<br>obj.arr = [];<br>obj.number = 2;<br>obj.deep = {};<br>obj.map = new Map();</pre><p>Moreover, despite what you can read in some places, you can add some dynamic keys to your object :</p><pre>const mykey = &#39;foo&#39; + Math.random();<br>const obj = {};<br>obj[mykey] = &#39;bar&#39;;</pre><p>Or even, using the new ES6 computed property syntax :</p><pre>const mykey = &#39;foo&#39; + Math.random();</pre><pre>const obj = {<br>  [mykey]: &#39;bar&#39;<br>}</pre><p>The last three examples should proved you that regular JS object are very flexible. Still there is major difference :</p><blockquote>Whereas Map can have keys of any type, keys from a JavaScript Object will be converted as String</blockquote><p>This difference might be subtitle, but might lead to interesting bugs when not understood correctly</p><pre>const map = new Map();<br>map.set(2, &#39;two&#39;);<br>map.set(&#39;2&#39;, &#39;TWO&#39;);<br>// Map {2 =&gt; &quot;two&quot;, &quot;2&quot; =&gt; &quot;TWO&quot;}</pre><pre>const obj = {};<br>obj[2] = &#39;two&#39;;<br>obj[&#39;2&#39;] = &#39;TWO&#39;;<br>obj;<br>// Object {2: &quot;TWO&quot;}</pre><p>In that case, both behavior can be useful depending of the context, but now, lets try to guess what would happen if you try to assign an object :</p><pre>const obj = {}<br>const key1 = { id: &#39;foo&#39; }<br>const key2 = { id: &#39;bar&#39; }</pre><pre>obj[key1] = &#39;KEY1&#39;;<br>obj[key2] = &#39;KEY2&#39;;</pre><pre>obj[key1];<br>// KEY2&quot;</pre><p>In the previous example, you assign to an object two different values to attributes provided by an object, but when you try to access the value of the first attribute, you get the value of the second. This might seem weird, but should be logical if you read carefully so far. As said before, object properties are converted to String before begin used. One could imagine, that the conversion is done using `JSON.stringify` or something similar, but the truth is much more simple: we simply do `new String(prop).toString()`</p><pre>String(key1).toString() <br>// &quot;[object Object]&quot;</pre><pre>String(key2).toString() <br>// &quot;[object Object]&quot;</pre><pre>new String(key1).toString() === new String(key2).toString()</pre><p>Given the previous example, it is now easy to understand why using complex types, such as Object, Arrays, or Map as a property name is not a good idea. As said, you could use a serialization layer before accessing your property, but this would give you a different behavior from map, if your key object is modified between the assignation and the access.</p><h3>Built-in Methods and attribute</h3><p>We have seen previously that if you need to use complex keys as properties names, you better use Map. But there are more reason it. One of them if the availability of built-in methods.</p><p>The most useful built-in attribute of the Map object is probably the size . It probably does not need further explanation, and simply return the current number of elements being in the map. It is probably pretty obvious why would someone prefer do map.size instead of Object.keys(obj).length .</p><p>Others instance methods, such as map.keys(), map.values() and map.entries() , are also very similar to what we could get with the corresponding static Object methods, but have a major difference: they return Iterators and not Arrays. I will not get into the details here, but I’ll come back to it in the second part of this article.</p><p>Finally, another method is provided as an helper function, which is the map.has(key) , and corresponding to the obj.hasOwnProperty(key) method.</p><p>Some more methods are available for Map. Details for most of them to be provided in the next section.</p><h3>Using it has a shared references</h3><p>Beside the Complex Object as Key feature, one of the reason to use a Map, would be to use it as a shared references across object, in a pure POO style.</p><p>This Map can be a Singleton, or simply shared across instances, but can be modified by them. This is here in total opposition with the everything Immutable trends of the JavaScript world, but again, everything is a matter of context.</p><p>Coming for the POO world, the map.get and map.set will feel very natural. Moreover, in the pure CRUD style, you probably want be able to remove a element from the map. Here you can just use the map.delete method, which you have to admit, feels much less hacky than delete obj.key</p><p>Finally, you also have the map.clear method, which allow you to reset your Map to the empty state.</p><h3>Iteration</h3><p>One of the most popular features of the Map object are the iteration features. Indeed, Map is coming with his new pal, the new for...of syntax.</p><p>The for...of syntax allow you to write code such as :</p><pre>let iterable = new Map([[&quot;a&quot;, 1], [&quot;b&quot;, 2], [&quot;c&quot;, 3]]);<br><br>for (let entry of iterable) {<br>  console.log(entry);<br>}<br>// [a, 1]<br>// [b, 2]<br>// [c, 3]<br><br>for (let [key, value] of iterable) {<br>  console.log(value);<br>}<br>// 1<br>// 2<br>// 3</pre><blockquote>Extracted from <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/for...of#Iterating_over_a_Map">https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/for...of#Iterating_over_a_Map</a></blockquote><p>Personally, I am not a big fan of those C style iterations, and prefer using higher order functions. Looks like I am not the only one, as this is also part of the famous <a href="https://github.com/airbnb/javascript#iterators--nope">Airbnb styleguide</a>.</p><h3>Different ways of Mapping a Map</h3><p>No we got the basic of Map, we will now attempt to solve the initial question</p><h4>for…of</h4><p>If you liked the for...of syntax, you are probably not into the functional approach nor with the immutable one. If so, then you might just want use the following syntax to map a Map.</p><pre>const iterable = new Map([[&quot;a&quot;, 1], [&quot;b&quot;, 2], [&quot;c&quot;, 3]]);</pre><pre>const squareValues = [];</pre><pre>for (let [key, value] of iterable) {<br>  squareValues.push(value * value);<br>}<br>squareValues;<br>// [1, 4, 9]</pre><blockquote>I would be really sad if you do so, since the goal of this whole article was for you to avoid using this syntax.</blockquote><p>We have not described it before, but this syntax is possible because the Map is an Iterable object — such are the return of map.keys() and map.values().</p><h4>forEach</h4><p>On top of Map instance methods already described, there is another one that was not discussed so far: map.forEach</p><p>The forEach method provided here is really similar to the forEach method provided by arrays. Using the same syntax as you would do for Array, it is pretty easy to implement a map method.</p><pre><strong>const</strong> mapMap <strong>=</strong> <strong>function</strong>(map, mapFunction){<br><br>  <strong>const</strong> toReturn <strong>=</strong> [];<br>  map.forEach(<strong>function</strong>(value, key){ // be careful to the args order<br>    toReturn.push(mapFunction(value, key));<br>  })<br><br>  <strong>return</strong> toReturn;<br>}</pre><p>Using this syntax feels ok to me, but still show a loop and the mutation of the toReturn array. This would be ok in a utils files, but we probably don’t want pollute our code with this everywhere. The syntax I would aim for would be a pure native functional one .</p><h4>Array.from</h4><p>We recently discussed the fact the map method that we are aiming for is available on Array. Maybe a good solution would be to implement our Map to an Array is order to call the map method. Moreover, we also described that the Map is an Iterable.</p><p>Also since the ES6 specification, new static methods are now available on Array. One of them is theArray.from method. It allows to duplicate an an Array, convert an Array like object to an array, and also, convert an Iterable to an Array.</p><p>One can now write something like :</p><pre>Array.from(p).map( ([key, value]) =&gt; value * value )</pre><p>I think this start to feel pretty good. We are converting our Map to an Array, and then applying a map on top. What else could we wish ? Do this is in only one operation ? Good news, this is possible.</p><p>Indeed, the Array.from method can be called with a second optional argument, corresponding to a mapping method.</p><p>We can then do :</p><pre>Array.from(p, ([key, value]) =&gt; value * value)</pre><p>This is to me the best way to answer the initial question: ‘How to map a Map in`</p><h3>Conclusion</h3><p>There is sometimes where using a Map instead of an Object really make sense. When the case, there is still sometimes the need to apply a map method to transform a Map into a array of transformed object. When doing so, the best method to me is using the Array.from method with two parameters, one for the map, the second one for a mapping function.</p><blockquote><a href="http://bit.ly/Hackernoon">Hacker Noon</a> is how hackers start their afternoons. We’re a part of the <a href="http://bit.ly/atAMIatAMI">@AMI</a>family. We are now <a href="http://bit.ly/hackernoonsubmission">accepting submissions</a> and happy to <a href="/service/mailto:partners@amipublications.com">discuss advertising &amp;sponsorship</a> opportunities.</blockquote><blockquote>To learn more, <a href="https://goo.gl/4ofytp">read our about page</a>, <a href="http://bit.ly/HackernoonFB">like/message us on Facebook</a>, or simply, <a href="https://goo.gl/k7XYbx">tweet/DM @HackerNoon.</a></blockquote><blockquote>If you enjoyed this story, we recommend reading our <a href="http://bit.ly/hackernoonlatestt">latest tech stories</a> and <a href="https://hackernoon.com/trending">trending tech stories</a>. Until next time, don’t take the realities of the world for granted!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12c6ef1c5b2e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/how-to-map-a-map-12c6ef1c5b2e">How to map a Map</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>