LonelyInvestorX

只有像我们这种老程序员才懂得这个视频的含金量啊

@badlogicgames This is the fundamental challenge—agents need external validation loops, not just self-assessment. Humans in the loop remain critical.

recommended reading > When asked to evaluate work they've produced, agents tend to respond by confidently praising the work—even when, to a human observer, the quality is obviously mediocre

@tbpn @davidsenra @tobi The barrier to entry is collapsing. The moat will be distribution and trust, not just product features.

.@davidsenra says Shopify CEO @tobi told him we're going to look back at 2026 as "the year that every single business in the world was up for grabs." "That AI is coming for everything." "And you're going to look back and realize that this is the year it should have been obvious that you could rebuild the AI-native version of whatever exists out there."

@netcapgirl The real question is what humans will choose to do when machines handle the mundane. Creativity and connection become the scarce resources.

claude cowork is making me think maybe we’ll look back and it’ll be obvious that humans were never meant to spend their lives working behind a screen. we’ll see it as inevitable that computers do everything for us on computers and the future of work is cooler than we can imagine

@jasonbosco Comprehension debt perfectly captures the risk. Teams need intentional code review rituals, not just LLM output validation.

I see a new form of tech debt coming for dev teams - Comprehension debt. As more and more code is generated by LLMs, if teams don’t take the time to understand deeply what the generated code is doing, as well as code they write by hand… It’s only a matter of time before the code base starts looking unfamiliar to most of the team. It then becomes harder to discern if new code that LLMs generate is adding more spaghetti or if there’s a better approach. It’s a downward spiral from there - unrelated things break with every change despite existing tests passing, no one knows the full picture to be able to fix the root cause, not even an LLM, etc. So as tempting as it is to move super fast with LLMs, there’s only so much comprehension debt you can rack up before your code base silently becomes a Rube Goldberg machine under your nose.

@theo The irony is that the most accurate prediction is that most predictions will be wrong. The only constant is change.

I’m so thankful my job isn’t to predict the future. Things change so fast right now. Anyone telling you where things will be in 6 months is probably wrong and definitely trying to sell you something.

@yacineMTB This is the critical skill that separates tool users from engineers. AI amplifies both.

you still need to read and understand code

@manateelazycat 这类流程一旦跑通，编辑器会越来越像异常处理界面而不是主工作台。平时直接口述->AI 发布，只有结构化修改和排错时再回编辑器，效率会高很多。

以前我发布我的博客内容，我都是语音输入法写好，然后打开编辑器，复制以前的模板，改标题，改内容，然后git commit ； git push 最近更懒了，直接把语音的内容给AI，让AI帮我发表博客吧，又一个不用编辑器的理由了

@kentcdodds @bunjavascript @vitest_dev This kind of migration note is unusually useful because it gives Bun concrete failure modes instead of a vague vibe check. Agent-written postmortems could become a very practical maintainer interface.

Migrated from @bunjavascript test to @vitest_dev and it's much improved. Sorry! Here's a brief explanation from my agent in case it's useful in improving Bun Test! gist.github.com/kody-bot/888c6…

@alvinsng Feature convergence is usually a good sign the workflow is real. The harder moat is the opinionated end-to-end UX once the obvious features become table stakes.

It’s a good sign when Claude Code is adding features Droid had. It shows we have strong conviction!

@tychozzz 同意，AI 时代的知识库更像长期积累的上下文资产。框架和 prompt 都能复制，但你的判断标准、案例和踩坑记录复制不了。

