Ask HN:AI 时代命名策略,来自开发者和技术创意人士

1作者: mockingloris9 个月前
我访问了一个来自 HN 讨论串的博客,注意到该网站的链接和标题命名得非常好;<i>链接名称简短</i>,而<i>标题也不过长</i>,却能很好地表达链接的内容/上下文。<p>这让我开始思考<i>我自己的</i>命名规范是如何逐渐变化的。我越来越多地与 AI 合作完成我的项目。<p>(我有一套自己的提供上下文的方法,但具体来说;TODO#N.gemini.md/TODO#N.v0-dev.md/)<p>(我每天使用 Sublime Text 作为编辑器 - 我用一台运行 Ubuntu 24.04 的二手联想 Thinkpad;两年前用的是 16.04。)<p>为了说明情况,<i>我</i>主要用 JavaScript 编程。你在工作中还遇到过哪些其他的命名规范/观察?<p>│<p>过渡:v0.dev 现在是 v0.app;他们指出,很多用户不是开发者,因此顶级域名需要反映这一点。<p>│ └── Yarn me; 聊聊吧
查看原文
I visited a blog from a HN thread and observed the site&#x27;s links and title were very well named; <i>links had shorter names</i> and the <i>titles were not too long</i> and managed to express the link&#x27;s content&#x2F;context.<p>This got me thinking about how <i>my own</i> naming conventions have gradually shifted. I collaborate with AI on more of my projects.<p>(I have my own process for feeding context but, on specific; TODO#N.gemini.md&#x2F;TODO#N.v0-dev.md&#x2F;)<p>(I use sublime text as my daily editor - I use a used Lenovo Thinkpad running Ubuntu 24.04; 16.04, 2 years prior.)<p>For context, <i>I</i> code primarily in JavaScript. What are other naming conventions&#x2F;observations you have stumbled on - on the job?<p>│<p>Segue: v0.dev is now v0.app; they noted that a good number of users aren&#x27;t devs and the TLD had to reflect.<p>│ └── Yarn me; Let&#x27;s talk