
Design & Build at @mealsuite
Toronto, Canada
Joined July 2013
- Tweets375
- Following5.4K
- Followers415
- Likes126K
We are entering an era that a multibillion-dollar company will be beat by one person thanks to AI. Prepare accordingly!
2
192
Mo Monfared retweeted
Not sure people understand what's required to make these interactions work, let alone feel so smooth.
Mo Monfared retweeted
Whatever you are studying, always keep a parallel portfolio of the things you create. A research result. A robot. A company. A piece of hardware. The world is becoming more interested in evidence of agency.
AI has collapsed the cost of building products, but not the cost of knowing what to build.
- The old loop: spec, scope, build
- The new loop: build, play, design, ship
Prototypes are cheap. Great products still require taste, judgment, and a clear understanding of what users actually need.
a16z's @joshelman on the artifact a product manager actually produces: a16z.news/p/product-manageme…
Mo Monfared retweeted
Introducing Interfaces
A design engineering magazine about building great interfaces.
A new issue is released every month covering topics across animation, typography, layout, color and everything else that makes an interface feel great.
interfaces.dev/
One of the many reasons that design engineers are needed and effective in startups.
Throwing things over the wall between design and engineering, with both groups using different tools, is really fragile and difficult.
On an accidental tyranny of programmers holding back interface invention, from my recent talk: andymatuschak.org/tat/
Future of interfaces....
Imagine every pixel on your screen, streamed live directly from a model. No HTML, no layout engine, no code. Just exactly what you want to see.
@eddiejiao_obj, @drewocarr and I built a prototype to see how this could actually work, and set out to make it real. We're calling it Flipbook. (1/5)
177
Figma's real problem isn't AI, it's that the design file was never the source of truth, code is.
tools like Paper and Pencil are starting to get this right, the canvas compiles to code and design files live in the repo, but they all still funnel input through a chat interface, which is the wrong modality for design.
most of what AI handles in design is deterministic. reproducing component states and applying an existing design system to new screens. you don't need heavy reasoning, you need a fast model that keeps up with visual thinking.
what i actually want is something closer to a live whiteboarding session than a chat window. voice as the primary input with real time feedback loops on canvas.
the question of "how do we turn designers into software engineers" fails to see the value in skipping an entire layer of abstraction
Mo Monfared retweeted
I think the role of the Software Engineer is evolving into a Product Engineer.
LLM tools have made writing code easier than ever. The real bottleneck isn't implementation anymore - it's deciding what to build and how the UX should work.
That's why I've been spending more of my time learning design and product skills. The most impactful engineers will be the ones who can shape products, not just ship features.
Mo Monfared retweeted
when designers can build and builders can design, magic happens.
watch:
Head of Design @ryolu_ helped transform Cursor from a feature-layer on top of VS Code into one of the world's leading AI code editors.
He joins YC's @aaron_epstein on Design Review to talk about the path that brought him to Cursor, how rapid prototyping reshaped the core product, and how he's on a mission to break down the barriers that once separated designers and coders.
00:00 — Designers Becoming Builders
04:11 — Learning by Building, Not Studying
08:39 — Inside Cursor’s Design Team
13:30 — Designing Systems, Not Features
17:40 — Rebuilding Cursor Around Agents
23:15 — Prototyping With “Baby Cursor”
30:52 — Design as Sculpting
36:10 — The Future of Designers and Engineers
Design in code is future!
we broke software into “design” and “engineering” and trapped ourselves in frames and specs.
Cursor’s new visual editor lets you play with ideas and designs in code, live.
no more hand-offs, just click, chat, tweak the tiniest detail, in the actual thing you will ship.
3
146
Good take and good article to read!
I happen to have a writing about the difficulty in verification for designers here!
design-engineer-blog.rickyzh…
2
166
Mo Monfared retweeted
hot take: designers often feel like they have to defend every single choice they make, as if they're constantly on trial. that's because design is so visual—anyone can glance at it and throw out opinions, even if those opinions are vague or come from someone without much expertise. for instance, a non-designer might casually say, "this color feels off," without backing it up or offering a real alternative. the bar for giving feedback is incredibly low; you don't need deep knowledge to chime in.
now, compare that to engineering: folks don't usually drop random technical suggestions unless they actually understand the code. instead, they'd point out a specific issue, like "clicking this button triggers an error." it's straightforward and functional, not just a gut reaction like "this code seems weird."
but here's where things get imbalanced: when someone hits a designer with that low-effort feedback, the expectation for the designer's reply is surprisingly high. if someone asks, "why this layout here?" answering "after a few iterations this one felt right" rarely satisfies them—they want a full breakdown of ux laws and design thinking with as many jargons as you can blurt out.
early in your career, or even later, articulating that intuition can be tough and sometimes there isn't any to articulate in the first place. it's built from experience, patterns you've absorbed, and subtle principles of what works visually. don't doubt it; it's likely spot on, even if the words aren't there yet.
this setup can make design feel draining, turning teamwork into a constant justification session rather than pure creation. yet, here's the key: designers don't need a defense for every little element. design isn't something that requires endless justification—it's the bridge that gets a user from point a to point b, all while deeply prioritizing their experience and convenience. trust the process and never let shallow feedback shake your core confidence.
ps: using above as a justification for poor design is definitely a skill issue but you get the gist of it.


























