与「principles」相关的搜索结果

开发系统最极致高效的Agents.md，没有之一： # AGENTS.md ## Core Principles - Choose the simplest implementation that fully satisfies the current requirements. Avoid unnecessary abstraction, configuration, indirection, or speculative extensibility. - Make the smallest necessary change that fixes the root cause. Do not refactor unrelated modules or change strategy semantics unless explicitly requested. - Grow the system in layers. Start from the smallest working end-to-end version and add new capabilities incrementally. Never replace a working system with unfinished complexity. - Reuse existing project components before creating new ones. Prefer extending proven modules over introducing parallel implementations. - Prefer well-maintained libraries when they reduce overall complexity or improve reliability. Do not reimplement common functionality without a clear benefit. - Keep components modular with clearly defined responsibilities. Avoid unnecessary coupling between strategy logic, execution, accounting, replay, and infrastructure. - Design for long-term maintainability once a feature or strategy has been validated. Do not over-engineer speculative ideas before evidence exists. --- ## Strategy Development - Validate hypotheses with historical replay before introducing forward-only logic whenever historical validation is possible. - Every trading strategy must progress through Replay → Shadow → Canary → Live. Do not skip validation stages. - Base design decisions on measurable evidence rather than intuition. Optimize only after demonstrating that an edge exists. - Treat every strategy as an independent contract. Do not silently alter frozen behavior without explicit authorization. --- ## Existing Systems - Do not break running Shadow or Live systems for unrelated work. - Preserve compatibility only when required by active production or validation workflows. Otherwise, remove obsolete code instead of accumulating compatibility layers. - Reuse existing infrastructure whenever possible, including replay engines, accounting, execution, wallet management, order book handling, logging, monitoring, and daemon frameworks. --- ## Engineering Standards - Prefer deterministic behavior over hidden automation. - Fail loudly when assumptions are violated. Do not silently ignore errors or fall back to unexpected behavior. - Keep configuration minimal. Introduce new configuration only when behavior genuinely needs to vary. - Remove dead code instead of leaving unused paths behind. - Write code that is easy to inspect, replay, test, and reason about. - Keep implementation consistent with existing project architecture unless an architectural change is explicitly requested. --- ## Scope Discipline - Implement only the requested scope. - Do not introduce unrelated optimizations, redesigns, migrations, or feature expansions. - Non-blocking findings outside the requested scope may be noted separately but must not be merged into the current task. - Consider a task complete once its agreed acceptance criteria are satisfied. Treat subsequent improvements as separate work items.

Legacy media has falsely tried to label normal people as “far right” Which of these things are bad? -Secure Borders -Safe Cities -Sensible Spending -Fair Justice System -Free Speech -Self-Protection These are common sense principles. The media is lying to you.

First Principles Ep. 6 with Ron Rivest Long before the internet became a place to bank, transact, or build blockchains, Turing Award winner Ron Rivest helped solve a foundational problem: how can strangers communicate securely without first meeting to exchange a secret? Rivest tells the story of inventing RSA with Adi Shamir and Leonard Adleman, why digital signatures fascinated him even more than encryption, and how cryptographic hashes, government pressure, patents, and standards shaped the security infrastructure we rely on today. Rivest shares his unusually candid views on quantum computing, post-quantum security, and more. Hosted by @Tim_Roughgarden with @danboneh. 00:00 Intro: the two problems that could break modern cryptography 01:10 Why Ron Rivest’s work underpins the internet and blockchains 08:10 Before public-key cryptography, there was no theory of security 11:05 The open problem that led to RSA 13:55 The night Ron Rivest discovered the core idea behind RSA 17:55 Why digital signatures were the real breakthrough 19:14 The RSA challenge — and a prediction that was off by quadrillions of years 28:33 How government pressure shaped cryptographic standards 30:36 Designing the hash functions that made digital signatures practical 33:26 The Fiat–Shamir transformation, explained 38:04 Building a cryptography company before the web existed 42:31 Will quantum computers ever become powerful enough to break RSA? 48:02 The cryptography securing the internet, elections, and everyday life 50:11 What surprised Dan: Quantum giveth and quantum taketh away

NEWS: Elon Musk rejects the far right label in an exchange with The Economist "I support the normal people. What you call the far right, falsely." He challenged the interviewer to say what is extreme about 3 positions. "Here are the principles and tell me which of these sound terrible. That we should have secure borders, that we should have safe cities, that we should have sensible spending. Which of those three are far right fringe?" Elon then turned on the framing itself. "I would like to just admonish you and the media for the absurd characterization of the far right. It is false and misleading and nonsense." He asked that the exchange survive the edit. "Please keep this part in." Elon said the same speeches get judged by who delivered them, describing a habit of reading Obama and Clinton speeches to people and telling them Trump said it. He named Rupert Lowe as an example of who he means by normal people. (Source: The Economist, July 2026)

