与「Victorious」相关的搜索结果

FM Wang Yi: Taiwan has been an integral part of China since ancient times. It never was, is not, and never will be a country. Its return to China is a victorious outcome of the Chinese People’s War of Resistance Against Japanese Aggression and the Second World War. Its status has been definitively fixed by a series of international legal instruments, including the Cairo Declaration, the Potsdam Proclamation, Japan’s Instrument of Surrender, and Resolution 2758 of the U.N. General Assembly. Any attempt to create “two Chinas” or “one China, one Taiwan” is doomed to fail. Resolving the Taiwan question and realizing the complete reunification of our motherland is a historic process that cannot be stopped. Those who support it are on the right side of history; those who defy it shall perish.

During the virtual meeting with Russian President Putin, President Xi noted that as responsible major countries and permanent members of the U.N. Security Council, China and Russia are duty-bound to pool global efforts to firmly uphold fairness and justice, firmly defend the victorious outcomes of WWII, firmly safeguard the U.N.-centered international system and the basic norms of international law, and jointly maintain global strategic stability.

A few random notes from claude coding quite a bit last few weeks. Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent. IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits. Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased. Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion. Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage. Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building. Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it. Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements. Questions. A few of the questions on my mind: - What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*. - Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro). - What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music? - How much of society is bottlenecked by digital knowledge work? TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.

President Xi Jinping met with Serbian President Aleksandar Vučić in Beijing. In the Asian and European theaters of WWII, China and Serbia each made immense sacrifices and made major contributions to the defeat of fascism. In a world fraught with changes and turbulence, it is even more imperative for China and Serbia to uphold a correct historical perspective on WWII and safeguard the victorious outcome of the anti-fascist war. Sustained effort should be made to enhance multilateral cooperation, always stand on the right side of history, resolutely safeguard national rights and interests as well as international fairness and justice, and firmly uphold the purposes and principles of the United Nations Charter.

记录：特朗普今日关于美伊战争的讲话主要内容总结（基于多家媒体报道和讲话要点)。 战争接近完成：特朗普宣称美国的核心战略目标“即将完成”（nearing completion），包括阻止伊朗拥有核武器、摧毁其核设施、导弹能力以及削弱恐怖主义支持网络。他表示过去一个多月（约四周）美军取得“迅捷、决定性、压倒性胜利”（swift, decisive, overwhelming victories），伊朗海军已被“彻底消灭”，空军“成为废墟”，大部分领导层“已死或失去控制”，指挥系统被严重破坏。 时间表：未来2至3周内将继续对伊朗进行“极其猛烈的打击”（hit them extremely hard / very hard），之后美国将“很快撤出”主要军事行动，完成所有目标“非常短时间”（very shortly）。不需要正式和平协议，只要伊朗无法制造核武器即可。 强硬威胁：如果霍尔木兹海峡（Strait of Hormuz）不重新开放，美国将继续行动，直至把伊朗“炸回石器时代”（bring them back to the Stone Ages where they belong）。他强调美国不对海峡关闭负责，依赖该海峡运输石油的国家应自行承担后果，通航问题会“自然解决”。 停火与谈判：特朗普提到伊朗“新政权”的总统（据称比前任更理性）已请求停火或 ceasefire，美国正在与“似乎在管理伊朗的人”进行“富有成效的对话”（productive talks）。但停火前提是海峡完全开放，否则继续打击。他同时表示谈判在进行中。 其他表态： 为能源（石油）价格短期上涨辩护，称这是暂时现象，美国很快会恢复稳定。 重申战争目的是纠正过去几十年政策失败，批评前任政府对伊朗的软弱。 强调美军表现“前所未有”（never been anything like it），并暗示北约支持不足，可能重新评估关系。 整体语气乐观且强硬，多次使用“我来了，我看见，我征服了”（I came, I saw, I conquered）类似风格，宣称“我们赢了”。