Mitchell Hashimoto 分享 Superlogical 的 Agent 时代团队开发方式

发布流程完全自动化，任何成员都能触发 release，Slack 会发出通知并启动 15 分钟倒计时，期间任何人可以暂停发布，倒计时不可被覆盖。各平台功能不靠会议对齐，而是先各自上线，再用人工加 AI 辅助事后审查识别 Windows 与 Mac 等平台之间的功能差异，实践中 24 到 48 小时内即可达成功能对齐。

Hashimoto 强调这套流程建立在互信基础上：push main 意味着你要收拾自己的问题，随意发布则要求每个人尊重 15 分钟的最终审查窗口。这套做法把传统 PR 流程和同步会议替换为机器审查与事后修复，是小型团队结合 Agent 工具后工作方式转变的一个具体样本。

这就是大神在 Superlogical 的开发方式，团队不大，但是非常符合现代 Agent 的开发方式： 1 直接 push main，采用 agent pre-push review + 人工 + agent post-push 审查的方式，几乎不开 PR 2 谁都可以发新的 release，启动发布 release 会触发 Slack 通知并开始 15 分钟倒计时，任何人都可以在这 15 分钟内暂停。（让大家都有机会去最后 review 一次这个版本的修改，主动权交给所有人） 3 服务器和各平台做到快速上线，事后用人工加假期 review的方式来识别不同平台的差异度，并且做到快速补齐，不通过浪费时间的会议来完成功能对齐。（应该说的就是说各干各的，完成就上线，别的平台来对齐最新的功能就好） Mitchell Hashimoto @mitchellh We're still so small but I'm loving the team we've got at Superlogical. They're so talented and kind and love their craft. It's a different era of software development and our expectations and practices reflect that. I want to share a bit about how we work. First, everyone is trusted to push to main. We do machine-aided code review pre-push and human plus more machine-aided code review post-push. Limited to no PRs. Culturally, we've all agreed that if we ever hire someone who we DON'T trust to push directly to main, then they probably aren't the right fit for the team (so far, not an issue). Some common sense here: if someone is stepping outside their lane or comfort zone, we'll open PRs. For example, I'm pretty trash at macOS/iOS UI, so I'll open PRs for UI-affecting functionality and ask for eyeballs/help. But for business logic and internals, I push to main. Second, everyone can cut a release. Our release process is fully automated and when you start a release (for any platform) it triggers a Slack notification and a 15 minute countdown. The 15 minute warning is a final gate that allows people to review plus collaborate on a changelog. During that 15 minutes, anyone in the company can pause the release rollout. After 15 minutes, the train leaves the station. You can't override the 15 minutes (except to pause). It gives everyone a chance to step in. Third, we avoid synchronization through fast remediation rather than through planning. The server and clients on various platforms ship features as fast as they can. We use post-hoc human review and AI-assistance to identify feature mismatches across products ("Windows has support for X and Mac doesn't." or "Mac and Windows differ in their behaviors for Y in this way."). This avoids expensive "sync" meetings and coordination. We trust that producers of features are mindful of what they're producing and we trust that adjacent product lines will self-synchronize quickly. In practice, we see feature parity across platforms within 24 to 48 hours. All of this works on mutual trust. It ONLY works with mutual trust. Everyone at all times has to trust that they've got each others back: 1. Push to main only works if you fix your mess, or if you don't, that someone else will quickly but that you'd do the same (and generally in equal amounts). 2. Anyone can deploy only works if you trust everyone to cut at the right time, with the right changelog, and that people will respect the 15 minute timer. 3. Sync through fast remediation only works if you trust other teams will pick up and integrate your work quickly, which only works if you would too. It also only works if you are fairly producing mismatches (e.g. not constantly). We've got a great team. I know we're still small and that these practices will change in many ways as we scale. But this is already a markedly different practice than what I would've done 15 years ago. In general, we are building from day 1 on a foundation of mutual respect, excellence, and trust. And it's been awesome. 🔗 View Quoted Tweet📊 5 ⚡

This report is categorized under AITOP's "How-to" desk, focusing on US frontier AI labs and Silicon Valley technology leaders. Within our cross-regional analytical framework, it directly maps to AI developer toolchains, coding agents, and engineering workflows. Key entities and technical topics under continuous tracking include Mitchell Hashimoto, Superlogical, Agent, 代码审查.

Source attribution: curated from Viking (@vikingmute). Cross-source corroboration: 3 independent sources have covered this development (including shao__meng, TestingCatalog), confirming industry-wide signal strength.