用 DeepSeek V4.1 Flash 写代码、Opus 5.5 做审查的 5 条实践
作者总结：用 DeepSeek 实现、Opus 5.5 审 diff；跑 Chief→Builder→Reviewer 循环；实现用 high 而非 max 推理；任务切小给准文件；6 小时移植 2 个游戏约花 €3。
5 hacks i’ve found for getting more out of DeepSeek V4.1-Flash-1017: 1. use DeepSeek for implementation, Opus 5.5 for review. i’d rather spend the expensive tokens checking the final diff than writing every line. 2. run a Chief → Builder → Reviewer loop. DeepSeek is fast enough to handle most of the coding inside the loop without putting a frontier model in every step. 3. use high reasoning, not max, for implementation. max tends to overthink; high gets to the code faster and has been the better default for me. 4. keep tasks scoped. DeepSeek works much better when each worker gets the exact files, contract and goal instead of a giant repo dump. 5. use it aggressively for cheap long-running work. i’ve seen workflows like porting 2 games to Linux/Rust over ~6 hours for around €3 in tokens. the best use of DeepSeek isn’t replacing frontier models completely. it’s making them do less.
这条是引用着另一条写的：「DeepSeek V4.1-Flash-1017 上手观察」