~12 min · dispatch, patterns, anti-patterns, workflows
Setup 투자 정당화하는 Dispatch 작업이 다 세 속성 공유: 자주 일어남 (매일/매주), 검증 가능 (한눈에 output 맞는지 알 수 있음), 주의 free (절약된 시간이 결과 체크로 대체 안 됨). 그 셋에 optimize.
피할 안티패턴: Dispatch 를 일회성 reminder 로 사용 (Reminders.app 이 더 나음), iteration 필요한 작업에 Dispatch (책상 Cowork), 의존하는 Dispatch 작업 5개 한 번에 chain (track 잃어 — 작은 조각으로 나누거나 라이브로 run), Dispatch + 위험 권한 (SendEmail + open-ended 작업 = 안 좋은 날).
1) Train commute → workday startup
8:00 send Dispatch: "summarize yesterday's commits + open PRs"
8:25 notification fires; Mac has report ready
9:00 arrive at desk, start day with synthesis already done
2) Friday wind-down
17:00 scheduled: "compile weekly progress report"
18:00 leave, knowing Monday-self has summary ready
3) End-of-month billing
1st-9am scheduled: "reconcile last month's transactions"
Receive notification, review, file in 5 minutes instead of 30✗ "Dispatch: remind me to send the proposal"
→ Reminders.app does this in 2 seconds, no Mac required.
✗ "Dispatch: research, draft, refine, polish, send the doc"
→ Five steps, one ambiguous; needs Cowork at desk.
✗ "Dispatch: post my Twitter thread"
→ PostToSocialMedia is denied by default for a reason.
✗ "Dispatch: do the thing we talked about"
→ Strangers can't tell if it succeeded; neither can your Mac.아직 댓글이 없어요. 첫 댓글을 남겨보세요.