<?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 Jawara Gordon on Medium]]></title>
        <description><![CDATA[Stories by Jawara Gordon on Medium]]></description>
        <link>https://medium.com/@jawaragordon?source=rss-d4be0cf41dad------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*sD3LiysBc6jajFhovTcDrA@2x.jpeg</url>
            <title>Stories by Jawara Gordon on Medium</title>
            <link>https://medium.com/@jawaragordon?source=rss-d4be0cf41dad------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 11:50:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jawaragordon/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 Create Websites Your Clients Can Own]]></title>
            <link>https://medium.com/@jawaragordon/how-to-create-websites-your-clients-can-own-6ee4ab05753d?source=rss-d4be0cf41dad------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ee4ab05753d</guid>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[small-busness]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Jawara Gordon]]></dc:creator>
            <pubDate>Mon, 12 May 2025 00:20:57 GMT</pubDate>
            <atom:updated>2025-05-12T09:58:18.851Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0JY9lMe7sobLnbovE2mT-w.png" /></figure><blockquote>“My web development approach is simple, build sites that clients can call their own.”</blockquote><p>That may sound easy but it’s not as simple as it sounds. It took plenty of trial and error before finding a workflow that allowed me to become successful as a solo developer with multiple clients.</p><p>Early in my career, I reached for the tools I was trained on. React, Ruby on Rails, PostgreSQL, the MERN stack, and frameworks like Gatsby or Next.js. These are great choices for teams of developers and clients who may not need constant upkeep. However, these options are so locked down that every minor text change or image update landed back on my to-do list.</p><p>One of my first projects involved transforming a simple GoDaddy Website Builder page for a <a href="https://brotherhoodofmen.org/">nonprofit organization</a> into a custom JavaScript and MySQL solution. I took on the role of SCRUM master with a team of Full Stack developers while jumping in on front-end, back-end, and design tasks as needed. I’m glad to say we shipped the project on time with positive feedback from the organization!</p><p>This worked great at first, but after the team moved on, and after a year of constant updates, something had to give. The site was eventually migrated to WordPress to allow the client to manage content more easily.</p><p>This experience opened my eyes to the problem of using enterprise-level solutions for everyday challenges. I still enjoy working with advanced tools for my personal projects or when I take on larger clients, but I realized that choosing the <em>right</em> tool for the job is more important than choosing the <em>newest</em> one.</p><p>Since then, I started my own web design &amp; development business called <a href="https://staticfreedesigns.com/">Static Free Designs</a> which fills the gap between no-code platforms like Squarespace or Wix, and bespoke solutions that are too costly for the average person to afford.</p><p>This philosophy has allowed me to create the perfect blend of custom code and client-accessible upkeep that’s enabled me to be successful as an army of one.</p><p>This blog series is focused on sharing my approach to web development for solopreneurs. I’ll be using examples from my most recent project to teach you this methodology.</p><p>In this first post, we’ll discuss the importance of discovery conversations, how to create a brand identity, introduce UI/UX principles, draft a contract, and establish a comprehensive timeline to lay a solid foundation for your next big project.</p><p>Let’s get started!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ze0mrszKeCZTzCMI" /><figcaption>Photo by <a href="https://unsplash.com/@bradencollum?utm_source=medium&amp;utm_medium=referral">Braden Collum</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3><strong>Part 1: Client Onboarding &amp; Brand Identity</strong></h3><p>Before writing a single line of code or sketching a wireframe, it’s important to get a good understanding of your client’s expectations.</p><p>I leaned into this strategy when I first spoke with the founder of <a href="https://yanasisters.com/">YANASISTERS</a>— a brand focused on connecting more than 20,000 women from around the world. My goal was to collect data on why this brand exists and who it serves, what the website needed to accomplish, and how to measure success.</p><p>Those early conversations not only informed my design choices but also helped to guide every technical decision along the way.</p><p>I sent her a questionnaire full of onboarding questions, then we discussed her answers during a kick-off call.</p><p><strong>Here’s what we covered:</strong></p><ul><li>Business Description &amp; Mission</li><li>Primary Website Objectives</li><li>Target Audience</li><li>Design Preferences</li><li>E-commerce</li><li>Timeline &amp; Budget</li><li>Success Metrics</li></ul><p>These answers shaped our visual direction and development decisions such as what design tools and tech stack to use. Walking away from this call, I could make confident choices about every color, font, and user interface that would echo her mission statement while speaking directly to the people she wanted to reach. We also decided to use WordPress for this project allowing her to make ongoing updates to the site without needing to hire me for small changes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HYjan2iQgGerdRTA" /><figcaption>Photo by <a href="https://unsplash.com/@nickmorrison?utm_source=medium&amp;utm_medium=referral">Nick Morrison</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Project Management, Timeline &amp; Contract</h3><p>The first step in any successful project is establishing a timeline and contract. This will allow you to clearly define the project scope and set realistic goals for shipping your MVP.</p><p>Take the notes from your discovery call to create an overview of deadlines, and due dates to manage client expectations. You can use whatever project management tools that work for you. I like to use <a href="https://trello.com/">Trello</a> boards, which have all kinds of useful templates to jumpstart this process. Share this timeline with your client and have them sign off before adding this info to an agreement.</p><p>Your contract should include as much detail as possible to ensure that nothing is assumed or gets lost in the mix. Clearly define your role, what you will and will not cover in the project scope, and any resources your client needs to provide.</p><p>I’m not a lawyer and this is not professional advice — but feel free to use this template as a starting point for creating your own agreements:</p><p>⬇️ <a href="https://jawaragordon.com/docs/Web-Developer-Contract-Template%20.pdf">Web Development Contract Template</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5NQuMd1r2FO9OY-YLahOPg.png" /></figure><h3><strong>Building a Brand Identity</strong></h3><p>The next step is to create a brand kit.</p><blockquote>“You can think of a brand kit as a set of assets or toolbox that contains all the aspects of your brand’s visual identity — logos, templates, color palette, font, and other graphics.”</blockquote><blockquote><a href="https://create.microsoft.com/en-us/learn/articles/what-is-a-brand-kit">- microsoft.com</a></blockquote><p>I used Canva as a central location to collect this information since the client was already familiar with this platform. We included her existing logo, a color palette, brand voice, mission statement, tagline, and font options. We also created a mood board with screenshots of design elements for inspiration.</p><h4><strong>Defining A Color Palette</strong></h4><p>We selected colors that reinforced her mission statement and resonated with visitors’ <a href="https://looka.com/blog/colors-and-emotions/">emotions</a>. Knowing that “deeper turquoise” was our primary focus allowed us to refine a color palette that provided contrast without losing warmth. I ended up compromising on some of the accessibility metrics to find that balance but sometimes, you just have to keep the process going!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qw8Nvaemvo6swIRlXaqOlg.png" /></figure><h4><strong>Choosing Typography</strong></h4><p>We continued to build out the brand kit by focusing on typography.</p><blockquote>“‍Typography is the discipline designers use to arrange typefaces in a user interface to ensure text is legible, readable, and scalable. It must also be visually appealing to users. The right typography can enhance a product’s aesthetic, optimize user-friendliness, and contribute to brand perception.”</blockquote><blockquote>- <a href="https://www.interaction-design.org/literature/topics/typography?srsltid=AfmBOoorf-7qNpK6XaYNnlArMFrgjkl9FvSuuqMmlSGSVbwWGNDtxXgM">Interaction Design Foundation</a></blockquote><p>The client didn’t have strong typeface preferences so we tried a few examples until something stuck:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aU1FdARuLUwEUr0NgtimhA.png" /></figure><p>It’s important to choose typography that supports the emotional impact of the brand. Choosing “Comic Sans” for a law office is not going to create much trust. Picking “Times New Roman” for an art center is boring and won’t connect with that audience.</p><p>These may seem like small decisions but they have a huge effect on the overall perception of a brand.</p><p>Spend as much time as it takes to get this part right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IP_QxLTCrNMgeA82GaHi8Q.png" /></figure><h3><strong>UI/UX Design</strong></h3><p>This is the perfect time to introduce UI/UX principles to the development process. Here’s a quick breakdown of what UI/UX means:</p><blockquote>“A user interface (UI) is the part of a website, application, or device you interact with. It includes screens, buttons, toggles, icons, navigation menus, and other visual elements. User experience (UX) refers to your entire interaction with a product, including how you feel about the interaction. “</blockquote><blockquote>- <a href="https://www.coursera.org/articles/ui-vs-ux-design">coursera.org</a></blockquote><p>UI/UX principles run deep and I could write an entire blog series on just this topic. I recommend taking some time to get familiar with the basics before diving into the next steps.</p><p>On a high level, you need to make sure that you’re following guidelines like the “<a href="https://uxdesign.cc/10-usability-heuristics-every-designer-should-know-129b9779ac53">10 Usability Heuristics</a>” when designing products:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CHmRilm2dHXveQKFDDgbvA.jpeg" /></figure><p>This means that you should be thinking of how the end user is going to interact with the website during every part of the development process. Ask yourself these types of questions:</p><ul><li>Will the end user be able to read the font on the labels?</li><li>Is this button going to be large enough for mobile devices?</li><li>Does the application provide feedback to the user such as progress bars and spinners?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LCEft4uTM-_wTLl1bww-xA.png" /></figure><h4><strong>User Personas &amp; Journey Maps</strong></h4><p>You should have a good understanding of the end user based on your discovery call and client questionnaire. This information is important for creating user personas and journey maps that will help guide you through this next phase.</p><p><strong>What is a User Persona?</strong></p><blockquote>“A persona is a <strong>fictional, yet realistic, description of a typical or target user</strong> of the product. A persona is an archetype instead of an actual living human, but personas should be described as if they were real people.” <br>- <a href="https://www.nngroup.com/articles/persona/">Nielsen Norman Group</a></blockquote><p><strong>What is a Journey Map?</strong></p><blockquote>“A user journey map visualizes a customer’s experience. This visualization might cover a customer’s entire relationship with a brand or focus on a select experience they might have while interacting with an app or website. No matter the type, user journey maps serve as a useful tool for understanding user needs and pain points and ultimately optimizing user experience (UX).” <br>— <a href="https://www.coursera.org/articles/creating-user-journey-maps-a-guide">coursera.org</a></blockquote><h4><strong>Creating Personas</strong></h4><p>You should create 2–3 personas that represent the end users of the website you’re building. I like to choose the following persona types:</p><ul><li>An <strong>ideal persona</strong> — the most likely user of this website.</li><li>An <strong>average persona</strong> — someone who’s undecided or new to the website.</li><li>A <strong>less-than-ideal persona</strong> — someone who doesn’t like technology or is using this website as a last resort.</li></ul><p>This allows me to see the website from multiple angles and uncover pros and cons that I wouldn’t find on my own.</p><p>This part is fun for me as someone with an improv background, but you can use LLMs to create mock data for this phase if you’re not feeling creative.</p><p>I like to include the following data for each persona:</p><ul><li><strong>Headshot</strong>: (An avatar of some type.)</li><li><strong>Name</strong>: (An age-appropriate name for this persona.)</li><li><strong>Playlist</strong>: (What music would this person listen to daily?)</li><li><strong>Song</strong>: (What song will I play while I go on their user journey?)</li><li><strong>Device</strong>: (What device will they use the website with?)</li></ul><p><strong>Demographic Information</strong></p><ul><li>What is their age?</li><li>What is their occupation or industry?</li><li>Where are they located?</li><li>What is their level of education?</li></ul><p><strong>Personal Background</strong></p><ul><li>What are their hobbies or interests?</li><li>Describe their family or living situation.</li><li>How do they typically spend their free time?</li></ul><p><strong>Pain Points and Challenges</strong></p><ul><li>What is the biggest problem you want to solve with our website?</li><li>What makes you think that we can solve your problem?</li><li>Why would you choose us over competitors?</li><li>What makes it difficult for you to solve your problem?</li><li>What prevents you from taking action?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uLg5sRfru61DmjvpkGUoKA.png" /></figure><h4>Journey Maps</h4><p>Once you have the personas mapped out you can start to take them through a journey of an existing version of the website, a competitors site, or an imagined finished MVP.</p><p>Platforms like <a href="https://www.canva.com/templates/s/customer-journey-map/">Canva</a> offer tons of free templates to choose from. Find one that best fits your project:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TdJ1WhD5jCzE_7HTYbjecQ.png" /></figure><p>I like to get into the mind of the persona as I journey through these steps by listening to music that this person likes and by using the same type of device they would reach for. You can also change your physical location to match — is this someone who would visit this site from a cafe? Maybe they prefer to browse from their living room couch? Do whatever you can to take on the characteristics of the persona you have in mind!</p><p>With brand identity and UI/UX foundations in place, we’re ready to move on to the design phase. But first, you need to update your project timeline with these finished steps!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7rsu_qmo0ZrRXnuVntvObg.png" /></figure><h3>Sitemap &amp; Design Phase</h3><p>Now that we have a good understanding of what we need to build, we’ll jump into creating a sitemap and interactive wireframes in <a href="https://www.figma.com/downloads/">Figma</a>.</p><p>Whether you’re a designer or not, this phase will move along much more smoothly after investing time in those initial conversations!</p><p>Up Next:</p><p>Part 2: Sitemaps &amp; Interactive Wireframes with Figma</p><h3>Resources</h3><p><a href="https://trello.com/">https://trello.com/</a></p><p><a href="https://jawaragordon.com/docs/Web-Developer-Contract-Template%20.pdf">https://jawaragordon.com/docs/Web-Developer-Contract-Template%20.pdf</a></p><p><a href="https://looka.com/blog/colors-and-emotions/">https://looka.com/blog/colors-and-emotions/</a></p><p><a href="https://www.canva.com/templates/s/customer-journey-map/">https://www.canva.com/templates/s/customer-journey-map/</a></p><p><a href="https://www.figma.com/downloads/">Figma Downloads | Web Design App for Desktops &amp; Mobile</a></p><h3>Sources</h3><p><a href="https://brotherhoodofmen.org/">Home - The Brotherhood of Men | We Are Our Brothers Keeper</a></p><p><a href="https://staticfreedesigns.com/">https://staticfreedesigns.com/</a></p><p><a href="https://yanasisters.com/">Home - yanasisters</a></p><p><a href="https://create.microsoft.com/en-us/learn/articles/what-is-a-brand-kit">https://create.microsoft.com/en-us/learn/articles/what-is-a-brand-kit</a></p><p><a href="https://www.interaction-design.org/literature/topics/typography">https://www.interaction-design.org/literature/topics/typography</a></p><p><a href="https://www.coursera.org/articles/ui-vs-ux-design">https://www.coursera.org/articles/ui-vs-ux-design</a></p><p><a href="https://uxdesign.cc/10-usability-heuristics-every-designer-should-know-129b9779ac53">https://uxdesign.cc/10-usability-heuristics-every-designer-should-know-129b9779ac53</a></p><p><a href="https://www.coursera.org/articles/creating-user-journey-maps-a-guide">https://www.coursera.org/articles/creating-user-journey-maps-a-guide</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ee4ab05753d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JavaScript’s MutationObserver API (Secrets of the Ooze Revealed)]]></title>
            <link>https://medium.com/@jawaragordon/javascripts-mutationobserver-api-secrets-of-the-ooze-revealed-47137719c14b?source=rss-d4be0cf41dad------2</link>
            <guid isPermaLink="false">https://medium.com/p/47137719c14b</guid>
            <category><![CDATA[mutationobserver]]></category>
            <category><![CDATA[dom]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Jawara Gordon]]></dc:creator>
            <pubDate>Sun, 12 Jan 2025 16:16:54 GMT</pubDate>
            <atom:updated>2025-01-13T18:03:55.024Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qegGGUqxW2PUu-lZ4Q1d8w.png" /></figure><blockquote><strong>“First, we must <em>observe</em> the ancient ritual of the… traditional pre-fight donut.” — Leonardo, <em>TMNT 2</em></strong></blockquote><p>One of the most important skills you can develop is the ability to observe your surroundings. Stop for a moment and think about what’s going on around you right now. What can you hear, see and touch?</p><p>Just like a ninja, your web browser has the ability to sense its surroundings. The browser engine is constantly on the lookout for changes, and ready to react at a moment’s notice.</p><p>Have you ever stopped to think about how it can do this? Recently, I took the time to research what’s going on under the hood, and how the browser can communicate these changes to the screen. The secret ooze I found is called JavaScript’s <strong>MutationObserver API</strong>.</p><p>It allows you to watch for changes in the <strong>DOM</strong> (Document Object Model) and respond to them in real-time. This allows developers to create dynamic user experiences and debug issues by keeping an eye out for DOM changes using the observe() method.</p><p>In this article, we’ll explore the basics of MutationObserver, and its benefits, while breaking down the interactive app I made to reveal what’s going on behind the scenes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*6BIxO-aj05JNqCO_tjSDsQ@2x.jpeg" /></figure><h3><strong>What is MutationObserver?</strong></h3><p>The MutationObserver API is a built-in JavaScript feature that allows developers to monitor changes to the DOM.</p><blockquote>“The MutationObserver interface provides the ability to watch for changes being made to the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model">DOM</a> tree. It is designed as a replacement for the older <a href="https://developer.mozilla.org/en-US/docs/Web/API/MutationEvent">Mutation Events</a> feature, which was part of the DOM3 Events specification.” — MDN</blockquote><p>When a change is detected, the MutationObserver triggers a callback function that provides a list of changes for processing. During each observation cycle, changes are represented by MutationRecord objects, which contain info like the type of change and the affected node.</p><p>The API observes specific types of mutations, including:</p><p>• <strong>Child node changes</strong>: When child nodes are added, removed, or rearranged.</p><p>• <strong>Attribute changes</strong>: When the attributes of an element (class, style, id) are modified.</p><p>• <strong>Text content changes</strong>: When the content of a text node is updated.</p><p>MutationObserver is part of a larger JavaScript Observer API family that follows the <strong>Observer design pattern</strong>, where an object (called the subject) manages a list of observers that depend on its state and notifies them of any changes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hlFxdLcUtaIBvMHIeyiNIA.png" /><figcaption>The Observer API family; MutationObserver, IntersectionObserver, ResizeObserver, PerformanceObserver, ReportingObserver, and BroadcastChannel.</figcaption></figure><p><strong>MutationObserver</strong>, introduced in 2012 with the DOM4 specification, was designed to replace the older MutationEvents, which were slow and unreliable. This API provides a modern way to observe changes in the DOM and automatically respond to them.</p><p>I’ve also <a href="https://medium.com/@jawaragordon/making-scroll-effects-with-javascripts-intersection-observer-api-63c19d1b4b1d">written about its cousin<strong> IntersectionObserver</strong></a><strong> </strong>which<strong> </strong>was introduced in 2016 and focuses on detecting when elements enter or exit the viewport. It’s useful for lazy loading, infinite scroll, and view-based animations.</p><p>Together, these Observer APIs give developers the tools to monitor both <em>what</em> changes in the DOM and <em>when</em> elements come into view.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X_LRspaPiJcLwYllw_jcCA.png" /></figure><h3>The Benefits of MutationObserver</h3><p>Now that we’ve covered the technical side of things, let’s look at how the MutationObserver API is used in the real world. It’s more than just a tool for developers — it’s the secret sauce behind many of the interactive features we use on the web every day.</p><p>Here are some classic examples of MutationObserver in the wild:</p><p><strong>Live Chat and Messaging</strong></p><p>Whenever we type in a chat window, we expect new messages to pop up automatically. This experience is often powered by MutationObserver. By observing the message container for changes, MutationObserver can detect new messages, trigger animations, and auto-scroll for you.</p><p><strong>Infinite Scrolling</strong></p><p>Like its cousin IntersectionObserver, MutationObserver can be used with endless scrolling features for social media and e-commerce sites. When you reach the bottom of the page, new content is dynamically loaded and added to the DOM. MutationObserver ensures that the correct styles and event handlers are applied to the fresh content.</p><p><strong>Dynamic Forms</strong></p><p>Have you ever used a form where fields change based on your selections? MutationObserver can observe the form container and mutate the input fields to trigger visuals, add validation feedback, or create new elements based on child node or attribute changes.</p><p><strong>Accessibility</strong></p><p>Having an open and accessible web for everyone has never been more important. A great use case for MutationObserver is to notify screen readers when new elements are added or content is updated in the DOM. A perfect example of this is when MutationObserver notices changes to ARIA attributes and notifies users when new content has been added to the page.</p><p><strong>Debugging</strong></p><p>It can be hard to track which third-party libraries or frameworks are modifying the DOM. MutationObserver can observe mutations and help developers identify issues like memory leaks or unintended behavior by logging changes during runtime.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7ytVoROfdiDx-ZEyUjAyKQ.png" /></figure><h3>MutationObserver in Action</h3><p>With the basics under wraps, it’s time to get hands-on with this API to see how it truly works. The best way for me to learn is by creating interactive apps that force me to read docs, make mistakes, and get as close to the code as possible. That’s exactly what I did with this API and you can try it out yourself by following the link below:</p><p><strong>MutationObserver API App</strong>: <a href="https://mutation-observer.vercel.app/">https://mutation-observer.vercel.app/</a></p><p>Download the repo from <strong>GitHub</strong>: <a href="https://github.com/JawaraGordon/mutation-observer">https://github.com/JawaraGordon/mutation-observer</a></p><p>This app allows you to add, modify, and animate elements in the DOM while observing and logging the changes in real-time. In this next section, I’ll walk you through the codebase to get a deeper understanding of how this app was built so you can start to apply MutationObserver to your own projects.</p><h4><strong>Step 1: Setting Up the Observer</strong></h4><p>The first step is to initialize a new MutationObserver and configure it to watch specific changes in the DOM. This is done using the observe() method, which takes two arguments: the target node and a configuration object.</p><p>For the MutationObserver to work, it needs something to <em>observe</em>. In this app, the observer monitors a &lt;div&gt; with the ID #observable in the index.html file:</p><pre> &lt;div id=&quot;observable&quot;&gt;&lt;/div&gt;</pre><p>The API watches for the following changes:</p><p>• Adding or removing <strong>child elements</strong>.</p><p>• Modifications to <strong>attributes</strong> like class.</p><p>• Updates to <strong>text</strong> content.</p><p>Here’s the script.js code that sets it up:</p><pre>const targetNode = document.getElementById(&#39;observable&#39;);<br><br>const config = {<br>  childList: true,<br>  attributes: true,<br>  subtree: true,<br>  characterData: true<br>  // These extra config options are not used in this app:<br>  //   attributeOldValue: true,<br>  //   characterDataOldValue: true,<br>  //   attributeFilter: [&#39;class&#39;, &#39;id&#39;]<br>};<br><br>// Mutation log target node<br>const activityLog = document.getElementById(&#39;log&#39;);<br><br>// Update the mutation log<br>const logChange = (message) =&gt; {<br>  const logItem = document.createElement(&#39;li&#39;);<br>  logItem.textContent = message;<br>  activityLog.appendChild(logItem);<br><br>  // Show the latest log<br>  activityLog.scrollTop = activityLog.scrollHeight;<br>};<br><br>// Callback function that triggers when mutation is observed<br>const mutationCallbackFunc = (mutationsList, observer) =&gt; {<br>  // Open the console to see MutationRecord objects created by the browser<br>  console.log(mutationsList);<br>  for (const mutation of mutationsList) {<br>    if (mutation.type === &#39;childList&#39;) {<br>      logChange(<br>        `ChildList Mutated: ${mutation.addedNodes.length} added, ${mutation.removedNodes.length} removed.`<br>      );<br>    } else if (mutation.type === &#39;attributes&#39;) {<br>      logChange(`Attribute Mutated: ${mutation.attributeName} modified.`);<br>    } else if (mutation.type === &#39;characterData&#39;) {<br>      logChange(`Text was Mutated: &quot;${mutation.target.textContent}&quot;`);<br>    }<br>  }<br>};<br><br>// Makes an &quot;Observable&quot; instance<br>const observer = new MutationObserver(mutationCallbackFunc);<br><br>// Start the Observer<br>observer.observe(targetNode, config);</pre><p><strong>What’s Happening?</strong></p><p>• The config object specifies what types of changes to observe (childList, attributes, etc.).</p><p>• The mutationCallback function processes the changes and logs them to the console.</p><p>• The observer.observe() method starts the observation on the target node.</p><h4><strong>Step 2: Adding New Elements to the DOM</strong></h4><p>With the observer setup, we can trigger some changes! The app includes a button to add new &lt;p&gt; elements inside the observed &lt;div&gt;.</p><p>Here’s the code for adding elements:</p><pre>document.getElementById(&#39;addElement&#39;).addEventListener(&#39;click&#39;, () =&gt; {<br>  const newElement = document.createElement(&#39;p&#39;);<br>  newElement.textContent = &#39;Some text was added!&#39;;<br>  targetNode.appendChild(newElement);<br>});</pre><p><strong>Try It</strong>: Click the “Add Element” button in the app, and you’ll see the new paragraph appear inside the observed area. Scroll down to view the log. You&#39;ll see that the observer logs the addition of the new node:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JuYoxquRITYQwe04yVdbsA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*Mpn29eRxEUzTiIPAgdVJOA.png" /></figure><h4><strong>Step 3: Changing Text Content</strong></h4><p>Next, let’s modify the text content of the first child node. Doing so will remove the existing node and replace it with another. It will return “No text was found…” if there’s no existing child node.</p><p>This is the code that handles this change:</p><pre>document.getElementById(&#39;changeText&#39;).addEventListener(&#39;click&#39;, () =&gt; {<br>  if (targetNode.firstChild) {<br>    targetNode.firstChild.textContent = &#39;The text has been changed!&#39;;<br>  } else {<br>    logChange(&#39;No text was found...&#39;);<br>  }<br>});</pre><p><strong>Try It</strong>: Click the “Change Text” button, and the text of the first child node gets updated. The observer will log this as a mutation:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*XnNh_ut31JQCE3is8NuvGg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*OW6vgL57Z_STZ2y_nHdjWw.png" /></figure><h4><strong>Step 4: Adding and Removing Attributes</strong></h4><p>The app also allows you to toggle a background color or animation on the observed element by modifying class attributes.</p><p>Here’s the code that handles these changes:</p><pre>// Add and remove attributes<br><br>// Add color<br>document.getElementById(&#39;addColor&#39;).addEventListener(&#39;click&#39;, () =&gt; {<br>  targetNode.classList.add(&#39;colored&#39;);<br>  logChange(&#39;Mutated the color!&#39;);<br>});<br><br>// Remove color<br>document.getElementById(&#39;removeColor&#39;).addEventListener(&#39;click&#39;, () =&gt; {<br>  targetNode.classList.remove(&#39;colored&#39;);<br>  logChange(&#39;Mutated the color back.&#39;);<br>});<br><br>// Start animation<br>document.getElementById(&#39;startAnimation&#39;).addEventListener(&#39;click&#39;, () =&gt; {<br>  targetNode.classList.add(&#39;animated&#39;);<br>  logChange(&#39;Animation started!&#39;);<br>});<br><br>// Stop animation<br>document.getElementById(&#39;stopAnimation&#39;).addEventListener(&#39;click&#39;, () =&gt; {<br>  targetNode.classList.remove(&#39;animated&#39;);<br>  logChange(&#39;Animation stopped.&#39;);<br>});</pre><p><strong>Try It</strong>: Use the “Add Color” and “Remove Color” buttons to toggle a green background. The “Start” and “Stop” buttons will toggle a pulse animation. The observer will log these changes as mutations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nn5_WErvJaMV-pd_crgniQ.gif" /></figure><h4><strong>Step 5: Resetting the DOM</strong></h4><p>Sometimes, you may want to reset the observed area to its initial state. you can do that with the “Reset” button to remove all child nodes and restore the original content. You can also reset the log or toggle when the observer is running:</p><p>Check out the code:</p><pre><br>// Reset mutation demo<br>document.getElementById(&#39;resetBtn&#39;).addEventListener(&#39;click&#39;, () =&gt; {<br>  while (targetNode.firstChild) {<br>    targetNode.removeChild(targetNode.firstChild);<br>  }<br><br>  initialContent.forEach((node) =&gt; {<br>    targetNode.appendChild(node.cloneNode(true));<br>  });<br>});<br><br>// Reset log<br>document.getElementById(&#39;resetLogBtn&#39;).addEventListener(&#39;click&#39;, () =&gt; {<br>  activityLog.replaceChildren();<br>});<br><br>// Toggle Observe on/off<br><br>let isObserving = true;<br><br>document.getElementById(&#39;toggleObserving&#39;).addEventListener(&#39;click&#39;, () =&gt; {<br>  if (isObserving) {<br>    observer.disconnect();<br>    logChange(&#39;Observation stopped.&#39;);<br>  } else {<br>    observer.observe(targetNode, config);<br>    logChange(&#39;Observation started.&#39;);<br>  }<br>  isObserving = !isObserving;<br>});</pre><p><strong>Try It</strong>: Click the “Reset Demo“, “Reset Log”, and “Toggle Observation” buttons to clear the logs and start or stop the observer. When paused, changes to the DOM are not logged.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4gbznrNDjMfC1zDyiMKvPg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ogfcfzY3ZPiiCmtp7U6rlw.png" /></figure><p>See how it all works together by exploring this CodePen:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodepen.io%2FJawaraGordon%2Fembed%2Fpreview%2FdPbmwMW%3Fdefault-tabs%3Djs%252Cresult%26height%3D600%26host%3Dhttps%253A%252F%252Fcodepen.io%26slug-hash%3DdPbmwMW&amp;display_name=CodePen&amp;url=https%3A%2F%2Fcodepen.io%2FJawaraGordon%2Fpen%2FdPbmwMW&amp;image=https%3A%2F%2Fshots.codepen.io%2Fusername%2Fpen%2FdPbmwMW-512.jpg%3Fversion%3D1736693275&amp;type=text%2Fhtml&amp;schema=codepen" width="800" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/36c10ebc57c9b7f0a6f28d6ba67a7a4e/href">https://medium.com/media/36c10ebc57c9b7f0a6f28d6ba67a7a4e/href</a></iframe><h3><strong>Wrapping It Up</strong></h3><p>The MutationObserver API<strong> </strong>is a tool that gives developers the ability to monitor and respond to changes in the DOM with ninja-like precision. In this article, we’ve learned about the greater family of JavaScript Observer APIs, explored coding examples, and built a demo app to better understand how MutationObserver<strong> </strong>can be applied to the real world. I hope that you’ll walk away from this experience with new strategies to observe and react to the DOM in ways that you never knew were possible. From infinite scroll to debugging third-party frameworks, MutationObserver is the secret ooze that can take your web development to the next level.</p><h3>Sources:</h3><ul><li><a href="https://developer.mozilla.org/en-US/docs/Web/API/MutationObserver">MutationObserver - Web APIs | MDN</a></li><li><a href="https://www.w3schools.com/jsref/jsref_event.asp">W3Schools.com</a></li><li><a href="https://www.geeksforgeeks.org/web-api-mutation-observer/">Web API Mutation Observer - GeeksforGeeks</a></li></ul><h3>Resources:</h3><ul><li><a href="https://www.bennadel.com/blog/4627-playing-with-mutationobserver-in-javascript.htm">Playing With MutationObserver In JavaScript</a></li><li><a href="https://developer.mozilla.org/en-US/docs/Web/CSS/Nesting_selector">&amp; nesting selector - CSS: Cascading Style Sheets | MDN</a></li><li><a href="https://www.w3schools.com/css/css3_buttons.asp">W3Schools.com</a></li><li><a href="https://www.w3schools.com/tags/att_script_defer.asp">W3Schools.com</a></li><li><a href="https://vercel.com/">Agentic Infrastructure - Vercel</a></li><li><a href="https://realfavicongenerator.net/">Favicon Generator for perfect icons on all browsers</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47137719c14b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reflecting on 2024 — A Year of Growth, Challenges, and New Horizons as a Software Engineer]]></title>
            <link>https://medium.com/@jawaragordon/reflecting-on-2024-a-year-of-growth-challenges-and-new-horizons-as-a-software-engineer-468b094d7627?source=rss-d4be0cf41dad------2</link>
            <guid isPermaLink="false">https://medium.com/p/468b094d7627</guid>
            <category><![CDATA[public-speaking]]></category>
            <category><![CDATA[2024]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[software-enginner]]></category>
            <category><![CDATA[journal]]></category>
            <dc:creator><![CDATA[Jawara Gordon]]></dc:creator>
            <pubDate>Wed, 01 Jan 2025 23:38:30 GMT</pubDate>
            <atom:updated>2025-01-02T00:24:17.954Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Reflecting on 2024 — A Year of Growth, Challenges, and New Horizons as a Software Engineer</strong></h3><figure><img alt="Colorful discovery wheel with different electives overlaying a school hallway." src="https://cdn-images-1.medium.com/max/1024/1*IyJiI68koltbRqauQj1-Aw.png" /></figure><blockquote>“As I reflect on 2024, I’m excited by how much this year pushed me to grow — not just as a developer but as a leader, mentor, and creator. It was a year of embracing new opportunities, navigating challenges, and stepping out of my comfort zone. Looking back, the big wins (and sometimes big losses) worked together as stepping stones toward an even brighter future.”</blockquote><p>The best way I can describe my experience this past year is by comparing it to a ‘discovery wheel.’ Do you remember that from Junior High or Middle School? If you don’t, this is a program where students rotate through different electives, like art, music, drama, and technology, for a few weeks or a semester at a time. This process allows students to explore different subjects and discover passions and strengths they may not know they have.</p><p>That was my 2024 in a nutshell. I tried so many things and found a much deeper understanding of what I’m most passionate about. Let’s take a closer look at my ‘discovery wheel of goals’ from last year.</p><h3><strong>Starting with a Clear Vision</strong></h3><p>The year began with a clear set of goals:</p><ul><li>(Officially) Start a Web Dev Business</li><li>Build Community Through Networking and Events</li><li>Expand My Role as a Fullstack Developer</li><li>Host Workshops</li><li>Speak at a Conference</li></ul><h3><strong>Starting a Web Dev Business</strong></h3><p>I was accepted into a mentorship group started by <a href="https://www.linkedin.com/in/saronyitbarek/">Saron Yitbarek </a>at the beginning of 2024. This supercharged my growth as a small business owner by giving me one-on-one coaching with <a href="https://www.linkedin.com/in/ryanleecox/">Ryan Cox</a> along with access to a huge community of like-minded creatives like <a href="https://www.linkedin.com/in/irina-vishnevskaya/">Irina Vishnevskaya</a>. I was sitting on a business plan for almost a year while working for close friends and family but thanks to this group, I was soon on my way to officially launching my web dev business called ‘<a href="https://staticfreedesigns.com/">Static Free Designs’</a>. Since then, I’ve built four new projects while expanding my web development skills and growing my reputation as a freelance developer with clients across the country.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LnyB1HRyFgBiPrqjnqVUcA.png" /></figure><h3><strong>Networking, Community, and New Opportunities</strong></h3><p>In the spring, I attended the <a href="https://events.bsidestampa.net/BSidesTampa2025"><strong>BSides Cybersecurity Conference</strong></a><strong> </strong>for the second year in a row. This time with my son! Some of our highlights were meeting <a href="https://www.linkedin.com/in/chris-machowski-170b14139/">Chris Machowski</a> who talked with my son about digital art and how they came up with this year’s awesome ’Stranger Things’ theme. We learned about cybersecurity through interactive vendor booths and hands-on activities like a Dungeons &amp; Dragons capture the flag (CTF). We got to use drone simulators, learned how to pick locks, and attended lectures from industry leaders.</p><p>Attending <a href="https://www.renderatl.com/"><strong>RenderATL</strong></a> in June was one of my biggest highlights from the year. Surrounded by like-minded professionals, I found validation and inspiration everywhere I went and with each new conversation. Networking at RenderATL opened doors, such as getting invited to the Google office, receiving praise from an Intuit Senior Product Manager, meeting some of my greatest inspirations (<a href="https://www.linkedin.com/in/taylordesseyn/">Taylor Desseyn</a> and <a href="https://www.linkedin.com/in/dthompsondev/">Danny Thompson</a>), and getting to know some of the <a href="https://www.linkedin.com/showcase/karat-brilliant-black-minds/posts/?feedView=all">Karat Brilliant Black Minds</a> team including the great <a href="https://www.linkedin.com/in/anthonydmays/">Anthony D. Mays</a>. These interactions weren’t just about career advancement but also about building meaningful connections and finding a sense of belonging.</p><p>Those interactions, and my genuine praise for Brilliant Black Minds, led to an offer to become an ambassador for them! They tapped me to write an <a href="https://www.linkedin.com/pulse/hustle-gitflow-how-build-your-catalog-skills-income-streams-gordon-encve?utm_source=share&amp;utm_medium=member_ios&amp;utm_campaign=share_via">article about my experiences</a> as a ‘multi-hyphenate’ while encouraging Black Software Engineers to join a platform dedicated to empowering them with free mock interviews and workshops. This opportunity has allowed me to contribute to a cause I’m deeply passionate about while sharpening my skills as a content creator. Join the group and learn more from my special ambassador link:</p><p><a href="https://joinbrilliantblackminds.com/jawara-gordon">Brilliant Black Minds</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LVOqi8gDTTR01Lfn3G9d5w.png" /></figure><h3><strong>Expanding My Roles and Responsibilities</strong></h3><p>I realized there were gaps in my design knowledge and instead of shying away, I leaned in, earning certifications from Coursera and META that not only boosted my skill set but also resulted in an expanded UI/UX Designer role at my <a href="https://grapeinc.com/">organization</a>. These efforts led to a major design system overhaul and improvements to our web development workflow that introduced efficiency across the board. This minimized communication problems and increased our bottom line along with deepening my value to the company — making me a vital part of every new project.</p><p>During 2024, I also completed an <strong>AI Engineer Certification </strong>from <a href="https://scrimba.com/home">Scrimba</a>. I learned the fundamentals of LLMs, embeddings, vector databases, and how to leverage pre-trained AI models from platforms like Hugging Face. This knowledge allowed me to create chatbots, dynamic search tools, and interactive widgets. I built projects with a hands-on approach by setting up Node/Express servers, managing environment variables, and integrating LangChain for advanced AI workflows to deepen my understanding of full-stack cloud deployment and serverless functions. I then applied this knowledge to projects, such as a stock prediction app and a mentorship program chatbot for a non-profit organization. This experience allowed me to blend creativity with technical innovation, leading to a much deeper understanding of AI-driven tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ACpA4hdctq3ClX0jpEBFqQ.png" /></figure><h3><strong>Giving Back to the Community</strong></h3><p>I learned a lot about what goes on behind the scenes with LLMs and AI-driven apps. Most of it was great, however, I uncovered a much darker side of this technology. There are significant fiscal, environmental, and humanitarian costs to creating these large language models. There are astronomical monetary and resource costs to train them in addition to fine-tuning them to display ‘safe’ results by hiring third-world labor for dollars a day to sift through traumatizing images and text. That’s why I decided to host a workshop with the <a href="https://brotherhoodofmen.org/">Brotherhood of Men</a> non-profit group (the org which I donate time and hosting resources to maintain their website) by teaching underserved youth about AI ethics and life skills. I connected AI concepts to sports analytics, video games, music, and education helping to close the gap for these young men. This was part of a larger vision I had to share this knowledge with a larger audience by speaking at a tech conference for <a href="https://www.thepattersonfoundation.org/">The Patterson Foundation</a> focused on creating “<a href="https://www.thepattersonfoundation.org/digital-access-for-all.html">Digital Access for All</a>” — that is… until my home state got rocked by hurricanes!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*3AGLjPd-Jn7l6vLlUMzTAw.png" /></figure><h3><strong>Navigating Challenges with Resilience</strong></h3><p>2024 wasn’t without its hurdles. Burnout, miscommunications, and balancing multiple roles tested my resilience. But nothing compared to the emotional and mental toll I faced when my home state of Florida was pounded by back-to-back hurricanes. This led to 5 months of hard work getting thrown out the window as Hurricane Milton shut down most of the state exactly one week before I was set to speak at the ‘DA4A Symposium’. This was heartbreaking for me — not only because of the lost effort but because my well-researched talking points about AI ethics no longer had an audience. By the time makeup dates were offered and a virtual version of the event was created, I had already moved on to my remaining goals for the year. I’m still planning on reworking this presentation for the future so be on the lookout!</p><h3><strong>Exploring New Frontiers</strong></h3><p>Toward the end of the year, I ventured into podcasting, creating a strategy for my organization that integrates AI-driven tools. This project was a bold step into storytelling and content creation, blending technical expertise with creative aspirations I’ve had for a long time. Simply put, I never had a team to realize my dream of producing podcasts, and now I have the best one I could ask for!</p><p>It’s a reminder that growth often comes from stepping into unknown territory and seeing what’s possible when you step off the beaten path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yBbf6mBKsHFDJoySnHpvDQ.png" /></figure><h3><strong>Lessons Learned</strong></h3><p>As I close out this reflection on 2024, I can’t help but feel like I’ve been riding my own ‘discovery wheel.’ Each rotation brought new opportunities, challenges, and lessons, shaping not only my career but my entire sense of purpose. From launching a web dev business and exploring the cutting edge of AI to building community through meaningful connections and giving back in ways that matter, this year has been about trying, learning, and growing. Just like those elective rotations in middle school, every experience added a layer of clarity about who I am and where I want to go.</p><p>Here’s to continuing the journey and embracing whatever the next turn of the wheel brings in 2025 and beyond!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=468b094d7627" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Culture and Code:  A Beginner’s Guide to Render ATL]]></title>
            <link>https://medium.com/@jawaragordon/culture-and-code-a-beginners-guide-to-render-atl-b11825714cf3?source=rss-d4be0cf41dad------2</link>
            <guid isPermaLink="false">https://medium.com/p/b11825714cf3</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Jawara Gordon]]></dc:creator>
            <pubDate>Sat, 29 Jun 2024 13:54:37 GMT</pubDate>
            <atom:updated>2024-06-29T18:35:46.974Z</atom:updated>
            <content:encoded><![CDATA[<h2>Culture and Code: A Beginner’s Guide to Render ATL</h2><figure><img alt="A conference staff member hands a lanyard to an attendee at a check-in table in front of a bright pinnk and gold backdrop." src="https://cdn-images-1.medium.com/max/1024/1*kKIOZHAKL3ItATBmGg5NnA.png" /></figure><h3><strong>What is Render ATL?</strong></h3><p>Render ATL is an annual tech conference, expo, and music festival that blends networking events and live music with Atlanta GA&#39;s vibrant culture and southern hospitality.</p><p>This community-first event is brought to life by a dedicated team of volunteers led by Justin E. Samuels. It features keynote speakers, panel discussions, workshop sessions, and lectures from industry leaders. This conference provides a safe and inclusive environment for like-minded individuals to discuss tech trends while getting hands-on with activities and face-to-face with industry partners.</p><blockquote>Render ATL 2024 saw more than 4500 attendees slide through downtown Atlanta, nearly a 1200% increase from their first year.</blockquote><p>One of the reasons for the increase is the affordable cost of the event, offering scholarships and discounted rates for students in addition to “super early bird” tickets for the public. The event lasts 3 days, with a full day of workshops followed by two days of vendor booths, interactive lectures, and keynote speakers on the main stage.</p><figure><img alt="Main stage host Selena Hill introduces keynote speakers in front of a large LED screen." src="https://cdn-images-1.medium.com/max/1024/1*0BA-BLp2Vq1fzNYPqWjE6Q.png" /></figure><h3><strong>Why Attend Render ATL?</strong></h3><p>Render is the perfect place for students, professionals, or anyone in a tech-adjacent role to learn about the latest advancements in all things software engineering. The conference was originally focused on React (a popular JavaScript library) however, it has since evolved to offer sessions for a wide variety of topics including tracks for; Software Engineering, Design, Leadership Culture &amp; Management, and Accessibility &amp; Innovation.</p><p>Some of my favorite sessions weren’t focused on code at all, but instead encouraged a broader approach to problem-solving and systems thinking.</p><figure><img alt="Demetris Cheatham presenting for GitHub and speaking in a fireside discussion on the main event stage." src="https://cdn-images-1.medium.com/max/1024/1*ubvsjGSEXeqzv7gBB-Xczg.jpeg" /><figcaption><a href="https://www.linkedin.com/in/dwcheatham/">Demetris Cheatham </a>presenting for GitHub and speaking in a fireside chat.</figcaption></figure><p>An added perk with your ticket is the access it gives you to a healthy amount of networking events. These events are held at the hotels and surrounding businesses after the main conference rooms close for the day. They’re hosted by industry partners like Google, Zillow, and Intuit who provide a casual place to meet &amp; greet with VPs and recruiters while enjoying local food and live music.</p><blockquote><strong>Beginner’s Tip</strong>: Sign up for events as soon as they’re posted by using the Render web app — or you’ll miss out. These spots go fast!</blockquote><figure><img alt="A DJ performing in front of a crowd at a hotel happy hour event." src="https://cdn-images-1.medium.com/max/1024/1*Kf0WRKcgYQKgu1tZN4QqsA.jpeg" /></figure><p>You can also jump in the official Render ATL Discord channel where you can get up-to-the-minute conference news and insights from both seasoned vets and first-time attendees. I was surprised to see event founder Justin E. Samuels posting like a madman with special event details, community news, and giveaways. It was great to see this level of passion from the top down, which continued to affect every part of this curated experience.</p><figure><img alt="Attendees wait in line to attend an after-hours event at the Ponce Market rooftop." src="https://cdn-images-1.medium.com/max/1024/1*gq5OtGL6CS6D6ZFiShfSmw.jpeg" /></figure><h3>How it Started</h3><p>Render ATL was established in 2019 as a way to address the need for an inclusive space within the tech industry, focusing on BIPOC professionals and underrepresented groups.</p><p>The kick-off event planned for 2020 got postponed due to the pandemic, pushing the first official conference to 2021. It featured over 20 brands and brought in about 350 attendees.</p><p>Render ATL also runs parallel with Atlanta Tech Week, a week-long series of events and meetups across the greater Atlanta area.</p><blockquote>“Since its inception in 2019, RenderATL has scaled successfully with an economic impact of over 6.5 million dollars and over 6,500 attendees at Render’s social events across the city of Atlanta, in the engineering and tech communities.”</blockquote><blockquote>— Justin E. Samuels, Founder</blockquote><figure><img alt="Justin E. Samuels speaks to a packed crowd during an interview with Shannon Sharpe." src="https://cdn-images-1.medium.com/max/1024/1*6ZjBDLD0WLIqX_QEpIkxJA.jpeg" /></figure><h3><strong>What to Know Before You Go</strong></h3><p>Buying tickets from the Render ATL website was fast and easy. The discounted tickets were a huge factor in convincing my workplace to cover the cost. The “<a href="https://docs.google.com/document/d/11Hd7bYIJZj9XpNsXaOX2HyK-o2YI3y38a_lcSDsrFJA/edit#heading=h.dz7m1h7x8d86">Convince Your Boss Template</a>” they link to on their site is not only hilarious but surprisingly helpful with giving you those corporate talking points. I didn’t even need to use it though because <a href="https://www.linkedin.com/in/allison-imre-perkowski-89580311/">my boss</a> is awesome and said “Say no more!” when I pitched the idea. I got discounts on airfare and hotel since I stayed at the official conference-sponsored location.</p><p>You can also purchase tickets to “Render Haus” ( the live music-focused after-party) on their site which is a smart idea since they sell out quickly. After pressing send and getting the first round of confirmation emails, I was sent a steady stream of useful info and links to help prepare for the event as the event date got closer.</p><figure><img alt="An event flyer featuring Anderson . Paak as his DJ persona." src="https://cdn-images-1.medium.com/max/1024/1*WguwooLVLsq4STQx3UcSIg.jpeg" /></figure><p>Make sure to review the event agenda and list of speakers in advance. There’s a lot to see (and do) so make sure you create a plan going in that includes your “must-see” speakers, your favorite workshops (you may only have time for one if it’s all day), your go-to vendors, and hottest “must attend” networking events. I was glad I made this list since a few of my top speakers ended up having conflicting times which forced me to make some tough choices. Leaving flex time between sessions to visit the vendor space, enjoy the food trucks, and explore the downtown area was a great way to regroup when I ran into a scheduling conflict.</p><figure><img alt="Conference attendees danced outdoors to a DJ while waiting in line for food trucks." src="https://cdn-images-1.medium.com/max/1024/1*rWwUK5EeKTNmw0Rv3k0MuA.png" /></figure><h3><strong>Presentation Formats</strong></h3><p>Render offers a wide variety of presentation formats that appeal to different learning styles. From hands-on workshops to small lecture-style presentations and large keynote speeches, both beginners and experts will find ways to further their education. Smaller lectures and panels are held in various rooms, while keynote speeches and major presentations take center stage in larger spaces on different floors of the expansive event space.</p><p>Sessions typically last 30–50 minutes, leaving plenty of time for Q&amp;As. In my experience, most sessions ended on time or early creating a smooth transition between stages. There were plenty of maps and schedule kiosks in high-traffic areas and even a dedicated “FAQ” person to answer questions if you needed that human connection.</p><figure><img alt="Danny Thompson giving a presentation on TypeScript." src="https://cdn-images-1.medium.com/max/1024/1*YqFcZuS7vH_0R6UKb2Hi5Q.jpeg" /><figcaption><a href="https://www.linkedin.com/in/dthompsondev/">Danny Thompson</a> giving a presentation on TypeScript.</figcaption></figure><h3><strong>Workshops</strong></h3><p>The first day of the conference was completely dedicated to workshops. I got excited when I saw them pop up in the Render web app and added them to my list of favorites. That’s where I made a rookie mistake…</p><blockquote>These sessions are long — we’re talking 4+ hours or all day for some of them.</blockquote><p>Not only did I miss the session length, but I also didn’t catch the part saying “Please choose ONE” so I thought I’d be taking all kinds of mini-workshops during the day. I found out the hard way when presenter Kelly Vaughn (Spot AI) said “only 3 more hours to go” during her “Holding Influence for Engineers and EMs” workshop, I laughed out loud at what I thought was a joke — but as it turns out, my expectations were way off!</p><figure><img alt="Kelly Vaughn hosting a workshop in a classroom setting with a large projector and attendees sitting in groups around tables with laptops." src="https://cdn-images-1.medium.com/max/1024/1*5PQIQgxJJo0pOSxvE6LxbA.jpeg" /><figcaption><a href="https://www.linkedin.com/in/kellyvaughn/overlay/about-this-profile/">Kelly Vaughn</a> hosting a workshop on “Holding Influence for Engineers and EMs”.</figcaption></figure><p>In my defense, I had a lot going on that day and wasn’t checking my work email to get updates. To save you some hassle:</p><blockquote><strong>Beginner’s Tip</strong>: Find that “must-see” workshop and focus on only doing that for your first day at the conference.</blockquote><p>The event staff couldn’t have been more helpful when I realized my mistake and had me back on track in time for the Makeshift “How to Make Your Website a Vibe” workshop that I was able to reserve a spot for in the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hUQmUHm5pSPkH2qJVssPgw@2x.jpeg" /><figcaption>Makeswift hosting a workshop on designing websites with a packed room of attendees at tables with laptops.</figcaption></figure><h3><strong>Presentations</strong></h3><p>The second day saw the classroom style layout change to small lecture halls. Each room was filled with rows of chairs, a dedicated sound person, outstanding emcees, and covered in vibrant colors with Render ATL-themed graphics displayed on large backdrops.</p><figure><img alt="Mark (Techson) Thompson giving an early morning presentation on web development on a small stage in front of a large orange and gold backdrop." src="https://cdn-images-1.medium.com/max/1024/1*J7dXYSb16VwvBSyfcs6l-A.jpeg" /><figcaption><a href="https://www.linkedin.com/in/marktechson/">Mark (Techson) Thompson</a> giving an early morning presentation on web development.</figcaption></figure><p>I was surprised to start the day sitting right in front of keynote speaker and (retired) Googler Kelsey Hightower who came to support Mark Techson presenting all about “Building the Next Generation of Supercharged Web Applications Today.” A few rows away was Anthony D. Mays from Karat Brilliant Black Minds — a senior developer and person I look up to as a mentor. It was great to see that level of support from leaders in the community — the fact that they would show up so early ask questions and be engaged left me feeling great about making these same choices and who I’m choosing to be around. After Mark’s session I stuck around the stages for Monica Powell’s presentation on “An Exploration of Computational Creativity.” I was blown away by how much art you can create with JavaScript, the types of techniques to use and the huge community of creative devs out there.</p><p>This set me up perfectly for a session with Dan Mall titled “Design Systems Everywhere Else” which dug into his philosophy surrounding a “system of systems” and the best ways to audit and install design systems with companies big and small.</p><figure><img alt="Dan Mall giving a presentation on Design Systems on a small stage in front of a large banner with pink and white lettering." src="https://cdn-images-1.medium.com/max/1024/1*e_95qvs6JRZ_zbZ3j34qcQ@2x.jpeg" /><figcaption><a href="https://www.linkedin.com/in/danmall/">Dan Mall </a>giving a presentation on Design Systems.</figcaption></figure><p>After a lunch break in the food truck courtyard with a live DJ and basketball hoop challenge, I made my way to the vendor area for networking and a meet &amp; greet with the BBM fam. I became a <a href="https://karat.com/brilliant-black-minds/">Brilliant Black Minds</a> member after they read my <a href="https://peopleofcolorintech.com/author/jawara-gordon/">People of Color in Tech (POCIT) blog post</a>, and invited me to host a workshop called “<a href="https://jawaragordon.com/docs/Optimizing%20Your%20First%2090%20Days%20as%20a%20Software%20Engineer.pdf">Optimizing Your First 90 Days as a Software Engineer.</a>” VP Crystal Moore was hanging out with volunteers, mingling with the crowd, and inviting attendees to take advantage of their free headshots. Not far from them were booths from Zillow (thanks for the yoga mat!), Intuit (thanks for the basketball!), Microsoft, Vercel, and many, many more!</p><figure><img alt="Conference attendees standing in line to play basketball in a large vendor space with an oversized light-up “Intuit” branded sign." src="https://cdn-images-1.medium.com/max/1024/1*fLOoq9eMpRR4r4krlrcMTQ@2x.jpeg" /><figcaption>Conference attendees standing in line to play basketball in a large vendor space with an oversized light-up “Intuit” branded sign.</figcaption></figure><figure><img alt="Conference attendees explore a large area with multiple vendor booths." src="https://cdn-images-1.medium.com/max/1024/1*PPhIKQl18Yucv-e0mRsJVQ.jpeg" /><figcaption>Conference attendees explore a large area with multiple vendor booths.</figcaption></figure><p>Just past the vendor booths was another presentation stage right in the middle of all the action. “How’re they gonna present with all this noise?” I thought to myself until I was handed a pair of silent disco headphones to wear. This allowed us to hear the presentation like we were in the front row, with the added bonus of an actual silent disco spun by DJs in between the speakers.</p><figure><img alt="People with headphones on listening to a presentation in an open-air event space." src="https://cdn-images-1.medium.com/max/1024/1*UbmG3FnoPLDefFknvtu3lw@2x.jpeg" /></figure><p>It was a vibe! I enjoyed learning how to make “AI Trap Music” with Ken Wheeler and how to program React Native apps on the Apple Vision Pro thanks to Oskar Kwasniewski.</p><figure><img alt="Three people with headphones on watching a presentation while sitting on the floor." src="https://cdn-images-1.medium.com/max/1024/1*b4ssz46rNWyX51oNbeW-fw.jpeg" /></figure><h3><strong>Keynote Speakers &amp; Panel Discussions</strong></h3><p>All of the headlining acts were held in a large event space on a separate floor. The main stage reached across the room with dramatic Render themed graphics, and brightly colored backgrounds (#F584D5) spread across massive LED screens. The room left as much of an impact as the speakers, who represented the largest companies with the biggest reach in the tech industry. We’re talking Walmart, Zillow, Google, and Intuit to name a few. Some highlights from these sessions include:</p><p>Kelsey Hightower (Retired — Google) — Have you ever been on the edge of your seat during a presentation? Ok, but have you ever been captivated by a speaker who used nothing but a Google map for their slide deck? That’s how powerful Kelsey Hightower’s words are. No fancy slides, statistics or meme gifs, only genuine stories that were shared from the heart and cemented this man as one of (if not the best) speakers at the conference. I walked away from his talk inspired to lean on my IT roots and to look for opportunities to grow as a software engineer by solving problems through my own unique perspective.</p><figure><img alt="Kelsey Hightower giving a keynote speech on the main stage while projected on large video monitors." src="https://cdn-images-1.medium.com/max/1024/1*d8CwQxmcPjAu0A1ZJpOWzw.jpeg" /><figcaption><a href="https://www.linkedin.com/in/kelsey-hightower-849b342b1/overlay/about-this-profile/">Kelsey Hightower</a> giving a keynote speech on the main stage.</figcaption></figure><p>Crystal Moore (Karat — Brilliant Black Minds), Tanisha Barnett (Intuit, Mailchimp), and Justin Simpson (Walmart) appeared on a panel to talk about “IC to VP: A Conversation on Career Progression for Software Engineers.” They discussed the need to have self-awareness and humility, the importance of, “staying close to the tech”, and how they learned to be “students of the business” which allowed them to take risks and foster relationships through mentorships.</p><figure><img alt="Crystal Moore, Tanisha Barnett, and Justin Simpson speak on a group panel discussion on the main stage." src="https://cdn-images-1.medium.com/max/1024/1*qr491qr5AD_q5m3EY8pohw@2x.jpeg" /><figcaption><a href="https://www.linkedin.com/in/crystalnmoore/">Crystal Moore</a>, Tanisha <a href="https://www.linkedin.com/in/barnetttanisha/">Barnett</a>, and <a href="https://www.linkedin.com/in/justin-m-simpson/">Justin Simpson</a> speak on a group panel discussion on the main stage.</figcaption></figure><p>Atlanta Mayor Andre Dickens highlighted how events like Render ATL can inspire the next generation of tech innovators, especially those who come from underrepresented communities. He spoke of partnerships between the city and the growing tech sector which has cemented itself as the largest tech hub in the Southeast.</p><p>The big finish at Render ATL 2024 was a discussion with sports analyst and NFL Hall of Famer Shannon Sharpe. He focused on leadership, resilience, and the importance of diversity in technology. He shared insights on starting his successful podcast and life as an entrepreneur post-NFL:</p><blockquote>“There is no failure only delayed success.”</blockquote><blockquote>— Shannon Sharpe</blockquote><p>It was nice to see the conference’s commitment to creating a through-line between different industries that rely on tech and the diverse voices that represent them.</p><figure><img alt="A packed auditorium of attendees listening to a keynote panel discussion with Shannon Sharpe." src="https://cdn-images-1.medium.com/max/1024/1*r_McpTH6u1RNjhkMdC_9Pw@2x.jpeg" /><figcaption>A packed auditorium of attendees listening to a keynote panel discussion with Shannon Sharpe.</figcaption></figure><h3><strong>Networking and Events</strong></h3><p>Render ATL is promoted as both a tech and music conference — and let me tell you, they didn’t hold back on either. The main hotel kicked things off with a “Nextplay Live Mixer” happy hour event after the first day’s workshops ended. This event included a live artist, DJ, and pop-up shop in the hotel multifunction space.</p><figure><img alt="Mixed media physical art on display near a live artist." src="https://cdn-images-1.medium.com/max/1024/1*pZcVDUPTg9mVEjSPQ8ovAg@2x.jpeg" /></figure><p>Afterward, I attended the official rooftop party hosted by Render ATL and Netlify at Ponce Market. This is where the real magic happened for me. After jamming out to another great DJ and playing a few boardwalk games, I struck up a conversation with a senior dev and an Atlanta city commissioner who both invited me to continue talking in a quieter space. We made our way to a fire pit and talked about how we would fix the city’s parking problems using technology, all set to the soundtrack of an R&amp;B band (and after-sunset drone show). I was told I’d have these moments at Render, and that this is how the best networking happens — but I didn’t believe it until now! A casual conversation led to a senior dev being so impressed by our conversation that they reached out to <em>me</em> on LinkedIn.</p><figure><img alt="Render ATL hosts a rooftop event with organizers welcoming guests with an R&amp;B band in front of a bright orange sunset." src="https://cdn-images-1.medium.com/max/1024/1*bwQjm9-Aosc5wr1ZtWlQSQ.jpeg" /></figure><p>The next evening I was invited to the downtown Google office for a meet &amp; greet with Senior Developers, Recruiters, and VPs that included an open bar, buffet, and gorgeous views of the cityscape while we jammed out a talented DJ.</p><figure><img alt="Google VP welcomes guests to their downtown office during a meet &amp; greet event with attendees sitting in chairs listening to a. DJ." src="https://cdn-images-1.medium.com/max/1024/1*veuBAMctM1bPoZzHefTG_w.png" /></figure><p>Afterward, I made my way to Embr for a networking event with T. Rowe Price a few blocks away. They also had a DJ, full bar, and food that I shared with internet friends.</p><figure><img alt="Conference attendees at an after-hours lounge enjoying drinks and a DJ." src="https://cdn-images-1.medium.com/max/1024/1*1VJdQQhxurBnIlU-tYfK9Q.jpeg" /></figure><p>The grand finale event was called “Render Haus” which featured performances from DJ Pee.Wee (aka Anderson .Paak), Coco &amp; Breezy, and many more! Tickets went fast for this but there were a lot of people selling them in the Discord leading up to the party. I could tell a lot of folks, myself included, didn’t have much left in our social batteries after three days of non-stop action and as a result, decided to stay in that night. I felt some heavy FOMO when I decided to call it, but I don’t feel bad about making mental health a priority and getting plenty of rest after a very long week of meeting people from around the world.</p><figure><img alt="Dark purple LED lighting glowing off the top of a tent while a large audience listens to an R&amp;B band." src="https://cdn-images-1.medium.com/max/1024/1*a-qV1FRska1V3OcnqfEnHQ@2x.jpeg" /></figure><h3><strong>Wrap-Up</strong></h3><p>Render ATL combines diverse presentation formats, with diverse speakers, creating an engaging experience for beginners and experts. The conference has a smooth flow with plenty of space around sessions to explore and network while having fun with hands-on activities. The team’s positive attitude showcases the founders’ deep commitment to the core values of this event which shines through in everything they do. Render is truly a community-first conference, with its unique blend of tech and culture that highlights the importance of inclusivity and learning. From insightful talks to vibrant networking events, this conference offered a huge platform for growth, connection, and innovation, leaving us inspired and hungry for more.</p><p>Render ATL left a lasting impression on me and will be one of those career-defining experiences when I reflect on this time. After a week surrounded by my peers and embraced by a group that supports me, I feel empowered to be myself more than ever before. There’s no better reminder than looking down at my conference t-shirt to read the words “No code switching.” knowing that I’m not alone on this journey.</p><p>For more details about the event and to stay updated on future conferences, visit the official <a href="https://www.renderatl.com/">Render ATL website</a>.</p><p>Connect with me on <a href="https://www.linkedin.com/in/jawaragordon">LinkedIn</a> and follow me on Medium for more stories about coding, technology, and music.</p><figure><img alt="A drone show spelling the words “Render ATL” in the night sky overlooking an outdoor viewing area." src="https://cdn-images-1.medium.com/max/1024/1*NiaxcqFqANQWJWUJRhwdtQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b11825714cf3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ready Player React: How to Build a Video Game With JavaScript — Part 4]]></title>
            <link>https://medium.com/@jawaragordon/ready-player-react-how-to-build-a-video-game-with-javascript-part-4-b4396c85eec9?source=rss-d4be0cf41dad------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4396c85eec9</guid>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Jawara Gordon]]></dc:creator>
            <pubDate>Sun, 25 Feb 2024 17:12:46 GMT</pubDate>
            <atom:updated>2024-02-26T21:39:15.791Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ready Player React: How to Build a Video Game With JavaScript — Part 4</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*stlsAsghxccsw8A9MO98Lw.png" /></figure><p>In this last installment of “Ready Player React,” all of our hard work has paid off and we’re ready to release our games to the world! We’ve journeyed from concept to the final steps of deployment, following through from planning in <a href="https://medium.com/@jawaragordon/ready-player-react-how-to-build-a-video-game-with-javascript-part-1-fbda59e173f5">Part 1</a>, refining and testing in <a href="https://medium.com/@jawaragordon/ready-player-react-how-to-build-a-video-game-with-javascript-part-2-29b29ea93a9c">Part 2,</a> to enhancing performance and finalizing features in <a href="https://medium.com/@jawaragordon/ready-player-react-how-to-build-a-video-game-with-javascript-part-3-be633e4adcd4">Part 3.</a></p><p>This chapter will guide you through picking a domain name, choosing a hosting platform, creating a deployment pipeline, and post-launch feedback.</p><p>So get ready to hit “continue” as we jump into the final phase in this series — Deployment!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y21kortZ9Qq6j99e4A59rg.png" /></figure><h3>Launch Checklist</h3><p>Deploying your game involves a final check to ensure everything’s set for launch. Your pre-deployment checklist should include:</p><ul><li><strong>Code Optimization</strong>: Check your code for efficiency, ensuring it’s DRY, well-documented, and free of console errors (and warnings) that will cause your deployment to fail.</li><li><strong>Meta Data &amp; SEO:</strong> Change the default information in the head of your index.html file. Enhance your title tags, descriptions, and keywords to reflect your game’s content accurately, making it easier for search engines to index and users to find your game.</li><li><strong>Security Checks</strong>: Ensure that user data is stored securely such as salting and hashing passwords, and properly resetting cookies and tokens when the game session has ended.</li><li><strong>Domain Name</strong>: Your game needs a place to live where it can be easily found online. Hosting services will give you a generic name for free, but you can also add your own custom URL.</li></ul><blockquote><strong>Pro Tip</strong>: Consider purchasing a custom domain name for your game. I got <a href="https://vibecheck.today/">vibecheck.today </a>from <a href="https://www.namecheap.com/domains/domain-name-search/?gad_source=1&amp;gclid=Cj0KCQiA5-uuBhDzARIsAAa21T8enjwggcRM-m0wTz0VYq_tqaFZRHZPiIo7kY41FNK2KRnilPeTjqsaAnOnEALw_wcB">namecheap.com</a> for only a few dollars!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L_-jJ0L1itSgASrep7s61A.png" /></figure><h3>Hosting</h3><p>It’s time to choose a forever home for your game. The good news is you have tons of great hosting options, however, that can lead to confusion with picking the right one.</p><p>Developers have a wide range of hosting options to choose from depending on your project requirements:</p><ul><li><strong>Self-Hosting on a Dedicated Server:</strong> Offers full control over the hosting environment, allowing for custom configurations and optimizations.</li><li><strong>Platform as a Service (PaaS)</strong>: Providers like Heroku automate infrastructure management, simplifying deployment and scaling.<br><strong>Cloud Services</strong>: AWS, Google Cloud, and Azure provide scalable and flexible hosting solutions for large player bases.</li><li><strong>Static Site Hosts</strong>: Netlify and GitHub Pages are ideal for static sites, offering easy deployment and maintenance using a Git pipeline.</li></ul><p>Each platform has its unique pros and cons and it’s important to take time to research your options. Keep in mind that <strong>PaaS</strong> providers offer convenience over cost savings, and may be too expensive for hosting a project of this size. <strong>Self-hosting </strong>options are cost-effective and offer greater control; however, they require a deep understanding of backend networking and security.</p><p>GitHub Pages and Netlify are the recommended choices for hosting a self-contained, static app of this size. Netlify was chosen as the best option for ‘Vibe Check’ for its simplicity and integration with Github.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wJD1Z76Kiw5sv70oH-tKwQ.png" /></figure><h4>Getting Started</h4><p>Netlify stands out for its simplicity and efficiency, offering continuous deployment (with instant rollbacks ) from Git across all of its plans, including a free tier!</p><p>It’s easy to get started with creating an account and I recommend using your GitHub credentials: <a href="https://app.netlify.com/signup">https://app.netlify.com/signup</a></p><p>Next, install the Netlify CLI tool using this guide from the docs:</p><h3>Deploy your Create React App project with Netlify CLI</h3><p>You can <a href="https://docs.netlify.com/site-deploys/create-deploys/#netlify-cli">deploy your project from the command line</a> using <a href="https://docs.netlify.com/cli/get-started/">Netlify CLI</a>.</p><ol><li>To ensure you have the latest version of Netlify CLI installed, run this command from any directory in your terminal:</li></ol><pre>npm install netlify-cli -g</pre><p>2. In the directory for your project, run the following command to create a new Netlify site:</p><pre>netlify init</pre><p>3. Follow the prompts to create your site, select a team if necessary, and optionally create a site name. If you already initialized a Git repository, you can authorize your Git provider and set your build command and directory.</p><p>Here’s a quick start guide for linking up your Github account to Netlify:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F4h8B080Mv4U%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D4h8B080Mv4U&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F4h8B080Mv4U%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/18dc24152072bf9d3daaa8db80aa2618/href">https://medium.com/media/18dc24152072bf9d3daaa8db80aa2618/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r7gNGydujyMsZuyTDxLl1w.png" /></figure><p>You did it! Congratulations on deploying your very own video game using React! This fully optimized and playtested game is ready to share with the world and start collecting feedback.</p><h3>Feedback</h3><p>Now that your game is live, you can start collecting feedback from actual users. This transition from development to production offers a unique opportunity to find those pesky edge cases. This fresh perspective can be used to guide future improvements and bug fixes by revealing key aspects of user engagement.</p><blockquote>“This game’s got such an intriguing premise — coming up with words before the beat hits. It really makes you laugh at how many words you actually know. Clever, challenging, and a whole lot of fun!” — React Jam Judges</blockquote><p>Hearing this feedback from the hackathon committee was incredibly validating. Having gone from concept to deployment with minimal React skills and even less game design knowledge was a huge milestone! Receiving such positive feedback from the judges was icing on the cake underscoring this challenging and rewarding experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gxPuB4q1mtTs8M0-YqVE5A.png" /></figure><h3>Getting Help</h3><p>This process would have been nearly impossible without support from the official Reddit and Discord communities. These platforms allowed me to engage with other developers, playtest their games, ask questions, and get invaluable insights when I was feeling lost.</p><p>These interactions not only gave me a sneak peek at game development but also highlighted the importance of collaboration in the dev community, offering lessons that extend far beyond the boundaries of this hackathon.</p><h4>Acknowledgments</h4><p>You can play all ~30 of the finished games on the React Jam website:</p><p>All games: <a href="https://reactjam.com/winners">https://reactjam.com/winners</a></p><p>You can play the official React Jam-hosted version of ‘Vibe Check’ here: <a href="https://vibe-check.winter-2023.reactjam.com/">https://vibe-check.winter-2023.reactjam.com/</a></p><p>Learn more about React Jam and how you can join the next challenge: <a href="https://reactjam.com/#faq">https://reactjam.com/#faq</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kdZT2QX5U2q-yHXQIOvHEA.png" /></figure><h3>Conclusion</h3><p>Throughout the “Ready Player React” series, we’ve journeyed from concept to deployment. Along the way, we’ve learned the importance of careful project planning, testing and playtesting, optimization, and hosting.</p><p>We were met with several challenges along the way such as using the HTML audio element for gameplay and the overly-ambitious use of technologies like Storybook. These experiences highlight the importance of finding a good balance of both innovation and grounded expectations when creating a video game.</p><p>Reflecting on the overall experience, the process of game development feels very similar to the traditional approach of web development with some major differences in UX/UI and deployment. This series not only chronicles the technical steps to build your very own game from scratch but also celebrates the collaborative spirit of the React dev community.</p><p>This journey was equal parts exciting and exhausting! The rush of beating the deadline and having a game accepted was thrilling — doing it solo was hard! This experience gave me a deep understanding of project management, advanced debugging, and a deep appreciation for the creativity and passion required to bring a video game to life with React.</p><p>If you’ve enjoyed this series <a href="https://medium.com/@jawaragordon">follow me on Medium</a> and <a href="https://www.linkedin.com/in/jawaragordon/">connect with me on social media</a> to get more of my articles on coding, mindfulness, and project management.</p><h3>Sources</h3><ul><li><a href="https://reactjam.com/#faq">React Jam</a></li><li><a href="https://docs.netlify.com/site-deploys/create-deploys/#netlify-cli">Create deploys</a></li></ul><p><a href="https://pages.github.com/">https://pages.github.com/</a></p><h3>Resources</h3><p><a href="https://www.reddit.com/r/reactjam/">https://www.reddit.com/r/reactjam/</a></p><p><a href="https://www.namecheap.com/domains/domain-name-search/?gad_source=1&amp;gclid=Cj0KCQiA5-uuBhDzARIsAAa21T8enjwggcRM-m0wTz0VYq_tqaFZRHZPiIo7kY41FNK2KRnilPeTjqsaAnOnEALw_wcB">Domain Name Search | Free Check Domain Availability Tool - Namecheap</a></p><p><a href="https://www.digitalocean.com/products/droplets">https://www.digitalocean.com/products/droplets</a></p><p><a href="https://github.com/JawaraGordon/vibe-check">https://github.com/JawaraGordon/vibe-check</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4396c85eec9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ready Player React: How to Build a Video Game with JavaScript — Part 3]]></title>
            <link>https://medium.com/@jawaragordon/ready-player-react-how-to-build-a-video-game-with-javascript-part-3-be633e4adcd4?source=rss-d4be0cf41dad------2</link>
            <guid isPermaLink="false">https://medium.com/p/be633e4adcd4</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Jawara Gordon]]></dc:creator>
            <pubDate>Sun, 11 Feb 2024 02:14:59 GMT</pubDate>
            <atom:updated>2024-02-26T21:08:52.454Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ready Player React: How to Build a Video Game With JavaScript — Part 3</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fdixV5r4PO8EvCxz5xvM7w.png" /></figure><p>It’s time for the penultimate episode of “Ready Player React: How to Build a Video Game with JavaScript” — Testing!</p><p>Before moving on, let’s reflect on our journey so far. In <a href="https://medium.com/@jawaragordon/ready-player-react-how-to-build-a-video-game-with-javascript-part-1-fbda59e173f5">part one</a>, we tackled the essentials of game planning like choosing our game loop and hook. Then, in <a href="https://medium.com/@jawaragordon/ready-player-react-how-to-build-a-video-game-with-javascript-part-2-29b29ea93a9c">part two</a>, we set up our environment, inserted game logic using test-driven development, and tackled the challenge of using audio in the browser.</p><p>Now, let’s shift our focus to “Testing” — a critical phase where we playtest our game from beginning to end, gather feedback from beta testers, fix bugs, improve performance, and optimize our build for the final phase — deployment!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pFL7yliHkLduRd9IzTSK3Q.png" /></figure><h3>Playtesting</h3><p>Let’s talk about an important stage of the game development process: playtesting. Playtesting is when developers and QA engineers rigorously test the game to find problems and fix bugs. This ensures that the game mechanics work as intended for as many players, in as many scenarios as possible.</p><p>Think of this phase as an opportunity to see how your game holds up under pressure — it’s a heat check to gather critical insights, catch edge cases, and build a final game that can hold its own in a production environment.</p><p>Here are some tips to get the most from playtesting:</p><ul><li><strong>Player Selection</strong>: Find players from all walks of life to test your game. Find the youngest and oldest people you know and ask them to provide feedback using a <a href="https://github.com/mikeb-stripe/friction-logging-toolkit?tab=readme-ov-file">friction log</a>.</li><li><strong>Observations</strong>: Watch beta testers play your game without stopping them or interfering in any way. Allow them to give honest feedback on where they encounter difficulties or enjoyment.</li><li><strong>Bug Fixes</strong>: Use feedback to make iterative bug fixes, logging each change with detailed notes and commits.</li></ul><p>Effective playtesting transforms frustrating bugs and errors into a fine-tuned experience that players will want to replay again and again! It’s important to iron out any issues now before trying (and failing) to deploy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3DMIh62XuXhHQmAs1tyDoA.png" /></figure><h3>Performance</h3><p>The next crucial step is enhancing our game’s performance. This involves code splitting, refactoring, and managing state to reduce complexity and improve responsiveness. A great place to get started is by caching game assets to reduce load times. Then you should remove any unused dependencies that may bloat your bundled game file.</p><p>You can get started with code-splitting by doing the following:</p><ul><li>Use React.lazy to dynamically import components that are loaded only when they are needed.</li><li>Employ Suspense to display fallback content while your components are being loaded, like thumbnails and spinners.</li><li>Structure routes to dynamically load components at the route level, optimizing faster load times.</li></ul><blockquote><strong>!important</strong>: Don’t forget to run the testing suites we created eariler while making any changes to the codebase.</blockquote><p>This is where that safety net we created comes into play. We can catch bugs and issues immediately by keeping a careful eye on our unit tests. This approach not only streamlines the development process but also significantly enhances the maintainability and quality of the code as you introduce more features down the road.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kTdi2hkcUlH541kthypTIA.png" /></figure><h3>Pre-Deployment</h3><p>This is it! We have a finished game that’s ready to make its big debut! We only have one phase left to go — deployment. But how do we get it out of our computer and into the hands of other players?</p><h4>Bundling</h4><p>The process of compiling and combining various files and assets of an application together is called bundling. This is crucial for optimizing performance by reducing the number of requests needed when loading the game. Tools like Webpack or Parcel analyze your project’s dependencies, re-package, and minify your JS, CSS, and other assets into small, fast-loading files.</p><blockquote><strong>Note</strong>: Create React App (CRA) utilizes Webpack under the hood for bundling. Webpack automatically compiles and bundles all JavaScript, CSS, and asset files into efficient static files ready for production.</blockquote><p>The npm run build command is what initiates the process of taking our game from dev mode to production mode. When you execute this command it triggers the creation of a build folder, compiling your app into static files optimized for production transforming your dynamic, development-stage project into a fast-loading package suitable for deployment on your favorite platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zQqcvEgxvgnGtQ05CoLdhw.png" /></figure><p>As we wrap up this chapter, we’ve fully optimized our game and we’re almost at the finish line. <a href="https://medium.com/@jawaragordon/ready-player-react-how-to-build-a-video-game-with-javascript-part-4-b4396c85eec9">In the final phase, we’ll deploy our game and prepare for future updates and features</a>.</p><p>Make sure to subscribe and <a href="https://www.linkedin.com/in/jawaragordon/">follow</a> to get notified about the last installment of “Ready Player React,” along with more of my insights on coding, mindfulness, and project management.</p><h3>Sources</h3><ul><li><a href="https://webpack.js.org/concepts/why-webpack/">Why webpack | webpack</a></li><li><a href="https://reactjs.org/docs/code-splitting.html">Code-Splitting - React</a></li><li><a href="https://jestjs.io/docs/getting-started">Getting Started · Jest</a></li></ul><h3>Resources:</h3><ul><li><a href="https://github.com/mikeb-stripe/friction-logging-toolkit/blob/main/how-we-use-friction-logs-at-stripe.md">friction-logging-toolkit/how-we-use-friction-logs-at-stripe.md at main · mikeb-stripe/friction-logging-toolkit</a></li><li><a href="https://parceljs.org/">Parcel - The zero configuration build tool for the web.</a></li><li><a href="https://developers.google.com/web/tools/lighthouse">Overview | Lighthouse | Chrome for Developers</a></li><li><a href="https://github.com/webpack-contrib/webpack-bundle-analyzer">GitHub - webpack-contrib/webpack-bundle-analyzer: Webpack plugin and CLI utility that represents bundle content as convenient interactive zoomable treemap</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be633e4adcd4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ready Player React: How to Build a Video Game with JavaScript — Part 2]]></title>
            <link>https://medium.com/@jawaragordon/ready-player-react-how-to-build-a-video-game-with-javascript-part-2-29b29ea93a9c?source=rss-d4be0cf41dad------2</link>
            <guid isPermaLink="false">https://medium.com/p/29b29ea93a9c</guid>
            <category><![CDATA[test-driven-development]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[component-driven-dev]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Jawara Gordon]]></dc:creator>
            <pubDate>Mon, 29 Jan 2024 04:56:40 GMT</pubDate>
            <atom:updated>2024-02-26T21:07:54.688Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ready Player React: How to Build a Video Game With JavaScript — Part 2</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dDEd9eIHchX1RlcX4rorXQ.png" /></figure><p>As we move on to the next level of “Ready Player React,” it’s time to shift gears from concept to creation in Phase 2: Building.</p><p>Last time, we covered the basics from sketching a plan to deciding on a game loop and hook. In this next chapter, we’ll walk through setting up your environment and building out the initial structure for test-driven development. We’ll select tools and libraries, project structure, and game architecture.</p><p>We’ll start by introducing test-driven development (TDD) using a pragmatic approach to coding each game element. Next, we’ll build our first components while infusing them with game logic and styling. Finally, we’ll tackle one of the more challenging aspects of using React for game development — working with sound in the browser!</p><p>So, get ready as we gear up for the next round in this step-by-step guide to building a game with JavaScript!</p><p>(Before moving on, make sure you’re up to speed with <a href="https://medium.com/@jawaragordon/ready-player-react-how-to-build-a-video-game-with-javascript-part-1-fbda59e173f5">Part 1 here</a>.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v1Ei9ROJElTkwm00Lyx_-Q.png" /></figure><h3>Setting up the Environment</h3><p>This stage is all about choosing the right tools and setting up a project structure that allows for a streamlined workflow.</p><p>This project uses Create React App (“Happy hacking!”), Tailwind, Storybook, and Jest to get the vibes right straight from the start. Visualizing components, and mapping out state management for prop drilling is an important step in building a strong foundation for your game.</p><h4>Create React App</h4><p>The <a href="https://react.dev/learn/installation">official React docs</a> have stopped recommending create-react-app (CRA) as the best way to jumpstart a React project. I decided to go against this recommendation having used CRA to bootstrap many projects similar to this one in the past. You’re welcome to install React however you prefer using whatever framework works best for you — just keep in mind that all steps in this guide will assume you are using CRA or that you’re savvy enough to work around that!</p><p>To get started with CRA follow these steps:</p><ul><li>Run the following command in your terminal replacing &quot;my-project-name&quot; with your project’s name:</li></ul><pre>npx create-react-app my-project-name</pre><ul><li>Change into your new project directory:</li></ul><pre>cd my-project-name</pre><h4>Tailwind CSS</h4><p>Next up — installing Tailwind. This allows elements to be styled quickly and in a uniform way throughout the game:</p><blockquote>“The simplest and fastest way to get up and running with Tailwind CSS from scratch is with the Tailwind CLI tool“— tailwindcss.com</blockquote><p>If you’ve never installed Tailwind, I recommend following the dev team’s advice by using the CLI tool. You can learn more about it and read step-by-step instructions here: <a href="https://tailwindcss.com/docs/installation">https://tailwindcss.com/docs/installation</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m-SS0T7JeemPTar1eRf_ug.png" /></figure><h4>Storybook UI</h4><blockquote>“Storybook is an interactive directory of your UI components and their stories.” — storybook.js.org</blockquote><p>I decided to use Storybook to build out the component library for this project following a strict component-driven-development (CDD) methodology. That was great in theory, but adding this extra step to a project with such a short deadline ended up not working out. As a result, I had to abandon this approach part of the way into development.</p><p>You can see some of the earlier stories I created for my game in the project repo here: <a href="https://github.com/JawaraGordon/vibe-check/tree/main/src/stories">Vibe Check — Storybook Stories</a></p><p>You can get started with adding Storybook to your project by following their step-by-step guide here: <a href="https://storybook.js.org/docs/get-started/install">https://storybook.js.org/docs/get-started/install</a></p><p>Although I had to move away from this approach for this project, I learned enough to add CDD to my workflow for future projects — and you should too!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uFl2DSaaBzRh4g0hCQn3pA.png" /></figure><h4>Jest Testing</h4><p>Testing is vital to adding efficiency to your development process while reducing errors and bugs.</p><p>I went with Jest for this project but there are plenty of testing options to choose from. You can get started by following my guide here: <a href="https://medium.com/@jawaragordon/jest-the-delightful-javascript-testing-suite-e129390ee65">https://medium.com/@jawaragordon/jest-the-delightful-javascript-testing-suite-e129390ee65</a></p><p>Once you’re up and running, you can start the process of TDD.</p><p>Test-driven development was first introduced to me through the curriculum at my Flatiron bootcamp. We were tasked with getting tests to pass from the very first lessons — and let me tell you, it was <em>frustrating</em>!</p><p>Testing has grown on me since then, having seen first-hand why it’s so important for creating an efficient workflow, and how it saves you time when introducing new features or fixes.</p><p>TDD is like setting the rules of a puzzle before you start solving it. We start by writing the tests for our game’s functions before writing any of the code that makes them work. Sort of like creating a checklist of things for the program to do and only starting to code once you have that list. Then you can start building each part, checking items off the list one by one.</p><p>Embracing TDD is like having a safety net as you fly through the development process, ensuring every new feature performs flawlessly. It’s a disciplined way to build reliable and bug-free software that every developer should adopt.</p><h3>Bonus</h3><p>There are endless ways to transform your ideas into reality using React to build classic, 2D, or even 3D games!</p><p>Here are some suggestions from ReactJam.com:</p><p>DOM-based games using plain React: <a href="https://github.com/rune/rune-games-sdk/tree/staging/examples/sudoku">see multiplayer Sudoku</a>.</p><p>2D canvas games using plain canvas: <a href="https://github.com/pixijs/pixi-react">see React Pixi</a>.</p><p>3D canvas games using: <a href="https://github.com/pmndrs/react-three-fiber">React Three Fiber</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GGRMKKdpN16KVNEkIXmSBA.png" /></figure><h3>Designing the Game Architecture</h3><p>This is where we turn our abstract ideas into tangible components. Think of it as drafting the blueprint of your game’s world, where every component has its place and purpose. This includes creating a comprehensive list of components, each serving as a building block for our game’s structure.</p><p>Keeping track of each component on a <a href="https://trello.com/c/rr3mu5vf/2-basic-game-framework">Trello board</a> is a great place to start organizing your thoughts. This is also a good place to break down the functionality for each element before adding them to Storybook or your component library.</p><pre>Component List<br>1. Basic UI Components (Foundational Elements)<br><br>Button: For actions like starting the game, selecting options, etc.<br>InputField: For text inputs, including the vibe words entry.<br>Modal: Reusable modal component for dialogues, alerts, etc.<br>Slider: For the intensity selection feature.</pre><p>All of this planning should start to pay off as your workflow should look something like this:</p><ul><li>Write a test for the next step in your development process:</li></ul><pre>import { render, screen } from &#39;@testing-library/react&#39;;<br>import TestComponent from &#39;../components/TestComponent&#39;;<br><br>test(&#39;renders learn react link&#39;, () =&gt; {<br>  render(&lt;TestComponent /&gt;);<br>  const linkElement = screen.getByText(/thinking in react/i);<br>  expect(linkElement).toBeInTheDocument();<br><br>  expect(linkElement).toHaveAttribute(&#39;href&#39;, &#39;https://react.dev/learn/thinking-in-react&#39;);<br>});</pre><ul><li>Create a component that causes the test to go from red (failing) to green (passing):</li></ul><pre>const TestComponent = () =&gt; {<br>  return (<br>    &lt;div&gt;<br>      &lt;a<br>        href=&quot;https://react.dev/learn/thinking-in-react&quot;<br>        target=&quot;_blank&quot;<br>        rel=&quot;noopener noreferrer&quot;<br>      &gt;<br>        thinking in react<br>      &lt;/a&gt;<br>    &lt;/div&gt;<br>  );<br>};<br><br>export default TestComponent;</pre><ul><li>Build a story to view and update this component’s state:</li></ul><pre>import Test from &#39;../components/TestComponent&#39;;<br><br>export default {<br>  title: &#39;Test&#39;,<br>  component: Test<br>};<br><br>export const Default = () =&gt; &lt;Test /&gt;;</pre><p>The tight feedback loop of CDD, TDD, and error handling will allow you to fly through your component list in no time! Remember to break down each step of your game loop into individual screens, then use your diagram to map out each component for each screen, then you can fill in the blanks for each function inside of those components. What goes inside those functions? The game logic of course!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PS2v_am9yAu-BuozV2CfAg.png" /></figure><h3>Integrating Game logic</h3><p>Mileage may vary, but I ended up with four game screens of logic to implement. They included the following:</p><ul><li>Main</li><li>GameSetup</li><li>GamePlay</li><li>GameResults</li></ul><p>Each of these screens acts as a parent container, overseeing the commonly shared state and components. This structure allows for different logic on each screen while keeping consistent global conditions and state management.</p><p>Let’s take a look behind the scenes.</p><p><strong>Centralized State Management</strong>: React’s state management is key in handling global conditions like player scores, game levels, or overall game stats. This ensures that any changes in state, like player progress or game settings, are consistently updated throughout the game.</p><p><strong>Component-Specific Logic</strong>: Each screen will have its own unique logic, controlling the behavior and interactions within that specific part of the game. For example, a home screen might handle player registrations, while a gameplay screen manages the actual game mechanics.</p><p><strong>React Hooks for Lifecycle and State</strong>: React Hooks are crucial for managing the lifecycle and state of your components. The useState hook allows you to add state to your components, while the useEffect hook is perfect for handling side effects like fetching data or subscribing to a service. For game development, you might use these hooks to control animations, trigger sound effects, or update the UI based on user interactions.</p><p><strong>Implementing the Game Loop</strong>: Incorporating the game loop within React involves setting up a process that continuously updates the game state and UI. This could be managed through a combination of useEffect for triggering updates and useState to reflect the current state. For example, in a turn-based game, your loop might check for player actions, update the game state, and then render the updated state to the user.</p><p><strong>Global Conditions Handling</strong>: Global conditions like winning criteria, game over scenarios, or high scores are managed through centralized state logic. By setting up global conditions, you ensure that the game reacts appropriately to certain events, regardless of the screen or component in focus</p><p>Once you have a good understanding of how to implement your game logic, start to build out each of the components and elements from your list with pseudocode and comments for any sections that you’re unsure about. The goal is to make progress without getting stuck on one component or function for too long. You can always come back to work on challenging sections later, for now — keep moving down your checklist!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kwsGJIDVonSK2byuG6sslw.png" /></figure><h3>Sound and Music</h3><p>We’ve reached an important and often overlooked aspect of game development — sound and music. My son recently asked me why the sound was so bad in the game he was playing, almost like it was an afterthought. And I said, “It probably was!” — which is sadly the case with game audio. Due to a combination of time and financial constraints, game audio is often brought in too late, and on too small of a budget to enhance the game in the way that it should.</p><p>Audio adds a rich layer to the gaming experience, enhancing our emotional connection to the game and its characters. Understanding how to effectively synchronize audio with game events is an important part of creating a dynamic and fun gaming experience.</p><p>However, working with audio in React presents its own set of challenges from handling audio file formats to managing playback in the browser.</p><p>Yes, there are plenty of excellent React audio players to try for a project like this. Feel free to explore those options. If you’re a purist like me, then you’ll be spending time working with the HTML5 &lt;audio&gt;element.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/1*ZwPLRCFjVbzfVztttu-QpA.png" /></figure><p>I decided to make a game based around a hook of streaming music, then having players describe the song by typing words into an input that matches the song&#39;s “vibe” for points. Getting the input mechanics to work was tricky but nothing <em>too</em> crazy — the audio, on the other hand, was not.</p><p>The irony of being an audio engineer working as a web developer realizing that I didn’t have much experience working with audio in the browser was not lost on me. As I’m sure you’ve realized, there isn&#39;t much music on websites because it’s equal parts annoying and invasive. That presents a significant hurdle when using a browser for game development — its restriction on auto-playing audio. Audio can&#39;t play in modern browsers until the user interacts with the page.</p><p>This limitation means that developers need to design a user interaction (like a click or a tap) as a trigger to start audio playback. This could be a ‘Start’ button at the start of the game or any interaction within the game’s UI. While this adds an extra step for the user, it can be seamlessly integrated into the game’s flow as part of the initial game start sequence.</p><p>Another challenge is browser compatibility. Different browsers may have varied support for audio file formats, creating a situation where sounds might play correctly in one browser but not in another. This means you should only use universally supported formats like MP3 or provide multiple audio file sources in different formats.</p><p>Adding audio can turn a good game into a great one! Even if your game isn’t audio-focused, having background music and sound effects will enhance the user experience. However, integrating audio in React and managing it within the browser environment is challenging.</p><p>(I had to resubmit my game for React Jam after fixing a major bug with Safari browsers.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NvJIyDoAeApEYqbNRunfyw.png" /></figure><p>With the essential groundwork laid, we’re ready to rock onto phase three of our React game development journey. It’s crucial to ensure that you’re completely invested in your game concept, game loop, and have the right project structure because there’s no going back at this point. You should have all of your game screens and main components completely built out and ready to start testing before moving on.</p><p>Be sure to subscribe to this blog and follow me on <a href="https://www.linkedin.com/in/jawaragordon/">social media</a> to be notified about the next chapter of “Ready Player React: How to Build a Video Game with JavaScript.” <a href="https://medium.com/@jawaragordon/ready-player-react-how-to-build-a-video-game-with-javascript-part-3-be633e4adcd4">In the next installment, we’ll move into the crucial third phase: Testing</a>.</p><h3>Sources:</h3><ul><li><a href="https://react.dev/learn/installation">Installation - React</a></li><li><a href="https://tailwindcss.com/docs/installation">Installation - Tailwind CSS</a></li><li><a href="https://storybook.js.org/docs/get-started/why-storybook">Why Storybook? * Storybook docs</a></li></ul><p><a href="https://en.wikipedia.org/wiki/Test-driven_development">https://en.wikipedia.org/wiki/Test-driven_development</a></p><h3>Resources:</h3><ul><li><a href="https://jestjs.io/docs/getting-started">Getting Started · Jest</a></li><li><a href="https://www.geeksforgeeks.org/what-are-some-advantages-of-component-driven-development/">What are some advantages of Component Driven Development ? - GeeksforGeeks</a></li><li><a href="https://www.geeksforgeeks.org/test-driven-development-tdd/">What is Test Driven Development (TDD)? - GeeksforGeeks</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29b29ea93a9c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ready Player React: How to Build a Video Game with JavaScript — Part 1]]></title>
            <link>https://medium.com/@jawaragordon/ready-player-react-how-to-build-a-video-game-with-javascript-part-1-fbda59e173f5?source=rss-d4be0cf41dad------2</link>
            <guid isPermaLink="false">https://medium.com/p/fbda59e173f5</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[videogames]]></category>
            <dc:creator><![CDATA[Jawara Gordon]]></dc:creator>
            <pubDate>Sun, 14 Jan 2024 13:23:08 GMT</pubDate>
            <atom:updated>2024-02-26T21:06:46.119Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ready Player React: How to Build a Video Game With JavaScript — Part 1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C1q95VHqopHAaJhZumSy6g.png" /><figcaption>Screenshot of a development environment with a split-screen view. On the left side, there’s a code editor.</figcaption></figure><p>This four-part series is your step-by-step guide for developing a video game using the JavaScript React library. We’ll cover the entire process of creating a game, including project planning, wireframing and design, coding, testing, and deployment.</p><p>This project is designed for both brand-new and experienced devs, covering every aspect of game development from the initial idea to the final launch. Our goal is to showcase how React’s features can be effectively applied to build dynamic and engaging gaming experiences. As we progress, we’ll face many of the challenges encountered in game development and learn how to use our skills to overcome them.</p><p>If you’re ready to jump in, hit that “Start” button, and let’s go!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zKsAjsPGvqvkErqA0_WATQ.png" /></figure><h3>Getting Started</h3><p>Until recently, I hadn’t thought about React as a platform for creating games. It’s widely known for building interactive websites and apps — some of which may include simple games or game-like experiences but JavaScript is certainly not the first language people reach for in the gaming community.</p><p>Traditional game development has leaned towards engines like Unity or C++ known for their ability to handle complex graphics and interactivity. However, I recently stumbled across a hackathon called “<a href="https://reactjam.com/">React Jam</a>” that encourages developers to use React as a game development solution instead. They highlight React’s component-based architecture which offers unique advantages, like state management, and a closed feedback loop for testing as a viable approach for building games. Having React at the helm opens up a whole new world of possibilities for creating lighter, easy-to-use, and most of all FUN to program video games!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t5SmV3UtAb9mssl7dGfiOg.png" /></figure><h4><strong>Phase 1: Planning</strong></h4><p>The process of creating a video game entirely from scratch can feel overwhelming. (Especially if you choose to do it all in less than two weeks!) There are lots of moving parts to consider like art style, gaming mechanics, asset management, storage constraints, device compatibility and so much more! That’s why it’s important to start with a detailed plan.</p><p>To overcome this hurdle, I created a ‘React Game Guide GPT’ trained on the latest React docs and game development best practices. You can try it here (requires ChatGPT Plus): <a href="https://chat.openai.com/g/g-7VeFPUMCb-react-game-guide">React Game Guide</a></p><p>You can also reference the docs directly if you prefer. Regardless of your approach, the goal is to create a structured and detailed plan for each step in your development process. “<a href="https://react.dev/learn/thinking-in-react">Thinking in React</a>” is a great refresher!</p><p>Next, it’s time to choose a project management system. I decided to use a Trello board. This system provides a visual overview that organizes complex tasks into actionable items and tracks progress along the way. Here’s the finished board for my game: <a href="https://trello.com/b/9J2Bl4wf">Vibe Check — Trello</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Wsekx5IgAjOjBMi4ls0SA.png" /></figure><h4><strong>Game Concept</strong></h4><p>The next step in this phase is arguably the most important — deciding on a game concept and hook. Ask yourself these questions:</p><ul><li><strong>Who is your target audience?</strong></li><li><strong>What makes your game unique?</strong></li><li><strong>How does your game keep the player engaged?</strong></li></ul><p>The hook of your game is what grabs the player’s attention right from the start. It could be a compelling story, an interesting gameplay mechanic, or a distinctive art style. Whatever you choose, make sure it’s something that players will want to revisit over and over again.</p><p>It’s important to spend a large percentage of your project time focused on this step. There’s no point in moving forward with the rest of the phases if you don’t have a solid plan for exactly how your game will look and feel. Once you’ve brainstormed ideas for a game concept, it’s time to start thinking about the game loop.</p><h4><strong>Game Loop</strong></h4><p>Mapping out the game loop is crucial to understanding the flow and player interactions of your game. At its core, a game loop is the continuous cycle of events that keeps the game running. This loop typically starts when the game is launched and repeats until the game is closed. It consists of three primary stages: processing user input, updating the game state, and rendering the game visuals on the screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bhGhhalTjA0SFt8LkPJW6w.png" /></figure><h4><strong>Tech Stack</strong></h4><p>Choosing the right tech stack is a crucial decision that will impact both the development process and the final quality of your game. It’s important to select a stack that’s not only within your area of expertise but also powerful enough to meet the demands of your game. Sticking with technologies you’re already familiar with allows for a smoother development process, and reduces the potential for unforeseen “gotchas!” I decided to use Figma and Tailwind to fast-track the design portion while introducing test-driven development (TDD) using Jest and a Storybook UI component library to my workflow.</p><blockquote>Pro Tip: I made a huge mistake here and decided to try too many new things at once which slowed me down a lot! <strong>Don’t make the same mistake.</strong></blockquote><h4><strong>Version Control</strong></h4><p>Initializing your project repository and implementing version control are the next steps to take. This is the perfect time to establish a “Git flow” routine if you don’t already have one. Using a structured naming convention for code comments and commit messages is necessary to build consistency and readability. Trust me when I say you’ll thank yourself later when you revisit this project and actually know what those variable names mean! I’ve started using the Angular team’s system after learning about this resource: <a href="https://www.conventionalcommits.org/en/v1.0.0/#summary">Conventional Commits</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jIMCqqkOw8GFMjXidDZ9Lg.png" /></figure><h4><strong>Project Layout &amp; Structure</strong></h4><p>Next up is planning the layout and file folder system for the project. This is when you plan out how different components of the game will interact and work together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PKORNjbscNdTZEimyvV6Cg.png" /></figure><p>A Game Design Document (GDD) can be created to outline the game’s design, scoring system, and mechanics allowing for a single point of truth for any game rules or physics. You should also create a storyboard to serve as a visual representation for each game screen along with keeping a consistent style and aesthetic.</p><p>This step also includes wireframing and blueprinting the game’s interface and project folders. Mark up these documents to outline and organize what each screen of the game will look like and contain.</p><p>I’m sure you’re <em>itching to start coding already</em> — I was too, but I can’t stress enough how much this planning helped me to stay focused when I felt lost, or unsure of what to do next.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kkWcxR9wX5dkAH4BPtkjOg.png" /></figure><p>With a solid foundation in place, we’re ready to move on to the <a href="https://medium.com/@jawaragordon/ready-player-react-how-to-build-a-video-game-with-javascript-part-2-29b29ea93a9c">next phase of this project “Building”.</a> Make sure you’re fully committed to a game concept and loop with the appropriate tech stack and project structure in place before moving on to the next steps.</p><p>Don’t miss out on the next chapter of “Ready Player React: How to Build a Video Game with JavaScript” by subscribing to this blog and following me on <a href="https://www.linkedin.com/in/jawaragordon/">social media</a>. Next up, we’ll start bringing our video game to life by setting up the development environment, laying out the structure of components, and introducing the game logic — as we continue on this journey to level up your game development skills!</p><h3>Sources:</h3><ul><li><a href="https://react.dev/learn/thinking-in-react">Thinking in React - React</a></li><li><a href="https://reactjam.com/">React Jam</a></li><li><a href="https://www.gamedesigning.org/video-game-development/">What is Video Game Development? (The Complete Guide)</a></li></ul><h3>Resources:</h3><ul><li><a href="https://github.com/JawaraGordon/vibe-check">GitHub - JawaraGordon/vibe-check</a></li><li><a href="https://www.conventionalcommits.org/en/v1.0.0/#summary">Conventional Commits</a></li><li><a href="https://trello.com/">Capture, organize, and tackle your to-dos from anywhere | Trello</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fbda59e173f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Choose Your Own Adventure: NEXT.js App vs. Pages Router]]></title>
            <link>https://medium.com/@jawaragordon/choose-your-own-adventure-next-js-app-vs-pages-router-528dbf25b37f?source=rss-d4be0cf41dad------2</link>
            <guid isPermaLink="false">https://medium.com/p/528dbf25b37f</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[app-router]]></category>
            <dc:creator><![CDATA[Jawara Gordon]]></dc:creator>
            <pubDate>Sun, 01 Oct 2023 22:10:15 GMT</pubDate>
            <atom:updated>2024-05-13T17:20:14.663Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dZu13qi1hzSToB6Y2Ei64Q.png" /></figure><blockquote>“Next.js is a React framework for building full-stack web applications.” — NEXTjs.org</blockquote><h3>What is Next.js?</h3><p>In the crowded JavaScript framework space, Next.js stands out from the crowd. This streamlined tool allows developers to create modern web applications quickly and efficiently.</p><p>Imagine combining the power of React, with the added bonus of server-side rendering and static site generation. The beauty of Next.js lies in its simplicity, enabling developers to focus on what truly matters — creating exceptional user experiences. Whether you’re building a personal blog or a dynamic enterprise application, Next.js will transform your coding journey from an uphill battle to a fun-filled adventure!</p><p>Let’s dive into a brief history of Next.js, build a new app from scratch, and decide which routing option works best for your next project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*73MrVHtt0Z_w92q1BofVDg.png" /></figure><h4>A Fork In The Road</h4><p>Rooted in the need for better performance, scalability, and efficiency, Next.js was introduced in October 2016 by Vercel (formerly known as Zeit). This lightweight framework was designed with an emphasis on convention over configuration. Next’s out-of-the-box server-side rendering, routing, and tooling is a direct response to the challenges faced in single-page applications (SPAs), such as SEO optimization, load times, and code splitting.</p><p>By addressing these issues, Next.js continues to gain popularity within the React community while contining to adapt to the ever-changing landscape of web development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*26LxDs-8saIsxm9B" /><figcaption>Photo by <a href="https://unsplash.com/@miteneva?utm_source=medium&amp;utm_medium=referral">Maria Teneva</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Getting Started</h3><p>This guide assumes you’re familiar with using command line tools along with having a basic understanding of Node.js, React, and vanilla JavaScript.</p><h4>Installation</h4><p>Next.js can be completely bootstrapped through an automatic installation process called `create-next-app`.</p><p>To create a new project, run this command in your terminal:</p><pre><br>$ npx create-next-app@latest</pre><p>You’ll see the following prompts:</p><pre><br>What is your project named? my-app<br>Would you like to use TypeScript? No / Yes<br>Would you like to use ESLint? No / Yes<br>Would you like to use Tailwind CSS? No / Yes<br>Would you like to use `src/` directory? No / Yes<br>Would you like to use App Router? (recommended) No / Yes<br>Would you like to customize the default import alias (@/*)? No / Yes<br>What import alias would you like configured? @/*<br></pre><p>Choose the prompts that work best for you and remember — <strong>you can always add more dependencies later. </strong>Next.js ships with TypeScript, ESLint, and Tailwind CSS by default in addition to an optional `src` directory to separate application code from configuration files.</p><p><strong>Note</strong>: <em>This example uses TypeScript, however replacing .tsx with .js will yield the same results.</em></p><p>Create-next-app will generate a folder with your project name and install the required dependencies.</p><p><strong>You also have the option to do a manual installation.</strong></p><p>To install manually, add these packages:</p><pre><br>$ npm install next@latest react@latest react-dom@latest<br></pre><p>Open your `package.json` file and add the following scripts:</p><pre><br>{<br> “scripts”: {<br> “dev”: “next dev”,<br> “build”: “next build”,<br> “start”: “next start”,<br> “lint”: “next lint”<br> }<br>}<br></pre><p>These scripts refer to different stages of your development cycle:</p><ul><li>`<strong>dev</strong>`: runs `next dev` to start Next.js in development mode.</li><li>`<strong>build</strong>`: runs `next build` to build the application for production usage.</li><li>`<strong>start</strong>`: runs `next start` to start a Next.js production server.</li><li>`<strong>lint</strong>`: runs `next lint` to set up Next.js’ built-in ESLint configuration.</li></ul><h3>Project Structure</h3><p>Next.js uses file-system routing, which means the routes in your application are determined by how you structure your files. This convention requires you to make a big decision at the start of any new project. <strong>App Router vs. Pages Router — </strong>which<strong> </strong>one should you choose?</p><p>Let’s take a closer look at the pros and cons of each, and what this means for your application:</p><h4>App Router</h4><p>The App Router is Next.js’s answer to advanced routing needs, allowing for more complex patterns and setups.</p><p><strong>Structure</strong>:</p><p>Introducing a shift away from traditional structures, app router adopts a more modular and organized directory approach:</p><pre>└── app<br>    ├── about<br>    │   └── page.tsx<br>    ├── globals.css<br>    ├── layout.tsx<br>    ├── login<br>    │   └── page.tsx<br>    ├── page.js <br>    └── team<br>        └── route.tsx</pre><p><strong>Features</strong>:</p><ol><li><strong>Client and Server Components</strong>: Allows differentiation between components that run on the server versus the client. This offers greater optimization, especially when dealing with server-side operations versus client-side interactivity.</li><li><strong>Easy Layouts</strong>: With `layout.js`, managing layouts becomes easier and more intuitive. Nested layouts further simplify hierarchical page structures.</li><li><strong>Server Actions</strong>: This feature lets you execute server-side code based on client-side events.</li><li><strong>Intercepting Routes</strong>: Provides a mechanism to render different components based on conditions, even if the URL remains the same.</li><li><strong>Parallel Routing</strong>: Lets you render multiple pages on the same URL, enhancing flexibility.</li><li><strong>Built-in SEO</strong>: App router introduces a built-in approach to handling metadata, making the `next/head` redundant.</li></ol><p><strong>Pros</strong></p><ul><li><strong>Flexibility</strong>: Adapt to a wide range of routing scenarios.</li><li><strong>Dynamic Data Handling</strong>: Seamlessly integrates with varying data sources.</li></ul><p><strong>Cons</strong></p><ul><li><strong>Learning Curve</strong>: Might be overwhelming for beginners.</li><li><strong>Optimization</strong>: Requires additional efforts to ensure best performance.</li></ul><h4>Pages Router</h4><p>The Pages Routing system is both intuitive and effective. By adding React components to the `pages` directory, routes are automatically established.</p><p><strong>Structure</strong>:</p><p>Historically Next.js used the `pages` directory to automatically generate routes based on the filenames:</p><pre>└── pages<br>    ├── about.tsx<br>    ├── index.tsx<br>    └── team.tsx</pre><p><strong>Features</strong>:</p><ol><li><strong>Automatic Routes</strong>: Adding a `.js` or `.tsx` file to the `pages` directory automatically creates a route.</li><li><strong>SEO Optimization</strong>:With the `next/head` component, SEO optimization was straightforward.</li><li><strong>Data Fetching Methods</strong>: Included `<strong>getStaticProps</strong>`, `<strong>getServerSideProps</strong>`, and `<strong>getStaticPaths</strong>` for fetching data.</li><li><strong>Custom Document &amp; App Component</strong>: Allowed for customization of the overall document structure and layout.</li></ol><p><strong>Pros</strong></p><ul><li><strong>Efficiency</strong>: Next.js streamlines the development process, saving time.</li><li><strong>SEO Ready</strong>: With server-side rendering, content is ready for both users and search engines.</li></ul><p><strong>Cons</strong></p><ul><li><strong>Complex Routes</strong>: Might not be ideal for intricate routing needs.</li><li><strong>Naming Convention</strong>: The structure is tied to file and folder names, demanding accurate naming.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7yidfzduHexuc5AlVmu4Gg@2x.jpeg" /><figcaption>Photo by Paulo Silva on Unsplash</figcaption></figure><h4>Making A Decision</h4><p>So, how do you decide which way to go and what’s right for your project?</p><blockquote>“For new applications, we recommend using the App Router.” — NEXTjs.org</blockquote><p>The Next.js team has clearly gone all-in on app router — but consider the following before making a decision:</p><p>• <strong>Project scope</strong>: Is it a minimalistic blog or a multifaceted e-commerce platform?</p><p>• <strong>Scalability</strong>: Factor in future growth and scaling needs.</p><blockquote>“The Pages Router is the original Next.js router, […] and continues to be supported for older Next.js applications.” — NEXTjs.org</blockquote><p>Your routing choice today can and <em>will</em> influence your project’s evolution so choose wisely!</p><h3>App Router</h3><p>Here’s how to get started using ‘app router’.</p><p>Create an `app/` folder, then add a `layout.tsx` and `page.tsx` file:</p><pre><br>// app/layout.tsx<br><br>export default function RootLayout({<br> children,<br>}: {<br> children: React.ReactNode<br>}) {<br> return (<br> &lt;html lang=&quot;en&quot;&gt;<br> &lt;body&gt;{children}&lt;/body&gt;<br> &lt;/html&gt;<br> );<br>}</pre><pre>// app/page.tsx<br>export default function Page() {<br> return &lt;h1&gt;Hello, Next.js!&lt;/h1&gt;;<br>}</pre><p>If you forget to create `layout.tsx`, Next.js will automatically add this file when running the development server with `next dev`.</p><h3>Pages Router</h3><p>If you prefer to use the Pages Router, you should create a `pages/` directory at the root of your project.</p><pre><br>// pages/index.tsx<br><br>export default function Page() {<br> return &lt;h1&gt;Hello, Next.js!&lt;/h1&gt;;<br>}<br></pre><pre>// pages/_app.tsx<br>import type { AppProps } from &#39;next/app&#39;<br> <br>export default function App({ Component, pageProps }: AppProps) {<br> return &lt;Component {…pageProps} /&gt;;<br>}</pre><pre>// pages/_document.tsx<br>import { Html, Head, Main, NextScript } from &#39;next/document&#39;<br> <br>export default function Document() {<br> return (<br> &lt;Html&gt;<br> &lt;Head /&gt;<br> &lt;body&gt;<br> &lt;Main /&gt;<br> &lt;NextScript /&gt;<br> &lt;/body&gt;<br> &lt;/Html&gt;<br> );<br>}</pre><p><strong>Pro Tip: </strong><br>You can use both routers in the same project with `app` routes prioritized over `pages` — but it’s recommend to use only <strong>one</strong> to avoid confusion.</p><h4>Final Steps</h4><p>Create a `public` folder to store static assets such as images, fonts, etc. Files inside the `public` directory can then be referenced by your code starting from the base URL.</p><p>Additional folders dynamic routes and config files can be added to the project structure by referencing this list: <a href="https://nextjs.org/docs/getting-started/project-structure">Project Structure</a></p><h4>Run the Development Server</h4><p>To see all your work come to life, run:</p><pre>$ npm run dev</pre><p>Visit [<a href="http://localhost:3000](http://localhost:3000)">http://localhost:3000](http://localhost:3000)</a> to view your application.</p><p>Edit `app/layout.tsx` (or `pages/index.tsx`) to see your changes compile in your browser.</p><p><strong>Success!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IFUaMBpc3f5LN6HOv7ZRYg@2x.jpeg" /><figcaption>Photo by Benjamin Davies on Unsplash</figcaption></figure><h3>The Path Forward</h3><p>App Router introduces a significant evolution in the Next.js framework, offering advanced features and enhanced flexibility. While the Pages Router will remain sufficient for many applications, the recommended App Router’s capabilities offer greater control and functionality.</p><p>Keep in mind, choosing between the two routers isn’t about “right” or “wrong” but about what best fits your project’s needs. Whether you’re new to Next.js or an experienced user looking to adapt the latest features, this guide aims to point you in the right direction for your next project!</p><h3>Sources:</h3><p>- <a href="https://nextjs.org/blog/next-2-0">https://nextjs.org/blog/next-2-0</a><br>- <a href="https://vercel.com/">https://vercel.com</a><br>- <a href="https://nextjs.org/docs">https://nextjs.org/docs</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=528dbf25b37f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Parents Who Code: An Open (Love) Letter]]></title>
            <link>https://medium.com/@jawaragordon/parents-who-code-an-open-love-letter-13d46cc7e2a0?source=rss-d4be0cf41dad------2</link>
            <guid isPermaLink="false">https://medium.com/p/13d46cc7e2a0</guid>
            <category><![CDATA[parenting]]></category>
            <category><![CDATA[open-letter]]></category>
            <category><![CDATA[inspiration]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Jawara Gordon]]></dc:creator>
            <pubDate>Sun, 24 Sep 2023 15:03:12 GMT</pubDate>
            <atom:updated>2023-09-25T01:11:11.273Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GDJSIlM0G-_fgMeKEyzTGQ.png" /></figure><p>Dear Parents Who Code,</p><p>Your stories have inspired me to keep going during the hardest times — the “I made a huge mistake” moments, and the sleepless nights full of doubt.</p><p>You’ve shown me that those feelings are justified because we are doing the <strong><em>impossible</em></strong>.</p><p>Parenting is a non-stop whirlwind of chaos and it’s easy to get lost in the grind. Housekeeping, scheduling, medical emergencies, birthday parties, and school activities are just some of the obstacles we face on a daily basis.</p><p>The drive to push forward under such extreme stress is a testament to our resilience. Balancing midnight feedings with coding projects is not for the faint of heart. Navigating the ever-changing world of tech while staying present with your family is one of the biggest challenges we face.</p><p>As we tackle this duality, it’s important to recognize the skills we develop as parents can beautifully complement our coding prowess. Empathy, communication, and adaptability not only enrich our parenting journeys but also our ability to write clean, efficient code. Patience, problem-solving, and a growth mindset can be directly applied to developing innovative solutions. Leadership, <a href="https://medium.com/@jawaragordon/letting-go-of-code-the-zen-approach-to-programming-bdd5e2b25ba3">mindfulness</a>, and conflict resolution are some of the greatest soft skills we bring to any team.</p><p>One of the most remarkable aspects of this journey is how this dual role enables us to ignite curiosity in our children. When we share our passion for coding, we encourage them to dive into the world of technology while cultivating their own interests. What’s truly special is that we have a unique opportunity to teach them not only how to harness the full potential of technology but, most importantly, how to use it safely, respectfully, and responsibly.</p><p>To all parents who code, THANK YOU. Your path is a beautiful mosaic of love and dedication. While you move through this intricate dance of parenthood and programming, remember that your commitment serves as both a beacon of inspiration and a foundation to reach unimaginable heights for generations to come.</p><p>With admiration and solidarity,</p><p>Jawara Gordon</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13d46cc7e2a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>