注册并分享邀请链接,可获得视频播放与邀请奖励。

AYi (@AYi_AInotes) “这可能是今年 AI 编码最反常识的结论,跑了一整年生产环境的人告诉你,最好的 AI 编码” — TopicDigg

AYi 的个人资料封面
AYi 的头像
AYi
@AYi_AInotes
AI 实用主义 大厂组织发展专家 × 心理学硕士(QS30) 分享有用的 AI 实践,也分享工具之外的深度认知 AIGC | Prompt | 商业思维 丨职场丨认知心理学 合作/交流:DM/TG @AYi_AInotes
加入 October 2025
368 正在关注    53.6K 粉丝
这可能是今年 AI 编码最反常识的结论,跑了一整年生产环境的人告诉你,最好的 AI 编码环境根本不是你的笔记本。 Pieter Levels 用近一年的真实生产数据验证了这套玩法, Claude Code 常驻 VPS,Agent 直接在线编辑生产环境代码, 传统本地编码加 Git 加部署的流程要一分钟迭代一个特性, 现在改完刷新就能测,反馈循环直接压到秒级。 十二个月生产环境跑下来只出过两次小故障, 每次都是十秒级的 PHP 报错随即自愈, 搭配严格的多份备份策略,风险完全可控。 不用一直开着电脑,手机接个 SSH 就能续上任务, 丢个目标指令 Agent 就能自己跑一整夜。 真正的变化藏在表层玩法下面。 第一是 Agent 的定位变了, 从本地 IDE 的辅助插件,变成生产环境里常驻的执行者, 代码和运行环境第一次贴得这么近。 第二是速度的复利效应, 对独立开发者来说不是快一点, 是能同时跑更多实验更快验证想法, 单位时间的试错次数直接拉开量级差距。 第三是风险的标准变了, 团队要合规走预发布环境天经地义, 但 solo 开发者用备份兜底换极致效率, 本来就是完全不同的取舍逻辑。 第四是基础设施的方向反了, 以前本地重云端只负责部署, 现在云端成了主力开发加运行环境, 本地设备只是个接入终端。 AI 编码的竞争早就不在谁补代码更快了, 在谁先把 Agent 放进真正的生产环境里, 让它成为永远在线的执行层。 想试的朋友从非核心项目入手, 配好快照和备份,门槛比想象的低很多。
显示更多
✨ I think I've been coding almost solely on my VPS with Claude Code for almost a year now All I can say it's just fantastic: - no need to keep laptop open ever - no laptop battery drain - can switch to phone or any other device you like whenever you want to continue (like when you're outside) - it just keeps going all night while you sleep (esp with /goal) - you can start hacky projects from scratch and go live in seconds because you're already on the server which is great to ship things and get it used by people fast (not stuck on your local laptop webserver) - it just feels like living in the future I used to code on my laptop, test locally, then push to GitHub, then it auto pulled and deploy to production, that'd take me ~1 minute to get a new feature out But then when I bought a new Mac Book Pro a few years ago I was too lazy to install a local Nginx environment, so I just started pushing to prod and everything went fine, and I sped up deploying to about 3 seconds from laptop to server, which people called me crazy for too But now with Claude Code on my VPS in the last year, it just live edits on my production server, which sounds like it should go wrong but it just doesn't, it's very careful and only twice in 12 months messed up which meant my site didn't load for 10 seconds which is OK If I wasn't working solo, like at a big company, I' think I'd recommend the same workflow but with a staging server, so it wouldn't touch production, for safety and regulatory reasons etc. but for me it's fine I agree with @theo completely, it's clear to me this is where it's going, also seeing @karpathy with Claude moving to the cloud (via Slack etc), I think AI "agents" and AI coding will operate on servers / from the cloud first P.S. I have 3-2-1 backups, multiple on-site and off-site backups which you should also even if you wouldn't code with AI, safety first!
显示更多