<?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 stevemmitchell on Medium]]></title>
        <description><![CDATA[Stories by stevemmitchell on Medium]]></description>
        <link>https://medium.com/@sstevemmitchell?source=rss-44bc7e8f5525------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*EimTRvqbja1DcBadRkpcnw.jpeg</url>
            <title>Stories by stevemmitchell on Medium</title>
            <link>https://medium.com/@sstevemmitchell?source=rss-44bc7e8f5525------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 12:03:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sstevemmitchell/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[The Invisible Frame: How Aspect Ratio Quietly Runs Your Life]]></title>
            <link>https://medium.com/@sstevemmitchell/the-invisible-frame-how-aspect-ratio-quietly-runs-your-life-39e118e438e3?source=rss-44bc7e8f5525------2</link>
            <guid isPermaLink="false">https://medium.com/p/39e118e438e3</guid>
            <category><![CDATA[frames]]></category>
            <category><![CDATA[aspect-oriented]]></category>
            <dc:creator><![CDATA[stevemmitchell]]></dc:creator>
            <pubDate>Wed, 14 Oct 2026 03:44:37 GMT</pubDate>
            <atom:updated>2026-10-14T03:44:37.854Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Every screen you’ve ever stared at had a shape. That shape was a decision and it’s been talking to you the whole time.</em></p><p>Last night I watched a film shot in 2.39:1 the sweeping, panoramic widescreen that directors reach for when they want you to feel small inside something vast. I watched it on my phone, which meant a third of the screen was black bars and the bottom sliver was a “continue watching” bar I couldn’t dismiss.</p><figure><img alt="Aspect Ratio" src="https://cdn-images-1.medium.com/max/1024/1*4U43HYdV8HKnPEjKO9gn4A.png" /></figure><p>The movie was still beautiful. But it was beautiful the way a symphony is beautiful through a single earbud.</p><p>We almost never think about aspect ratio. It’s the quiet constant behind every image we consume: the frame inside the frame. And yet it might be the single most underrated creative and commercial decision in modern media. It shapes how stories feel, how products sell, and how our brains respond to the rectangle of light we hold six inches from our faces.</p><p>So let’s talk about it.</p><h3>What Aspect Ratio Actually Is (and Isn’t)</h3><p>Strip away the jargon and the concept is simple: aspect ratio is the proportional relationship between an image’s width and its height. 16:9 means sixteen units wide for every nine units tall. 1:1 is a square. 9:16 flips the whole thing on its head.</p><p>Notice what it’s <em>not</em>: resolution. A pristine 4K frame and a grainy webcam feed can share the same aspect ratio. Resolution tells you how many pixels you have. The aspect ratio tells you what shape those pixels form. It’s architecture, not detail.</p><p>And architecture matters. The same room feels radically different with cathedral ceilings versus a low, cozy loft. The same image feels different wide versus tall, and that difference is doing psychological work whether you notice it or not.</p><h3>A Brief History of the Rectangle</h3><p>For cinema’s first few decades, the standard was 4:3 sometimes called the Academy ratio. It wasn’t chosen for artistic reasons; it was roughly the shape of a strip of 35mm film, and film was what existed. The frame was modest, almost portrait-adjacent, well suited to close-ups and faces.</p><p>Then television arrived and stole the movies’ audience. Hollywood, facing existential panic in the 1950s, needed something TV couldn’t offer. Its answer was width. Cinerama, CinemaScope, VistaVision — an entire arms race of ever-wider formats, each promising spectacle a small living-room box couldn’t match. If television was a window into your neighbor’s living room, widescreen was a window into the world.</p><p>It worked. Audiences came back for sheer scale. And 2.35:1 or thereabouts became the visual language of “cinema” a code so strong that when a modern film opens with black bars on top and bottom, we instinctively lean in.</p><p>The twist came with high-definition television. In the 1990s, engineers had to pick a shape for the HD era. The compromise they landed on was 16:9 — a middling rectangle, wider than old TV, narrower than anamorphic film. It was designed so both could fit reasonably well. And because HD became the default for screens everywhere, 16:9 became the invisible container of the internet: YouTube, Netflix on your laptop, Zoom, video games, everything.</p><p>For about twenty years, the horizontal rectangle reigned unchallenged.</p><p>Then we picked up our phones.</p><h3>The Square Interlude</h3><p>In 2010, Instagram launched with one hard rule: photos had to be square. It was partly a practical constraint — squares tiled neatly into a grid — but it became an aesthetic. The square is the most diplomatic of formats. It flatters nothing and favors nothing, forcing the subject into the center and killing the lazy left-to-right composition of landscape photography.</p><p>A generation learned to see in 1:1. Instagram eventually relaxed the constraint in 2015 (4:5 portrait became the beloved “tall post”), but the square had already done its work. It proved something important: the “correct” aspect ratio isn’t a law of physics. It’s a cultural agreement, and cultural agreements can change.</p><h3>The Vertical Revolution</h3><p>Here’s a sentence that would have sounded absurd in 2010: the most dominant format in the world is now a video shot vertically, 9:16, designed to be watched one-handed.</p><p>The story of vertical video is the story of an instinct being wrong. For years, vertical video was a punchline. There was even a name for the mockery “Vertical Video Syndrome” and public service announcements begging people to turn their phones sideways. Filmmakers scoffed. Professionals insisted that vertical was amateurish, unnatural, a crime against how human eyes actually work.</p><p>Then Snapchat normalized it. Then TikTok detonated the entire internet’s layout. Then Instagram, YouTube, Facebook, and LinkedIn every horizontal-native platform on Earth scrambled to bolt vertical feeds onto their products.</p><p>What happened? The mobile phone happened. It’s the screen people actually use, and it’s shaped like a vertical rectangle. Content didn’t defeat physics; it surrendered to it. When the entire audience is holding a tall screen in one hand, the tall frame isn’t a gimmick. It’s the water everyone’s swimming in.</p><p>I think the lesson generalizes far beyond video: formats don’t win because they’re better. They win because they match the device, the posture, and the moment.</p><h3>The Psychology of Shape</h3><p>So what does each shape actually <em>say</em>? A rough field guide:</p><p>Wide formats (16:9, 2.39:1) speak the language of <em>worlds</em>. Landscapes, cities, crowds, car chases, two people seated at opposite ends of a frame with all their unspoken distance between them. Width implies space, geography, scale. It’s the format of spectacle and objectivity — the camera as a window onto somewhere.</p><p>Tall formats (9:16, 4:5) speak the language of <em>people</em>. A vertical frame is a portrait by definition: one face, one body, one voice, delivered close. There’s nowhere to hide. Vertical video is inherently intimate, which is why it supercharges parasocial connection the person on screen appears larger than life, but closer than life, talking directly to <em>you</em>. It’s the format of presence.</p><p>Squares (1:1) speak the language of <em>neutrality</em>. Balance, symmetry, centering. Nothing is prioritized; everything is presented. It’s the Switzerland of aspect ratios.</p><p>None of this is accidental. Filmmakers know it, advertisers know it, and the platforms — through years of A/B testing on billions of people — know it better than anyone. When TikTok fills your entire vertical screen with a human face, that’s not laziness. That’s engineering aimed directly at your attention.</p><h3>Aspect Ratio as a Storytelling Choice</h3><p>The most interesting directors have stopped treating aspect ratio as a fixed container and started treating it as a narrative instrument.</p><p>Wes Anderson’s <em>The Grand Budapest Hotel</em> cycles through three ratios to mark three eras: the 1930s in 4:3 (the shape of film at that time), the 1960s in widescreen, the 1980s in 16:9. The screen itself becomes a time machine.</p><p>Xavier Dolan’s <em>Mommy</em> is mostly a claustrophobic 1:1 mother and son boxed in by grief, debt, and each other. Then, in a moment of joy, the son physically pulls the frame wider with his hands, and the screen explodes into full widescreen. It’s one of the great moments in modern cinema, and it’s made entirely of aspect ratio.</p><p><em>The Lighthouse</em> sits at a near-square 1.19:1, evoking early film to make isolation feel historical and inescapable. Documentaries shoot interview subjects in vertical while cutting to wide B-roll to separate “the person” from “the world.”</p><p>The principle underneath all of these: the frame is an opinion. Choosing where the edges go is choosing what the audience is allowed to feel. Wide says <em>look at all this</em>. Tall says <em>look at me</em>. The best creators choose deliberately.</p><h3>A Practical Field Guide for Creators</h3><p>If you make things videos, photos, ads, decks here’s what I’d actually take from all this:</p><p>1. Choose by intent, not habit. “We’ve always made 16:9” is not a strategy. Ask: is this content about a world (wide) or a person (tall)? Is the moment intimate or epic?</p><p>2. Match the device and the posture. Desktop at work leans horizontal. Phone in bed, phone in line at the coffee shop, phone on the toilet — vertical. You’re not choosing what looks best in a studio; you’re choosing what fits a hand.</p><p>3. Shoot protectively. If one asset must live on many platforms, frame with the center safe and keep critical elements away from the edges. A horizontal master can be cropped to vertical you can even <a href="https://www.onlineresizeimage.com/change-image-aspect-ratio/">change image aspect ratio</a> in seconds with free online tools but you can’t crop back what you never shot.</p><p>4. Respect the face. Vertical formats live and die on faces. Big, centered, expressive. If your vertical video’s subject is a tiny person in a distant landscape, you’ve made a horizontal video in a vertical costume.</p><p>5. Don’t fake it. Pasting a horizontal video onto a vertical canvas with blurry bars is the modern equivalent of letterboxing a TV broadcast technically acceptable, emotionally dead. If vertical is the destination, design for vertical.</p><p>6. Use ratio changes sparingly. One deliberate ratio shift in a project is a statement. Five is a migraine.</p><h3>The Rectangle Might Not Survive</h3><p>Here’s the strange part: just as we’ve all internalized the great formats, the fixed rectangle itself may be dissolving.</p><p>Foldable phones change shape mid-use. AR headsets and spatial computing don’t really have “screens” at all they have <em>places</em>, and you can hang content of any size anywhere in a room. If you’ve watched video in a VR headset, you know the feeling: the concept of a fixed frame starts to feel quaint. Why should the movie decide how big it is, when the viewer could?</p><p>I suspect the near future looks like this: content that carries information about its own shape but lets the <em>context</em> — the device, the room, the viewer — make the final call. Aspect ratio stops being a lock and becomes a suggestion. The creator proposes; the environment disposes.</p><p>Which would be a fitting end, in a way. For 130 years, the frame was the one thing everyone agreed on. Letting go of it might be the most interesting creative opportunity of the next decade.</p><h3>The First Decision You Forgot You Made</h3><p>Every image you’ve ever seen arrived inside a decision you weren’t consulted on. The wide shot that made a battlefield feel endless. The square that made an outfit look intentional. The vertical face that made a stranger feel like a friend.</p><p>The aspect ratio is the first decision in visual storytelling, made before lighting, before camera, and before the first word of a script. It’s also the one audiences feel most and notice least.</p><p>So next time something on a screen moves you, pause for a second and ask: How tall is this? How wide? Why this shape and not another?</p><p>The answer won’t always explain the whole effect. But you’ll never look at black bars the same way again.</p><p><em>Enjoyed this? Leave a clap or two, and if you’re feeling bold, try watching your favorite film cropped to 9:16. Then tell me the frame doesn’t matter.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39e118e438e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I Stopped Reaching for a Database on Every Side Project]]></title>
            <link>https://medium.com/@sstevemmitchell/why-i-stopped-reaching-for-a-database-on-every-side-project-e61e9db2a1e6?source=rss-44bc7e8f5525------2</link>
            <guid isPermaLink="false">https://medium.com/p/e61e9db2a1e6</guid>
            <category><![CDATA[localstorage]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[stevemmitchell]]></dc:creator>
            <pubDate>Fri, 10 Jul 2026 05:59:52 GMT</pubDate>
            <atom:updated>2026-07-10T05:59:52.003Z</atom:updated>
            <content:encoded><![CDATA[<p>There’s a reflex a lot of full-stack developers pick up early: new project, new database. Spin up Postgres, define a schema, wire up an ORM, write migrations before you’ve even finished deciding what the app actually does. It’s a habit that makes sense for anything with real user accounts or data that needs to survive across devices. But somewhere along the way it stops being a decision and just becomes muscle memory, applied even to projects that never needed it in the first place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yiSZZvdyzbzE3wEM2Tyx4Q.png" /></figure><p>I noticed this most clearly while building a handful of small browser games — word games mostly, the kind with daily streaks, mistake counters, and difficulty settings that only matter to the one person playing on that one device. My first instinct on each of them was the same as always: user accounts, a database table for progress, an API route to fetch and update it. Then I actually thought about what the data was doing, and the whole backend disappeared.</p><h3>What the Data Actually Needed</h3><p>A streak counter doesn’t need to survive a server outage. It doesn’t need to be queried by anyone but the browser it lives in. It doesn’t need row-level security, foreign keys, or a migration history. It needs to persist across page reloads on one device, for one person, and that’s it. The moment I framed it that way, the database stopped being the obvious choice and started looking like overhead I’d added out of habit rather than need.</p><p>localStorage turned out to cover almost the entire feature set these games actually needed: current streak, best streak, today&#39;s puzzle state, hard-mode preference, mistake count. All of it is small, all of it is scoped to one browser, and all of it can be written and read synchronously with a two-line API that ships in every browser without a single dependency.</p><pre>// Saving progress after a round<br>function saveStreak(current, best) {<br>  localStorage.setItem(&#39;streak&#39;, JSON.stringify({ current, best }));<br>}</pre><pre>// Reading it back on load<br>function loadStreak() {<br>  const saved = localStorage.getItem(&#39;streak&#39;);<br>  return saved ? JSON.parse(saved) : { current: 0, best: 0 };<br>}</pre><p>That’s genuinely most of the persistence layer for a casual game. No auth flow, no API route, no server round-trip that has to succeed before the UI can update. The game just works, instantly, the moment the page loads.</p><h3>The Trade-Offs Worth Being Honest About</h3><p>None of this is a universal argument against databases — it’s an argument against defaulting to one without checking whether the problem actually calls for it. LocalStorage has real limits, and pretending otherwise just trades one bad habit for another.</p><p>It’s tied to a single browser on a single device, so a streak built up on a phone won’t show up on a laptop. It’s capped at roughly five to ten megabytes depending on the browser, which is plenty for game state but nowhere near enough for anything resembling real application data. It’s also trivially editable by anyone who opens dev tools, which is a non-issue for a personal streak counter and an immediate disqualifier for anything involving money, permissions, or another person’s data.</p><p>The honest rule I’ve settled on is pretty simple: if the data is personal, small, and disposable, localStorage is usually the right call and a database is often just ceremony. The moment the data needs to be shared across devices, verified server-side, or trusted for anything with real stakes, that’s the signal to bring a backend back into the picture.</p><h3>Where This Shows Up in Practice</h3><p>This pattern ended up shaping a handful of the word games I’ve shipped — an unlimited Wordle clone, a Connections-style grouping game, a numeric guessing game — all of which track streaks and preferences entirely client-side. It also applies a level up, to search-heavy tools like <a href="https://unscrambleit.net/">Unscramble It</a>, where the actual word-lookup logic runs entirely in-browser against a preloaded dictionary structure, with no server round-trip needed to answer “what words can I make from these letters.” Once the core computation doesn’t need a server, a lot of the surrounding architecture gets to disappear along with it.</p><p>It’s a small shift in thinking, but it changes how a project starts. Instead of asking “what’s my schema going to look like,” the first question becomes “does this actually need to leave the browser at all.” More often than I expected, the answer is no.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e61e9db2a1e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>