TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Column Names as Contracts

55 点作者 MaysonL超过 4 年前

6 条评论

closed超过 4 年前
&gt; Using controlled vocabularies for column names is a low-tech, low-friction approach to building a shared understanding of how each field in a data set is intended to work.<p>Can&#x27;t stress how useful this has been working on data science teams. There is really an art for getting a group of people to standardize around a vocabulary of column name pre&#x2F;suffixes without being overly prescriptive.<p>Being able to unlock nifty tools &#x2F; behaviors by naming your columns certain ways seems crazy powerful. (Like a form of function dispatching)
评论 #24403928 未加载
Cieplak超过 4 年前
This sounds a lot like Hungarian notation [1].<p>[1] <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Hungarian_notation" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Hungarian_notation</a>
评论 #24406122 未加载
ZeroClickOk超过 4 年前
Now I remember my pain to work in a system with hundreds of tables and near 4-5 different column name schemas :&#x2F;
fmjrey超过 4 年前
Reminds me of what clojure spec is trying to do: create data specifications that can be named and reused via a registry. The metadata is just data on the shape of the data so it can serve as doc, validation, data generation, property testing, etc. Spec names are namespaced but no specific guidelines are given it&#x27;s just organizational.<p>Separately clojure also allows for namespaced names for map entries, but again provides no specific guidelines on what namespaces should be: in code this could be a library name, but it could also be an entity name as suggested by datomic best practices.<p>The combination of both features, namespaced var&#x2F;entry names associated with namespaced specs, seems to make more sense than using name parts conventions, but if you&#x27;re not clojure all the way then the latter might be the only way.
paperwork超过 4 年前
I really like the idea of being more thoughtful about naming columns and being more explicit about the “type” of data contained in them.<p>Is this idea already known among data modelers or data engineers?<p>I’d love to read any other references, if available.
评论 #24405386 未加载
评论 #24405246 未加载
anamax超过 4 年前
There are two hard problems in computer science. Naming things, cache invalidation, and off-by-one errors.<p>The first is about people, not algorithms.