Dive Club 🤿: Drew Wilson - How Designers Become Builders and the Future of Tooling

Host: Ridd
Guest: Drew Wilson
Date: October 24, 2025
Episode Theme:
A deep dive with Drew Wilson (founder of Opacity) exploring the merge of design and engineering, the evolution of design tools, the rise of AI-powered workflows, what it means for the role of designers, and practical advice for designers wanting to stay ahead in the rapidly changing landscape.

Episode Overview

Drew Wilson, a veteran designer, engineer, and founder, joins Ridd to discuss how the historical divide between designers and engineers is dissolving with new tools—and why the designers of tomorrow must become builders. The conversation covers Drew’s startup Opacity, AI’s growing influence on workflows, what single-source-of-truth tooling unlocks for teams, the future of design systems, career advice, and how design teams should adapt to remain relevant in an AI-driven era.

Key Discussion Points & Insights

1. The Friction Between Design & Engineering: Why Drew Started Opacity

• Drew’s Motivation & Vision:

  • Drew's extensive background in both design and engineering drove him to question why delivering a design still felt like, "nothing's ever totally finished...it's just a pretty picture." The bulk of work, and thus pain, is in engineering. Opacity’s mission is to close this gap by eliminating redundant, labor-intensive handoff processes.
    • [02:22] Drew:

      “When you get a design, that's just literally the starting point. You haven't even actually done any real work yet. It's just a pretty picture...then this overwhelming feeling of dread, of like, oh my gosh, I haven't even started. Now I got to build the whole freaking thing.”

• The Core Problem:

  • Handoff is inefficient and demotivating. Decades of tools have reinforced the separation between design and engineering source-of-truths (e.g. Figma vs. codebases).
    • [05:18] Drew:

      "Companies will spend their entire life cycle trying to get [design and code] to be in sync, but they'll never be in sync. It's a massive waste of manpower, woman power, creativity, and money...I'm hoping Opacity is the way that it will happen."

2. The Concept of a "Single Source of Truth"

• Technical Vision for Unified Workflows:

  • The future is a shared environment where design artifacts are DOM/code-based, not just a visual spec.
  • Eliminating duality: What you see and manipulate visually as a designer is the production code engineers use (via NPM packages, for example).
    • [07:49] Drew:

      “Now ... there needs to be a single source of truth where a designer can draw things on a canvas, but it's actually creating ... this underlying DOM object, actual browser code, CSS-driven code. ... They’re not copying and pasting, they’re grabbing the actual code and referencing it from their code files.”

• Impact on Collaboration:

  • Handoff becomes obsolete. Designers don’t just create "pictures," but shipping, production-ready components, bridging the skill gap—and possibly even the roles—between designers and engineers.

3. AI as an Accelerator—But With New Constraints

• AI’s Role in Expanding Access & Productivity:

  • LLMs are "faster than you'll ever be" (but not necessarily more skilled), enabling more people—designers and non-engineers alike—to participate in building software.
    • [09:18] Drew:

      "I don't think engineering is going to be the same...I think there'll be a lot more engineers. ... On the design side, the same thing is going to happen...AI design will get good enough that it's always going to look good enough. And anybody can be a designer at that point...the soccer mom, the football dad, they can all be designers."

• Limits of AI for Design:

  • Differences in how AI “thinks” about code (logical, binary) vs. design (subjective, taste-driven). Design still has subjective thresholds ("you can tell when something’s good"), but better systems and components will allow models to achieve higher quality by default.

4. Opacity’s Approach: Merging Visual Tools With Systematized Code

• From Canvas to Code Instantly:

  • Designers work visually but build real components, complete with variables (“props”), so changes and iterations are automatically reflected in live products.
    • [13:35] Drew:

      "Whenever you click, you know, publish, it generates these NPM packages ... and the engineers or the AI in most cases will pull that down and use that in the code base. ... That node is that systematized design I was talking about."

  • Opacity aims to do for design systems what Figma did for design teams—putting live, sharable building blocks at the center of the workflow.

• Versioning, Collaboration & GitHub-Like PRs:

  • Built-in PR flows let design teams review and merge changes visually, not just in code—a missing piece in design tools until now.
    • [22:06] Drew:

      “You can approve [PRs], you can comment...Once you approve it, it gets merged in and a new version package is created. ... You’re going to click our one click import from Figma ... your engineers can pull it down at that very second and start using it.”

• Marketplace & Community Future:

  • Envisioning a space where design components are shared, bought, or sold, so AI agents have richer material to draw from.

5. The New Minimum: Technical Fluency for Designers

• Rising Bar for Designers:
  • Designers can no longer be content with static mockups or analog workflows; the expectation is real, interactive output ready for engineers/AI to drop in—a new “technical threshold.”
    • [17:49] Drew:

      "If you're still operating under the mindset that ... I take a month to come out with this design and expect the team to now redo my design from scratch in code, I think you're going to find that's not acceptable anymore."

• But: Accessible On-Ramps Remain:
  • Learning variables, props, etc., is not difficult, and tools like Opacity are lowering the barrier.
    • [17:49] Drew:

      “It is not that hard to add variables. So if that's the sticking point for you, then ... just take the 15 minutes it takes to figure it out.”

