问HN：AI时代的命名策略，来自开发者和技术创意者
我访问了一个来自HN线程的博客，观察到该网站的链接和标题命名非常得当；<i>链接的名称较短</i>，而<i>标题也不太长</i>，能够有效表达链接的内容和上下文。<p>这让我思考自己的命名规范是如何逐渐变化的。我在更多的项目中与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>│
└── 让我来聊聊
查看原文
I visited a blog from a HN thread and observed the site'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's content/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/TODO#N.v0-dev.md/)<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/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't devs and the TLD had to reflect.<p>│
└── Yarn me; Let's talk