Library
Articles
Shorter Library articles on rates, focus, meetings, and working days. Guides remain the longer methods.
From the shelf
A full-stack draw that reshuffles each day. Nothing stays on top forever, and nothing is labeled new or stale.
-
Blockers
How to report blockers without sounding passive-aggressive
Blockers are requests with deadlines, not scorekeeping. Rewrite weak messages, keep tone factual, and make one-reply unblocks possible.
-
Batching
When batching tasks helps and when it hurts
Grouping similar work cuts setup tax until it becomes avoidance. How to batch email, reviews, and admin without starving features of depth.
-
Background work
What to Work on While a Build, Upload, or Render Runs
Machine waits have a clock and an alarm. Rank the work that fits them, see a two-hour build handled well, and know what never to start.
-
Delivery
Green CI is not finished work for developers
Passing checks are a checkpoint, not a deliverable. How to separate pipeline green from merged, verified, user-visible outcomes.
-
Change orders
How to raise a freelance change order without awkwardness
A scope-change protocol with pricing language you can paste. Name the change, price it, and keep the relationship when the brief grows mid-project.
-
Systems
Why productivity systems fail after a perfect first week
Week-one systems ignore interrupt reality, maintenance cost, and identity theater. Build a minimum system that survives ordinary Tuesdays.
-
Clients
Client feedback delays and how they should affect pricing
Waiting on approvals stretches calendar and opportunity cost. Build feedback assumptions into estimates, contracts, and rate - not silent resentment.
-
Decision records
How to document decisions without building bureaucracy
Capture decisions in a short, durable form: context, options, choice, owners, date. Enough to prevent re-litigation - not a wiki religion.
-
Response norms
Response expectations that respect time zones
Set reply windows a distributed team can keep. Replace ASAP and just-ping-me with overlap hours, urgency labels, and one written default the team shares.
Useful topic groups
Finishable days
Plan and protect a workday that actually ends
Focus under pressure
Keep deep work intact when the day frays
Async teams
Status, blockers, and when a meeting is worth it
Freelance capacity
Billable hours, buffers, and pricing choices
Developer depth
Builds, debugging, and expensive interrupts
Time zones
Overlap windows and DST traps
Notes that move work
Capture enough to continue without a second Notion