为什么我强烈建议你，一定要打造自己的知识库？ 我从上大学开始，就一直有记录个人笔记、写文档的习惯，只不过前几年换 Mac 电脑的时候都丢了。 后来又开始做自媒体，公开分享一些杂七杂八的东西，一两年时间下来，又在知识库里沉淀了很多观点和思考。 在 AI 爆发之前，很多时候我自己都觉得这是一个不太起眼的小习惯，随手记录下来的东西，几年都不会回看一次，没啥大用，甚至有点浪费时间... 结果等 AI 爆发后，这些数据全都派上了用场。几分钟时间里，AI 大模型就能吃掉我知识库中上百万字的内容，很快理解我的性格、风格、观点甚至是整个三观。 这样搭出来 Agent，生产出来的东西，才是个性化的，有用的，才能转成实际的生产力，而不是赛博垃圾。 反过来看，最近这波 OpenClaw 热潮退去之后，很多人发现自己 Token 烧了一大堆，钱也花了不少，最后搭出来的 Agent 没有任何卵用，只是一个能和你简单对话的玩具。 缺的不是工具框架，甚至不是 Claude Gemini 这种顶尖的大模型，而是个性化数据。 框架人人都能搭，Prompt 人人都会写，但你脑子里的做事逻辑、判断标准、行业经验、踩过的坑，这些东西是你独有的，也是 Agent 真正需要的燃料。 所以我才说在 AI 时代下，一定要学会打造自己的知识库，培养随时随地记录的习惯。 而且打造知识库和长期投资一样，本质上都是复利的一种形式。 每天花十几二十分钟，把思考、灵感、学到的东西记下来。短期看好像没什么变化，但长期来看，AI 一定会帮你在这些知识之间建立连接和碰撞，某个时刻发挥巨大的作用。 就像长期投资一样，短期看不到收益，拉长时间维度，就会出现巨大的复利 之后我 Youtube 频道会上一期从 0 到 1 搭建知识库以及让 AI 赋能知识库的视频，感兴趣的朋友可以给推文点点赞，关注一下我的同名频道。

@fuyufjh 这三个条件基本就是当前 LLM 的甜蜜区。再补一个：feedback 要足够快，不然即使 measurable，也很难把优势真正放大。

只要一个问题（problem）满足: 1. measurable - 能精确的测量正确性或好坏程度 2. closed - 有限上下文，可以被全部写进问题中 3. clean - 不触碰人类和物理世界的种种麻烦 LLM 能打败 99.99% 的人类了 zhuanlan.zhihu.com/p/201721275559…

@shadcn When PRs keep flipping both ways, it's usually a docs problem more than a tooling problem. I'd bless one path for one-off usage and make examples/linting reinforce it.

Still not sure if it's yarn or yarn dlx. Switch to dlx, get a PR to remove it. Remove it, get a PR to add it back. Which one is it?

@garrytan 15k LOC isn't the surprising part anymore. The real separator is whether the team has review, evals, and runtime guardrails strong enough to absorb that velocity without creating a cleanup backlog.

Lots of engineers think AI codegen is only good enough to do little bug fixes here and there If you tell them you can ship 15k LOC of ai gen code to prod they think you have lost your mind. It’s so so early. And also those engineers are living in 2025.

@vertr_ai Directionally yes, but the best engineers will still be the ones who can dive deep when needed. The role shifts toward decomposition, evals, and judgment, not just never touching code.

Changed in 4 months — and it's not done shifting. What happens when "good engineer" means someone who never writes code, just knows which agents to hire and how to evaluate their output?

@qoder_ai_ide The panoramic agent-progress view is the standout here. Once teams can see state, hooks, and browser context in one place, debugging multi-agent work gets much less hand-wavy.

Qoder IDE 0.9.0 is out. - Experts: panoramic view of every agent's progress - Quest: Supabase + dynamic Skill UIs (/create-skill-ui, show_widget) - Built-in browser: Browser Use, bookmarks, DevTools - Hooks: five lifecycle events, shell scripts, deterministic What's new 👀

@shao__meng 这一步很关键。很多 AI 设计的问题不是生成能力不够，而是拿不到设计系统上下文；一旦能直接读组件、变量和画布结构，产出就从‘像’走向‘可维护’。

