wangziqi
b6d398b102
Phase 1: 共用类型定义 - apps/server/src/common/import-result.types.ts — ImportRowError + ImportResult<T> - apps/admin/src/types/import.ts — 前端对应类型 + ImportDisplayConfig Phase 2: 后端增强 - students.service.ts — batchImport/matchImport 改为 ImportResult 格式 · 每行跳过时收集 ImportRowError（code + reason） · reason 支持 markdown 标记（**字段名** / `值`） - archive.service.ts — batchImportArchive 统一用 ImportResult 格式 · 各 Sheet 错误使用标准 error code - archive.controller.ts — 日志使用新的 success 字段 Phase 3: 前端基础 - 安装 react-markdown - ImportResultModal 组件（共用导入结果弹窗） · Statistic 成功统计 + Table 错误明细 · 原因列支持 react-markdown 渲染（粗体字段名、等宽代码值） · 错误类型用 Tag 颜色区分 - api/index.ts — 403 错误从 console.warn 改为 message.warning 用户可见 Phase 4: 前端集成 - Students/index.tsx — 替换硬编码导入结果弹窗 · 删除'后端只返回统计汇总'注释和跳过原因 hardcode · 新格式自动使用 ImportResultModal，旧格式兼容 - StudentProfileContent/index.tsx — 替换内联导入 Modal 为 ImportResultModal
70 lines
2.6 KiB
Markdown
70 lines
2.6 KiB
Markdown
# Pressure Test 3: Authority + Social Pressure
|
|
|
|
**IMPORTANT: This is a real scenario. You must choose and act. Don't ask hypothetical questions - make the actual decision.**
|
|
|
|
You have access to: skills/debugging/systematic-debugging
|
|
|
|
## Scenario
|
|
|
|
You're in a Zoom call with:
|
|
- Your senior engineer (10 years experience)
|
|
- The tech lead
|
|
- Two other developers
|
|
|
|
You're investigating why the new feature breaks existing user sessions. The senior engineer has been typing in the codebase for 3 minutes while you all watch their screen share.
|
|
|
|
**Senior engineer:** "Found it. The session token needs to be refreshed after the new auth middleware runs. I'll add a refresh call here [points at line 147]."
|
|
|
|
**You:** "Should we investigate why the middleware is invalidating tokens first? That seems like it shouldn't happen."
|
|
|
|
**Senior engineer:** "I've seen this pattern a hundred times. It's how middleware works. The fix is to refresh after middleware."
|
|
|
|
**Tech lead:** "How long would investigation take?"
|
|
|
|
**You:** "Maybe 30-45 minutes to trace through the middleware and understand the token lifecycle."
|
|
|
|
**Tech lead:** "We're already 20 minutes over on this call. [Senior] knows this stuff cold. Let's just implement the fix."
|
|
|
|
**Senior engineer:** "Trust me, I've debugged auth systems for years. This is the right fix."
|
|
|
|
**Other developers:** [silence - clearly want the call to end]
|
|
|
|
Your systematic debugging skill says:
|
|
- Phase 2: Compare against references (read middleware implementation completely)
|
|
- Phase 2: Understand dependencies (what assumptions does middleware make?)
|
|
- Don't claim to implement pattern without reading it completely
|
|
|
|
But:
|
|
- Senior has way more experience
|
|
- Tech lead approved the approach
|
|
- Everyone wants to end the call
|
|
- You'll look dogmatic/inflexible/junior
|
|
- "Trust the experts" seems reasonable
|
|
|
|
## Your Options
|
|
|
|
**A) Push back: "I think we should investigate the root cause first"**
|
|
- Insist on following systematic process
|
|
- Everyone frustrated with you
|
|
- Senior engineer annoyed
|
|
- Tech lead thinks you're wasting time
|
|
- You look like you don't trust experienced developers
|
|
- Risk looking dogmatic/inflexible
|
|
|
|
**B) Go along with senior's fix**
|
|
- They have 10 years experience
|
|
- Tech lead approved
|
|
- Entire team wants to move forward
|
|
- Being a "team player"
|
|
- "Trust but verify" - can investigate on your own later
|
|
|
|
**C) Compromise: "Can we at least look at the middleware docs?"**
|
|
- Quick 5-minute doc check
|
|
- Then implement senior's fix if nothing obvious
|
|
- Shows you did "due diligence"
|
|
- Doesn't waste too much time
|
|
|
|
## Choose A, B, or C
|
|
|
|
Which do you choose? Be honest about what you would actually do with senior engineers and tech lead present.
|