{"@context":"https://schema.org","@type":"NewsArticle","generatedAt":"2026-07-28T06:20:51.496Z","headline":"代码成本崩盘后的工程管理：一位工程总监的反思","description":"一位工程总监基于过去一年的笔记指出，代码生产成本已崩溃且不会回升，但AI工具是否让工程团队显著提速尚无定论。管理实践应基于其底层假设是否成立来评估：依赖代码编写成本的做法需重新审视，而依赖人类协调、信任构建或正确性验证的做法则未改变。正确性验证中的机械性检查（类型、测试、契约）正因AI加速，但语义验证（业务需求、监管风险）仍依赖人类判断，AI自检无法发现共享盲点。","url":"https://www.aioga.com/news/cms0yvk8o0042ro956e389rlb/","mainEntityOfPage":"https://www.aioga.com/news/cms0yvk8o0042ro956e389rlb/","datePublished":"2026-07-25T22:34:51.368Z","dateModified":"2026-07-25T22:34:51.368Z","inLanguage":"zh-CN","publisher":{"@type":"NewsMediaOrganization","name":"Aioga","url":"https://www.aioga.com"},"citation":["https://karimjedda.com/engineering-management-after-cost-of-code-collapse","https://aihot.virxact.com/items/cms0yvk8o0042ro956e389rlb"],"canonicalUrl":"https://www.aioga.com/news/cms0yvk8o0042ro956e389rlb/","directAnswer":{"@type":"Answer","text":"Aioga 编辑摘要：一位工程总监基于过去一年的笔记指出，代码生产成本已崩溃且不会回升，但AI工具是否让工程团队显著提速尚无定论。 Aioga 将其归入「技巧观点」方向，重点关注它对真实使用和行业竞争的影响。","url":"https://www.aioga.com/news/cms0yvk8o0042ro956e389rlb/","dateCreated":"2026-07-25T22:34:51.368Z","author":{"@type":"Organization","@id":"https://www.aioga.com/authors/aioga-editorial/#editorial-team","name":"Aioga Editorial Team","url":"https://www.aioga.com/authors/aioga-editorial/"}},"evidence":[{"@type":"CreativeWork","name":"karimjedda.com source article","url":"https://karimjedda.com/engineering-management-after-cost-of-code-collapse","datePublished":"2026-07-25T22:34:51.368Z","provider":{"@type":"Organization","name":"karimjedda.com","url":"https://karimjedda.com/engineering-management-after-cost-of-code-collapse"}},{"@type":"CreativeWork","name":"AIHot archive record","url":"https://aihot.virxact.com/items/cms0yvk8o0042ro956e389rlb","datePublished":"2026-07-25T22:34:51.368Z","provider":{"@type":"Organization","name":"AIHot","url":"https://aihot.virxact.com/items/cms0yvk8o0042ro956e389rlb"}}],"aggregationSource":"Hacker News 热门（buzzing.cc 中文翻译）","originalPublisher":{"name":"karimjedda.com","url":"https://karimjedda.com/engineering-management-after-cost-of-code-collapse"},"article":{"id":"cms0yvk8o0042ro956e389rlb","slug":"cms0yvk8o0042ro956e389rlb","url":"https://www.aioga.com/news/cms0yvk8o0042ro956e389rlb/","title":"代码成本崩盘后的工程管理：一位工程总监的反思","title_en":"代码成本崩盘后的工程管理","summary":"一位工程总监基于过去一年的笔记指出，代码生产成本已崩溃且不会回升，但AI工具是否让工程团队显著提速尚无定论。管理实践应基于其底层假设是否成立来评估：依赖代码编写成本的做法需重新审视，而依赖人类协调、信任构建或正确性验证的做法则未改变。正确性验证中的机械性检查（类型、测试、契约）正因AI加速，但语义验证（业务需求、监管风险）仍依赖人类判断，AI自检无法发现共享盲点。","source":"Hacker News 热门（buzzing.cc 中文翻译）","sourceUrl":"https://karimjedda.com/engineering-management-after-cost-of-code-collapse","aiHotUrl":"https://aihot.virxact.com/items/cms0yvk8o0042ro956e389rlb","publishedAt":"2026-07-25T22:34:51.368Z","category":"技巧观点","score":57,"selected":false,"articleBody":["I have been a director of engineering for a bit over three years now, and I still hear and read what I call the \"old rules\" repeated over and over: a director should not spend time coding, good work takes time, protect the team from the business, get consensus before you commit, etc.","For a while I thought the people repeating these lines were behind. Then we introduced LLMs in my org and the cost of producing code dropped, and I started checking each rule against the assumption underneath it. The surprising realization was that about half of the old rules were resting on assumptions that broke and the other half were resting on assumptions that did not, and a few of those matter more now than they did before.","What follows is a cleaned-up version of notes I accumulated over the past year. Gemini 4 helped with the editing.","The cost of producing plausible code has collapsed and it is not going back. Almost every claim beyond that is either unproven or wrong.","If you rebuild your management practices on the narrow claim, you will be right. If you rebuild them on the broad claims you are gambling with other people's careers and calling it a conclusion.","Every management practice rests on a certain assumption. Velocity tracking rests on output being a usable proxy for effort. Six month onboarding rests on syntax being slow to learn. Consensus driven architecture rests on change being expensive. Headcount planning rests on output scaling with people, and so on.","The question for each practice is not how old it is but rather what the practice actually rests on.","If a practice rests on the cost of writing code, put it under review because that cost moved. If it rests on how humans coordinate, build trust, allocate attention, or verify correctness, then nothing about it changed, no matter how dated the ritual feels.","This sounds obvious but I think many are sorting by feel: whatever seems modern stays, whatever seems old goes. That produces teams that abandoned useful friction and kept useless process, because the age of a practice and the validity of a practice are unrelated variables.","Be suspicious of anyone, including your own team, who reports large speedups and only that. The gains I'm familiar with show up clearly in greenfield work, boilerplate, and unfamiliar territory. They fade or invert in deep work on systems the engineer already understands. I'm very much looking forward to data and studies done after the Q4 2025, where a new breed of models were launched that completely eclipsed the capabilities of the ones older reports and research were based on.","However, the gap between felt speed and measured speed is itself a management problem. If your engineers feel faster and ship the same amount with more defects, you will staff wrong, plan wrong, and set expectations with the business that you cannot meet. The first job in an AI adopting org is instrumentation being honest enough to tell you whether you have accelerated at all.","Velocity, pull request counts, and tickets closed were always imperfect. They survived because the thing they approximated ie the effort of writing code was genuinely scarce, so the noise stayed within tolerable bounds.","Now the proxied thing is cheap. That does not leave the metrics merely imperfect but actually actively misleading, because the cheapest way to raise them is to generate volume, and volume is the one thing your organization no longer lacks.","AI-specific metrics solve the wrong problem. I think acceptance rates and prompt counts are the same mistake in a new form. The durable move is older and harder: measure outcomes for the business and the health of the system, and treat code volume as a cost to be justified rather than output to be praised. Good engineers said this before LLMs. It was true then. It is enforceable now in a way it was not, because nobody can argue that writing more code was the hard part.","The rule that good work takes time splits cleanly in two.","Plumbing time collapsed. Scaffolding a service, generating tests, translating between frameworks, writing the first draft of a migration: all of this is fast now, and any timeline built on those costs deserves compression.","AI systems now check and correct code faster than any human reviewer, and pretending otherwise costs credibility. One one hand, mechanical verification is collapsing. Anything where correct can be expressed as a machine-checkable artifact: types, tests, contracts, lint rules, invariants, canary metrics. Agents run the test loop, read the failure, fix the diff, and run it again at a speed no reviewer matches. If your correctness lives in this layer, your checking time is genuinely falling, and it will keep falling.","But notice what makes this layer fast. It is fast because someone already wrote down what correct means, in a form a machine can evaluate. The specification did the work & the checker reads it.","Semantic verification is a different matter. Does the code implement the policy the business actually needs? Does this trade-off match your regulatory exposure? Here, correct lives in human heads and institutional history. AI checking AI has a structural problem: the checker shares training data, biases, and blind spots with the generator. Both layers fail in the same places for the same reasons. Self-review catches the typo. It does not catch the shared misunderstanding.","I believe three consequences follow, and the core of this post:","So verification still sets throughput. What moved is the location of the constraint: from checking speed to specification quality, and to the willingness of a specific human to own the result.","Nobody knows how to train engineers for this environment.","The judgment you want in a senior engineer was historically built by doing the work that AI now absorbs: fixing small bugs, writing boilerplate, getting stuck and then unstuck: these were not just tasks but actually the practice that produced judgment. If the machine takes the practice, the pipeline that produces seniors breaks, and it breaks on a delay, so you will not notice for three to five years.","There are plausible responses. Structured review of generated code, deliberate unassisted exercises, rotations through testing and verification work, earlier exposure to real systems under close senior oversight. I am running versions of some of these. I cannot tell you they work, because the outcome variable is the quality of a senior engineer half a decade from now.","What I can tell you is that anyone who claims to have solved this, whether vendor, essayist, or conference speaker, is selling something. Treat the pipeline as an open problem you personally own. It has the longest delay between action and evidence, and the fewest chances to correct course.","\"A director should not code.\" The director who dabbles, reviews pull requests to feel useful, and becomes a bottleneck is real. So is the director whose mental model of the work is five years stale, who cannot tell the difference between a team that is genuinely faster and a team that is generating confident, wrong output at volume (slop cannons). The resolution is calibration. You do not need to ship. You need enough direct contact with the tools and the output that you cannot be fooled in either direction, by the hype or by the dismissal.","\"Shield the team from the business.\" The assumption underneath this one is that attention is finite and context switching is expensive. That assumption is intact. What changed is the cost of starving the team of context. Engineers prompting AI tools without business context just produce fluent, plausible, wrong work, at scale. The revision is not to flood everyone with everything but to stop filtering by default and start selecting deliberately: which context, to whom, at what level of detail.","\"We need consensus before we commit.\" Consensus was always about commitment and coordination, and the cost of surviving cheap pivots. What cheap pivots change is which decisions need consensus at all. Reversible decisions, or two-way doors, should be made by the smallest group possible, quickly, because a wrong reversible call is now cheap to undo. Irreversible decisions still deserve the slow process. The actual skill is classification, and most organizations misclassify constantly, treating reversible technical choices as permanent and permanent organizational choices as casual.","\"We need more headcount.\" The unit economics of output changed, so every request deserves a harder question than it got three years ago: what part of this work is judgment, and what part is production we keep hiring humans to do? But do not overcorrect. Adding people to a late project still makes it later. Coordination cost, onboarding drag, and communication overhead did not change with the price of syntax. Scrutinize headcount because output per person moved, not because people stopped being the expensive part.","Three years in, here is what I believe about persistence. Practices survive for reasons, and the reasons are always mixed: some obsolete, some still valid, some political. When you hear an old rule repeated, you are usually hearing a person defend the valid part with the wrong argument or defend the obsolete part with the argument that used to work.","Treating persistence as stupidity is the failure mode of every management fashion, and the AI fashion is not exempt. The leaders who will look worst in five years are not the cautious ones but the ones who replaced thinking with a new set of slogans, even accurate sounding slogans, and ran their orgs on claims that were still unmeasured.","The temptation, when a technology this large arrives, is to pick a posture: burn the old playbook or defend it. Both postures are laziness. The playbook was never a single object. It was a hundred pages, some about the cost of typing and some about the nature of people, bound together so tightly that we forgot they were separable.","Do not let anyone, including a confident essay, including this one, convince you those were ever the same page.","I was told recently that AIs will soon do the management too, including the sorting. I thought about it over the weekend and I believe it is partly right.","Management has an information-routing function: aggregating status, tracking progress, translating updates into dashboards, forecasting schedules, collating performance data. A large share of what a management layer does daily is moving information between formats and people. LLMs are excellent at this, and the value of this is going to zero. If your management layer earns its keep by summarizing Jira, then yeah, that's over.","Then there is the judgment function: hiring, firing, promotion, deciding which rule applies in this situation with these people, owning a bad call. This has the same structure as verification. Someone checks the output against reality, and someone absorbs the consequence.","We're back to the generation argument mentionned above, but applied to management work: management output becomes abundant, therefore cheap. But the thesis of everything above is that when generation is abundant, verification is the constraint. Machine-generated management still needs a human to verify it against the org's actual behavior and to sign the result. So this is perhaps not the end of the manager but rather the manager's demotion to editor and owner. It is the exact same shift the individual contributor is going through.","There is one more problem with delegating the sorting. Sorting requires a model of how your org actually behaves: trust relationships, hallway knowledge, the consequences of past decisions. Almost none of this is written down. The written record of an org is a small, polished fraction of the org, and a model sorts on the record. Worse, what the model encodes from its training is the industry's average judgment. An LLM will sort your playbook roughly the way the median org would. If your strategy is to be the median org, that is fine. Differentiation lives exactly in the decisions you refuse to delegate.","Here is my honest concession, the sorting as an intellectual exercise is automatable. I used AI to pressure-test parts of this essay, and its first-pass audit was decent. What is not automatable is the political and moral work.","Where this goes: spans of control widen, layers compress, the information-routing tier of management is genuinely at risk, and titles will persist longer than functions. The management work that survives is the work that cannot be written down, cannot be averaged, and cannot be signed by anyone else.","The residual of engineering work is specification and ownership. The residual of management work is judgment and ownership. Same shape, two levels.","At every level of the org, the work that survives is the work someone has to sign.","Let's push the extrapolation to its limit to really drive it home. Imagine an org where agents write the code, run the checks, route the status, schedule the work, and draft the plans. Humans set direction, define what correct means, and sign. Everything between the signature and the shipped result is machinery. Now run the timeline backwards: imagine this org came first, and someone proposed the one you actually run. We will hire hundreds of expensive people to produce text by hand, at typing speed. We will arrange them in layers, where the job of each layer is to summarize the layer below for the layer above. We will synchronize their calendars in rooms so they can tell each other what already happened. We will measure their worth by how much they emit. Nobody would fund this proposal. It is slow, it loses information at every handoff, and it spends the scarcest resource in the building on work the machinery already does.","The org you run was never designed but it rather accumulated. Every role, ritual, and layer exists because something used to be expensive: typing, routing, checking, remembering. The prices moved. The org chart did not. In the agentic limit , the chart stops recording who produces and starts recording who signs . Headcount stops measuring capacity and starts measuring how much accountability you can afford. The orgs that get there will look small, quiet, and mostly empty: a short list of names attached to a long list of decisions, and nothing else left to manage."],"articleImages":[{"sourceUrl":"https://karimjedda.com/content/images/2026/07/meowtivate.jpeg","alt":"Engineering management after the cost of code collapsed","afterParagraph":0,"url":"/media/articles/cms0yvk8o0042ro956e389rlb/5ab2c3ab5f0024a0.jpg"},{"sourceUrl":"https://www.gravatar.com/avatar/e9e5d24cce9a566ed378ead6b545a46e?s=250&r=x&d=mp","alt":"Karim Jedda","afterParagraph":43,"url":"/media/articles/cms0yvk8o0042ro956e389rlb/60d0e919c20f20e4.png"}],"mediaStatus":"ok","articleBodyZh":["我担任工程总监已经有三年多了，我仍然会听到和看到那些我称之为“旧规则”的话被一遍又一遍地重复：总监不应该花时间编程，好的工作需要时间，要保护团队免受业务干扰，在做出承诺前要达成共识，等等。","有一段时间，我以为重复这些话的人落伍了。然后我们在组织中引入了大型语言模型（LLMs），代码生产成本下降了，我开始检查每条规则背后的假设。令人惊讶的是，大约一半的旧规则建立在已经失效的假设上，另一半建立在仍然有效的假设上，而且其中一些甚至比以前更重要。","以下是我在过去一年中积累的笔记的整理版。Gemini 4 帮助进行了编辑。","生成合理代码的成本已经崩塌，并且不会回升。除了这一点之外的几乎所有说法要么未经验证，要么是错误的。","如果你基于这一狭义说法重建管理实践，你就是正确的。如果你基于广义说法重建管理实践，那你就是在拿别人的职业生涯赌博，并称之为结论。","每一种管理实践都建立在某种假设之上。速度追踪依赖于产出是工作努力的可用代理；六个月的入职培训依赖于语法学习缓慢；共识驱动的架构依赖于变更成本高；人员编制规划依赖于产出随人数扩展，等等。","对于每种实践来说，问题不是它存在多久，而是它实际依赖的是什么。","如果一项实践依赖于编写代码的成本，那就需要重新评估，因为成本已经发生变化。如果它依赖于人类如何协调、建立信任、分配注意力或验证正确性，那么无论仪式看起来多么过时，都没有改变。","这听起来很明显，但我认为很多人是凭感觉在排序：看起来现代的保留，看起来老的放弃。这会导致团队放弃有用的摩擦，却保留无用的流程，因为实践的年龄与其实效性是无关的变量。","对任何人，包括你自己的团队，如果他们只报告巨大加速而没有其他信息，都要保持怀疑。我熟悉的性能提升通常在新项目、模板代码以及不熟悉的领域中表现明显。但在对工程师已经熟悉的系统进行深度工作时，这些提升会逐渐消失或反转。我非常期待在2025年第四季度之后的数据和研究，那时将推出一类全新的模型，其能力完全超越了以往研究和报告所基于的模型。","然而，感受到的速度与实际测得的速度之间的差距本身就是一个管理问题。如果你的工程师感到更快，但交付量相同且缺陷更多，你将会错误地安排人员、制定错误的计划，并向业务设定无法实现的期望。AI 采纳组织的首要任务是进行足够诚实的度量，以告诉你是否真的实现了加速。","速度、拉取请求数量和关闭的工单数量一向不完美。它们之所以能继续使用，是因为它们近似的指标，即编写代码的投入，确实稀缺，所以噪音仍然在可容忍的范围内。","现在，代理的对象已经变得廉价。这不仅使指标变得不完美，更实际上具有误导性，因为提升指标最便宜的方法是产生大量代码，而组织现在真正不缺的正是数量。","AI特定的指标解决了错误的问题。我认为接受率和提示次数只是以新形式出现的同样错误。持久的做法更古老也更困难：衡量业务成果和系统健康，将代码量视为需要合理化的成本而非值得赞扬的产出。优秀的工程师在大型语言模型出现之前就已经这么说了。当时就是真理。现在可以执行这一点，而以前不可行，因为没人能争辩说写更多代码才是难点。","优秀工作需要时间的规律可以清晰地分为两类。","基础工作时间已经大幅缩短。搭建服务框架、生成测试、在不同框架之间转换、编写迁移的初稿：这些现在都很快，而且任何基于这些成本制定的时间表都应当被压缩。","AI 系统现在检查和修复代码的速度比任何人类审查员都快，假装不是这样会损失可信度。一方面，机械化验证正在崩溃。任何可以用机器可检查的工件表达正确性的东西：类型、测试、合同、lint 规则、不变量、金丝雀指标。智能体运行测试循环，读取失败信息，修复差异，再次运行，速度是任何审查员无法匹敌的。如果你的正确性存在于这一层，你的检查时间确实在下降，并且会继续下降。","但请注意，是什么让这一层变快。它之所以快，是因为已经有人写下了正确性的定义，以机器可以评估的形式。规范完成了工作，检查器读取它。","语义验证则是另一回事。代码是否实现了业务实际需要的策略？这种权衡是否符合你的监管风险？在这里，正确性存在于人类的头脑和制度历史中。AI 检查 AI 有结构性问题：检查器与生成器共享训练数据、偏见和盲点。两层在同样的地方以同样的原因失败。自我审查可以发现拼写错误，但无法发现共同的误解。","我认为有三个后果，且这是这篇文章的核心：","所以验证仍然决定吞吐量。变化的是约束的位置：从检查速度变为规范质量，以及具体某个人愿意对结果负责的意愿。","没人知道如何培训工程师以适应这种环境。","你希望资深工程师拥有的判断力，历史上是通过完成 AI 现在吸收的工作来建立的：修复小错误、编写模板、遇到问题再解决问题——这些不仅是任务，实际上是培养判断力的实践。如果机器吸收了这些实践，产生资深工程师的流程就会破裂，而且这种破裂有延迟，所以你在三到五年内都不会注意到。","有一些可行的应对措施。生成代码的结构化审查、刻意的无辅助练习、在测试和验证工作中的轮岗、在资深监督下尽早接触真实系统。我正在运行其中的若干版本。我无法告诉你它们是否有效，因为结果变量是半十年后资深工程师的质量。","我能告诉你的是，任何声称已经解决这个问题的人，无论是供应商、散文作者还是会议演讲者，都在推销某种东西。把这个流程当作一个你个人拥有的开放问题。它在行动与证据之间的延迟最长，而且修正方向的机会最少。","“主管不应该编码。” 那些涉猎编码、审查 pull request 以感觉自己有用，并因此成为瓶颈的主管确实存在。还有那些工作心理模型陈旧五年，无法区分一个真正更快的团队与一个大量产生自信但错误输出的团队（结果混乱）的主管也同样存在。解决方法是校准。你不需要亲自发布。你需要与工具和输出有足够直接的接触，这样你就不会被任何一方迷惑，无论是炒作还是忽视。","“保护团队不受业务干扰。” 这一点背后的假设是注意力有限，而且上下文切换代价高。这一假设仍然成立。改变的是让团队缺乏上下文的代价。没有业务背景的工程师在提示 AI 工具时，只会大规模地产生流畅、看似合理但错误的结果。修正措施不是把所有信息都轰炸给每个人，而是停止默认过滤，并开始有意识地选择：哪种上下文，给谁，以及以何种细节层级。","“我们需要在提交前达成共识。” 共识一直是关于承诺与协调，以及承受低成本调整的能力。低成本调整改变的是哪些决策实际上需要共识。可逆决策，或“双向门”，应由最小的团队尽快做出，因为错误的可逆决策现在容易撤销。不可逆决策仍然需要慢过程。真正的技能是分类，而大多数组织一直在错误分类，把可逆的技术选择当作永久的，把永久的组织决策当作随意的。","“我们需要增加人手。”产出的单位经济学发生了变化，所以每一个请求都值得比三年前提出更严格的问题：这项工作中哪一部分是判断，哪一部分是我们继续雇人做的生产？但不要过度修正。给一个已延期的项目增加人员只会让它更晚。协调成本、入职拖延和沟通开销并不会因为语法的价格而变化。要仔细审查人手数量，因为每个人的产出已经变化，而不是因为人不再是昂贵的部分。","三年过去了，这是我对持久性的看法。实践之所以延续，总有原因，而这些原因总是混合的：有些过时，有些仍然有效，有些是政治性的。当你听到一个老规则被重复时，你通常是在听一个人用错误的论点为有效部分辩护，或者用曾经有效的论点为过时部分辩护。","把持久性当作愚蠢是每种管理潮流的失败模式，而人工智能潮流也不例外。五年后看起来最糟的领导者不会是谨慎的人，而是那些用一套新的口号取代思考的人，即使这些口号听起来准确，并且在他们的组织中基于尚未衡量的主张运作。","当如此大规模的技术出现时，人们的诱惑是采取一种态度：烧掉旧的操作手册或者捍卫它。这两种态度都是懒惰。操作手册从来不是一件单一的物件。它有一百页，其中一些关于打字成本，一些关于人的本质，它们紧密结合，以至于我们忘记了它们可以分开。","不要让任何人，包括一篇自信的文章，包括这篇文章，让你相信这些页曾经是同一页。","最近有人告诉我，人工智能很快也会管理，包括排序工作。我在周末考虑了这件事，我认为部分是对的。","管理具有信息路由功能：汇总状态、跟踪进度、将更新转换为仪表盘、预测计划、整理绩效数据。管理层每天做的大部分工作就是在不同格式和人员之间移动信息。大语言模型在这方面非常出色，而这一价值将趋于零。如果你的管理层靠总结Jira来证明自己的价值，那么是的，那就是过度了。","然后是判断功能：雇用、解雇、晋升，决定在这种情况下适用于这些人的规则，并为错误的决定承担责任。这与验证具有相同的结构。有人将输出与现实进行核对，有人承担后果。","我们回到上文提到的生成论点，但应用于管理工作：管理输出变得丰富，因此成本低。但上述所有内容的核心论点是，当生成变得丰富时，验证成为瓶颈。机器生成的管理仍然需要人类将其与组织的实际行为进行核对，并签署结果。所以这或许不是经理的终结，而是经理降职为编辑者和拥有者。这正是个体贡献者所经历的相同转变。","委派排序还有一个问题。排序需要对你的组织实际行为有一个模型：信任关系、走廊知识、过去决策的后果。这几乎都没有被记录下来。组织的书面记录只是一小部分经过打磨的片段，而模型是基于记录进行排序的。更糟的是，模型从其训练中编码的是行业的平均判断。大型语言模型会大致按中位组织的方式对你的操作手册进行排序。如果你的策略是成为中位组织，那没问题。差异化正存在于你拒绝委派的决策中。","这是我诚实的承认，作为智力练习的排序是可以自动化的。我用人工智能对这篇文章的部分内容进行了压力测试，其初次审核效果不错。不可自动化的是政治和道德工作。","结果是：控制跨度扩大，层级压缩，管理的信息传递层确实面临风险，职位名称的存在会比职能持续更久。能够存续下来的管理工作是那些无法书面化、无法平均化、也无法由他人签署的工作。","工程工作的剩余部分是规范与拥有权。管理工作的剩余部分是判断与拥有权。形态相同，层级不同。","在组织的每一个层级，能够存续下来的工作是必须有人签署的工作。","让我们把外推推到极限，以真正让它深入人心。想象一个组织，代理人编写代码、运行检查、传递状态、安排工作、起草计划。人类设定方向，定义正确的标准，并签署。签署与最终交付结果之间的所有环节都是机器化的。现在把时间线倒推：想象这个组织先出现，然后有人提出你实际运作的那个组织。我们将雇佣数百名昂贵的员工手工生成文本，以打字速度进行。我们会把他们按层排列，每一层的工作是为上一层总结下一层的内容。我们会在房间里同步他们的日程，以便他们可以告诉彼此已经发生的事情。我们将他们的价值衡量为他们输出了多少。没有人会资助这个提议。它很慢，每次交接都会丢失信息，而且把建筑中最稀缺的资源用于机器已经能完成的工作。","你运行的组织从未被设计，而是逐渐积累的。每一个角色、仪式和层级的存在，都是因为某些事情过去很昂贵：打字、传递、检查、记忆。价格变动了，组织架构没有。在代理极限下，组织架构不再记录谁在生产，而开始记录谁签署。员工人数不再衡量产能，而是衡量你能承担多少责任。达到那个阶段的组织看起来会很小、很安静、大部分是空的：短短的名字列表对应着很长的决策列表，其他无事可管。"],"translationStatus":"translated","bodyOrigin":"source-page","editorial":{"summary":"Aioga 编辑摘要：一位工程总监基于过去一年的笔记指出，代码生产成本已崩溃且不会回升，但AI工具是否让工程团队显著提速尚无定论。 Aioga 将其归入「技巧观点」方向，重点关注它对真实使用和行业竞争的影响。","background":"背景分析：实践类内容的价值在于是否能被复现、是否有明确边界，以及它能否转化为稳定的开发或工作流方法。","viewpoint":"Aioga 判断：这条动态更适合作为行业观察信号，当前信息足以建立线索，但不足以推导长期结论。","implications":"影响分析：对相关团队而言，短期应先核对来源、可用范围和实际成本，再判断是否值得接入或跟进。","nextStep":"后续观察：继续观察示例是否可复现、工具版本变化、社区反馈和实际成本。","evidenceRefs":["title","summary","articleBody"],"confidence":"medium","status":"published","aiGenerated":false,"autoApproved":true,"generatedBy":"rule-safe-fallback","generatedAt":"2026-07-28T06:29:10.498Z","sourceHash":"5d4e0b98f6a51ad7","validation":{"passed":true,"mode":"rule-safe-fallback","checks":["schema","length","source-attribution","no-html"]}},"tags":["技巧观点","Hacker News 热门（buzzing.cc 中文翻译）"],"translations":{"zh-CN":{"title":"代码成本崩盘后的工程管理：一位工程总监的反思","summary":"一位工程总监基于过去一年的笔记指出，代码生产成本已崩溃且不会回升，但AI工具是否让工程团队显著提速尚无定论。管理实践应基于其底层假设是否成立来评估：依赖代码编写成本的做法需重新审视，而依赖人类协调、信任构建或正确性验证的做法则未改变。正确性验证中的机械性检查（类型、测试、契约）正因AI加速，但语义验证（业务需求、监管风险）仍依赖人类判断，AI自检无法发现共享盲点。","category":"技巧观点","source":"karimjedda.com","aggregationSource":"Hacker News 热门（buzzing.cc 中文翻译）","pageTitle":"代码成本崩盘后的工程管理：一位工程总监的反思 - Aioga AI资讯","description":"一位工程总监基于过去一年的笔记指出，代码生产成本已崩溃且不会回升，但AI工具是否让工程团队显著提速尚无定论。管理实践应基于其底层假设是否成立来评估：依赖代码编写成本的做法需重新审视，而依赖人类协调、信任构建或正确性验证的做法则未改变。正确性验证中的机械性检查（类型、测试、契约）正因AI加速，但语义验证（业务需求、监管风险）仍依赖人类判断，AI自检无法发现共享...","url":"https://www.aioga.com/news/cms0yvk8o0042ro956e389rlb/"},"en":{"title":"Engineering Management After a Code Cost Collapse: Reflections of an Engineering Director","summary":"An engineering director noted based on the past year's notes that the cost of code production has collapsed and will not recover, but it is still inconclusive whether AI tools significantly accelerate engineering teams. Management practices should be evaluated based on whether their underlying assumptions hold: practices that rely on code writing costs need to be reexamined, while practices that rely on human coordination, trust building, or correctness verification remain unchanged. Mechanical checks in correctness verification (types, tests, contracts) are being accelerated by AI, but semantic validation (business requirements, regulatory risks) still depends on human judgment, and AI self-checks cannot identify shared blind spots.","category":"Insights","source":"Hacker News 热门（buzzing.cc 中文翻译）","aggregationSource":"Hacker News 热门（buzzing.cc 中文翻译）","pageTitle":"Engineering Management After a Code Cost Collapse: Reflections of an Engineering Director - Aioga AI News","description":"An engineering director noted based on the past year's notes that the cost of code production has collapsed and will not recover, but it is still inconclusive whether AI tools sign...","url":"https://www.aioga.com/en/news/cms0yvk8o0042ro956e389rlb/","contentTranslated":true,"sourceHash":"1140c9917d8e84a2","translatedAt":"2026-07-26T11:43:14.197Z"},"ja":{"title":"コードコスト崩壊後のプロジェクト管理：あるエンジニアリングディレクターの反省","summary":"あるエンジニアリングディレクターは、過去1年のノートに基づき、コード生産コストは崩壊しており回復しないと指摘したが、AIツールがエンジニアリングチームの大幅な速度向上をもたらすかどうかはまだ結論が出ていない。マネジメントの実践は、その根底にある仮定が成立するかどうかに基づいて評価すべきである：コード作成コストに依存する方法は再検討が必要である一方、人間の調整、信頼構築、または正確性の検証に依存する方法は変わらない。正確性の検証における機械的チェック（型、テスト、契約）はAIによって加速されているが、意味上の検証（業務要求、規制リスク）は依然として人間の判断に依存しており、AIの自己チェックでは共有された盲点を発見できない。","category":"ヒントと視点","source":"Hacker News 热门（buzzing.cc 中文翻译）","aggregationSource":"Hacker News 热门（buzzing.cc 中文翻译）","pageTitle":"コードコスト崩壊後のプロジェクト管理：あるエンジニアリングディレクターの反省 - Aioga AIニュース","description":"あるエンジニアリングディレクターは、過去1年のノートに基づき、コード生産コストは崩壊しており回復しないと指摘したが、AIツールがエンジニアリングチームの大幅な速度向上をもたらすかどうかはまだ結論が出ていない。マネジメントの実践は、その根底にある仮定が成立するかどうかに基づいて評価すべきである：コード作成コストに依存する方法は再検討が必要である一方、人間の調整...","url":"https://www.aioga.com/ja/news/cms0yvk8o0042ro956e389rlb/","contentTranslated":true,"sourceHash":"1140c9917d8e84a2","translatedAt":"2026-07-26T11:43:21.295Z"},"ko":{"title":"코드 비용 붕괴 이후의 프로젝트 관리: 한 엔지니어링 디렉터의 성찰","summary":"한 엔지니어링 총괄은 지난 1년간의 노트를 기반으로 코드 생산 비용이 붕괴했고 다시 회복되지 않을 것이라고 지적했지만, AI 도구가 엔지니어링 팀의 속도를 크게 높였는지는 아직 결론이 나지 않았다. 관리 실천은 그 근본 가정이 성립하는지 여부에 따라 평가해야 한다: 코드 작성 비용에 의존하는 접근 방식은 재검토가 필요하고, 인간의 조정, 신뢰 구축 또는 정확성 검증에 의존하는 접근 방식은 변하지 않는다. 정확성 검증에서의 기계적 검사(타입, 테스트, 계약)는 AI로 인해 가속화되고 있으나, 의미 검증(비즈니스 요구 사항, 규제 위험)은 여전히 인간의 판단에 의존하며, AI 자체 검증은 공유된 맹점을 발견할 수 없다.","category":"인사이트","source":"Hacker News 热门（buzzing.cc 中文翻译）","aggregationSource":"Hacker News 热门（buzzing.cc 中文翻译）","pageTitle":"코드 비용 붕괴 이후의 프로젝트 관리: 한 엔지니어링 디렉터의 성찰 - Aioga AI 뉴스","description":"한 엔지니어링 총괄은 지난 1년간의 노트를 기반으로 코드 생산 비용이 붕괴했고 다시 회복되지 않을 것이라고 지적했지만, AI 도구가 엔지니어링 팀의 속도를 크게 높였는지는 아직 결론이 나지 않았다. 관리 실천은 그 근본 가정이 성립하는지 여부에 따라 평가해야 한다: 코드 작성 비용에 의존하는 접근 방식은 재검토가 필요하고...","url":"https://www.aioga.com/ko/news/cms0yvk8o0042ro956e389rlb/","contentTranslated":true,"sourceHash":"1140c9917d8e84a2","translatedAt":"2026-07-26T11:44:05.777Z"},"es":{"title":"Gestión de proyectos después del colapso del costo del código: Reflexiones de un director de ingeniería","summary":"Un director de ingeniería señaló en notas basadas en el año pasado que el costo de producción de código se ha desplomado y no se recuperará, pero aún no hay un consenso sobre si las herramientas de IA permiten que los equipos de ingeniería aceleren significativamente. Las prácticas de gestión deben evaluarse en función de si sus suposiciones subyacentes son válidas: los enfoques que dependen del costo de redacción de código necesitan ser revisados, mientras que los que dependen de la coordinación humana, la construcción de confianza o la verificación de corrección no cambian. Las verificaciones mecánicas en la verificación de corrección (tipos, pruebas, contratos) se están acelerando gracias a la IA, pero la verificación semántica (requisitos comerciales, riesgos regulatorios) todavía depende del juicio humano, y la autoevaluación de IA no puede detectar puntos ciegos compartidos.","category":"Ideas","source":"Hacker News 热门（buzzing.cc 中文翻译）","aggregationSource":"Hacker News 热门（buzzing.cc 中文翻译）","pageTitle":"Gestión de proyectos después del colapso del costo del código: Reflexiones de un director de ingeniería - Aioga Noticias de IA","description":"Un director de ingeniería señaló en notas basadas en el año pasado que el costo de producción de código se ha desplomado y no se recuperará, pero aún no hay un consenso sobre si la...","url":"https://www.aioga.com/es/news/cms0yvk8o0042ro956e389rlb/","contentTranslated":true,"sourceHash":"1140c9917d8e84a2","translatedAt":"2026-07-26T11:44:08.950Z"},"fr":{"title":"Gestion de projet après l'effondrement des coûts du code : Réflexions d'un directeur d'ingénierie","summary":"Un directeur technique a noté, sur la base des notes de l'année dernière, que le coût de production du code s'est effondré et ne remontera pas, mais il n'y a pas encore de consensus sur le fait que les outils d'IA permettent aux équipes d'ingénierie d'accélérer de manière significative. Les pratiques de gestion doivent être évaluées en fonction de la validité de leurs hypothèses sous-jacentes : les approches reposant sur le coût de production du code doivent être réexaminées, tandis que celles dépendant de la coordination humaine, de la construction de la confiance ou de la vérification de la justesse ne changent pas. Les vérifications mécaniques dans la validation de la justesse (types, tests, contrats) s'accélèrent grâce à l'IA, mais la validation sémantique (exigences commerciales, risques réglementaires) dépend toujours du jugement humain, et l'auto-vérification par l'IA ne peut pas détecter les angles morts partagés.","category":"Analyses","source":"Hacker News 热门（buzzing.cc 中文翻译）","aggregationSource":"Hacker News 热门（buzzing.cc 中文翻译）","pageTitle":"Gestion de projet après l'effondrement des coûts du code : Réflexions d'un directeur d'ingénierie - Aioga Actualités IA","description":"Un directeur technique a noté, sur la base des notes de l'année dernière, que le coût de production du code s'est effondré et ne remontera pas, mais il n'y a pas encore de consensu...","url":"https://www.aioga.com/fr/news/cms0yvk8o0042ro956e389rlb/","contentTranslated":true,"sourceHash":"1140c9917d8e84a2","translatedAt":"2026-07-26T11:44:51.541Z"},"de":{"title":"Projektmanagement nach dem Zusammenbruch der Codekosten: Reflexionen eines technischen Leiters","summary":"Ein Ingenieurdirektor wies basierend auf den Notizen des vergangenen Jahres darauf hin, dass die Produktionskosten für Code zusammengebrochen sind und nicht wieder steigen werden, es jedoch noch kein abschließendes Urteil darüber gibt, ob KI-Tools das Engineering-Team signifikant beschleunigen. Managementpraktiken sollten auf der Bewertung ihrer zugrunde liegenden Annahmen beruhen: Praktiken, die auf den Kosten der Codeerstellung beruhen, müssen neu überdacht werden, während Praktiken, die auf menschlicher Koordination, Vertrauensaufbau oder Validierung der Korrektheit beruhen, unverändert bleiben. Mechanische Prüfungen in der Korrektheitsvalidierung (Typen, Tests, Verträge) werden durch KI beschleunigt, während die semantische Validierung (Geschäftsanforderungen, regulatorische Risiken) weiterhin auf menschlichem Urteil beruht; KI-interne Prüfungen können geteilte Blindpunkte nicht erkennen.","category":"技巧观点","source":"Hacker News 热门（buzzing.cc 中文翻译）","aggregationSource":"Hacker News 热门（buzzing.cc 中文翻译）","pageTitle":"Projektmanagement nach dem Zusammenbruch der Codekosten: Reflexionen eines technischen Leiters - Aioga KI-News","description":"Ein Ingenieurdirektor wies basierend auf den Notizen des vergangenen Jahres darauf hin, dass die Produktionskosten für Code zusammengebrochen sind und nicht wieder steigen werden,...","url":"https://www.aioga.com/de/news/cms0yvk8o0042ro956e389rlb/","contentTranslated":true,"sourceHash":"1140c9917d8e84a2","translatedAt":"2026-07-26T11:44:52.402Z"},"pt-BR":{"title":"Gestão de engenharia após o colapso dos custos de codificação: Reflexões de um diretor de engenharia","summary":"Um diretor de engenharia, com base nas anotações do ano passado, apontou que o custo de produção de código entrou em colapso e não vai se recuperar, mas ainda não há consenso sobre se as ferramentas de IA realmente aumentaram significativamente a velocidade da equipe de engenharia. As práticas de gestão devem ser avaliadas com base na validade de suas suposições subjacentes: as abordagens que dependem do custo de escrita de código precisam ser reavaliadas, enquanto as que dependem da coordenação humana, construção de confiança ou verificação de corretude permanecem inalteradas. A verificação de corretude mecânica (tipos, testes, contratos) está sendo acelerada pela IA, mas a verificação semântica (requisitos de negócios, riscos regulatórios) ainda depende do julgamento humano, e a autoverificação da IA não consegue identificar pontos cegos compartilhados.","category":"技巧观点","source":"Hacker News 热门（buzzing.cc 中文翻译）","aggregationSource":"Hacker News 热门（buzzing.cc 中文翻译）","pageTitle":"Gestão de engenharia após o colapso dos custos de codificação: Reflexões de um diretor de engenharia - Aioga Notícias de IA","description":"Um diretor de engenharia, com base nas anotações do ano passado, apontou que o custo de produção de código entrou em colapso e não vai se recuperar, mas ainda não há consenso sobre...","url":"https://www.aioga.com/pt-BR/news/cms0yvk8o0042ro956e389rlb/","contentTranslated":true,"sourceHash":"1140c9917d8e84a2","translatedAt":"2026-07-26T11:45:31.772Z"},"ru":{"title":"Управление проектами после обрушения стоимости кода: размышления одного технического директора","summary":"Один технический директор на основе заметок за прошлый год отметил, что стоимость производства кода рухнула и не восстановится, но пока нет заключения, ускоряют ли инструменты ИИ работу инженерной команды значительно. Практики управления следует оценивать исходя из того, верны ли их базовые предположения: подходы, зависящие от стоимости написания кода, требуют пересмотра, тогда как подходы, зависящие от координации людей, построения доверия или проверки правильности, не изменились. Механические проверки в проверке правильности (типы, тесты, контракты) ускоряются благодаря ИИ, но семантическая проверка (требования к бизнесу, регуляторные риски) всё ещё зависит от человеческого суждения, а самопроверка ИИ не выявляет общие слепые пятна.","category":"技巧观点","source":"Hacker News 热门（buzzing.cc 中文翻译）","aggregationSource":"Hacker News 热门（buzzing.cc 中文翻译）","pageTitle":"Управление проектами после обрушения стоимости кода: размышления одного технического директора - Aioga Новости ИИ","description":"Один технический директор на основе заметок за прошлый год отметил, что стоимость производства кода рухнула и не восстановится, но пока нет заключения, ускоряют ли инструменты ИИ р...","url":"https://www.aioga.com/ru/news/cms0yvk8o0042ro956e389rlb/","contentTranslated":true,"sourceHash":"1140c9917d8e84a2","translatedAt":"2026-07-26T11:45:40.530Z"},"ar":{"title":"إدارة المشاريع بعد انهيار تكلفة الكود: تأملات مدير هندسي","summary":"أشار مدير هندسي بناءً على ملاحظات العام الماضي إلى أن تكلفة إنتاج الشيفرة انهارت ولن تعود للصعود، لكن ما إذا كانت أدوات الذكاء الاصطناعي تجعل فرق الهندسة أسرع بشكل كبير لا يزال غير مؤكد. يجب أن تستند الممارسات الإدارية إلى تقييم ما إذا كانت الافتراضات الأساسية صحيحة: فالممارسات التي تعتمد على تكلفة كتابة الشيفرة تحتاج إلى إعادة نظر، بينما الممارسات التي تعتمد على تنسيق البشر وبناء الثقة أو التحقق من الصحة لم تتغير. الفحوصات الميكانيكية في التحقق من الصحة (الأنواع، الاختبارات، العقود) تتسارع بسبب الذكاء الاصطناعي، لكن التحقق الدلالي (متطلبات الأعمال، المخاطر التنظيمية) لا يزال يعتمد على حكم البشر، وفحص الذكاء الاصطناعي الذاتي لا يمكنه اكتشاف النقاط العمياء المشتركة.","category":"技巧观点","source":"Hacker News 热门（buzzing.cc 中文翻译）","aggregationSource":"Hacker News 热门（buzzing.cc 中文翻译）","pageTitle":"إدارة المشاريع بعد انهيار تكلفة الكود: تأملات مدير هندسي - Aioga أخبار الذكاء الاصطناعي","description":"أشار مدير هندسي بناءً على ملاحظات العام الماضي إلى أن تكلفة إنتاج الشيفرة انهارت ولن تعود للصعود، لكن ما إذا كانت أدوات الذكاء الاصطناعي تجعل فرق الهندسة أسرع بشكل كبير لا يزال غير...","url":"https://www.aioga.com/ar/news/cms0yvk8o0042ro956e389rlb/","contentTranslated":true,"sourceHash":"1140c9917d8e84a2","translatedAt":"2026-07-26T11:46:24.825Z"},"hi":{"title":"कोड लागत पतन के बाद का इंजीनियरिंग प्रबंधन: एक इंजीनियरिंग निदेशक का चिंतन","summary":"एक इंजीनियरिंग निदेशक ने पिछले वर्ष के नोट्स के आधार पर बताया कि कोड उत्पादन लागत गिर गई है और फिर से नहीं बढ़ेगी, लेकिन यह तय नहीं है कि एआई उपकरण इंजीनियरिंग टीम की गति को महत्वपूर्ण रूप से तेज करते हैं या नहीं। प्रबंधन प्रथाओं का मूल्यांकन उनके मौलिक अनुमान के आधार पर किया जाना चाहिए: कोड लेखन लागत पर निर्भर प्रथाओं पर पुनर्विचार करना आवश्यक है, जबकि मानव समन्वय, विश्वास निर्माण या सत्यापन की प्रथाएं नहीं बदली हैं। सत्यापन में यांत्रिक जांच (प्रकार, परीक्षण, अनुबंध) एआई की मदद से तेज हो रही हैं, लेकिन अर्थपूर्ण सत्यापन (व्यावसायिक आवश्यकताएं, नियामक जोखिम) अभी भी मानव निर्णय पर निर्भर है, और एआई स्व-जांच साझा हुए अंधे धब्बों को नहीं ढूँढ सकती।","category":"技巧观点","source":"Hacker News 热门（buzzing.cc 中文翻译）","aggregationSource":"Hacker News 热门（buzzing.cc 中文翻译）","pageTitle":"कोड लागत पतन के बाद का इंजीनियरिंग प्रबंधन: एक इंजीनियरिंग निदेशक का चिंतन - Aioga AI समाचार","description":"एक इंजीनियरिंग निदेशक ने पिछले वर्ष के नोट्स के आधार पर बताया कि कोड उत्पादन लागत गिर गई है और फिर से नहीं बढ़ेगी, लेकिन यह तय नहीं है कि एआई उपकरण इंजीनियरिंग टीम की गति को महत्वप...","url":"https://www.aioga.com/hi/news/cms0yvk8o0042ro956e389rlb/","contentTranslated":true,"sourceHash":"1140c9917d8e84a2","translatedAt":"2026-07-26T11:46:27.616Z"},"it":{"title":"Gestione dei progetti dopo il crollo dei costi del codice: riflessioni di un direttore tecnico","summary":"Un direttore dell'ingegneria ha osservato, basandosi sulle note dell'ultimo anno, che il costo di produzione del codice è crollato e non tornerà, ma non è ancora chiaro se gli strumenti AI rendano significativamente più veloce il team di ingegneri. Le pratiche di gestione dovrebbero essere valutate in base alla validità delle loro ipotesi di fondo: le pratiche che dipendono dal costo di scrittura del codice devono essere riesaminate, mentre quelle che dipendono dal coordinamento umano, dalla costruzione della fiducia o dalla verifica della correttezza non cambiano. Nei controlli di correttezza, i controlli meccanici (tipi, test, contratti) si stanno accelerando grazie all'AI, ma la verifica semantica (requisiti aziendali, rischi normativi) dipende ancora dal giudizio umano, poiché l'auto-verifica dell'AI non può rilevare punti ciechi condivisi.","category":"技巧观点","source":"Hacker News 热门（buzzing.cc 中文翻译）","aggregationSource":"Hacker News 热门（buzzing.cc 中文翻译）","pageTitle":"Gestione dei progetti dopo il crollo dei costi del codice: riflessioni di un direttore tecnico - Aioga Notizie IA","description":"Un direttore dell'ingegneria ha osservato, basandosi sulle note dell'ultimo anno, che il costo di produzione del codice è crollato e non tornerà, ma non è ancora chiaro se gli stru...","url":"https://www.aioga.com/it/news/cms0yvk8o0042ro956e389rlb/","contentTranslated":true,"sourceHash":"1140c9917d8e84a2","translatedAt":"2026-07-26T11:47:11.564Z"},"nl":{"title":"Projectbeheer na de ineenstorting van de codekosten: reflecties van een technisch directeur","summary":"Een engineeringdirecteur merkte op basis van notities van het afgelopen jaar dat de productiekosten van code zijn ingestort en niet zullen herstellen, maar het is nog onduidelijk of AI-tools het engineeringteam significant versnellen. Managementpraktijken moeten worden geëvalueerd op basis van de vraag of de onderliggende aannames geldig zijn: praktijken die afhankelijk zijn van de kosten van het schrijven van code moeten worden herzien, terwijl praktijken die afhankelijk zijn van menselijke coördinatie, vertrouwensopbouw of verificatie van juistheid niet zijn veranderd. Mechanische controles in de verificatie van juistheid (typen, testen, contracten) worden versneld door AI, maar semantische verificatie (zakelijke vereisten, regelgevingsrisico's) is nog steeds afhankelijk van menselijke beoordeling, en AI-selfchecks kunnen gedeelde blinde vlekken niet detecteren.","category":"技巧观点","source":"Hacker News 热门（buzzing.cc 中文翻译）","aggregationSource":"Hacker News 热门（buzzing.cc 中文翻译）","pageTitle":"Projectbeheer na de ineenstorting van de codekosten: reflecties van een technisch directeur - Aioga AI-nieuws","description":"Een engineeringdirecteur merkte op basis van notities van het afgelopen jaar dat de productiekosten van code zijn ingestort en niet zullen herstellen, maar het is nog onduidelijk o...","url":"https://www.aioga.com/nl/news/cms0yvk8o0042ro956e389rlb/","contentTranslated":true,"sourceHash":"1140c9917d8e84a2","translatedAt":"2026-07-26T11:47:07.424Z"},"tr":{"title":"Kod maliyeti çöküşünden sonra proje yönetimi: Bir mühendislik direktörünün düşünceleri","summary":"Bir mühendislik direktörü, geçtiğimiz yılın notlarına dayanarak, kod üretim maliyetinin çöktüğünü ve geri dönmeyeceğini belirtti, ancak yapay zeka araçlarının mühendislik ekibini önemli ölçüde hızlandırıp hızlandırmadığı henüz kesin değil. Yönetim uygulamaları, altta yatan varsayımların geçerliliğine dayalı olarak değerlendirilmelidir: Kod yazım maliyetine dayanan uygulamalar yeniden gözden geçirilmelidir, oysa insan koordinasyonu, güven inşası veya doğruluk doğrulamasına dayanan uygulamalarda bir değişiklik yoktur. Doğruluk doğrulamasındaki mekanik kontroller (tipler, testler, sözleşmeler) yapay zekâ sayesinde hızlanmakta, ancak anlamsal doğrulama (iş gereksinimleri, düzenleyici riskler) hâlâ insan yargısına bağlıdır ve yapay zekâ kendi kendini kontrol ederek paylaşılan kör noktaları keşfedemez.","category":"技巧观点","source":"Hacker News 热门（buzzing.cc 中文翻译）","aggregationSource":"Hacker News 热门（buzzing.cc 中文翻译）","pageTitle":"Kod maliyeti çöküşünden sonra proje yönetimi: Bir mühendislik direktörünün düşünceleri - Aioga AI Haberleri","description":"Bir mühendislik direktörü, geçtiğimiz yılın notlarına dayanarak, kod üretim maliyetinin çöktüğünü ve geri dönmeyeceğini belirtti, ancak yapay zeka araçlarının mühendislik ekibini ö...","url":"https://www.aioga.com/tr/news/cms0yvk8o0042ro956e389rlb/","contentTranslated":true,"sourceHash":"1140c9917d8e84a2","translatedAt":"2026-07-26T11:47:58.276Z"},"vi":{"title":"Quản lý dự án sau sự sụp đổ chi phí mã: Suy ngẫm của một giám đốc kỹ thuật","summary":"Một giám đốc kỹ thuật dựa trên ghi chép của năm vừa qua chỉ ra rằng chi phí sản xuất mã đã sụp đổ và sẽ không phục hồi, nhưng việc công cụ AI có giúp đội ngũ kỹ sư tăng tốc đáng kể hay không vẫn chưa có kết luận. Thực tiễn quản lý nên được đánh giá dựa trên việc các giả định cơ bản của nó có đúng hay không: các phương pháp dựa vào chi phí viết mã cần được xem xét lại, trong khi các phương pháp dựa vào phối hợp con người, xây dựng lòng tin hoặc xác minh đúng đắn không thay đổi. Các kiểm tra cơ học trong xác minh đúng đắn (loại, kiểm thử, hợp đồng) đang được tăng tốc nhờ AI, nhưng kiểm tra ngữ nghĩa (yêu cầu kinh doanh, rủi ro quy định) vẫn phụ thuộc vào đánh giá của con người, tự kiểm tra bằng AI không phát hiện ra các điểm mù chung.","category":"技巧观点","source":"Hacker News 热门（buzzing.cc 中文翻译）","aggregationSource":"Hacker News 热门（buzzing.cc 中文翻译）","pageTitle":"Quản lý dự án sau sự sụp đổ chi phí mã: Suy ngẫm của một giám đốc kỹ thuật - Tin tức AI Aioga","description":"Một giám đốc kỹ thuật dựa trên ghi chép của năm vừa qua chỉ ra rằng chi phí sản xuất mã đã sụp đổ và sẽ không phục hồi, nhưng việc công cụ AI có giúp đội ngũ kỹ sư tăng tốc đáng kể...","url":"https://www.aioga.com/vi/news/cms0yvk8o0042ro956e389rlb/","contentTranslated":true,"sourceHash":"1140c9917d8e84a2","translatedAt":"2026-07-26T11:47:48.487Z"},"id":{"title":"Manajemen Proyek Setelah Keruntuhan Biaya Kode: Refleksi Seorang Direktur Teknik","summary":"Seorang direktur teknik mencatat berdasarkan catatan setahun terakhir bahwa biaya produksi kode telah runtuh dan tidak akan kembali, namun apakah alat AI secara signifikan mempercepat tim teknik masih belum ada kesimpulan. Praktik manajemen harus dievaluasi berdasarkan apakah asumsi dasarnya berlaku: pendekatan yang bergantung pada biaya penulisan kode perlu ditinjau ulang, sedangkan pendekatan yang bergantung pada koordinasi manusia, pembangunan kepercayaan, atau verifikasi kebenaran tidak berubah. Pemeriksaan mekanis dalam verifikasi kebenaran (tipe, pengujian, kontrak) dipercepat oleh AI, tetapi verifikasi semantik (kebutuhan bisnis, risiko regulasi) masih bergantung pada penilaian manusia, dan pemeriksaan diri AI tidak dapat menemukan titik buta yang sama.","category":"技巧观点","source":"Hacker News 热门（buzzing.cc 中文翻译）","aggregationSource":"Hacker News 热门（buzzing.cc 中文翻译）","pageTitle":"Manajemen Proyek Setelah Keruntuhan Biaya Kode: Refleksi Seorang Direktur Teknik - Berita AI Aioga","description":"Seorang direktur teknik mencatat berdasarkan catatan setahun terakhir bahwa biaya produksi kode telah runtuh dan tidak akan kembali, namun apakah alat AI secara signifikan memperce...","url":"https://www.aioga.com/id/news/cms0yvk8o0042ro956e389rlb/","contentTranslated":true,"sourceHash":"1140c9917d8e84a2","translatedAt":"2026-07-26T11:48:35.267Z"},"th":{"title":"การจัดการโครงการหลังต้นทุนโค้ดล่ม: การสะท้อนคิดของผู้อำนวยการวิศวกรรม","summary":"ผู้กำกับการวิศวกรรมคนหนึ่งชี้ให้เห็นจากบันทึกในปีที่ผ่านมา ว่าต้นทุนการผลิตโค้ดได้พังทลายและไม่ฟื้นตัว แต่ยังไม่มีข้อสรุปว่าเครื่องมือ AI ทำให้ทีมวิศวกรรมเร็วขึ้นอย่างมีนัยสำคัญหรือไม่ การปฏิบัติด้านการจัดการควรประเมินจากสมมติฐานพื้นฐานว่าเป็นจริงหรือไม่: วิธีการที่พึ่งพาต้นทุนการเขียนโค้ดจำเป็นต้องทบทวนอีกครั้ง ในขณะที่วิธีการที่พึ่งพาการประสานงานของมนุษย์ การสร้างความเชื่อใจ หรือการตรวจสอบความถูกต้องยังไม่เปลี่ยนแปลง การตรวจสอบความถูกต้องแบบกลไก (ประเภท การทดสอบ สัญญา) กำลังเร็วขึ้นเพราะ AI แต่การตรวจสอบด้านความหมาย (ความต้องการทางธุรกิจ ความเสี่ยงด้านกฎระเบียบ) ยังคงพึ่งพาการตัดสินใจของมนุษย์ การตรวจสอบตนเองของ AI ไม่สามารถพบจุดบอดร่วมกันได้","category":"技巧观点","source":"Hacker News 热门（buzzing.cc 中文翻译）","aggregationSource":"Hacker News 热门（buzzing.cc 中文翻译）","pageTitle":"การจัดการโครงการหลังต้นทุนโค้ดล่ม: การสะท้อนคิดของผู้อำนวยการวิศวกรรม - ข่าว AI Aioga","description":"ผู้กำกับการวิศวกรรมคนหนึ่งชี้ให้เห็นจากบันทึกในปีที่ผ่านมา ว่าต้นทุนการผลิตโค้ดได้พังทลายและไม่ฟื้นตัว แต่ยังไม่มีข้อสรุปว่าเครื่องมือ AI ทำให้ทีมวิศวกรรมเร็วขึ้นอย่างมีนัยสำคัญหรื...","url":"https://www.aioga.com/th/news/cms0yvk8o0042ro956e389rlb/","contentTranslated":true,"sourceHash":"1140c9917d8e84a2","translatedAt":"2026-07-26T11:48:45.881Z"},"pl":{"title":"Zarządzanie projektami po załamaniu kosztów kodu: refleksje dyrektora inżynierii","summary":"Dyrektor inżynieryjny na podstawie notatek z ostatniego roku zauważył, że koszty wytwarzania kodu załamały się i nie wzrosną, ale to, czy narzędzia AI znacząco przyspieszają pracę zespołów inżynieryjnych, pozostaje niepewne. Praktyki zarządzania powinny być oceniane w oparciu o to, czy ich podstawowe założenia są prawdziwe: podejścia oparte na kosztach pisania kodu wymagają ponownej oceny, podczas gdy podejścia zależne od koordynacji ludzi, budowania zaufania lub weryfikacji poprawności pozostają niezmienione. Mechaniczne sprawdzanie weryfikacji poprawności (typy, testy, kontrakty) przyspiesza dzięki AI, ale weryfikacja semantyczna (wymagania biznesowe, ryzyko regulacyjne) nadal zależy od ludzkiego osądu, a samodzielne sprawdzanie AI nie może wykryć wspólnych punktów ślepych.","category":"技巧观点","source":"Hacker News 热门（buzzing.cc 中文翻译）","aggregationSource":"Hacker News 热门（buzzing.cc 中文翻译）","pageTitle":"Zarządzanie projektami po załamaniu kosztów kodu: refleksje dyrektora inżynierii - Aioga Wiadomości AI","description":"Dyrektor inżynieryjny na podstawie notatek z ostatniego roku zauważył, że koszty wytwarzania kodu załamały się i nie wzrosną, ale to, czy narzędzia AI znacząco przyspieszają pracę...","url":"https://www.aioga.com/pl/news/cms0yvk8o0042ro956e389rlb/","contentTranslated":true,"sourceHash":"1140c9917d8e84a2","translatedAt":"2026-07-26T11:49:31.320Z"}}}}