代码不是牢笼，它是人类历史上唯一真正没有边界的材料。你可以用它重建、重组、重新想象，速度超过任何其他媒介。认为“在代码中工作会把你锁进既有模式”的想法，只有在你害怕这种材料时才成立。 真相只会在你真正开始构建时显现。不是在你思考构建的时候，不是在一个受保护的空间里勾勒可能性的时候——而是在你把东西真正做出来、让现实对你作出回应的时候。草图和探索之所以让人感觉自由，是因为它们允许你回避那些艰难的问题。而构建会迫使你回答这些问题，这正是你发现什么才真正可行的地方。 把设计拆分成不同阶段的那一整套框架——先自由探索，再引入约束，最后才开始构建——本质上只是对创作过程的官僚化处理。它把本该鲜活、迭代的过程强行线性化。结果就是：你在错误的媒介里“寻找”得太久，等到真正接触现实材料时，已经对最初的想法投入过深，无法推倒重来。你只得到一次探索，然后就被迫承诺。这不是在保护创造力，而是在限制它。 最好的作品，来自于在真实材料中反复迭代。构建、学习、重建、再学习。代码让这一切发生得比任何草图都快。它会暴露边界条件、涌现行为，以及那些只有在系统真实存在时才会出现的交互。约束并不是等你“准备好了”再引入的东西——正是约束，让你发现那些在抽象层面根本看不到的优雅解法。 建筑师不会先脱离物理规律随意画草图，然后再“邀请”重力登场。他们从第一笔开始就考虑材料，因为他们知道：真理存在于材料之中。草图之所以有效，是因为它压缩了对材料的理解，而不是把幻想隔绝于现实之外。软件也应该如此。真正理解系统——它的原语、数据模型、能力边界——不会限制你的想象力，反而会扩展它。它让你看到真正可行的东西，而不是仅仅“看起来能想象”的东西。 把“设计”与“媒介本身”分离，并不会保护探索，它只是让你在太晚之前都不用面对一个问题：你的想法到底行不行。真正有价值的痛苦，不是在一切皆有可能的搜索阶段，而是在你把东西做出来、被现实反击、被迫找到更好方案的时候。工艺就在这里。突破也发生在这里。 把代码当成“等真正思考完成后再进入的阶段”， 这才是真正的牢笼。这意味着：不理解材料能力的设计师在幻想空间里构思，然后把半成品想法交给别人去实现。损失不仅发生在交接过程中，更发生在思考本身。 伟大的软件，来自那些能在所有层级同时思考的人—— 从模糊的想法，到交互方式，到数据结构，一并成立。 未来不是去保护阶段、维持分工边界。而是要更快地接近真实材料本身。是要有那种让你在同一个动作里思考、构建、迭代的工具，让你发现真正可行的东西，而不是过早承诺那些只在草图里看起来不错的想法。 代码不是探索的敌人， 它是探索真正变成现实的唯一场所。 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.