HackerURLs

一次又一次被重新发现的经典。

同一个链接,相隔一年以上,一次又一次被人重新发现、再次冲上 Hacker News 首页。能经受住这种时间检验的,大多是值得一读再读的文章。每篇附中文标题,讨论最热的那些再加上中文导读和高赞评论翻译。

从名人堂开始
  • 4,700+篇经过时间检验的经典

Hall of fame

名人堂

在经典库里看全部精选

上首页次数最多、而且有中文导读的 30 篇。时间轴上每个黑点是一次上首页,空心点是一次没冲上去的投稿。

  1. 正在载入经典…

Archive

经典库

按第一次上首页的年份分布,点柱子筛选。

排序

    About

    这些经典是怎么挑出来的

    1. 01

      合并同一个链接

      读取 Hacker News 自 2006 年以来的全部链接投稿,把 http/https、www、跟踪参数等写法不同的同一篇文章合并成一条。

    2. 02

      只留经得起时间的

      同一链接至少两次拿到 50 分以上(约等于上首页),而且两次相隔一年以上;再由 AI 剔除状态页、产品首页和新闻事件。

    3. 03

      写导读、译评论

      上首页次数最多的 2,000 篇配上中文导读、"为什么经久不衰",并精选翻译 HN 高赞评论。导读由 AI 生成,可能有误。

    创业与商业training.kalzumeus.com编辑精选

    我如何从每小时100美元的编程工作,做到每周数万美元的咨询业务

    How I went from $100-an-hour programming to $X0,000-a-week consulting

    2次上首页
    5年跨度
    1,814累计得分
    733条评论

    2012 — 2017,它一次次回到首页

    黑点是上首页(≥ 50 分)的那次投稿,空心点是没冲上去的投稿,点越大分数越高。

    导读

    这是 Patrick McKenzie(kalzumeus)的咨询系列文章之一,讲他如何从每小时 100 美元的编程/自由职业,转向按周收费、按商业价值而非工时定价的咨询模式。文中涉及把服务定位为帮客户增收、用软件产品带来主动上门的咨询,以及改变与客户谈钱的方式。

    为什么经久不衰:它把独立开发者最难的定价与定位问题讲得具体可操作,十几年后仍是自由职业者升级商业模式的经典参考。

    关键词 咨询定价价值定价自由职业独立开发者

    HN 评论精选

    高薪咨询应帮客户增收而非降本,因为增收更受管理层重视。

    很多评论集中在「这听起来很棒,我希望能收更高」或「怎么找到高薪合同」。一个办法是:找高薪咨询合同时,专注于帮公司赚钱而不是省钱;帮客户增加收入比降低开支更值钱。因为管理层目标更多与增收相关,有预算的人会更看重能帮他们增收的人,而降本自动化往往被推到下个月。

    F_J_H查看英文原文

    There seem to be a lot of comments centered on “wow, this sounds great – I wish I could charge more” or “how do I find these high paying contracts”? Here’s one way. It may seem obvious to many, but I think it bears stating. If you are looking for consulting contracts that pay really well, focus on providing a service that helps companies make money rather than save money. In other words, help grow revenues rather than reduce expenses – people pay much more for that. Here’s the reasoning: When business managers, executives, etc. are given targets, they typically relate to increasing revenues much more often than reducing expenses. Not surprisingly, increasing revenues is therefore “front of mind” for those with budgets to make it happen, and they see tremendous value in someone who can help them do that. The fact that a little automation in the accounting system will save a data entry clerk a few hours a month – hmmm...maybe next month. Case in point - I remember reading a comment somewhere from a Google employee who was complaining that at Google, those working on the revenue generation side of the business (i.e. advertising, adwords, etc.) got all the “love and attention” in terms of getting the resources required to get their job done, while others working on more obscure projects had to put up with leftovers. Now I’m not sure if that is actually true at Google, but I wouldn't be surprised as I've seen it at many other companies – the “rain makers” are the darlings with dollars to spend, and the back office ops folks are left to struggle with fewer resources. All injustices aside, find a way to provide something to the rain makers. The type of work that Patrick does directly improves revenues. If you are a DBA selling tuning services to help companies re-write gnarly queries for example, well, unless a slow performing query/process is directly impacting revenues in some way, it likely is a secondary priority in devops/support where budgets are tight and “learn to live with it” is becoming a way of life.

    按周收费简化计费,按价值收费避免时薪比较并让客户从价值角度谈预算。

    我学到的两个要点是:1)按周收费,2)按你将提供的价值收费,而不是按你的时间值多少钱。按周收费让你不用追踪每一分钟是否可计费;按价值收费则避免客户说「你每小时收 200 美元,比我还多,能不能降到 90」,转而让对话变成「我们想获得至少 4 万美元价值,但这次预算只有 1 万美元,你能在多少周内提供多少价值」。

    ronyeh查看英文原文

    Two important points I learned was: 1) charge by the week, and 2) charge by the value you will be providing, rather than how much your time is worth. Charging by the week allows you to not have to keep track of what's billable and what's not (e.g., you chatted with the customer on the phone for 34 minutes). Charging by the value you provide avoids the conversation of "Hey, you're charging $200 per hour... that's more than I make. And that's like almost $400K per year! Can we get your rate down to like, $90?" Instead, the conversation becomes, "We want to get at least $40K of value out of talking to you, but have only budgeted $10K for this exercise. How much value can you provide us over how many weeks?" That was definitely an interesting writeup!

    软件产品带来主动上门的定制咨询需求,使作者转向周 retainer 和近六位数项目。

    我偶然来到这里,但能证明这套系统的价值。我曾以每小时 75 到 100 美元做自由职业,每个合同都要非常努力。副业做软件卖得不错,但不足以退休。后来购买软件的客户开始问能否做定制版本;起初多数没成,后来突然变成按周收 retainer、做接近六位数的项目,而且都是因为我们的软件主动找上门的业务。

    nhangen查看英文原文

    I ended up here on accident, but I can vouch for this system's value. I WAS freelancing at between $75-$100/hour, but having to work very hard for every contract. On the side my partner and I were building software, selling a nice amount but nothing that was going to allow us to retire in a year. However, suddenly people starting emailing us after purchase, asking if we could build custom versions for them. Most turned out to be duds, at first, and then something changed. Suddenly we're charging weekly retainers and working on near six-figure projects, all on business that sought us out because of our software. Will this work for everyone? I'm not sure, but it did for us, and we didn't even see it coming.

    文章实质是开发转营销咨询;营销被视为创收而 IT 常是成本中心,且路径并非人人可复制。

    也许其他人也和我一样以为:这篇文章讲从合同工/雇员的技术开发转向技术咨询。其实不是,它讲的是从开发转向营销。这没有错,但发现致富路径意味着和公司里我最不喜欢的一群人打交道,让我有点失望。营销更可能为咨询付高价,而 IT 只在非常绝望时才为外部帮助付大钱;营销被视为创收,IT 和产品开发却常被视为成本中心。这种转变也不是大多数人都准备好的。

    blunte查看英文原文

    Perhaps other people here shared the same assumption that I did - that this essay was about moving from tech development as a contractor/employee to tech (development) consulting. It's not. It's about moving from developing to marketing. There's nothing wrong with that, but it was a let-down to me to discover that the path to riches meant mingling with the group of people I tend to like the least in a company. Also, I think it's fair to say that amongst departments in companies, marketing is much more likely to pay (and pay a lot) for a consultant, whereas IT is only likely to pay a lot for outside help when things are really, really desperate. Marketing is seen as revenue generating, and at many places, IT and (ironically) product development are seen as cost centers. This might as well have been an article about how to 100x your income by moving from your current job into a similar job in a fintech company. That's a bit like moving from serving tables at Denny's to Del Frisco's steakhouse. Most Denny's waiters are not prepared nor capable of making that transition.

    历次讨论

    同类还值得读

    1. 微软已死(2007)

      Microsoft is Dead (2007)

      Paul Graham 2007 年的一篇短文,判断微软在互联网与创业竞争中已不再令人畏惧、失去影响力——所谓“死”并非字面倒闭。

      创业与商业上首页 8 次 · 2007–2025paulgraham.com
    2. H&R Block 与 Intuit 游说反对简化报税(2017)

      H&R Block and Intuit Lobbying Against Simpler Tax Filing (2017)

      2017年ProPublica调查报道梳理了H&R Block和Intuit如何通过游说反对更简单的美国报税方式,尤其是政府预填税表和免费申报等改革。

      创业与商业上首页 5 次 · 2017–2022propublica.org
    3. 你本不该有老板

      You Weren't Meant to Have a Boss (2008)

      Paul Graham 2008 年的经典文章,论证人类在演化中习惯于小团体协作,而大公司的层级结构和老板制度是人为产物,对程序员尤其有害——因为编程的本质是创造新事物,而大公司…

      创业与商业上首页 5 次 · 2008–2020paulgraham.com
    4. 为什么要在经济糟糕时创业

      Why to Start a Startup in a Bad Economy

      Paul Graham 的经典短文,论证经济衰退并不是创业的障碍:真正决定成败的是创始人和产品,而非宏观环境;衰退期反而竞争更少、人才更易招、成本更低。

      创业与商业上首页 5 次 · 2008–2022paulgraham.com
    5. 做那些不可规模化的事

      Do Things that Don't Scale

      Paul Graham 2013 年的经典创业文章《Do Things that Don't Scale》。

      创业与商业上首页 4 次 · 2013–2025paulgraham.com编辑精选

    打赏支持

    打赏二维码

    觉得有用,请作者喝杯咖啡。

    WeChat

    关注向阳乔木

    微信公众号「向阳乔木推荐看」

    微信公众号「向阳乔木推荐看」二维码

    微信扫一扫;在微信里打开本页时,长按二维码识别。