跳到正文
原文
François Chollet· @fchollet · X·· 21 天前AI 评分44
AI 导读

可以委托写代码。永远不要委托理解。 如果代码此前是你管理理解的事实来源,那么你需要一个新的事实来源载体。如果以代码为中心的工作流曾是你形成这种理解的方式,那么你需要新的工作流。

正文

Delegate coding. Never delegate understanding.

If code was previously your source of truth for managing understanding, then you need a new source of truth artifact. If code-centric workflows were how you developed that understanding, then you need new workflows.

引用voxium@v0xium
I am done with this shit. It is over. The state of engineering right now is horrible. It has been half a month since I started a new role at a big company. Nobody knows anything here. The specs, code, tests, PRDs, tickets, resolution of those tickets, reports, etc., everything is made by Claude Code. Nobody on my team likes this. They are being forced to ship as much as they can. I have heard multiple times from higher management that pushing code is not a bottleneck, so why are we slow? People are working 12 to 13 hours a day just to press enter. Nobody is reading anything. Humans in corporate are doing nothing on their own. Everyone, literally everyone, from an L1 to an L7 engineer here is doing the same thing. Talk to Claude. There is no sense of victory. Nobody is resolving bugs. In reality, nobody is thinking anymore. Everything is done by LLMs. It is so soul-sucking. I would not mind it, to be honest, if we were at least given the time to check out the code and see what is going where. But no, the goal is to just ship. No matter what happens.
在 X 查看被引用的帖子

来源:François Chollet · x.com