6. The Future Role of Designers (and How to Stay Relevant)

• Where Do Designers Add Value When AI Can Output "Good Enough"?

  • The baseline for quality (and customization) will rise thanks to ever-better shared libraries/components and AI; differentiation shifts from raw making to curating, configuring, and evolving unique systems.
    • [41:49] Drew:

      "The only way to [differentiate] is to go out and find somebody to help you do that. Now, I don't know if that means that person is going to build something 100% from scratch ... I think you're going to be the ones building those components. ... Realistically there's going to be a lot less [designers], but maybe that's fine ... there's going to be so much more, it's going to be so much cheaper to start a company.”

• The Collapse of the Hierarchical Designer-Engineer Divide:

  • Teams may become smaller and higher-leverage, roles more fluid, driven by component libraries and AI.
    • [11:59] Ridd:

      "In that world you just have a much greater percentage of people on a team that are committing code."

• Advice for Designers:

  • You don’t need to become a “senior engineer,” but you need to be comfortable building and working alongside AI/code tools.

    • [36:43] Drew:

      “I don’t think you will have to [learn all engineering]. ... If all you care about is the design and the UX of the thing, something like Opacity is exactly what you want because you’re not just delivering your clients a picture, you’re delivering them working code...”

  • Practical Getting Started Advice:

    • Explore AI tools (Claude, Cursor, v0, etc.) and start prototyping product ideas. When you hit limits in no-code, export and try low-level tools; you’ll learn by doing, not by taking traditional coding courses.
      • [50:18] Drew:

        “You can just be an average engineer and be just as effective. ... You just need to start working with AI and try to separate in your mind AI as a political statement ... from the practicality of working with AI to build a product.”

7. Product Development: Ship Early, Loop Tightly With AI

• Opacity’s Roadmap & Internal Dogfooding:

  • The Opacity team is now redesigning Opacity’s UI in Opacity itself (the ultimate test)—with an internal loop for fast iteration and QA.
    • [24:46] Drew:

      "I've done it a few different times, but we're in the middle of making larger architectural changes ... We're almost at the point now where we're going to be ready to do it. I'll be live streaming that as I do it."

  • Drew built a new AI-centric IDE (Loupe) in just 10 days, demonstrating how fast experienced builders can move with modern tooling.

• Lean Teams—Supercharged by AI:

  • Drew points out that with AI agents now, a single builder can achieve more than multiple traditional hires—or at least ship much faster.
    • [53:34] Drew:

      “I already have like a bunch of AI agents working for me and honestly they're doing so much more than hiring a team of seven engineers. It's insane. ... Doing things a little differently because of the state of product building today.”

Notable Quotes & Memorable Moments

• On Handoff:

  "I want to delete the need to ever code out a design again from the history of planet Earth. That'd be great."
  — Drew, [09:18]

• On the Future Designer vs. Engineer Divide:

  “This idea of designers and engineers and these two profiles building everything ... I think that’s going to go away.”
  — Drew, [10:10]

• On Technical Fluency and the Minimum Bar:

  “If you're still operating under the mindset that ... I take a month to come out with this design and expect the team to now redo my design from scratch in code, I think you're going to find that's not acceptable anymore.”
  — Drew, [17:49]

• On Creative Limits & AI Standardization:

  “Are we at some sort of limit with how good design can be for this use case? ... Is there a need for us to come up with something new and unique every time other than just it's new, buy it?”
  — Drew, [45:06]

• On How to Future-Proof Your Career:

  “You just need to start working with AI ... Open up Claude AI ... just start building something that you wish existed and just see how far you get.”
  — Drew, [50:18]

Timestamps for Important Segments

| Time | Segment/Topic | |----------|------------------------------------------------------------------------------| | 01:11 | Drew explains his motivation and the historical pain in design/engineering | | 02:22 | What’s broken about design handoff | | 05:18 | The technical case for a single source of truth | | 07:49 | How Figma and tools today reinforce the split between design and code | | 09:18 | AI and the future designer/engineer hybrid | | 13:35 | Opacity’s workflow: from pixels to code, components, and nodes | | 17:49 | New expectations for designers in the age of instant code | | 22:06 | Opacity's vision for Figma import, code generation, and GitHub-like team flows| | 36:43 | Where modern designers draw the “line”—how much code should they know? | | 41:49 | How to differentiate as a designer when AI and templates dominate | | 50:18 | Concrete advice for designers entering the new era | | 53:34 | Lessons from Drew’s founder journey; building product teams with AI |

Conclusion: Action Steps for Designers

• Understand that rapid change is the new normal—familiarize yourself with AI tools and component-driven design.
• Don’t fear the technical layer; tools are making it more accessible every day.
• The value of unique design persists, but the production processes (and hiring expectations) will change.
• Founders and builders: Lean, AI-augmented teams will move faster than ever—early adoption of these practices can be a superpower.

Final words from Drew:

"Let me just caveat what I said earlier. It does not mean I will be successful in making that stuff happen, but I’m going to try." ([57:29])

Want to stay updated or try Opacity? Watch for announcements in the coming weeks and consider joining the alpha!

(For all resources and the Dive Club archive: dive.club)