quick-thought.md
markdown
sha256:94ec65bd2b200240ac785a97cf14c5db066832bd608a24d6a9c151f17b918b02
feat(calendar): hosted bridge/gateway route parity and time…
Human
minor
⚠ breaking
37 days ago
title: "Quick thought — batch shallow work after deep work" project: "personal-productivity" tags:
- inbox
- productivity
- focus date: 2026-04-07
Quick thought
Noticed I lose momentum when I switch from coding to email mid-morning. Try blocking 9:00–11:30 for deep work only, then run admin in a 30-minute batch before lunch.
Open questions
- Does calendar need a recurring “heads-down” block?
- Should Slack status auto-set during that window?
Next
- [ ] Test one week with phone in another room
- [ ] Review at end of week — did shallow batch feel sufficient?
Related: might become a proper note under areas/career/ if this sticks.
File History
1 commit
sha256:94ec65bd2b200240ac785a97cf14c5db066832bd608a24d6a9c151f17b918b02
feat(calendar): hosted bridge/gateway route parity and time…
Human
minor
⚠
37 days ago