Dr. Stephanie Haridopolos, Director of National Communications for the Office of the Surgeon General, examines the historical events and ethical failures that led to the creation of the Belmont Report. Built on the principles of respect for persons, beneficence, and justice, the Belmont Report established the ethical framework that continues to guide research involving human participants. Nearly 50 years after its publication, this landmark document remains a cornerstone of bioethics and an enduring guide for the human research protections community.

Kimi K3 massively beats NVIDIA’s Nemotron 3 Ultra model. If America wants to lead in open-source AI, Jensen should recognize that progress comes from independent labs competing against each other based on the free-market principles of testing different ideas, architectures, and approaches, just like China’s AI labs are shipping and iterating. 1/5🧵

For Marcus, mentorship has shaped every step of his career. From his early days as a financial analyst on the plant floor to today, the lessons he learned from his mentor still hang on his wall - principles like servant leadership and leading with trust. #FromOurCampus#

Japanese local assemblies strongly call for upholding the three non-nuclear principles — a clear sign that the people want peace, not remilitarization. Tokyo’s rush to abandon the pacifist Constitution is out of step with the public. Japan is an #NPT# non-nuclear-weapon state. That means: no receiving, no manufacturing, no acquiring, no transferring of nuclear weapons are Japan’s non-negotiable obligations. The world expects full compliance from Japan. Tokyo needs to hear this loud and clear: 🔷 Honor its NPT obligations 🔷 Abandon remilitarization & nuclear ambitions 🔷 Stop undermining the three non-nuclear principles 🔷 Quit “extended deterrence” cooperation 🔷 No allies’ nukes in Japan 🔷 Fix oversupply of sensitive nuclear materials ASAP

First Principles Ep. 5 with Paul Milgrom One of the most important auction designs in modern history was sold to the FCC on a 3.5-inch disk. Nobel Prize winner Paul Milgrom on auctions, price discovery, and how mechanism design became real-world infrastructure — from spectrum auctions to DeFi. Hosted by @Tim_Roughgarden with @skominers. 00:00 Intro: economics assumptions that are “just wrong” 02:19 Scott Kominers and Tim Roughgarden on the genius of Paul Milgrom 05:35 An intro to the  Glosten-Milgrom model: The paper that created entire fields of economics 07:48 The auction theory breakthroughs of the 1980s 17:15 Why market microstructure matters for DeFi 24:17 When math teaches economics something new 32:38 How theory became spectrum auction design 36:22 The floppy disk that helped convince the FCC 41:05 What changed when auctions moved online 45:28 The auction that reorganized television 1:07:30 What economics and computer science can learn from each other 1:13:22 Futures markets for compute 1:15:12 Paul Milgrom’s advice for builders

FULL INTERVIEW: Former SpaceX CIO Ken Venner on Scaling Broadcom & SpaceX "@elonmusk was really good about keeping the mission as a forefront focus for what we were doing, & just energized everyone to get it done." Now Chief Tech & Product Officer, @Senra_Systems Ken Venner spent 11 years at Broadcom, joining at 1,000 people and $400 million in revenue and leaving at 10,000 employees and $8.6 billion, across 52 acquisitions. Then he became CIO of SpaceX, where Elon hired him to build the digital nervous system for a 21st century rocket company. The result was Warp Drive, the custom operating system that helped scale SpaceX from about 1 booster a year and 1,000 employees to 40 boosters and 9,000 employees. He recently joined Senra Systems as Chief Technology and Product Officer, this is a sit-down on how he scales companies.. wish we had more time. "Scaling up & scaling out are my core skills." We cover the Broadcom years & why process kills growth if you add it too early, the tour of the Hawthorne factory that got him to leave, working for Elon & @Gwynne_Shotwell, why he spent two years thinking Warp Drive was a terrible idea.. & what changed in year three. Ken also breaks down Elon's playbook: first principles thinking, "remove before automate," and the responsible engineer model where one person owns a part from requirements through post-flight with no handoffs. Plus: why he had 175 engineers building core platforms at SpaceX and only needs 6 at Senra, the law of threes for scaling factories, why he still works after one of the largest wealth creation events ever, and his winery in Sonoma. 𝐓𝐈𝐌𝐄𝐒𝐓𝐀𝐌𝐏𝐒 00:00 Meet Ken Venner 00:17 Why Join Senra 01:26 Scaling Playbook 02:08 Broadcom Growth Lessons 03:48 Broadcom Jump to SpaceX 05:16 Building SpaceX Systems 06:39 Elon Leadership Principles 07:43 Gwynne & SpaceX Culture 09:39 Why Keep Working? 11:14 Law of Threes - Scaling 11:56 AI & Automation Changing the Game 13:35 Senra Name Story 14:07 Winery Side Project (Auteur Wines - Healdsburg, CA) 14:55 Next 12 Months Outlook