<?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 Arissa Fram on Medium]]></title>
        <description><![CDATA[Stories by Arissa Fram on Medium]]></description>
        <link>https://medium.com/@arissafram?source=rss-9e1f411e7344------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*y_CO1__gRJueQZWykCVZxw.jpeg</url>
            <title>Stories by Arissa Fram on Medium</title>
            <link>https://medium.com/@arissafram?source=rss-9e1f411e7344------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:44:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@arissafram/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[React Jigsaw]]></title>
            <link>https://medium.com/@arissafram/react-jigsaw-1fe69e633831?source=rss-9e1f411e7344------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fe69e633831</guid>
            <category><![CDATA[javascript-game]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Arissa Fram]]></dc:creator>
            <pubDate>Mon, 11 Aug 2025 00:17:26 GMT</pubDate>
            <atom:updated>2025-09-06T13:29:30.940Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eBAhW_dr19NwgZOvpTvnLw.png" /></figure><h4>I built a customizable react jigsaw puzzle. AI helped. It was incredible and awful in equal parts.</h4><h4><strong>I like mini-games. I like to build them in vanilla JS. For ages I’ve had a puzzle on my personal site. It worked, but it was simple. Was finally inspired to rebuild it in React with help from our friend AI. Here are all of my thoughts.</strong></h4><p>There’s no way I could have coaxed the AI into doing what it did without my years of experience and yet there’s no way I could have built this without the AI on years of experience alone.</p><p>Maybe I could have. It would’ve taken six months at least. Probably couldn’t have. I’d have needed far more packages and polyfills.</p><figure><a href="https://arissafram.github.io/react-jigsaw/demo/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IycK3LUm7xS2gGcp18uU8w.png" /></a><figcaption><a href="https://arissafram.github.io/react-jigsaw/demo/">https://arissafram.github.io/react-jigsaw/demo/</a></figcaption></figure><p>I understand the code. I can pinpoint the bugs and the flaws. I know when something is over-engineered or doesn’t make sense, if it’s written well or written poorly, but I don’t understand bezier curves well enough to have written the generate path logic from scratch. Forcing pointer events to work with touch devices makes my head spin. It would have taken many days to sort through my publish demo bugs.</p><p>For example, the AI’s initial attempts at turning my explanation of a puzzle piece into an svg was rough, but I’d debug and give feedback and highlight the broken bits and eventually we got there. I want to say the fault was 70/30 them (it wasn’t).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*F2FtJ-abyN7nUudC4xijiQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*CMtJAO8aaTTR9PMS1afdHg.png" /><figcaption>“Innies and outies connect the pieces. They kind of look like a neck and a head” provided these fine renderings.</figcaption></figure><p>I think the main issue was my direction. Gotta learn how to prompt is what they’re saying — prompting and pre-planning is key. I didn’t consider that the AI wouldn’t have assumptions about the way a puzzle piece should look. It was the agent’s clarification questions that finally led to a solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HGYyYWKfCPrE1hQmffZshw.png" /><figcaption>Points of clarification that seem obvious in hindsight</figcaption></figure><p>I “prompted” and I “pre-planned”, but I was too vague and my approach was more “give some general direction, answer some clarification questions, let the AI cook”. Then we’d redo the task step-by-step in a fresh branch and eventually I’d push up the work, open a PR and review it, asking questions about the bits that went over my head.</p><p>It was similar to how I work <em>without</em> AI. I like to see the messy-60-file-change-proof-of-concept then redo it with intention once I know where I’m heading. I don’t think the AI needs that. In fact, I’m sure it does not. We could’ve gotten right down to it if I had explained things better in the beginning. Now I know.</p><p>My take away is this: I’m excited about AI, but I’m a little overwhelmed. I’m overwhelmed, but it’s a damn thrill when the AI explains things to me and helps solve the hard problems and I love that I finally built a javascript puzzle that looks and feels like a real puzzle.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fe69e633831" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Amplify hosted site with Squarespace domain]]></title>
            <link>https://medium.com/@arissafram/aws-amplify-with-squarespace-domain-7d6a1505e98c?source=rss-9e1f411e7344------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d6a1505e98c</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[web-site-hosting]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[squarespace]]></category>
            <category><![CDATA[dns]]></category>
            <dc:creator><![CDATA[Arissa Fram]]></dc:creator>
            <pubDate>Fri, 17 May 2024 11:49:00 GMT</pubDate>
            <atom:updated>2025-08-11T03:58:19.092Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-inSP00TXwo8cxfsIK98ug.png" /></figure><h4>I don’t typically post on Medium, but it took me far too long to sort this out. Figured it might save someone the headache.</h4><h4>This doc will get your Amplify site live on a Squarespace domain.</h4><h4><strong>I’m not a dev ops person. I’m a frontend person dealing with change. Squarespace migrated over all of my Google domains and modified a few things in the process. The Amplify dashboard updated too. Unsure how sound these steps are, but for a low-stakes personal project it’s reliable. This drove me nuts, so a brain dump of notes for the internet.</strong></h4><h4>1. Go to your Amplify console</h4><h4>2. In the side navigation, click ‘Hosting &gt; Custom Domains’</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/299/1*EUryAwQzE1ukwyNck0v5wg.png" /></figure><h4>3. Click the ‘Add domain’ button</h4><h4>4. AWS will prompt you to enter your root domain. They want you to use Route 53. You don’t need to. If you’re using Route 53, this doc won’t help you.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V91qhumqP2nwx9ryvb3zQQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZDsUgphwgPUjie8trPFnWA.png" /></figure><ul><li>Click ‘Manual configuration</li><li>Then click ‘Configure domain’</li></ul><h4>5. Wait while AWS configures your SSL certificate</h4><h4>6. After the SSL cert is configured, you’ll see this screen populate</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tD9b5vltkfNss32c99rIfw.png" /></figure><h4>7. Now open the DNS settings for your Squarespace domain.</h4><h4>The image below is what you’ll see if you purchased your domain through Squarespace:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6XJQ_ziMGbgpzX5T8xjYiQ.png" /></figure><ul><li>Click the red trash can to delete the Squarespace Defaults (you can re-populate them later if you need to)</li></ul><h4><strong>The image below is what you’ll see if you purchased your domain through Google prior to the migration.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ECOgPJA-Fnq03YsAphUm5A.png" /></figure><ul><li>Don’t delete this</li></ul><h4>8. Now you’ll update the existing records</h4><ul><li>Click ‘ADD RECORD’</li><li>Copy your first CNAME from AWS. Add it as a CNAME, then add the data.</li><li>You do not need the . at the end of either of these. I don’t know why, I’ve always needed it in the past, but you need to delete it or it’ll error. If anyone ever reads this <em>and</em> knows why, please comment 🙃</li><li>Then copy the ANAME from AWS and add it as an ALIAS (not as an ANAME).</li><li>Then copy the other CNAME.</li><li>Your DNS settings should look like this (there may be an additional google record):</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nTXu9MItfcTK_4RmJtc9Tg.png" /></figure><h4>9. Go back to the Amplify dashboard. If you’ve done this correctly, AWS <em>will automatically verify ownership. Wait a few minutes. It does take a few minutes.</em></h4><h4>10. After ownership is verified, AWS will activate your domain. This could take 30 minutes. It’ll probably take one or two. After it’s complete, you should be able to navigate to your site with and without the subdomain.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d6a1505e98c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>