Use Case

Developer Diary

Your work, written up before the next standup starts

You push commits and open pull requests on GitHub, hash out reviews in Slack, move tickets through Linear, sit in standups and sprint reviews on Google Calendar, and track focus blocks with Toggl. deariary stitches all of it together into a single entry every morning: commits shipped, the threads that mattered, tickets moved, and the hours you actually spent in flow.

Services to connect

Sign up for the following services and enable tracking (e.g. GitHub commit events, Slack workspace access, Toggl time entries).

GitHub Capture your coding activity automatically Slack Capture your conversations and highlights Linear Turn your Linear activity into a record of what you shipped Google Calendar Turn your schedule into diary context Toggl Track See where your time actually goes

A day in your life

9:00 AM

Standup fires. The day already holds sprint review at 2, a 1:1 with the lead at 4, and two review blocks in between.

9:45 AM

Pick up DEV-482 ("Fix rate-limit backoff on ingest worker") and drag it into In Progress.

10:30 AM

Start a 90-minute focus timer on the ticket. Headphones on, no Slack, first block of real work.

1:15 PM

PR #1421 opened against the ingest repo. 14 commits, 6 files touched, CI goes green on the first run.

3:00 PM

Review request posted in #eng-reviews. A thread spins up, 8 messages, one good suggestion about jitter.

6:40 PM

DEV-482 flipped to Done with the PR link attached. Laptop closes before dinner for once.

Next morning

Your devlog is waiting. Tickets, commits, reviews, meetings, and focus hours, all in one entry.

Sample diary entry

Saturday, March 14, 2026

Plans & Meetings

Standup, sprint review, and a 1:1 with the lead. The calendar looked dense from the first coffee, but the two review blocks in between held long enough to actually ship something.

Sprint review covered the ingest reliability track. The 1:1 landed on scope for next week, slightly trimmed.

Code & Tickets

DEV-482 "Fix rate-limit backoff on ingest worker" closed out end of day. Opened PR #1421 against the ingest repo with 14 commits across 6 files, and CI went green on the first run (a small miracle).

Review thread spun up in #eng-reviews, 8 messages deep. One good call about adding jitter to the backoff; folded it in before merging.

Focus & Rhythm

Two Toggl blocks, 4h 20m of focused time. The 10:30 block carried the ticket through to the PR. The afternoon block was shorter but enough to address review feedback and pair on a flaky test.

Conversations

Back-and-forth in #eng-reviews on the backoff change. Side thread in #infra about the next ingest deploy window, with a screenshot of the dashboard after the fix.

A standup, a green CI run, a review that landed cleanly, and a ticket shipped before dinner. The kind of day that earns a small celebratory beer.

Highlights

ingest-worker / Pull Requests 2 opened, 1 merged

api-gateway / Pull Requests 1 merged

ingest-worker / Issues 2 opened, 1 closed

Ingest / Issues Completed 3

ingest refactor / Time Tracked 4h 20m

Photos & Videos

Pairing over a paper sketch of the ingest backoff flow

Ubuntu terminal glowing green at the end of the day

How the diary gets written

Fully automatic

Commits, PRs, reviews, and issue activity pulled from every repo you touch.
Messages you send in connected channels, threads you reply to, and reactions you get.
Tickets you open, move, or close. Status changes and comments are captured.
Standups, reviews, and 1:1s from your working calendars.

Set them up once, then let them run. You do not need to log anything by hand for these to show up in tomorrow's diary.

Up to you

Start a focus timer before a deep-work block, stop it when you surface
Write a PR description that says why, not just what
Drop a screenshot or a short note in a review thread
Leave a comment on a ticket when a decision changes, not just when it closes

These are the parts that turn a log of events into a devlog you want to re-read. A Toggl block frames the day into chapters, and a line of reasoning in a PR or a comment on a ticket gives the entry its voice.