Best GTD for Software Engineers

What GTD actually asks of you

Get every commitment out of your head and into one trusted inbox, then decide the very next physical action for each.

Lists are organized by the verb — call, draft, review — never by topic. The non-negotiable part is the review: without it the lists rot into noise within two weeks.

How software engineers put it to work

1. 1

   Decisions at review time, not after

   The architecture decision is captured when the review happens — the alternatives rejected, the constraint that decided it — while the reasoning is still in the room. ADRs written from memory a month later are fiction.

2. 2

   Postmortem seeds during the incident

   Notes start while the incident is live: what was tried, what the dashboards said, what the timeline was. Linked to past incidents, they turn "didn't this happen before?" from folklore into retrieval.

3. 3

   Research trails that survive the tab

   RFC reading and bug hunts leave a linked trail — the Stack Overflow answer, the commit that explained the behavior, the doc that contradicted it. Next time the same error appears, the trail is one search away.

The capture habit, the linking, and the retrieval are the parts tentus automates — gtd without the daily upkeep.

Other methods worth trying