HackerNews中文版

我一直在指导初级开发者（同时也反思自己的习惯），并注意到一个模式：“消费者开发者”。我们可以无限获取高质量的教程（如 freeCodeCamp、YouTube、文档），但从零开始构建的能力似乎在下降。我们更倾向于追求学习的感觉（观看视频），而不是调试的痛苦。我尝试了一些标准的“自律”技巧（如番茄工作法、屏蔽应用程序）来强迫自己进行开发，但都没有成功。于是我进行了一次实验：我写了一个 Discord 机器人来跟踪我的 GitHub 活动。规则是：如果我在 30 天内没有提交代码或发布项目更新，机器人将永久禁止我访问自己的社区。结果是：“社交拒绝”的恐惧和失去访问权限的担忧立刻产生了效果。在过去的 7 天里，我的产出比过去 6 个月还要多。我在这里记录了这个逻辑和“NPC 陷阱”理论：https://youtu.be/i2xdJ5ISoTI 我的问题是：依赖“恐惧/后果”是否可持续，能够促进长期的工程成长，还是这只是导致倦怠的一个方法？我很想听听其他人是否也使用“高风险”的承诺来推动副项目的进展。

查看原文

I’ve been mentoring junior devs (and looking at my own habits), and I’ve noticed a pattern: "Consumer Developers."We have endless access to high-quality tutorials (freeCodeCamp, YouTube, documentation), yet the ability to build from scratch seems to be dropping. We optimize for the feeling of learning (watching a video) rather than the pain of debugging.I tried standard "discipline" techniques (Pomodoro, blocking apps) to force myself to build, but they failed.So I ran an experiment: I wrote a discord bot that tracks my GitHub activity. The Rule: If I don't push a commit or ship a project update in 30 days, the bot permanently bans me from my own community.Result: The fear of "social rejection" and losing access worked instantly. I’ve shipped more in 7 days than in the last 6 months.I documented the logic and the "NPC Trap" theory here: https://youtu.be/i2xdJ5ISoTIMy Question: Is relying on "fear/stakes" sustainable for long-term engineering growth, or is this just a recipe for burnout? Curious to hear if others use "high stakes" commitments to ship side projects.

“负强化”（对被禁止的恐惧）是一种有效的学习策略吗？