<?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 Kaylie Kwon on Medium]]></title>
        <description><![CDATA[Stories by Kaylie Kwon on Medium]]></description>
        <link>https://medium.com/@kayliealexa?source=rss-f9126b883e80------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uuzfrwSn9GXKS3z43T2rZw.jpeg</url>
            <title>Stories by Kaylie Kwon on Medium</title>
            <link>https://medium.com/@kayliealexa?source=rss-f9126b883e80------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 14:45:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kayliealexa/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[Visualizing the Stock Market Using D3]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://javascript.plainenglish.io/visualizing-the-stock-market-using-d3-c99e349506e7?source=rss-f9126b883e80------2"><img src="https://cdn-images-1.medium.com/max/1882/1*UF-IHcEVXeAaRWlregdqkg.png" width="1882"></a></p><p class="medium-feed-snippet">Zoom trades places with Boeing.</p><p class="medium-feed-link"><a href="https://javascript.plainenglish.io/visualizing-the-stock-market-using-d3-c99e349506e7?source=rss-f9126b883e80------2">Continue reading on JavaScript in Plain English »</a></p></div>]]></description>
            <link>https://javascript.plainenglish.io/visualizing-the-stock-market-using-d3-c99e349506e7?source=rss-f9126b883e80------2</link>
            <guid isPermaLink="false">https://medium.com/p/c99e349506e7</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[d3js]]></category>
            <category><![CDATA[stock-market]]></category>
            <dc:creator><![CDATA[Kaylie Kwon]]></dc:creator>
            <pubDate>Fri, 01 Jan 2021 10:19:26 GMT</pubDate>
            <atom:updated>2021-01-01T10:19:26.690Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Applying CSS Transitions with React Hooks]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://javascript.plainenglish.io/applying-css-transitions-with-react-hooks-7bd84671bc6b?source=rss-f9126b883e80------2"><img src="https://cdn-images-1.medium.com/max/2600/0*yS8yvWY8piRHKRXQ" width="5752"></a></p><p class="medium-feed-snippet">No libraries required</p><p class="medium-feed-link"><a href="https://javascript.plainenglish.io/applying-css-transitions-with-react-hooks-7bd84671bc6b?source=rss-f9126b883e80------2">Continue reading on JavaScript in Plain English »</a></p></div>]]></description>
            <link>https://javascript.plainenglish.io/applying-css-transitions-with-react-hooks-7bd84671bc6b?source=rss-f9126b883e80------2</link>
            <guid isPermaLink="false">https://medium.com/p/7bd84671bc6b</guid>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Kaylie Kwon]]></dc:creator>
            <pubDate>Thu, 22 Oct 2020 17:09:54 GMT</pubDate>
            <atom:updated>2020-10-22T17:09:54.302Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[5 Advanced VSCode Snippets for JavaScript + React Autocompletion]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://javascript.plainenglish.io/5-advanced-vscode-snippets-for-javascript-react-autocompletion-21aa6c5688aa?source=rss-f9126b883e80------2"><img src="https://cdn-images-1.medium.com/max/2600/0*i0zxQkLuELkbyaJX" width="6016"></a></p><p class="medium-feed-snippet">A better way to copypasta &#x1F35D;</p><p class="medium-feed-link"><a href="https://javascript.plainenglish.io/5-advanced-vscode-snippets-for-javascript-react-autocompletion-21aa6c5688aa?source=rss-f9126b883e80------2">Continue reading on JavaScript in Plain English »</a></p></div>]]></description>
            <link>https://javascript.plainenglish.io/5-advanced-vscode-snippets-for-javascript-react-autocompletion-21aa6c5688aa?source=rss-f9126b883e80------2</link>
            <guid isPermaLink="false">https://medium.com/p/21aa6c5688aa</guid>
            <category><![CDATA[vscode]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Kaylie Kwon]]></dc:creator>
            <pubDate>Mon, 28 Sep 2020 07:23:33 GMT</pubDate>
            <atom:updated>2020-09-28T07:23:33.495Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why You Should Avoid Abstract Classes in Typescript]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://javascript.plainenglish.io/why-you-should-avoid-abstract-classes-in-typescript-bcbdd3a87db6?source=rss-f9126b883e80------2"><img src="https://cdn-images-1.medium.com/max/2600/0*iZk_ocHOLdltGl1W" width="4305"></a></p><p class="medium-feed-snippet">The benefits of code sharing are often overestimated</p><p class="medium-feed-link"><a href="https://javascript.plainenglish.io/why-you-should-avoid-abstract-classes-in-typescript-bcbdd3a87db6?source=rss-f9126b883e80------2">Continue reading on JavaScript in Plain English »</a></p></div>]]></description>
            <link>https://javascript.plainenglish.io/why-you-should-avoid-abstract-classes-in-typescript-bcbdd3a87db6?source=rss-f9126b883e80------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcbdd3a87db6</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Kaylie Kwon]]></dc:creator>
            <pubDate>Sun, 09 Aug 2020 07:43:31 GMT</pubDate>
            <atom:updated>2020-08-09T07:43:31.728Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[3 Ways to Improve Type Safety in Jest Tests]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://javascript.plainenglish.io/3-ways-to-improve-type-safety-in-jest-tests-42957a362668?source=rss-f9126b883e80------2"><img src="https://cdn-images-1.medium.com/max/2600/0*tHO89ZHB_gcb2PA5" width="5184"></a></p><p class="medium-feed-snippet">Avoid direct type assertions and ts-ignore comments</p><p class="medium-feed-link"><a href="https://javascript.plainenglish.io/3-ways-to-improve-type-safety-in-jest-tests-42957a362668?source=rss-f9126b883e80------2">Continue reading on JavaScript in Plain English »</a></p></div>]]></description>
            <link>https://javascript.plainenglish.io/3-ways-to-improve-type-safety-in-jest-tests-42957a362668?source=rss-f9126b883e80------2</link>
            <guid isPermaLink="false">https://medium.com/p/42957a362668</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[jest]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Kaylie Kwon]]></dc:creator>
            <pubDate>Mon, 18 May 2020 06:18:31 GMT</pubDate>
            <atom:updated>2020-05-18T06:18:31.632Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Start Using ES2020 Features with React]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://codeburst.io/start-using-es2020-features-with-react-b677c81a4b09?source=rss-f9126b883e80------2"><img src="https://cdn-images-1.medium.com/max/1350/1*o7k7uzC90jx9xjpNAhbGxw.png" width="1350"></a></p><p class="medium-feed-snippet">tldr&#x200A;&#x2014;&#x200A;write less, express more</p><p class="medium-feed-link"><a href="https://codeburst.io/start-using-es2020-features-with-react-b677c81a4b09?source=rss-f9126b883e80------2">Continue reading on codeburst »</a></p></div>]]></description>
            <link>https://codeburst.io/start-using-es2020-features-with-react-b677c81a4b09?source=rss-f9126b883e80------2</link>
            <guid isPermaLink="false">https://medium.com/p/b677c81a4b09</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Kaylie Kwon]]></dc:creator>
            <pubDate>Wed, 15 Jan 2020 01:25:14 GMT</pubDate>
            <atom:updated>2020-01-15T16:35:02.794Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[4 Things I Learned from Reading Effective Typescript]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://javascript.plainenglish.io/4-things-i-learned-from-reading-effective-typescript-59bc5e517f31?source=rss-f9126b883e80------2"><img src="https://cdn-images-1.medium.com/max/2600/0*mK87bpn18D_aq_vb" width="3537"></a></p><p class="medium-feed-snippet">Few days ago, I finished reading Dan Vanderkam&#x2019;s Effective Typescript over a long flight (8 hours to be exact!). The book is concisely&#x2026;</p><p class="medium-feed-link"><a href="https://javascript.plainenglish.io/4-things-i-learned-from-reading-effective-typescript-59bc5e517f31?source=rss-f9126b883e80------2">Continue reading on JavaScript in Plain English »</a></p></div>]]></description>
            <link>https://javascript.plainenglish.io/4-things-i-learned-from-reading-effective-typescript-59bc5e517f31?source=rss-f9126b883e80------2</link>
            <guid isPermaLink="false">https://medium.com/p/59bc5e517f31</guid>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Kaylie Kwon]]></dc:creator>
            <pubDate>Fri, 03 Jan 2020 19:01:41 GMT</pubDate>
            <atom:updated>2022-03-31T17:49:58.133Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Cost  of Getting It Right]]></title>
            <link>https://levelup.gitconnected.com/the-cost-of-getting-it-right-ae5a87a20160?source=rss-f9126b883e80------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae5a87a20160</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[javascript-frameworks]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Kaylie Kwon]]></dc:creator>
            <pubDate>Tue, 17 Dec 2019 15:50:54 GMT</pubDate>
            <atom:updated>2020-01-05T17:22:06.507Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Cost of Getting It Right</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O53TIaIVR0p0_yutCVPlxA.jpeg" /></figure><p><em>“Am I doing this right?”</em></p><p>The question comes up because right <em>feels</em> good, and that means I <em>am</em> good.</p><p>As a software developer, being right for me has been somewhat narrowly defined in terms of efficiency, as in algorithmically better for machines or ergonomically better for developers. It took me a while to realize that getting the right technical solution is just one part of the tradeoff equation. In this article, I try to list examples from the cost side and tips that helped me minimize them.</p><h4>Cost of discussion</h4><p>An architectural change can sometimes mean a change that takes months to discuss and deliver but has no immediate benefit to the user. While it’s true that better features can be built on top of framework level changes, every engineer in the meeting room has an opportunity cost of not working on something that has immediate user impact. As a community, we tend to poke fun at bike shedding in a playful “engineers being engineers” kind of way, but it also carries actual financial costs, as well as diminishing returns.</p><p><em>Tip</em>: S<em>et the meeting agenda with specific decision goals and a time box for each, so that the time limit acts both as an estimate for magnitude of the problem, as well as a forcing mechanism for decision-making.</em></p><h4><strong>Cost of adoption</strong></h4><p>Switching to a new framework doesn’t mean everyone will immediately jump on board to start using it. I used to think, “<em>but how can you not try this cool new XYZ??!</em>” To a large group of engineers, migrating and upgrading to the latest thing is a hindrance to their daily work unless the benefits and usage are clearly communicated. There is less glamorous but critical work of writing documentation, evangelizing, educating, and supporting those to leverage the full impact of the work that was done. Otherwise, it’s just a piece of code no one else understands!</p><p><em>Tip</em>: <em>Provide estimates for adoption, and track tasks such as writing documentation and sharing knowledge with the larger group. Pair programming is also a great way to get more adopters and get work done at the same time.</em></p><h4>Cost of complexity</h4><p>Adding a feature, even if it’s a one liner change, is not without costs. Maintenance comes with a long tail of backwards compatibility and support. Every line of indirection and configuration adds to the developers’ mental overhead. As the codebase also grows in size, it can also experience performance issues with build times, CI, and deployment.</p><p><em>Tip</em>: <em>Have a metric that acts as a proxy for complexity. Maybe it’s tracking build times or introducing tooling for static code analysis. Even if it’s a bulleted list of frustrations, documenting the source of the problem with hard data can justify allocating resources to cleaning up existing tech debt or choosing an alternative approach that prevents adding further complexity.</em></p><h4>Cost of inclusion</h4><p>In many tech companies, I’ve seen diversity lacking in teams responsible for architecture. In practice, it matters who proposes and supports ideas. Sometimes that authority comes from the person’s position in the company or community, and other times it’s influenced by factors such as gender, age, race, and education. When the direction of the code base is constantly shaped by the same voices in the room, not only do stereotypes get reinforced, but the proposed solutions can also start to mirror personal familiarity or preference towards an existing paradigm, regardless of whether they solve the problems others face.</p><p><em>Tip</em>: <em>When evaluating tradeoffs, surface potential biases and discuss with the group whether it can have an effect on the proposal. Avoid using language like “it feels natural” or “it just feels right.” Try to solicit feedback from all levels of engineering, not just senior engineers. I don’t think there’s a single solution to solving inclusion problems in an organization, but honest communication is a good place to start.</em></p><h4>Cost of getting it wrong</h4><p>It’s not fun to think about all the ways our code can be wrong. Sometimes we don’t even know if we did the right thing until we implement it. A better way to consider this might be thinking of it in terms of switching costs. There is value in choosing a solution that allows you to revert and pursue the alternative approach.</p><p><em>Tip: When it comes to tasks with low switching costs, prioritize initial implementation and iteration over driving consensus. Get feedback early and often, instead of trying to get it perfect the first time.</em></p><p>I hope that this article helps broaden the perspective on engineering tradeoffs. If you have any suggestions or feedback, I’m @kaylie_alexa on Twitter.</p><p>Also, thanks to <a href="https://medium.com/u/bc098c4610b7">Ben Ilegbodu</a> and <a href="https://medium.com/u/8b775d508257">Maria Kazandjieva</a> for ideas and suggestions!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae5a87a20160" width="1" height="1" alt=""><hr><p><a href="https://levelup.gitconnected.com/the-cost-of-getting-it-right-ae5a87a20160">The Cost  of Getting It Right</a> was originally published in <a href="https://levelup.gitconnected.com/">Level Up Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dining with Strangers]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/the-bold-italic/communal-dining-in-san-francisco-5b25fee61328?source=rss-f9126b883e80------2"><img src="https://cdn-images-1.medium.com/max/880/0*x_-77pUHUNeAU6x8.jpg" width="880"></a></p><p class="medium-feed-snippet">Eating fish semen together can really bond people</p><p class="medium-feed-link"><a href="https://medium.com/the-bold-italic/communal-dining-in-san-francisco-5b25fee61328?source=rss-f9126b883e80------2">Continue reading on The Bold Italic »</a></p></div>]]></description>
            <link>https://medium.com/the-bold-italic/communal-dining-in-san-francisco-5b25fee61328?source=rss-f9126b883e80------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b25fee61328</guid>
            <category><![CDATA[san-francisco]]></category>
            <category><![CDATA[this-just-in]]></category>
            <category><![CDATA[restaurant]]></category>
            <category><![CDATA[foodies]]></category>
            <category><![CDATA[food]]></category>
            <dc:creator><![CDATA[Kaylie Kwon]]></dc:creator>
            <pubDate>Wed, 05 Sep 2018 16:31:01 GMT</pubDate>
            <atom:updated>2018-09-05T19:56:30.025Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Yarn Workspaces + CRA + Now = Fullstack React ❤️]]></title>
            <link>https://medium.com/@kayliealexa/yarn-workspaces-cra-now-fullstack-react-%EF%B8%8F-35bcb9229f79?source=rss-f9126b883e80------2</link>
            <guid isPermaLink="false">https://medium.com/p/35bcb9229f79</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[yarn]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[now]]></category>
            <dc:creator><![CDATA[Kaylie Kwon]]></dc:creator>
            <pubDate>Thu, 26 Apr 2018 21:55:51 GMT</pubDate>
            <atom:updated>2018-04-27T07:24:25.911Z</atom:updated>
            <content:encoded><![CDATA[<p>Create React App (CRA) has given us a quick and easy way to get our app bootstrapped and running on the frontend. However, what if you want to build a scalable full-stack web application with real APIs (node server) and multiple frontend apps interacting with them?</p><blockquote>tldr;</blockquote><blockquote>You’ll be creating a mono-repo using yarn workspaces and create-react-app</blockquote><blockquote>In development, you’ll be running two servers — 1) CRA’s webpack dev server, which will proxy the requests to the 2) express server, which provides the apis.</blockquote><blockquote>In production, you’ll be running the express server that statically serves the built app, in addition to handling api requests</blockquote><p>By the end of the tutorial, your project will resemble a folder structure like below.</p><pre>server.js<br>packages/<br>  my-app<br>    build/<br>    public/<br>    src/<br>    package.json<br>package.json<br>yarn.lock</pre><h4>Let’s get started!</h4><p><em>*Prerequisites: You need npm 5.2.0 or higher to use npx (or you can download it separately), Yarn &gt; 1.5.0, and </em><a href="https://zeit.co/now"><em>Zeit’s Now</em></a><em> account</em></p><pre>yarn init -y<br>yarn add nodemon now express<br>mkdir packages &amp;&amp; touch server.js</pre><h4>1. Create a simple express server with an endpoint</h4><pre>// server.js</pre><pre>const path = require(&#39;path&#39;);<br>const express = require(&#39;express&#39;);</pre><pre>const port = process.env.PORT || 8080;<br>const app = express();</pre><pre>app.get(&#39;/api&#39;, (req, res) =&gt; {<br>   res.send(JSON.stringify({ &#39;name&#39;: &#39;Kaylie&#39; }));<br>});</pre><h4>2. Update your root package.json with workspaces and new scripts</h4><pre>{<br>  &quot;workspaces&quot;: {<br>    &quot;packages&quot;: [&quot;packages/**&quot;],<br>    &quot;nohoist&quot;: [&quot;**/react-scripts&quot;, &quot;**/react-scripts/**&quot;]<br>  },<br>  &quot;scripts&quot;: {<br>    &quot;bootstrap&quot;: &quot;cd packages &amp;&amp; npx create-react-app&quot;<br>    &quot;deploy&quot;: &quot;now&quot;,<br>    &quot;start&quot;: &quot;nodemon server.js&quot;,<br>    &quot;now-start&quot;: &quot;node server.js&quot;<br>  }<br>}</pre><blockquote><strong>start </strong>command will be used for local development because nodemon will do helpful things like restarting the server when your app crashes, whereas <strong>now-start </strong>will be used by now to run the node.js server in production.</blockquote><p>Note that for deployment in production, Now uses its own package manager so Yarn features will not be available (it will, however, respect your lockfile).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qbZo2veoYL-amP1yhfRdyg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*d6jI5TOKOwqgSQjGYJZR7A.png" /></figure><h4>3. Start your express server</h4><pre>yarn start</pre><p>Now your first server is up and running, handling any requests that come to `/api` endpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qbZo2veoYL-amP1yhfRdyg.png" /></figure><h4>4. Open a new tab in your terminal, then create your react app</h4><pre>yarn bootstrap [my-app]</pre><h4>5. Update your app’s package.json with a new `proxy` key</h4><pre>// packages/my-app/package.json</pre><pre>{<br>  &quot;proxy&quot;: &quot;http://localhost:8080&quot;<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kx9iGrEV4qyZ6KRlh8X7ag.png" /></figure><h4>6. Start your CRA server</h4><pre>yarn workspace my-app start</pre><p>CRA will now have your browser opened to your new app</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qbZo2veoYL-amP1yhfRdyg.png" /></figure><h4>7. Now you can make API requests in your app!</h4><pre>import React, { Component } from &#39;react&#39;;</pre><pre>class App extends Component {</pre><pre>  state = {<br>     name: &#39;&#39;<br>  }</pre><pre>  componentDidMount() {<br>    fetch(&#39;/api&#39;)<br>       .then(res =&gt; res.json())<br>       .then(({ name }) =&gt; this.setState({ name }))<br>  }</pre><pre>  render() {<br>    const { name } = this.state;</pre><pre>    return (<br>       &lt;div className=&quot;App&quot;&gt;<br>         Hello, {`${name}`}<br>       &lt;/div&gt;<br>    );<br>  }</pre><pre>}</pre><pre>export default App;</pre><p>That’s it! Your development environment is now set up with hot reloading client side code, as well as restarting the server when your server side code changes. Because we have the mono-repo structure, you can also add a second app by running yarn bootstrap again at the root directory (i.e. repeating steps 4–6). This means all your apps can take advantage of the same APIs but you can independently choose which apps to run your CRA webpack dev server.</p><p>Now, let’s finish the setup for deployment.</p><h4>8. Go back to your server.js to set up static path and app route</h4><pre>const path = require(&#39;path&#39;);</pre><pre>const MY_APP_BUILT_DIRECTORY = path.join(__dirname, &#39;packages/my-app/build&#39;);<br>const MY_APP_INDEX = path.join(MY_APP_BUILT_DIRECTORY, &#39;index.html&#39;);</pre><pre>// Make the directory available for serving assets statically<br>app.use(express.static(MY_APP_BUILT_DIRECTORY));</pre><pre>// Define a route for your app<br>app.get(&#39;/my-app&#39;, (req, res) =&gt; {<br>  res.sendFile(MY_APP_INDEX);<br>});</pre><h4>9. Build your production files using CRA’s react-scripts</h4><pre>yarn workspace my-app build</pre><h4>10. Go back to your project root directory and deploy using now</h4><pre>yarn deploy</pre><p>And you’re done!</p><p><strong>To recap, some benefits of this setup are</strong></p><ol><li>Quickly iterate on both backend and frontend code using watch mode</li><li>Share APIs, configurations, and code between multiple apps</li><li>But if needed, independently bootstrap (e.g. non-CRA boilerplate), configure, or publish each app</li></ol><p><strong>We didn’t cover everything, so some next areas to explore are</strong></p><ol><li>Configure environment variables for development and production</li><li>In production, serve static files via CDN</li><li>Enable server side rendering</li><li>Connect to a database</li><li>Set up GraphQL</li></ol><p>Thanks for reading! I’d love any feedback, and if you have any, please reach out to me via Twitter (@kaylie_alexa)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35bcb9229f79" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>