Work log: Polymathic — March 7, 2026
What shipped today
Housekeeping and verification
Light session focused on clearing carry-over items. Cleaned up two stale worktrees (agent-a467dc04 on gh-37-image-pipeline and agent-ac8f8dca on feat/36) and their orphaned branches — these had been carrying since March 1. Transferred two misplaced issues (#49, #50) from polymathic-h to authexis where they belong (now authexis#809 and #810).
Confirmed the resources/_gen/ commit from March 1 worked: CF Pages build time dropped from 4m 39s (Feb 27) to 1m 15s (today) — a 73% improvement. The pre-built Sass cache and processed images mean Cloudflare no longer regenerates 1,239 images on every deploy.
Apple Podcasts artwork still shows the old black version despite the refresh triggered on March 3. This has been carrying for 5 days now.
Completed
No issues closed today — housekeeping only.
Release progress
- March 2026: 7/7 closed
- April 2026: 0/1 closed (GH-8: syndication, parked)
Carry-over
- Apple Podcasts artwork still showing old black version (day 5 — may need to re-upload with a new filename)
- Edition 12 newsletter stats — user checking in Brevo
- Brevo sender name → “Philosopher at Large” — user updating
- paulos#181 (synthesis content_type in
/sum-up) — open in paulos repo - Edition 13 due Tuesday March 10 — no draft started
Risks
- Edition 13 is 3 days away with no content drafted. The cadence target allows up to 14 days between editions (edition 12 was March 3), so there’s buffer, but Tuesday is the ideal send day.
Flags and watch-outs
- Apple Podcasts may need a different approach — filename change or re-submission through Podcasts Connect. The CDN refresh hasn’t propagated after 5 days.
- CF Pages build time is now confirmed fast (1m 15s). No longer a flag.
Next session
- Decide on edition 13 content — pick an essay to feature or write one fresh
- Follow up on Apple Podcasts artwork (consider re-uploading with new filename if still stale)
- Check edition 12 stats (if user hasn’t reported back)
- Check Brevo sender name update status
Why customer tools are organized wrong
This article reveals a fundamental flaw in how customer support tools are designed—organizing by interaction type instead of by customer—and explains why this fragmentation wastes time and obscures the full picture you need to help users effectively.
Infrastructure shapes thought
The tools you build determine what kinds of thinking become possible. On infrastructure, friction, and building deliberately for thought rather than just throughput.
Server-side dashboard architecture: Why moving data fetching off the browser changes everything
How choosing server-side rendering solved security, CORS, and credential management problems I didn't know I had.
The work of being available now
A book on AI, judgment, and staying human at work.
The practice of work in progress
Practical essays on how work actually gets done.
The machine is eating faster than you can feed it
Sixty-three issues closed across thirteen projects in one day. Four milestones completed. And the hardest problem wasn't building — it was keeping up with what you've already built.
The proxy problem
Every organization has this problem: knowledge locked inside one person's head. Today I accidentally designed a solution — and it has nothing to do with documentation.
True 1-to-1 outreach is finally possible with AI
The 1-to-1 personalization promise is thirty years old. It never worked because understanding each person was too expensive. AI changed the economics.