<?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 Dylan Noorland on Medium]]></title>
        <description><![CDATA[Stories by Dylan Noorland on Medium]]></description>
        <link>https://medium.com/@dylannoorland?source=rss-37036a5dd8c2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*vShp8Z3kgFB8IZHx0mTsaQ@2x.jpeg</url>
            <title>Stories by Dylan Noorland on Medium</title>
            <link>https://medium.com/@dylannoorland?source=rss-37036a5dd8c2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 04:21:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dylannoorland/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[TypeScript Variance: Why Your Types Sometimes Hate Each Other (And How to Fix It)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@dylannoorland/typescript-variance-why-your-types-sometimes-hate-each-other-and-how-to-fix-it-e26f32a6ae14?source=rss-37036a5dd8c2------2"><img src="https://cdn-images-1.medium.com/max/1240/1*cMV9k4Emk5VLFTUwMPOp2g.jpeg" width="1240"></a></p><p class="medium-feed-snippet">Understanding variance makes you better at designing APIs. Consider how users will compose your types with their own.</p><p class="medium-feed-link"><a href="https://medium.com/@dylannoorland/typescript-variance-why-your-types-sometimes-hate-each-other-and-how-to-fix-it-e26f32a6ae14?source=rss-37036a5dd8c2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@dylannoorland/typescript-variance-why-your-types-sometimes-hate-each-other-and-how-to-fix-it-e26f32a6ae14?source=rss-37036a5dd8c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/e26f32a6ae14</guid>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[computer-science]]></category>
            <dc:creator><![CDATA[Dylan Noorland]]></dc:creator>
            <pubDate>Fri, 26 Sep 2025 11:35:59 GMT</pubDate>
            <atom:updated>2025-09-26T11:36:20.208Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Three Spotify Features You Should Turn Off Right Now]]></title>
            <link>https://medium.com/@dylannoorland/three-spotify-features-you-should-turn-off-right-now-d64cc5d0bedb?source=rss-37036a5dd8c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/d64cc5d0bedb</guid>
            <category><![CDATA[software]]></category>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[spotify]]></category>
            <dc:creator><![CDATA[Dylan Noorland]]></dc:creator>
            <pubDate>Wed, 24 Sep 2025 08:47:47 GMT</pubDate>
            <atom:updated>2025-09-24T08:47:47.922Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p>Ever notice your iPhone battery draining faster when you’re jamming to your favorite playlist? Or wonder why your data cap vanishes before the month’s even halfway done? Some of Spotify’s flashiest features may be working against you</p><p>Here’s the thing: Spotify loves rolling out shiny new features. Sometimes they’re brilliant. Other times, they’re battery-draining, data-gobbling monsters disguised as “enhancements.” Let’s dive into three features you’ll want to switch off immediately.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*O2pxGKezmeC_Ok9R" /><figcaption>Photo by <a href="https://unsplash.com/@visualbyfath?utm_source=medium&amp;utm_medium=referral">Fath</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>1. Canvas: The Silent Battery Killer</h3><p>Picture this scenario. You’re commuting, phone in pocket, music flowing through your earbuds. Meanwhile, Spotify’s playing mini music videos you can’t even see. Sounds ridiculous, right? Yet that’s exactly what Canvas does — it loops short video clips behind every song, whether you’re watching or not.</p><p>These aren’t just static images. We’re talking actual video content that chomps through your data plan like a teenager at an all-you-can-eat buffet. Canvas comes enabled by default. Spotify assumes you want this feature, even though most users never realize it exists.</p><p>Think about the math here. Video content uses roughly 3–5 times more data than audio alone. If you’re streaming three hours of music daily during your commute, Canvas transforms your reasonable data usage into a monthly nightmare. Your battery suffers too — processing video drains power significantly faster than audio playback.</p><h4>How to Turn Off Canvas:</h4><ol><li>Open <strong>Spotify</strong></li><li>Tap your <strong>profile photo </strong>(top-left corner)</li><li>Select <strong>Settings and Privacy</strong></li><li>Choose <strong>Content and Display</strong></li><li>Toggle <strong>Canvas</strong> to OFF</li></ol><blockquote>Time needed: 30 seconds</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TtrYfRHUGkqwJItKXaxHcQ.jpeg" /></figure><h3>2. The “Create” Button Nobody Asked For</h3><p>Spotify’s latest interface update brought something peculiar: a massive “Create” button that’s replaced your library shortcut. It sits right there in the navigation bar, practically begging for accidental taps. Unless you’re constantly making playlists, Blends, or starting Jam sessions, this button’s about as useful as a chocolate teapot.</p><p>Here’s what makes this particularly annoying. The Create button occupies prime real estate — that bottom navigation bar you interact with constantly. Where you once had quick library access, now there’s a feature many users touch maybe once a month. If ever.</p><p>The psychology behind this change is transparent. Spotify wants users creating more collaborative content, sharing playlists, and essentially becoming unpaid brand ambassadors. But forcing this button into such a prominent position feels pushy. It’s like having a salesperson follow you around the store, constantly suggesting you “create something special.”</p><p>Muscle memory becomes your enemy here. You’ll find yourself hitting that Create button when you meant to access your library, then backing out, frustrated. It disrupts your flow. Breaks the seamless experience Spotify usually provides.</p><h4>How to Remove the Create Button:</h4><ol><li>Open <strong>Spotify</strong></li><li>Tap your <strong>profile photo</strong> (top-left corner)</li><li>Go to <strong>Settings and Privacy</strong></li><li>Select <strong>Content and Display</strong></li><li>Switch <strong>Create Button</strong> to OFF</li></ol><blockquote>Time needed: 30 seconds</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oRIm8Id_7WixEyhZxeVaoQ.jpeg" /></figure><h3>3. Mobile Data Downloads</h3><p>Downloads seem like the perfect solution for saving data, right? Cache your favorite albums while on WiFi, then listen offline during your commute. Smart thinking — until Spotify starts downloading over cellular without you realizing it.</p><p>This sneaky setting can demolish your data plan faster than streaming ever could. Imagine this: you add a high-quality album to your library, expecting it’ll download next time you’re home. Instead, Spotify immediately starts pulling down 150MB of music over LTE. Add a few playlists, and suddenly you’re looking at gigabytes of unexpected data usage.</p><p>The feature makes sense in theory. Spotify wants your music available instantly, wherever you are. But the execution assumes unlimited data plans are universal. They’re not. Many users still juggle limited monthly allowances, and surprise downloads can trigger overage charges that’ll make your eyes water.</p><p>What’s particularly frustrating is how this setting hides among other preferences. You won’t stumble across it naturally. Most users discover it exists only after receiving a shocking phone bill or a “you’ve used 90% of your data” warning halfway through the month.</p><h4>How to Stop Mobile Data Downloads:</h4><ol><li>Open <strong>Spotify</strong></li><li>Tap your <strong>profile photo</strong> (top-left corner)</li><li>Select <strong>Data Saver and Offline</strong></li><li>Toggle <strong>Download using cellular</strong> to OFF</li></ol><blockquote>Time needed: 30 seconds</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l775hCO0qd5Ho-V_JIOYIQ.jpeg" /></figure><h3>The Bigger Picture</h3><p>These three features share something telling — they all prioritize Spotify’s goals over user experience. Canvas keeps you engaged visually (even when you’re not looking). The Create button pushes social features. Mobile downloads ensure instant gratification.</p><p>None of these inherently improve how you enjoy music. They’re growth hacks dressed up as features, designed to boost engagement metrics and user retention stats. But at what cost? Your battery life, data plan, and seamless experience all take hits.</p><p>Modern apps increasingly blur the line between helpful features and corporate objectives. Spotify isn’t alone here — most major platforms pull similar tricks. The difference is that music streaming should be simple. Press play, enjoy tunes, get on with life. These extra features complicate that beautiful simplicity.</p><h3>Taking Back Control</h3><p>Here’s the beautiful part: you can customize Spotify to work exactly how you want. Those default settings are suggestions, not requirements. By spending five minutes in the settings menu, you transform Spotify from a bloated, battery-draining app into a lean music machine.</p><p>Consider this your periodic reminder to audit your app settings. Not just Spotify — everything. Companies constantly add features through updates, often enabling them by default. What worked perfectly last month might be wasting resources today. Stay vigilant.</p><p>The ideal Spotify experience differs for everyone. Maybe you love Canvas and collaborative playlists. That’s cool — keep them enabled. But if you’re like most users who just want music without the bells and whistles, these tweaks will dramatically improve your experience.</p><p>Remember: technology should adapt to your life, not the other way around. Don’t accept default settings just because they exist. Question every feature. If it doesn’t actively improve your experience, it’s probably working against you. Switch it off, simplify your digital life, and get back to what matters — the music.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d64cc5d0bedb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Your Best Code Is Your Worst Enemy]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@dylannoorland/why-your-best-code-is-your-worst-enemy-1db4d67e57c5?source=rss-37036a5dd8c2------2"><img src="https://cdn-images-1.medium.com/max/2600/0*ww1EtvHjfq9OzVSl" width="6000"></a></p><p class="medium-feed-snippet">Your next project doesn&#x2019;t need perfect architecture. It needs day one&#x200A;&#x2014;&#x200A;the first ugly version live where real humans can break it and&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@dylannoorland/why-your-best-code-is-your-worst-enemy-1db4d67e57c5?source=rss-37036a5dd8c2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@dylannoorland/why-your-best-code-is-your-worst-enemy-1db4d67e57c5?source=rss-37036a5dd8c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/1db4d67e57c5</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[indie]]></category>
            <dc:creator><![CDATA[Dylan Noorland]]></dc:creator>
            <pubDate>Mon, 22 Sep 2025 19:39:28 GMT</pubDate>
            <atom:updated>2025-09-22T19:39:28.723Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
        </item>
        <item>
            <title><![CDATA[The $1500 bug and the art of system design]]></title>
            <link>https://medium.com/@dylannoorland/the-1500-dollar-bug-a3386dbf1260?source=rss-37036a5dd8c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3386dbf1260</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[solopreneur]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Dylan Noorland]]></dc:creator>
            <pubDate>Wed, 10 Sep 2025 15:13:35 GMT</pubDate>
            <atom:updated>2025-09-12T07:24:56.074Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>The $1,500 bug and the art of system design</h3><p>A user in South Korea accidentally paid $1,500 for my $30 yearly subscription. After processing the refund and apologizing, I sat at my desk staring at the currency conversion code that had caused this disaster. The immediate fixed seemed pretty obvious. Just add validation, check the decimal handling, test more edge cases. But something deeper was bothering me.</p><p>The truth was uncomfortable but undeniable: I had no idea how this code actually worked.</p><p>Sure, I had integrated it and connected the APIs. I parsed the responses and made the numbers appear in the right places. But after trying many different things, I just couldn’t figure out why this anomaly had happened. I realized that I didn’t understand the full intricacies of how and where the conversion from Korean won to dollars went wrong.</p><p>So I made the decision to delete the currency conversion feature. From that point forward, every country would see prices in USD only. Take it or leave it.</p><p>This moment taught me that you cannot effectively own code you don’t understand. And that the world of solo develoment, everything you build becomes your responsibility alone.</p><p>Finally, while writing this article, I found the culprit. KRW/JPY are zero-decimal in Stripe. Multiplying by 100 causes 100x charges.</p><figure><img alt="The Tower of Babel — By Pieter Brueghel the Elder" src="https://cdn-images-1.medium.com/max/1024/1*QE9_YAfCr6upwoSFTCTgNQ.jpeg" /><figcaption>The Tower of Babel — by Pieter Brueghel the Elder</figcaption></figure><h3>The weight of what you pretend to know</h3><p>The conversion code had mostly worked. It had successfully handled thousands of transactions before this one failure. I couldn’t shake a growing unease about what else might be lurking in that code. When the next person gets charged their mortgage payment for my little app, would I even know where to begin debugging?</p><p>As a solo developer, you don’t have the luxury of a teammate who specializes in payment systems. When something breaks at 3 AM, it’s just you, your code, and the sinking realization that you’re in over your head. The feature had become a mental liability I couldn’t afford. Every transaction was essentially a dice roll with someone else’s money.</p><p>This realization about cognitive load would reshape how I thought about making design decisions going forward. The question wasn’t whether I could implement something, but whether I could truly understand and maintain it over time.</p><h3>My monorepo ate my sanity</h3><p>I learned this lesson about cognitive limits repeatedly, often the hard way. Consider my project structure; everything lived in one massive repository. The installer built with Rust and Tauri, the Windows service, the Nuxt.js website, the Node.js server — all of it crammed into a single monolithic repository.</p><p>The logic seemed good initially. Shared dependencies would reduce duplication, unified testing would ensure consistency, and having everything in one place would simplify development. Instead, I had created a monster I could barely navigate.</p><p>The project grew so massive that finding any specific file became an archaeological expedition through layers of nested directories. I would start a build, make coffee, return to my desk, and by then forget what I was even trying to test. The breaking point came when I spent two hours debugging an issue, only to realize I had been editing the wrong files; in my own codebase. The very structure meant to simplify my work had become an obstacle.</p><p>Splitting the monorepo was an admission that my brain has finite capacity. Separate repos meant that when I was fixing the installer, the website ceased to exist in my mental model. These were boundaries of sanity, which without I would have been drowning in complexity of my own making.</p><blockquote><em>“Monorepos create accidental complexity. For small teams, multi-repo setups mean clearer boundaries and less cognitive load.”</em> — Thoughtworks Tech Radar</blockquote><h3>An expensive lesson in boring architecture</h3><p>When my application hit five million downloads, success bred overconfidence. Suddenly I felt the need to move away from Stripe’s checkout and make my own. So I embarked on building a custom payment flow, complete with smooth animations and branding that matched my application.</p><p>The conversion rate dropped slightly, but that wasn’t the real problem. The real problem was that I had unknowingly appointed myself as a payments compliance expert; without the expertise part. Every few months brought new challenges regarding regulatory updates, PCI compliance requirements, etc.</p><p>Meanwhile, Stripe’s checkout page just kept working. It was handling edge cases I didn’t even know existed. They had a <em>team</em> at their disposal who could test these edge cases — a luxury I don’t have.</p><p>Returning to Stripe’s standard checkout felt like admitting defeat at first. Now I recognize it as a smart decision. I was choosing which battles were worth fighting, and payment processing wasn’t my battle. This principle extends to any complex domain where specialized knowledge matters more than customization.</p><blockquote><em>“Innovation tokens are limited. Spend them only where it matters. Everywhere else, choose boring technology.”</em> — Dan McKinley, <em>Choose Boring Technology</em></blockquote><h3>I couldn’t stop rebuilding my website</h3><p>Perhaps nothing illustrates the danger of unchecked ambition better than my website. I rebuilt it from scratch three times, each iteration supposedly superior to the last.</p><p>I started with WordPress because it was easy. Then I rebuilt everything in Nuxt.js because I had outgrown WordPress. The second Nuxt version came because the first wasn’t <em>clean</em> enough and became a liability to maintain. The third emerged after I discovered new patterns that would make everything<em> “better”</em>. Each version was technically superior to its predecessor. I was proud of how well designed the third version was.</p><p>I also hated it.</p><p>Every time I needed to make a simple change, I had to re-learn my own code. What started as a straightforward website had transformed into a computer science exercise. Users noticed almost nothing when I launched each new version; which was painful and ironic. In fact, conversion rates actually dropped with some iterations. Users didn’t care about my elegant architecture or clever patterns. They just wanted to download the software.</p><blockquote><em>“I spent $46,000 on a redesign. It looked amazing and hurt conversions. Users didn’t care.”</em> — Michael Lynch, <em>I Regret My $46k Website Redesign</em></blockquote><blockquote><em>“The single worst strategic mistake is a complete rewrite. Netscape did it, and it killed them.”</em> — Joel Spolsky, <em>Things You Should Never Do</em></blockquote><h3>What questions do I ask now?</h3><p>That $1,500 bug fundamentally changed how I approached building systems. Before adding any feature or making any architectural decision, I force myself to answer three uncomfortable questions.</p><p>First: <strong>Do I actually understand this, or am I just hoping it works? </strong>This means more than just getting code to run. Can I explain the logic to someone else? Can I predict how it will fail? Do I understand not just the happy path but also the edge cases?</p><p>Second: <strong>Will I be able to understand this at 3 AM in six months? </strong>When I’m exhausted, stressed, and dealing with angry people, will this code make sense? Is it self-documenting enough that I won’t need to reverse-engineer my own thinking?</p><p>Third: <strong>Am I solving a real problem or just proving I’m clever?</strong> And this is a big one because it relates to ego. Does this genuinely improve the user experience, or am I just showing off my technical skills (often times to me myself and I)? <strong>Is the complexity justified by tangible benefits?</strong></p><p>The honest answers to these questions are usually humbling. More often than not, they lead to simpler solutions than my ego would prefer.</p><h3>There’s freedom in accepting your limits</h3><p>Solo development forces a confrontation with personal constraints that team environments can mask. In a team, you can have specialists. As a solo developer, you must be competent in a broad range of areas while accepting you’ll never be an expert in most of them.</p><p>This reality isn’t a weakness to overcome but a constraint to design around. These days, I deliberately choose boring, battle-tested solutions for anything that isn’t core to what makes my product unique. I build walls between different parts of my system, even when it seems inefficient, because those walls protect me from complexity overflow. I choose tools I deeply understand over ones that make flashy promises of modernity.</p><p>Most importantly, I’ve learned to say no to features that would stretch me too thin, even when users request them. Building something so complex that you’re afraid to modify it is far worse than admitting your boundaries and working within them.</p><figure><img alt="Ensō (c. 2000) by Kanjuro Shibata XX" src="https://cdn-images-1.medium.com/max/520/1*9D0IRf5-laqWBPURnDKgeQ.jpeg" /><figcaption>Ensō (c. 2000) — by Kanjuro Shibata XX</figcaption></figure><h3>The art part</h3><p>People often discuss software architecture as pure engineering. But I see it more as interior design for your mind. You’re creating a space where you’ll spend countless hours, a space that needs to remain navigable even when you’re exhausted or stressed.</p><p>Every architectural decision shapes this mental space. Complex abstractions might be intellectually satisfying, but can you navigate them when debugging a issue? Will the clever patterns you’re building make sense when you return to the code months later? The creative challenge is building a system that fits the natural contours of your thinking.</p><p>I know that this is both abstract and deeply subjective. The key is honest self-awareness about your own cognitive limits.</p><h3>This lesson keeps teaching</h3><p>The $1,500 bug continues to influence my decisions years later. It taught me that the best system design is the one you can hold in your head while everything is on fire.</p><p>When you’re a solo developer, you are your entire team. The kindest thing you can do for yourself is build systems you genuinely understand, even if that means doing less than what’s technically possible.</p><p>Sometimes the most courageous decision is admitting what you don’t know and building something simpler instead. Because at 3 AM, when a critical bug threatens your business and your reputation, clever code won’t save you. Understanding will.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3386dbf1260" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Solo Developing Software Used by Millions — and What I Learned]]></title>
            <link>https://medium.com/@dylannoorland/solo-developing-software-used-by-millions-and-what-i-learned-ad51b597b84a?source=rss-37036a5dd8c2------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad51b597b84a</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Dylan Noorland]]></dc:creator>
            <pubDate>Mon, 02 Jun 2025 18:04:18 GMT</pubDate>
            <atom:updated>2025-06-04T08:19:48.300Z</atom:updated>
            <content:encoded><![CDATA[<h3>Solo Developing Software Used by Millions — and What I Learned</h3><p>Creating something that reaches millions of people is a dream for many developers. But what happens when that same project becomes impossible to sustain?</p><p>That’s the story of <strong>Roshade</strong>, a graphics installer I built to enhance Roblox visuals with realistic shaders — an experiment that exploded far beyond expectations, with over <strong>10 million downloads </strong>and a passionate community. What began as a side project quickly became a global tool used by gamers from every corner of the internet.</p><p>And then I shut it down.</p><p>This post isn’t about nostalgia or regret. It’s about the hard lessons I learned from watching a wildly popular project grow faster than I was prepared for — and why I ultimately chose to discontinue it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*mO-HL2YJmvjF0j1gaj8htw.jpeg" /><figcaption>Firebase user activity over time</figcaption></figure><h3>What Roshade Was (Briefly)</h3><p>For those unfamiliar: Roshade made it incredibly easy for Roblox players to install <strong>ReShade</strong> — a post-processing injector that can apply custom shaders like bloom, color correction, depth of field, and more. Normally, installing ReShade involved confusing steps, from manually placing DLLs to tweaking obscure config files.</p><p>Roshade changed that. One installer. One click. Instant visual upgrades.</p><p>It worked so well that the project grew almost overnight. Streamers, TikTok creators, and casual players picked it up. Before long, it had millions of users and more demand than I ever imagined.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/1*Pchw6Khf4DBnAL8aJCENog.png" /><figcaption>Before (left) and after (right)</figcaption></figure><h3>So Why Discontinue It?</h3><p>Because success isn’t just about downloads, it’s about <strong>sustainability</strong> — and I hadn’t planned for that. Here’s what I learned the hard way:</p><h4>1. Success Without a Plan Is a Hidden Liability</h4><p>I built Roshade for fun. I didn’t expect scale, support requests, patching, or server costs. But once millions of users relied on it, even minor bugs or Roblox updates created a wave of confusion. Suddenly I wasn’t just a developer — I was running customer support, QA, and infrastructure.</p><blockquote><strong>Lesson: </strong>If you build something that might scale, even as a side project, sketch out a support and maintenance model early. Success isn’t just building something people want — it’s being able to keep it running when they do.</blockquote><h4>2. Free Isn’t Free When Time Becomes Expensive</h4><p>Roshade was entirely free for a year. No ads, no upsells. That felt like the right thing to do — until it wasn’t. I was spending dozens of hours a month answering questions, making updates, and fixing issues triggered by third-party changes (like Roblox patches or antivirus false positives). There was no revenue, and no roadmap to make time for it long term.</p><blockquote><strong>Lesson: </strong>Passion can get you started. Sustainability keeps you going. Think about how your project survives after the excitement fades — whether through donations, premium tiers, or community involvement.</blockquote><h4>3. Platform Dependencies Will Break You Eventually</h4><p>Roshade relied on two moving targets: the Roblox platform, and ReShade’s injector. When any of them changed or decided to antagonize Roshade, that would become a potential breaking point. Eventually it was Roblox deciding to antagonize third-party addons that kickstarted Roshade’s downfall.</p><blockquote><strong>Lesson: </strong>If your software relies on someone else’s platform, expect<em> </em>instability.</blockquote><h4>4. You Can’t Scale Alone</h4><p>At first, it was easy to fix bugs, update documentation, or tweak features. But at scale? Not without a team. Users need translations, support forums, safe download mirrors, and guidance. I tried to do it all — but the burnout crept in.</p><blockquote><strong>Lesson:</strong> Growth means shifting from “builder” to “maintainer”. That’s a very different skillset — and one that benefits from community, delegation, or at the very least, boundaries.</blockquote><h4>5. If You Don’t Define Your Project, People Will Do It For You</h4><p>Some users thought I had built all the shaders from scratch. Others assumed ReShade was <em>my</em> technology, not the other way around. I realized too late that I hadn’t clearly communicated what Roshade actually was: a convenient installer and preset manager for someone else’s graphics framework. The result? Misunderstandings, misplaced credit, and even drama within the modding community.</p><blockquote><strong>Lesson:</strong> When you build on top of existing tools, be <strong>loudly clear </strong>about what’s yours and what isn’t. Give credit. Explain your value-add. If you don’t tell people what your project is, they’ll fill in the blanks — and that rarely works in your favor.</blockquote><h3>Would I do it again?</h3><p>Absolutely. Building Roshade was one of the most rewarding challenges of my life. But I’d do it differently — with a clearer plan, stronger foundation, and a better relationship with community and scale.</p><p>Roshade is now discontinued, but it taught me more than any textbook ever could about product-market fit, technical debt, community management, and personal capacity.</p><p>If you’re working on something that’s starting to gain traction, I hope this story helps you skip some of the mistakes I made.</p><p>Build smart. Plan Early. And don’t confuse virality with viability.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad51b597b84a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>