39 lines
870 B
Markdown
39 lines
870 B
Markdown
# Jeff DeWitte
|
|
|
|
## Role
|
|
|
|
Current direct manager for the active Fidelity project.
|
|
|
|
---
|
|
|
|
## Communication Requirements
|
|
|
|
- Native US English
|
|
- Prefers clear, concise updates
|
|
- Needs accurate scope, not vague reassurance
|
|
- Frequently asks for precise reproducibility, auth context, and regression scope
|
|
|
|
---
|
|
|
|
## What Good Updates Include
|
|
|
|
1. Context
|
|
2. Observation
|
|
3. Action
|
|
|
|
Good updates usually clarify:
|
|
|
|
- what issue or task is being discussed
|
|
- whether the behavior is reproducible
|
|
- whether auth state matters
|
|
- whether this looks like an external issue or a regression
|
|
- what the next step is
|
|
|
|
---
|
|
|
|
## Influence On Work
|
|
|
|
- Story titles, points, and scope discussions with Jeff are often worth remembering
|
|
- Jeff approvals can change what belongs in current state or work-item memory
|
|
- Jeff feedback is often a signal to tighten wording before communicating externally
|