Your weekday diary vs your weekend diary
Open an automatic diary to a random entry and you should be able to place it, workday or day off, before you check the date. The two are not the same kind of day, and the entries should not read alike. A workday is meetings, a branch merged, a task list that got shorter. A day off is a route through a few neighborhoods, an afternoon nobody scheduled. If both entries read the same, the diary is only capturing one of them.
The lopsided diary
deariary builds each day’s entry from whatever integrations you connect, and it can only write about the parts of your life that something is watching. That is the catch behind the convenience.
Connect only work tools, a calendar, a task manager, a code host, a chat app, and the diary turns sharp Monday through Friday and goes quiet the moment the week ends. Friday’s entry is full; the next day’s is two lines, or nothing. Connect only leisure tools, check-ins, watch history, music, and the opposite happens: vivid weekends, and Wednesdays that read as if the day barely occurred.
Both are lopsided diaries. One is good five days in seven, the other two days in seven, and either way a reader six months from now feels the half that is missing. The weekend recipe post made the point in one direction: work tools see almost nothing of a day spent out of the office. The reverse is just as true, and the fix for both is the same.
Two halves, two kinds of trace
The work half of the week leaves a structured trace. Meetings land in Google Calendar, finished items in Todoist, commits and merges in GitHub. The developer diary stack assembles that side in full.
The off-duty half leaves a looser trace. It is built from where you went and what held your attention: a Swarm check-in at a cafe, a Trakt entry for the film you finally caught. Neither shows up on a Tuesday at a desk, which is why a desk-only stack produces a blank Sunday.
Wednesday and Sunday, one stack
A diary that works all seven days needs a stack that straddles both halves. Picture five integrations connected: Calendar, Todoist, and GitHub on the work side, Swarm and Trakt on the off-duty side. Here is the same person’s Wednesday and Sunday from one week.
Wednesday:
Wednesday ran on a tight grid. The morning held sprint planning and a one-on-one back to back, and between them three tasks came off the list: the onboarding copy review, the staging deploy, the invoice open since Monday. The afternoon went to the search-indexing branch, four commits across two hours, the last merged just before six. Outside the grid there was lunch at a soba place near the office.
Sunday:
There was no grid at all on Sunday. It opened with one stray commit to the side project around eleven, then a slow walk to a cafe in Nakameguro and an hour lost in a secondhand bookshop. Lunch was a Thai place with Haru. The evening stayed in for three episodes of a show. No meetings, nothing on the task list, nothing merged after the morning.
Same five integrations, two entries that could not be confused. On Wednesday the work integrations carried almost everything, and the location feed offered one lunch check-in. On Sunday, Calendar and Todoist had nothing to say, and Swarm and Trakt carried the day. Each half of the stack covers for the other’s quiet days.
The contrast is the thing worth keeping
Re-read a diary months later and you do not take it one entry at a time. You feel the rhythm. The swing from five days of meetings into a Sunday of cafe names is the texture of the month, and a diary that reads the same every day flattens that rhythm into nothing.
The contrast carries something else, too: the real shape of the week, not the official one. The calendar declares Monday to Friday work and the rest not, but the integrations do not read the calendar. They log the Sunday-morning commit, the Tuesday-night film, the work problem that trailed you past five o’clock. A two-sided stack catches the side project bleeding into the days off and the days off that started on Thursday afternoon, because it watches both kinds of activity across all seven days. The point of covering both halves is not symmetry. It is seeing where the line between them actually falls for you.
A stack that covers both halves
The Free plan supports one integration, enough to capture one slice of one kind of day. The Basic plan raises the cap to five, the smallest plan that can hold both halves at once: a split such as three work slots and two leisure ones, or whatever ratio matches your week. The Advanced plan drops the cap for anyone whose days off are as instrumented as their workdays. The full plan comparison lives on the deariary homepage.
When slots are scarce, the most efficient picks are the integrations that ignore the work and leisure line entirely. Last.fm scrobbles on a Monday commute and a Sunday afternoon alike. A Bluesky post can go out any day. One slot on a both-halves tool feeds workday and weekend entries together.
What still falls outside
A two-sided stack closes the weekday vs weekend gap; it does not capture everything. The diary still knows only what an integration can see. A long hike that produced no digital trace is thin. A workday spent in a tool with no integration is thin. A book that defined a quiet afternoon lives nowhere these layers look, and reaching it means a webhook bridge until a native integration exists.
What the stack does fix is the most common failure: a diary rich on the days you work and empty on the days you do not, or the reverse. The aim is an entry you can open at random and place in the week before you ever look at the date.
