Ask HN: 开发者如何培养设计直觉？
1 分•作者: mercat•9 个月前
正如标题所说：作为一个程序员，同时又是一个渴望成为个体创业者的人，我经常发现自己更多地思考应用程序的架构，而不是真正影响用户体验和满意度的东西。比如前端和后端之间的 API，组件的布局方式，我需要什么样的数据结构，数据库查询回答哪些问题。在开发生命周期的早期引入哪些抽象，以及如何组织文件，这样以后我就不会感到困惑了。
另一方面，当我构建某些东西时，我这样做是为了客户满意度。任何工具或产品都应该解决某人的问题。我可以勾勒出一个问题陈述。而且我或多或少可以编排代码——如何捕捉问题，解决问题，并将结果传递出去。
但展示它——这对我来说是主要问题。是的，我可以在 Figma 中工作。是的，现在有不错的 AI 工具可以生成设计，但它们大多吐出相同的东西。而且用户界面充其量看起来很普通。感觉只要我接触设计，我就开始觉得它不是我喜欢的，而且我经常会回到我喜欢的东西——应用程序架构，一切如何连接，以及我之前已经描述过的所有内容。线框图是一回事，但当涉及到更高保真度的设计时，我最终会依赖预先打包的 UI 工具和库，比如 shadcn 和类似的东西。
我很想内化至少一点经验丰富的设计师所拥有的直觉，那些已经做了很多年并且知道如何布局的人。
我也明白这就像一个设计师问一个开发者如何成为开发者，而只知道开发者知识的 10% 却仍然发布产品一样。但我会大胆地说，视觉设计和我们用来创建它的工具仍然比软件开发少一些维度。
我认为从我的帖子中也可以清楚地看出，我消费了大量的内容并参加了设计课程，但什么也记不住（即使在实践中应用了一些）。如果你是一个也做设计的开发者，你会给出什么建议？在从某个角度开始设计之前，是否有任何可以贴在墙上并依靠的基础规则？你通常如何验证设计？特别是对于数据量大的视图，或者用户需要工具来完成工作，这样他们就不必点击太多次才能达到目标。
查看原文
As the title says: as a programmer and a wanna-be solopreneur, I often catch myself thinking way more about app architecture than about what actually matters for the user experience and satisfaction. Stuff like the API between frontend and backend, how the components are laid out, what data structures I’ll need, which questions the database queries answer. Which abstractions to introduce and how early in the development lifecycle, how to organize files so I do not confuse myself later.<p>On the flip side, when I build something, I am doing it for customer satisfaction. Any tool or product should solve someone’s problem. I can sketch a Problem Statement. And I can more or less orchestrate the code - how to capture the problem, solve it and pass the results along.<p>But showing it — that is the main problem for me. Yes, I can work in Figma. Yes, there are decent AI tools for generating designs now, but they mostly spit out the same thing. And a UI that looks average at best. It feels like as soon as I touch design, I start thinking it is not quite what I like and I often drift back to what I do like — app architecture, how everything connects and all that I already described. Wireframes are one thing, but when it gets to higher fidelity design, I end up leaning on pre-packaged UI tools and libraries like shadcn and similar stuff.<p>I would love to internalize at least a bit of the intuition that seasoned designers have, the folks who have done this for years and know how to lay things out.<p>I also get that this is like a designer asking a developer how to become a developer while knowing only 10% of what devs know and still shipping. But I will be a bit bold and say that visual design and the tools we have to create it still have fewer dimensions than software development.<p>I think it is also clear from my post that I have consumed tons of content and taken design courses, but nothing sticks (even after applying some to practice). If you are a developer who also designs, what advice would you give? Are there any foundational rules you can stick on the wall and lean on before you dive into a design from one angle or another? And how do you usually validate a design? Especially for views that are data heavy or where the user needs tools to get the job done, so they do not have to click too much to reach a goal.