<?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 Talita Gregory on Medium]]></title>
        <description><![CDATA[Stories by Talita Gregory on Medium]]></description>
        <link>https://medium.com/@poxagregory?source=rss-44c00916232c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*APfodpin8M8OSWJOntYSsA.png</url>
            <title>Stories by Talita Gregory on Medium</title>
            <link>https://medium.com/@poxagregory?source=rss-44c00916232c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:24:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@poxagregory/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[What on earth are Closures?]]></title>
            <link>https://medium.com/@poxagregory/what-on-earth-are-closures-bd022c55bd84?source=rss-44c00916232c------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd022c55bd84</guid>
            <category><![CDATA[closure]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[closure-in-javascript]]></category>
            <dc:creator><![CDATA[Talita Gregory]]></dc:creator>
            <pubDate>Wed, 26 Jul 2023 14:23:29 GMT</pubDate>
            <atom:updated>2023-07-26T14:23:29.537Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*Chd32GaXdYoONQnUwnkITA.png" /></figure><p>In the previous post, we explored the Thread of Execution, the Global and Local Memory, and the Call Stack. That should give us enough background information to dive into ✨Closures✨ … So, what on earth are they?</p><p>Accordingly to the Mozilla documentation:</p><blockquote>A closure is the combination of a function bundled together (enclosed) with references to its surrounding state (the lexical environment). In other words, a closure gives you access to an outer function’s scope from an inner function.</blockquote><p>In other words, a function that returns a function gives it the possibility to access and retain the values within its parent scope — notice that the inner function <strong>didn’t get executed but <em>returned</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*kIXGO4rM35ycjAC3J3vMVA.png" /></figure><h3>Wait… What? 🤔</h3><p>Let’s quickly recap what we covered in <a href="https://medium.com/@poxagregory/javascript-behind-the-scenes-tour-338e87c6f3f9">the previous post</a>.</p><p>When a function is executed, it gets added to the <strong>Call Stack</strong>, creating a <strong>Local Context</strong> that holds a <strong>Local Memory</strong> within it. Once the function <em>completes its execution</em>, the context and <em>its memory are promptly deleted</em>.</p><p>However, when a function returns another function — well, the story becomes a <em>bit</em> different 🤔. The function being returned gets to store the lexical environment from its parent, effectively carrying its own local memory along with it. This opens up a world of possibilities!🥳</p><p>I tried to illustrate the execution flow within the gif below 👇</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8_74Rv2X56qpmbjTX3sMqg.gif" /></figure><p>Now, there’s something you must bear in mind 👀. Not everything from the parent scope gets dragged into the closure of local memory. Our trusty <em>JavaScript garbage collector</em> swoops in to save the day, diligently removing anything that the inner function doesn’t use, as you wouldn’t be able to access it anyway — notice how in the gif the constant randomValue fade away from the memory 😉</p><h3>Cool… What can I use them for? 👀</h3><p>Closures can be used for ✨ many things ✨ They are — almost — everywhere!</p><p>Let’s start with <strong>Encapsulation and Data Privacy</strong> as it allow you to create <em>private variables </em>and functions within a scope, encapsulating the data and preventing access to it from outside of that scope.</p><p>We can also use it for creating <strong>Function Factories</strong>, where you can generate and return multiple functions with pre-configured behavior based on the arguments passed to the factory function — the greeting function above👆</p><p>Or it can be used for implementing <strong>Memoization</strong>, which is a technique used to cache the results of expensive function executions with the main goal of improving performance!</p><p>And many others! You see it by yourself! An example of closures being used in a fairly common library is the <a href="https://github.com/mui/material-ui/blob/c3a3413159f9c13421898366cfac41dca49c2371/packages/mui-styles/src/makeStyles/makeStyles.js#L204"><strong>makeStyles</strong></a> function from <strong>Material UI</strong> 😉 or you can also spot it being used within the <a href="https://github.com/lodash/lodash/blob/2da024c3b4f9947a48517639de7560457cd4ec6c/memoize.js#L43"><strong>memoize</strong></a> function from <strong>Lodash</strong>!</p><p>The list doesn’t stop there: React, Redux, Underscore.js, Express.js, JQueryUI… and so on 🎉</p><p>Now that you know what <strong>closures</strong> look like and what are they for, how about trying to spot them around the code bases? 😉 Or implementing your own closure? 🤓</p><p>With ❤️,</p><p>Talita</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd022c55bd84" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Javascript behind-the-scenes tour ]]></title>
            <link>https://medium.com/@poxagregory/javascript-behind-the-scenes-tour-338e87c6f3f9?source=rss-44c00916232c------2</link>
            <guid isPermaLink="false">https://medium.com/p/338e87c6f3f9</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[ecmascript]]></category>
            <category><![CDATA[basics-of-programming]]></category>
            <category><![CDATA[js]]></category>
            <dc:creator><![CDATA[Talita Gregory]]></dc:creator>
            <pubDate>Tue, 25 Jul 2023 19:02:43 GMT</pubDate>
            <atom:updated>2023-07-25T19:05:31.483Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Javascript behind-the-scene tour blog post map of the topics" src="https://cdn-images-1.medium.com/max/1024/1*aSf862wVBH_4sQKK1RKtzQ.png" /></figure><p>Welcome to the fascinating world of JavaScript — a programming language that has been around since 1995 and goes by various names such as JS or ECMAScript. You might have encountered it in your web development journey or heard others talk about it. But have you ever wondered what happens behind the scenes as your code gets executed?</p><p>Let’s explore the intricacies of its single-threaded, interpreted nature and discover how each line of code is processed by the browser’s JavaScript engine. So, get ready as we embark on a voyage that will take us through the Thread of Execution, the Global Memory, the Execution Context, the Local Memory, and finally, to our last destination: the Call Stack. ⛵️</p><p>These concepts are essential to understanding what really happens when you write and execute JavaScript code. So, buckle up, and let’s dive right in!</p><h3>Thread and Context of Execution</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HmlZKcIAUcpRTQdKNPETfw.png" /><figcaption>Code snippet for the Thread Execution and Context example</figcaption></figure><p>As mentioned earlier, JavaScript is a <strong>single-threaded and synchronous language</strong>, meaning it can only perform <strong>one task at a time</strong>, following a specific order of execution from <strong>top to bottom</strong>.</p><p>When the JavaScript engine encounters a script file, it creates an <strong>Execution Context</strong> responsible for handling the transformation and execution of each line of code. This process can be divided into two phases: <strong>Creation</strong> and <strong>Execution</strong></p><p>Within the <strong>Creation</strong> phase, the JavaScript engine will execute the entire source code, create the global execution context, instantiate the <strong>global object </strong>(window in the browser and global in NodeJs), set up the global memory and store <strong>functions</strong> <strong>references </strong>and <strong>values</strong> as <strong><em>undefined</em></strong> when<em> </em>those are declared<em> </em>using the<em> </em><em>var</em> keyword.</p><p>Once the <strong>Execution</strong> phase begins, JavaScript threads its way down the code, processing each line in sequence as it appears. As it progresses, it assigns values to each attribute in memory.📝</p><h3>Global and Local Memory</h3><p>Global memory refers to the memory allocated during the <strong>Creation phase of the Execution Context</strong> mentioned above.👆 As it is <strong>global</strong>, you can access anything stored within it at any time!</p><p>On the other hand, local memory refers to the memory that is related to a local context, such as a function, a class, or a module — anything that instantiates a context 😉. Once the execution of the local context is finished, its memory will be destroyed.</p><p>Using the same code snippet as an example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0eAuWa513MWCQgGLIrTvpw.png" /><figcaption>Code snipped to exemplify the Global vs Local memory</figcaption></figure><p>The values numand squareare stored at a <strong>global level</strong>, while the value resultis stored within the <strong>local memory</strong> of the squarefunction. Once its execution is finished, the memory will be destroyed.</p><h3>Call Stack</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hdBTGzjCdiUrsJ-bhDv9kA.png" /><figcaption>Code snippet for exemplify the Call Stack order</figcaption></figure><p>The <strong>call stack</strong> is how Javascript keeps track of all the contexts and execution orders.</p><p>For this purpose, it uses the principle “last in, first out” — LIFO for the closer friends 😉 — always returning to the bottom of the stack, which is the global context.</p><p>After allocating memory for the num constant and for the add2 and square functions, the code proceeds to allocate memory for output, which is <strong>empty</strong>, and then it invokes square() followed by add2() into the call stack.</p><p>Once the execution of each function is done, it will be removed from the call stack.</p><p>It resembles the <a href="https://shop.mattel.com/products/rock-a-stack-gkw58#:~:text=The%20Fisher%2DPrice%C2%AE%20Rock,that%20make%20fun%20rattle%20sounds!">“Rock-a-Stack”</a> kids&#39; toy but the bottom piece, as the global(), never leaves the stack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*Y3CvjcuN6GQsK8BCiyXAZw.gif" /><figcaption>Call Stack as “Rock-a-Stack” toy — Thank you Axel for the awesome animation 🤗</figcaption></figure><p>The call stack has its own fixed size depending on the system or browser. If the number of contexts exceeds the limit, then a stack overflow error will occur. This often happens with a <strong>recursive function</strong> that lacks a base condition — resulting in the program getting stuck in an <em>infinite </em>creation of contexts being added on top of the stack. 🥹👆</p><h3>Wrapping it up 🥳</h3><p>Even though we don’t realize many of those small things while coding on a daily basis, it’s always good to remember the inner workings of a language — it might help at times when sneaky bugs appear within your code and you have no idea where it comes from. 🥸</p><p>By diving into the Thread of Execution, the Global and Local Memory, and the Call Stack, you gain valuable insights into how your code is processed and executed and I hope I helped you to achieve that “A-ha” moment while reading it. 😊</p><p>As you continue your JavaScript journey, keep exploring these concepts, and don’t hesitate to experiment and apply your knowledge.</p><p>If you would like to learn more about these concepts I would recommend you the following resources:</p><ul><li><a href="https://dev.to/lydiahallie/javascript-visualized-scope-chain-13pd">⚡️⛓JavaScript Visualized: Scope (Chain)</a></li><li><a href="https://dev.to/lydiahallie/javascript-visualized-hoisting-478h">🔥🕺🏼 JavaScript Visualized: Hoisting</a></li><li><a href="https://frontendmasters.com/courses/javascript-hard-parts-v2/">JavaScript: The Hard Parts, v2</a></li></ul><p>Happy coding! 🚀</p><p>Talita</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=338e87c6f3f9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TF is the Compound Component pattern? ]]></title>
            <link>https://medium.com/@poxagregory/tf-is-the-compound-component-pattern-367c45f5a1a7?source=rss-44c00916232c------2</link>
            <guid isPermaLink="false">https://medium.com/p/367c45f5a1a7</guid>
            <category><![CDATA[compound-components]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[patterns]]></category>
            <dc:creator><![CDATA[Talita Gregory]]></dc:creator>
            <pubDate>Mon, 24 Jul 2023 14:51:05 GMT</pubDate>
            <atom:updated>2023-07-24T14:51:05.494Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*ypl3sH9G4kEgNeOWIcc4qg.png" /></figure><p>Back in May 2017, Dan Abramov presented the concept of <strong>Compound Component</strong> patterns during his talk “Beyond React 16” at the React Europe event. It wasn’t the first time it was mentioned, but it marked a significant point of reference for the pattern.</p><p>The concepts presented are rooted in the general idea of ✨composing components to work together seamlessly while maintaining clear boundaries between their responsibilities✨</p><p>In other words: you have two or more components that work together to accomplish a useful task, with one component acting as the parent and the others as its children, all while preserving readability.</p><p>You might have spotted this pattern here and there while reviewing some code or diving into repositories, but in case you are not sure <a href="https://github.com/backstage/backstage">Backstage</a> uses it in many different places, such as the <a href="https://github.com/backstage/backstage/blob/bdb004c8ad04efcb2501ad4152d521c134a9125a/packages/core-components/src/components/TabbedLayout/TabbedLayout.tsx#L86">TabbedLayout</a> or the <a href="https://github.com/backstage/backstage/blob/d3f5d6c8e0b775b7d7c835026ba54d6013f44039/packages/app/src/components/catalog/EntityPage.tsx#L4">EntitySwitch</a>.</p><h3>But enough talking, let’s dig in 👷</h3><p>As a Frontend developer, you might have encountered this “problem” in many different ways. How many times did you build up a <strong>component</strong> that, a few days later, you had to adjust to fit an edge case?</p><p>For example, a classic Card component where you started with just the prop title and description?</p><p>Then, a few days later, it gets a button added to its bottom and a subheader for situations where we need to be more descriptive…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p3Unybo-bqYWasWXenGlJw.png" /><figcaption>Card Component</figcaption></figure><p>For now, it’s looking — kind of — straightforward, with each property rendering accordingly to what it receives.</p><p>Except for the fact that <strong>on this other screen,</strong> the subheader is at the top of the title…</p><p>And we don’t have only <strong>one button</strong> but <strong>many</strong> that are aligned on <strong>top</strong>…</p><p>But overall, the design is the same, so what should we do? Does button become button<strong>s</strong>? Do we add a variant prop?</p><p>Guys, we already have <strong>3 conditions</strong> in our code, and we are about to add more… let’s just follow a different strategy, shall we? 🥹</p><h3>Let’s Compound it up 🎉</h3><p>Compound components can help us in this case by maintaining <strong>consistency</strong> across the design and <strong>providing</strong> the flexibility that we need within all those variations, all while offering a <strong>straightforward API </strong>to work with.</p><p>Looking at the code provided let’s break it down into each element from our Card</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/816/1*aOq-HCsB7KKx3xHto7pKuw.png" /><figcaption>Card component broke down</figcaption></figure><p>Now <em>each part</em> of our Card is separated into its own <strong>component</strong> and is exported as Card.Title, Card.Description, Card.Subheader and so on… Notice that nothing is hidden behind props and is easy to expand! If someday we need a Card.Image, we can just add it without affecting all the previously added components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yPXq7Qzf2rvHZtkg1q5-3g.png" /><figcaption>The many ways that you can build up the Card component</figcaption></figure><p>Now you can structure your Card for almost any situation ahead 😉, you can check out the code in-depth on the linked CodeSandbox 👇</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodesandbox.io%2Fembed%2Fwizardly-shape-j6wlps%3Ffontsize%3D14%26hidenavigation%3D1%26theme%3Ddark&amp;display_name=CodeSandbox&amp;url=https%3A%2F%2Fcodesandbox.io%2Fs%2Fj6wlps&amp;image=https%3A%2F%2Fcodesandbox.io%2Fapi%2Fv1%2Fsandboxes%2Fj6wlps%2Fscreenshot.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codesandbox" width="1000" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/a0d224dabc046327a5e4c39da9e791ca/href">https://medium.com/media/a0d224dabc046327a5e4c39da9e791ca/href</a></iframe><h3>Wrapping up 📝</h3><p>Even though the <strong>Compound Components pattern</strong> is ✨semi-new✨, it can still be applied for a <strong>wide range of use cases</strong>, from simple stateless UI elements like our Card example to more complex situations as presented by Backstage. The key is to identify the overall structure and break it down into more manageable and composable parts - getting a clear API in return 😉</p><p>So, the next time that you find yourself adding numerous conditions and props to fit in different cases, maybe its time to step back and consider a different approach 😊</p><p>With ❤️,</p><p>Talita</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=367c45f5a1a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Advanced London 2021 — My first conference ✨ ever ✨]]></title>
            <link>https://medium.com/dazn-tech/react-advanced-london-2021-my-first-conference-ever-130fdc458cb7?source=rss-44c00916232c------2</link>
            <guid isPermaLink="false">https://medium.com/p/130fdc458cb7</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[advanced-react]]></category>
            <dc:creator><![CDATA[Talita Gregory]]></dc:creator>
            <pubDate>Tue, 16 Nov 2021 12:31:32 GMT</pubDate>
            <atom:updated>2021-11-16T12:31:32.270Z</atom:updated>
            <content:encoded><![CDATA[<h3>React Advanced London 2021 — My first conference ✨ ever ✨</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OXM9zjpr2Kg5gDaJ.jpeg" /></figure><p>For those who weren’t aware, on the 22nd and 25th of October, the <a href="https://reactadvanced.com/">React Advanced</a> conference took place in London, and I, ✨Talita Gregory ✨, had the chance to join my DAZN colleagues to attend this AWESOME experience!</p><p>Before I start, I would like to say that it was the first conference ever in my life! I have always watched talks on YouTube — and wondered how it might feel to be there in person.<br>So if I sound over-excited about just a conference… well, it’s because I am! 😉</p><p>The conference was over 2 days, one hybrid and the other fully remote, with more than 60 speakers from around the world, with talks from adding 3D models into your applications, to Accessibility and to Microfrontends. We also could count on amazing MC’s like <a href="https://twitter.com/elibelly"><strong>Eli Schutze</strong></a>, <a href="https://twitter.com/chatterboxCoder"><strong>Nathaniel Okenwa</strong></a>, <a href="https://twitter.com/mettinparzinski"><strong>Mettin Parzinski</strong></a>,<strong> </strong>and <a href="https://twitter.com/jevakallio"><strong>Jani Eväkallio</strong></a><strong> </strong>that hype up the crowd all the time during the conference, definitely bringing the vibe of those fancy Netflix specials to the place.</p><p>A <strong>BIG </strong>shout out to a colleague from DAZN <a href="https://twitter.com/leimonio"><strong>Konstantinos Leimonis</strong></a>, as he was part of the organization of the event! It was definitely an environment full of awesome people and projects to get inspired 🤩.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*fvSzfnJLWwDbJx3W" /></figure><p>The first day started early, around 8 AM, jumping straight to the talk with <a href="https://twitter.com/NikkitaFTW"><strong>Sara Vieira</strong></a><strong>, </strong>“<a href="https://portal.gitnation.org/contents/from-blender-to-the-web-the-journey-of-a-3d-model">From Blender to the Web, the Journey of a 3D Model</a>”, where she showed all her skills and lack of fear because she live coded everything <strong>while making jokes</strong>.</p><p>It was a super exciting talk where she taught us how to implement a cute 3D model<strong><em> </em></strong>into our frontend application and how to insert some nice animations! If you are interested in stuff like this, I would definitely recommend you watch her talk!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*J0OX9llWG_T19Ci5.jpeg" /></figure><p>Right after that, <a href="https://twitter.com/mweststrate"><strong>Michel Weststrate</strong></a><strong> </strong>— MobX creator — had a chance to show us how he made it possible to render 100K items with 100s of updates/sec in React. It was amazing to see the thought process he used to reach this result.</p><p>If you would like to have a look at this topic, I couldn’t find his talk on the conference recordings yet, but I found him giving the same talk at JavaScript fwdays’21 online conference, which was held on June 5, 2021.<a href="https://www.youtube.com/watch?v=WCs09c1B1Lk&amp;ab_channel=fwdays"> You can check it out here.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*w1SFfZ_0jFEwa1Eu.jpeg" /></figure><p>Then, straight to the <strong>pro track</strong> — yes, we had two tracks on the conference 🚀. We had talks like <strong>“Components, Patterns, and Sh*t it’s hard to deal with” </strong>by <a href="https://twitter.com/cedmax"><strong>Marco Cedaro</strong></a>, <strong>“IaC for React application on AWS written in Typescript” </strong>by <a href="https://github.com/zaqqaz"><strong>Denis Artyuhovich</strong></a> — Principal Engineer at DAZN 😎 — and <strong>“(Easier</strong>) <strong>Interactive Data Visualization in React”</strong> by <a href="https://twitter.com/AnjanaVakil"><strong>Anjana Vaki</strong>l</a>.</p><p>During Denis’s talk, he showed how to use Terraform for automation of infrastructure creation and environment rollout — with a nice introduction for those who don’t have experience with TF yet 😉. We also talked about “what CDK for Terraform is and how we can synthesize TypeScript to Terraform configuration” doing everything step by step. React advanced didn’t release this talk on their channel yet, but if you are anxious like me you can click on <a href="https://youtu.be/RxQ3BoWdwTI">this link</a> over here… 🤫</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vqIf_NFolJzEu0xn.jpeg" /></figure><p>Due to the separate tracks, I couldn’t watch some other talks that were happening at the same time in the other room, which gave me a light <strong>✨</strong>FOMO<strong>✨</strong> feeling, <strong>BUT</strong> happily we already have access to <em>most of</em><strong><em> </em></strong>the presentations on the <a href="https://portal.gitnation.org/events/react-advanced-conference-2021">GitNation portal</a> or the <a href="https://www.youtube.com/c/ReactConferences">React Advanced youtube channel</a>!</p><p>And if you are asking yourself “What is the difference between the tracks?”, “Why did you choose this one over the other one?”, “WHYYYYYYYYYY?”.</p><p>My answer is: I don’t know ¯\_(ツ)_/¯. Both tracks were available on your ticket and they weren’t subject-focused, so in this sense, I couldn’t spot any specific reason for that besides making available more options of talks. So is definitely up to you and your interests which track you will go and you could switch anytime 🤓.</p><h3>📣 Things that you definitely should check out!</h3><ul><li>During the event, they announced the <a href="https://beta.reactjs.org/"><strong>React beta docs</strong></a>, which is React innovating the way that docs are made! I definitely recommend you to check it out, and if you are interested you can give feedback to the community!</li><li>I would also recommend the talk from <a href="https://twitter.com/mxstbr"><strong>Max Stoiber</strong> </a>about <strong>“</strong><a href="https://www.youtube.com/watch?v=zAXG-c_JrkQ&amp;ab_channel=codeSTACKr"><strong>How to Edge Cache GraphQL APIs</strong></a><strong>”</strong> where he did a dive deep into the inner workings of GraphCDN to figure out how to <strong>cache GraphQL</strong>.</li><li><strong>“Micro-frontends Performance and Centralised Data Caching” </strong>is an interesting presentation by <a href="https://twitter.com/Infoxicador"><strong>Ruben Casas</strong></a> where he demonstrated how Micro-frontends can make your applications faster and more resilient while keeping the benefits of independent deployments 😉</li><li>If you are interested in rendering applications asynchronously on the server you <strong>definitely </strong>should check <strong>“Living on the Edge” </strong>where <a href="https://twitter.com/threepointone"><strong>Sunil Pai</strong></a><strong> </strong>walks you through this new model of writing React applications, with insights into the implications for data fetching, styling, and more.</li><li>And last but not least <a href="https://twitter.com/Mappletons"><strong>Maggie Appleton</strong></a> shows React from a different perspective. Instead of a linear text file, in <strong>“Visualising React: Metaphors, Models, and Spatial Mediums” </strong>explore different ways to expand our understanding of how ✨React works✨</li></ul><p>All the talks that I didn’t place a link will eventually become available on the<a href="https://www.youtube.com/c/ReactConferences/videos"> React Advanced YouTube channel</a>!</p><p>Thank you DAZN and <a href="https://medium.com/dazn-tech/developer-experience-dx-at-dazn-e6de9a0208d2">DX team</a> ❤️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=130fdc458cb7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dazn-tech/react-advanced-london-2021-my-first-conference-ever-130fdc458cb7">React Advanced London 2021 — My first conference ✨ ever ✨</a> was originally published in <a href="https://medium.com/dazn-tech">DAZN Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>