Page 1 • Showing 6 tweets
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.
the real unlock isn't just “vibe coding” – it's ai native coders who deeply understand how to interact with Cursor and models. they know their strengths and use ai to amplify what they're already great at. that's when you get 100x output, not just vibes
no matter the title, we’re all builders prepping a talk to introduce @cursor_ai to designers – what would you want to see?
code isn't a cage, it's the only material that's actually boundless. you can rebuild, restructure, and reimagine faster than any other medium in human history. the idea that working in code locks you into existing patterns is only true if you're afraid of the material. the truth only reveals itself when you build. not when you think about building, not when you sketch possibilities in a protected space – when you actually make the thing real and let reality talk back. sketches and explorations feel free because they let you avoid the hard questions. building forces you to answer them, and that's where you discover what actually works. this whole framework of separating design into phases – first explore freely, then invite constraints, then build – that's just bureaucracy for the creative process. it linearizes something that should be iterative and alive. you end up spending so long "searching" in the wrong medium that by the time you touch the real material, you're too invested in your early idea to start over. you get one round of exploration, then commitment. that's not protecting creativity, that's limiting it. the best work happens when you can iterate in the actual material. build, learn, rebuild, learn again. code lets you do this faster than any sketch ever could. it shows you the edge cases, the emergent behaviors, the interactions that only exist when the system is real. constraints aren't something you invite later when you're ready – they're what reveal the elegant solution you couldn't see in the abstract. architects don't sketch free from physics then invite gravity later. they think through materials from the first line because they understand that the material is where truth lives. the sketch works because it's compressed material knowledge, not fantasy protected from reality. software should be the same. understanding the system deeply – the primitives, the data models, the capabilities – doesn't limit your imagination, it expands it. it shows you what's actually possible instead of what's merely conceivable. separating "design" from "the medium" doesn't protect exploration, it protects you from learning whether your idea works until it's too late to really change it. the valuable suffering isn't the searching phase where everything feels possible. it's when you build something and reality pushes back and forces you to find something better. that's where craft lives. that's where breakthroughs happen. treating code as something you "graduate to" after the real thinking is done – that's the actual cage. it means designers who don't understand what the material can do, building in a fantasy space, then handing off half-formed ideas to people who have to make them real. the translation loss isn't just in the handoff, it's in the thinking. great software comes from people who can think at every level, from the loose idea to the interaction to the data structure, all at once. the future isn't about protecting phases or preserving separation. it's about getting closer to the true material, faster. it's about tools that let you think and build and iterate in the same motion, so you can discover what actually works instead of committing to what seemed good in a sketch. code isn't the enemy of exploration, it's the only place exploration becomes real.
don't treat users like babies: the whole "we know better than you" vibe in software is condescending af. it's great to make the default path smooth and obvious – most people just want things to work. but the moment you seal off the deeper layers, you're basically saying "you're not smart enough to handle this." curiosity is natural. people want to understand how things work, they want to tinker, they want to make it theirs. when you hide the system, you're not protecting users – you're robbing them of agency and the joy of discovery. with cursor, you can just chat with it, or you can dive into the code, mess with context, tools, understand how the AI thinks. the system doesn't hide from you. black boxes create learned helplessness. transparent systems create power users. and power users become creators. they remix, they extend, they teach others. that's how communities form around tools. the best tools feel like instruments, not appliances. you can play a simple melody right away, but mastery is always available if you want it. make the layers discoverable, make the complexity gradual, make the tinkering fun. trust your users – they'll surprise you.