I’ve noticed a bit of a snarl in the design community lately. There is a very real, very understandable wave of "AI fatigue" sweeping through our industry. I’ve seen the eye-rolls aimed at those of us constantly talking about our new AI-enabled workflows, and honestly? I get it. The hype cycle is exhausting.
But to break up my recent wall of technical case studies, I want to be a little bit real for a second: I am not apologizing for my excitement.
Here is the truth: I feel completely entitled to be thrilled right now, because I literally trained for this my entire life. I grew up watching Captain Picard ask the Enterprise computer to run complex, multi-variable diagnostics while sipping Earl Grey. I watched Michael Knight banter with KITT to solve problems on the fly. I watched The Jetsons normalize the idea of living and working alongside automated intelligence.
For decades in UX, we have been trying to force humans to adapt to the rigid language of computers. Now, the computers are finally starting to speak ours.
To be clear: I am a UX Designer. I am not a formally trained developer. For years, that meant my creative vision was ultimately bound by my ability to negotiate for engineering resources. But sitting down with tools like Cursor or Claude and essentially co-building an interface makes me feel like I finally have the wind in my hair. I can just create without constantly hitting a technical wall.
It feels exactly like the sci-fi future I was promised, and it has fundamentally changed what I am capable of in two massive ways.
1. True Collaboration (Goodbye, Figma Handoffs)
The traditional designer-to-developer handoff is inherently broken. You throw a static, idealized Figma file over the wall, cross your fingers, and prepare for weeks of sync meetings to compromise on what is actually buildable.
AI hasn't just sped up my design process; it has completely changed my output. Instead of handing off static mocks, I am using AI assistance to build and deliver functioning, responsive Angular code sandboxes. I can validate my own UX in the browser before an engineer ever sees it. We aren't arguing about whether an interaction is possible anymore—I am handing them the structural code that proves it is. We are finally speaking the same language.
2. Total Independence
This is the part that truly feels like magic. Because the technical barrier to entry has been lowered, I can build and deploy my own digital products completely independently.
I no longer have to wait for a developer's free weekend to launch an idea. I am currently coding my own Portfolio 2.0 from the ground up using Cursor and deploying directly to Netlify. I am taking on freelance clients and deploying their entire static sites myself. I am completely upgrading the UI for my DIY cardmaker project—handling the front-end logic on my own.
I am building exactly what I want to build, exactly when I want to build it, entirely without developer time.
The Reality of Design Engineering
I know the broader tech landscape is incredibly noisy right now, and if you are feeling a bit of that general AI fatigue, I completely understand the skepticism.
But if you are a hiring manager or a fellow designer who wants to talk about how treating your IDE like the bridge of the Enterprise has made actual, code-level development possible for a UX professional, my inbox is open. We are entering an era where designers can build without limits, and I am going to enjoy every single second of it. 🖖