Debugging days

๐Ÿ› You debugged all day but didn't fix it
Yesterday: Full day on the auth race condition. Eliminated three possible causes โ€” it's not the session layer or the middleware. Narrowed to a timing issue in token refresh. Have a specific hypothesis now. Today: Testing the token refresh fix. Expect a patch by EOD. Blockers: Would help to have someone familiar with the refresh flow review my hypothesis before I implement.
๐Ÿ› You fixed a hard bug
Yesterday: Fixed the auth regression โ€” race condition in the token refresh window was causing intermittent 401s. Took two days to isolate but the fix is clean. PR up for review. Also added a regression test so this can't sneak back in. Today: Back to the dashboard mobile pass. Blockers: None.
๐Ÿ› You caused a bug and fixed it
Yesterday: Caught and fixed a bug in the migration script I shipped Tuesday โ€” it was causing slow queries on the analytics endpoint. Added the missing index. Verified no data integrity issues. Also ran performance checks after the fix. Today: Continuing the notification system work. Blockers: None.

Review and support days

๐Ÿ‘€ You spent the day reviewing PRs
Yesterday: Reviewed and approved Sarah's auth refactor (left detailed feedback on error handling) and Marcus's API changes (requested one change, re-reviewed and merged). Also pair-programmed with Priya on the analytics queries for about an hour. Today: Picking the notification system back up. Blockers: None.
๐Ÿ‘€ Mixed: some code, some reviews
Yesterday: Finished the CSV export fix and deployed to staging. Reviewed two PRs (feedback left on both). Spent an hour unblocking Marcus on the API rate limiting issue. Today: Starting on the settings page mobile pass. Blockers: None.

Meeting-heavy days

๐Ÿ“… Day lost to meetings
Yesterday: Four hours of scheduled meetings โ€” sprint planning (committed to the notification system scope), design sync (gave feedback that changed their approach to the sidebar nav), and a long product call that clarified the Q3 API priorities. No code. Today: Making up for it โ€” targeting a PR on the analytics endpoint by EOD. Blockers: None.
๐Ÿ“… One key meeting that moved things
Yesterday: Mostly meetings. The important one: had a long call with the design team on dashboard redesign โ€” pushed back on their nav structure and convinced them to simplify. That unblocks the mobile implementation. Also fixed two small bugs on the reports page. Today: Back to the notification system. Goal is to finish the data model. Blockers: None.

Blocked days

๐Ÿšง Waiting on someone else
Yesterday: Worked on the notification data model. Hit a wall waiting for the API spec from the backend team โ€” pivoted to cleaning up the settings page instead. Today: If the API spec comes in this morning, finishing the notification data model. Otherwise continuing settings. Blockers: Need the notification API spec from Jake to keep moving. Have been waiting since Wednesday.
๐Ÿšง Blocked by environment issue
Yesterday: Local dev environment was broken for most of the day โ€” Docker networking issue after the team infra update. Got it resolved by EOD with help from ops. Lost about 4 hours. Today: Catching up on the settings mobile pass and the notification system groundwork. Blockers: None now, but worth flagging: the infra update broke local dev setups for several people โ€” might be worth a team note.

Short weeks / low-output days

๐Ÿค’ Sick day / low output day
Yesterday: Out sick in the afternoon โ€” got through one PR review and responded to some Slack threads in the morning. Today: Back to full capacity. Picking up the notification system work where I left off. Blockers: None.
๐Ÿ—“ Before a holiday / short week
Yesterday: Wrapped up the settings mobile pass and merged it. Left detailed handoff notes for the notification system so whoever picks it up Monday has context. Also did a cleanup pass on the backlog tickets โ€” closed 6 stale ones. Today: Finishing any loose threads before the break. Blockers: None.

High-output days

๐Ÿš€ Strong shipping day
Yesterday: Shipped three things โ€” the CSV export fix, the date formatting on reports, and the onboarding flow to staging. All three deployed and verified in prod. Also cleared 4 review requests. Today: Starting on the notification system data model. Blockers: None.
๐Ÿš€ Long project milestone
Yesterday: Finally landed the auth refactor โ€” been in progress for 2 weeks. Merged, deployed, and ran the full test suite in staging. No regressions. This unblocks the SSO work. Today: Kicking off the SSO implementation with a design doc first. Blockers: Need Product to confirm scope of SSO providers before I spec the implementation.

Research and investigation days

๐Ÿ” You spent the day researching
Yesterday: Research day on the notification delivery system โ€” evaluated three approaches (polling, WebSocket, SSE) and wrote up a comparison. Recommending SSE given our architecture. Document is in Notion for feedback. Today: Starting implementation based on the recommendation, assuming no objections from the team. Blockers: Want to give the team until EOD to review the approach doc before I start building.
๐Ÿ” You investigated an incident
Yesterday: Spent most of the day on the API slowdown โ€” traced it to a missing index on the analytics table after a migration. Fixed and deployed. Also wrote a post-mortem doc explaining what happened and how we catch this earlier next time. Today: Back to the notification system. Blockers: None.

Onboarding / new territory

๐Ÿ“š First week on a new codebase
Yesterday: Reading through the auth module, payments flow, and the notification system (future work). Set up my local env and ran the test suite โ€” all green. Started on the onboarding ticket โ€” small scope, good first one. Today: Finishing the onboarding ticket and opening my first PR. Blockers: One question on the payments module when someone has a minute โ€” Slack is fine.
๐Ÿ“š Picking up someone else's work
Yesterday: Took over Marcus's notification system ticket. Spent the day getting context โ€” read the original design doc, the in-progress PR, and had a handoff call with Marcus. Identified one design question that needs resolution before I can continue. Today: Resolving the design question with Product, then continuing the implementation. Blockers: Need Product to clarify the notification priority levels before I implement the queue.

Remote / async teams

๐ŸŒ Timezone mismatch / async standup
EOD update (ahead of morning standup for US team): Today: Completed the analytics query optimization (3x improvement in load time), reviewed two PRs, and fixed the broken export link. About to sign off. Tomorrow: Picking up the settings mobile pass. Should have a draft PR by the time the US team wakes up. FYI / needs US attention: The export fix required a schema change โ€” Jake should double-check the migration script before the next deploy.
๐ŸŒ Written async standup (Slack/Notion)
**Yesterday** - Finished the mobile responsive pass on the settings page โ†’ PR #847 open for review - Investigated the analytics slowdown โ†’ root cause identified (table scan), fix deployed - Reviewed Priya's dashboard PR (approved) and left detailed feedback on Marcus's auth changes (needs update) **Today** - Starting the notification system data model - Will review Marcus's updated PR once he pushes changes **Anything blocking me?** Waiting on the API spec from backend team to finalize notification architecture. @Jake can you ETA?

Don't want to write yours from scratch?

Dump your raw notes into WorkLog. It pulls out a clean standup. Free, no signup, takes about 10 seconds.

Try WorkLog โ†’

See also: How to write standup when you had a bad week ยท Standup Generator ยท Live demo