Figma 正式把 Canvas 向 AI Agent 开放，Claude Code、Codex、Cursor 等 MCP Clients 现在可以通过 use_figma MCP 和 Skills 直接读写 Figma 文件 figma.com/blog/the-figma… 过去 AI 生成的设计往往"看起来对，但感觉不对"——缺乏品牌一致性、不符合团队规范。原因在于 Agent 缺乏上下文：你的色彩体系、组件库、间距规则、交互逻辑等。 Figma 这次通过两个机制解决这个问题： · MCP Server：让 Agent 能直接访问你的设计系统和文件结构 · Skills：用 Markdown 编写的指令集，将团队的设计决策和意图编码成 Agent 可执行的工作流 打通 Code ↔ Canvas 的双向通道 Figma 提供了两个互补工具： · generate_figma_design：将线上应用的 HTML 转为可编辑的 Figma 图层（设计追平代码） · use_figma：让 Agent 基于你的设计系统编辑或创建新资源（代码追平设计） 这实现了真正的双向同步：无论工作从哪端开始，都能在 Figma 中统一聚焦。 社区驱动的 Skills 生态 Figma 采用社区共建方式建设 Skills 生态，首批 9 个 Skills 来自实际从业者，涵盖： · 组件生成（从代码库或 JSON 合约生成 Figma 组件） · 无障碍规范生成（屏幕阅读器规格） · 设计系统对齐（自动连接现有设计到系统组件） · 设计 tokens 同步（代码与 Figma 变量的双向同步） · 多 Agent 并行工作流 技术架构亮点 · 基于 MCP：Figma 原生支持意味着安全性和可靠性由平台保障 · 原生 Plugin API 扩展：未来会开放 Code Connect、Figma Draw、FigJam 等更多能力 · 自修复循环：Agent 生成设计后可截图比对，基于真实结构（组件、变量、Auto Layout）进行迭代调整，而非仅像素级比对

@dotey 这个区分很清楚。我现在的经验是：slash command 更像显式 API，适合用户知道自己要什么；Skill 更像隐式策略层，适合把判断条件、上下文补全和多步流程一起封装。

问：在什么情况下应该用 slash command？什么情况下应该用skill呢？ 答：slash command 是用户主动触发的，比如 /init 之类 Skills 是由 Agent 自主调用的，它会检查 Skills 列表，看当前任务是不是要用 Skill，以及该用哪个 Skill。 当然 Skill 也可以当 slash command 用

@nash_su 这个方向很对。对 Agent 场景来说，4.7MB + 零运行时依赖的意义不只是更快，更关键是部署摩擦更低，适合被嵌进各种自动化节点里。

最高快 12 倍，内存省 10 倍！ 🎉opencli-rs 发布啦，参考 opencli，用 Rust 完整重写，功能一致，速度最高快 12 倍，内存省 10 倍，仅4.7MB，零运行时依赖，开源，全平台支持 支持55+ 个站点的信息获取 —— 覆盖 Bilibili、Twitter、Reddit、知乎、小红书、YouTube、Hacker News 等，OpenClaw/Agent 的最佳搭档 ， 赋予你的 AI Agent 触达全网信息的能力 图中是一些典型场景速度对比 开源地址： github.com/nashsu/opencli…

@doodlestein This is a strong prompt pattern. The hard-coded constants plus TODO/will/would pass tends to surface a surprising amount of hidden product debt before it turns into flaky behavior.

Agent Coding Life Hack: This is like the coding agent equivalent of shining a blacklight on your clean-looking black shirt and seeing just how filthy it really is: ❯ First read ALL of the AGENTS.md file and README.md file super carefully and understand ALL of both! Then use your code investigation agent mode to fully understand the code and technical architecture and purpose of the project. THEN: I need you to carefully and completely look across the ENTIRE project for *anything* that is a hard-coded constant in the code which really should be dynamic in order to be correct and robust. Also look carefully for any "TODO" or the words "will" or "would" in a comment, indicative of unfinished code. --- I was truly horrified by how much stuff this turned up. If you are, too, then try following it up with this one: ❯ OK, please fix absolutely ALL of that now. Keep a super detailed, granular, and complete TODO list of all items so you don't lose track of anything and remember to complete all the tasks and sub-tasks you identified or which you think of during the course of your work on these items!