He goes straight from gym to the code editor with phone off, no email, no support inbox, no X, and only does 'boring' work (email, support, Twitter) from around 4pm. Reading a bug report first thing hijacks the day into fixing instead of creating.
When it applies: solo builder whose output is shipping new products/features
Taking PG's maker's-schedule essay further, he removed meetings entirely so makers keep half-day blocks; all coordination happens asynchronously in Slack.
When it applies: small product teams / portfolio operators
Monday-Friday is building with no content work during the day; weekends are for content, and Sunday is for writing the newsletter plus a few tweets drawn from it.
Citing PG's 'founder mode', he says standard manager advice nearly broke two of his products and founders must stay close to details to keep the company alive.
When it applies: founder-led companies with a small team
Spend an hour every Monday scheduling seven days of tweets; even 24-48 hours of absence lets people forget you, and scheduling frees time to build things worth posting about.