<?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 Mehdi Maiez on Medium]]></title>
        <description><![CDATA[Stories by Mehdi Maiez on Medium]]></description>
        <link>https://medium.com/@mehdimaiez?source=rss-808ea30ba269------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*j2fShW41wzxbHI_IB_t2ig.jpeg</url>
            <title>Stories by Mehdi Maiez on Medium</title>
            <link>https://medium.com/@mehdimaiez?source=rss-808ea30ba269------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 10:28:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mehdimaiez/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[Vibe Coding vs. UX Design: The Dangerous Gamble of 2026]]></title>
            <link>https://medium.com/@mehdimaiez/vibe-coding-vs-ux-design-the-dangerous-gamble-of-2026-5beadbe503b0?source=rss-808ea30ba269------2</link>
            <guid isPermaLink="false">https://medium.com/p/5beadbe503b0</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[technology-trends]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Mehdi Maiez]]></dc:creator>
            <pubDate>Sun, 22 Feb 2026 14:47:44 GMT</pubDate>
            <atom:updated>2026-02-22T14:47:44.038Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R-3dsFxg2VTQKPWitk5LNg.png" /></figure><h3>Introduction: The Efficiency Trap</h3><p>The digital landscape of 2026 is moving at a frantic pace. While AI tools have democratized “creation,” they have also triggered a concerning shift: <strong>a 15–20% drop in traditional UX job postings.</strong> As recruitment cycles stretch and budgets tighten, many stakeholders are falling for the siren song of <strong>“Vibe Coding”</strong> — an intuitive, prompt-based approach to building products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jMdXxP4iqKGT4ihKcoUpqg.png" /></figure><p>But speed without direction is just a faster way to reach the wrong destination. Choosing “vibes” over UX isn’t just a trend; it’s a high-stakes market failure in the making.</p><h3>Section 1: Anatomy of a False Strategy</h3><p><strong>Vibe Coding</strong> is the antithesis of User Experience. It prioritizes the <em>feeling</em> of a builder over the <em>friction</em> of a user. While UX is a science fueled by behavioral psychology and rigorous testing, Vibe Coding is an aesthetic guess.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qIHQ5KW4Zjv0aW8XT8nofQ.png" /></figure><ul><li><strong>The Methodology Gap:</strong> UX uses empathy mapping and heatmaps; Vibe Coding uses “it looks right to me.”</li><li><strong>The Financial Toll:</strong></li><li><strong>Proactive UX:</strong> Rigorous early-stage planning reduces long-term development costs by <strong>30–50%</strong>.</li><li><strong>Reactive “Vibes”:</strong> Identifying a logic flaw <em>after</em> deployment costs <strong>10x more</strong> to fix than correcting it during the wireframe stage.</li></ul><h3>Section 2: When “Vibes” Meet Reality (Case Studies)</h3><p>The market in 2026 is unforgiving. Users have zero patience for “chaotic” interfaces, no matter how “cool” the tech behind them is.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6UQSkjvTPQZY9K_4RzlhUg.png" /></figure><p><strong>The “Vibe” Horror Story:</strong> In late 2025, a major e-commerce disruptor pivoted to an AI-driven “Vibe” interface, bypassing user testing to beat competitors to market. Within six months, they saw a <strong>15% drop in conversions</strong>. Users weren’t “vibing” with the lack of clear navigation; they were fleeing to competitors who respected their mental models.</p><h3>Section 3: The 2026 Survival Guide</h3><p>Neglecting UX in 2026 is sacrificing the <strong>sustainability</strong> of your product for the <strong>illusion</strong> of speed. In an era of infinite content and instant apps, UX expertise is the only thing that creates a “moat” around your brand.</p><ul><li><strong>Expertise over Automation:</strong> AI can build the house, but the UX Designer decides where the doors should go so people don’t walk into walls.</li><li><strong>Data over Instinct:</strong> In a complex market, your “gut feeling” is a liability. User data is your only insurance policy.</li></ul><h3>Conclusion: Don’t Code the Vibe, Design the Value</h3><p>The future belongs to those who use AI to <em>accelerate</em> UX, not <em>replace</em> it. UX Designers in 2026 must transition from “pixel pushers” to “strategic architects.” If you want your product to last until 2030, stop chasing the vibe and start solving the problem.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5beadbe503b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Systems Aren’t Dead. Manual Design Systems Are.]]></title>
            <link>https://medium.com/@mehdimaiez/design-systems-arent-dead-manual-design-systems-are-cabd67c176c2?source=rss-808ea30ba269------2</link>
            <guid isPermaLink="false">https://medium.com/p/cabd67c176c2</guid>
            <dc:creator><![CDATA[Mehdi Maiez]]></dc:creator>
            <pubDate>Mon, 26 Jan 2026 14:10:47 GMT</pubDate>
            <atom:updated>2026-01-26T14:10:47.509Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*abe_bdWF_uQ5Z46hyGL--w.jpeg" /></figure><p>Lately, every time I open LinkedIn, I see the same conversations looping endlessly.</p><p>Designers sharing UI components.<br>People debating button styles.<br>Threads arguing whether <em>this</em> design system is better than <em>that</em> one.<br>CEOs, CTOs, and lead designers are discussing design systems as if nothing fundamental has changed.</p><p>And every time, I have the same reaction: <strong>this conversation feels outdated.</strong></p><p>Not because design doesn’t matter.<br>Not because systems don’t matter.<br>But <strong>the way we talk about and build design systems hasn’t caught up with reality</strong>.</p><h3>The real problem isn’t design systems</h3><p>Let’s be clear: design systems themselves aren’t the issue. The issue is that many teams are still <strong>building and maintaining them manually</strong>, as if AI didn’t just rewrite the rules around speed, consistency, and execution.</p><p>If two companies start today:</p><ul><li>One uses AI and ready-to-use systems to generate, adapt, and enforce UI</li><li>The other hires people to manually design, document, sync, and maintain a design system</li></ul><p>The outcome is obvious.</p><p>One ships faster.<br>One iterates faster.<br>One wastes dramatically less time on things machines already do better.</p><p>This isn’t about taste or philosophy.<br>It’s about <strong>efficiency and leverage</strong>.</p><h3>What feels outdated today</h3><p>What feels outdated isn’t people — it’s <strong>how we work</strong>.</p><p>Things that made sense a few years ago now feel disconnected from reality:</p><ul><li>Manually maintaining UI libraries</li><li>Debating component variants in isolation</li><li>Treating visual consistency as a human coordination problem</li><li>Asking “Is this component better?” instead of “What decision does this encode?”</li></ul><p>These practices existed because tooling was limited.<br>AI removes those limits.</p><p>When AI can generate pixel-perfect UI, reuse components instantly, and adapt layouts on demand, the value of manual upkeep collapses.</p><h3>AI doesn’t kill design — it kills manual labor</h3><p>This is where the conversation often goes wrong.</p><p>AI is not replacing design.<br> It’s replacing <strong>repetitive execution, synchronization, and maintenance</strong>.</p><p>AI is incredibly good at:</p><ul><li>Generating UI consistently</li><li>Applying constraints automatically</li><li>Reusing patterns without drift</li><li>Scaling decisions instantly</li></ul><p>What it cannot do on its own is define:</p><ul><li>Intent</li><li>Experience goals</li><li>Product logic</li><li>Brand meaning</li></ul><p>That work still belongs to humans.</p><p>But it changes <em>what designers actually do</em>.</p><h3>The designer’s role is shifting — fast</h3><p>The designer of the future is not a component curator.</p><p>They are:</p><ul><li>Architects of rules</li><li>Definers of constraints</li><li>Translators of product intent into systems</li></ul><p>Design is moving away from:</p><blockquote><em>“How should this look?”</em></blockquote><p>Toward:</p><blockquote><em>“What decision is this encoding?”</em></blockquote><p>The future designer doesn’t design every screen.<br>They design <strong>systems that design</strong>.</p><h3>Why do these debates keep happening</h3><p>So why are people still arguing about design systems?</p><p>Because transitions are uncomfortable.</p><p>When an industry shifts, people defend what made them valuable before.<br>They optimize for familiar problems.<br>They debate details that no longer matter at scale.</p><p>That doesn’t make them stupid.<br>It makes them human.</p><p>But it does mean the conversation needs to evolve.</p><h3>The uncomfortable conclusion</h3><p>Design systems aren’t dead.<br><strong>Manually built and maintained design systems are.</strong></p><p>Designers won’t disappear.<br>But many current design roles will either evolve — or become irrelevant.</p><p>The teams that win won’t be the ones with the most polished component libraries.<br>They’ll be the ones who understand how to combine <strong>AI, intent, and systems</strong> to leverage.</p><p>The future isn’t about designing pixels.</p><p>It’s about designing <strong>the rules that generate them</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cabd67c176c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>