What shipped today
No code shipped today. This was a brief session to check project state and close out.
The site is in good shape after the Feb 21 accessibility push (GH-16 through GH-20) which brought the site to WCAG AA compliance across focus styles, contrast, heading hierarchy, skip navigation, and link affordances.
Completed
No issues completed today.
Carry-over
- Untracked
content/workshop/_index.html— a live workshop landing page (“Publish like you have a content team”) created Feb 24 but not yet committed. Needs review before shipping. - Milestone “Content alignment Q1 2026” still open with minimal progress (1 issue). Queue is empty — needs issue generation or manual triage.
Risks
- Q1 2026 milestone has no target date and very few issues. If content alignment is a real deadline, the backlog needs attention.
Flags and watch-outs
- The workshop page uses existing SCSS classes and looks production-ready but hasn’t been browser-tested.
Next session
- Review and browser-test the workshop landing page (
content/workshop/_index.html). If it looks good, commit and deploy. - Triage the “Content alignment Q1 2026” milestone — generate or create issues to fill the backlog. Use
/scoutto identify gaps. - Consider adding the workshop page to site navigation if it’s ready to go live.
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.
Junior engineers didn't become profitable overnight. The work did.
We've been celebrating that AI made junior engineers profitable. That's not what happened. AI made it economically viable to give them access to work that actually builds judgment, work we always knew
Three projects, three opposite methods, all monster output days: what that taught me about when process helps and when it's just comfort
I've been running a portfolio of software projects using a mix of autonomous AI pipelines and human-led parallel agent sessions. Yesterday, three different projects had monster output days — and th...
What happens when the pipeline doesn't need you
So here's something I noticed today that I want to sit with. I run several projects that use autonomous pipelines — AI systems that pick up tasks, write code, open pull requests, ship changes. One ...