Weekly letter

The Dispatch.

Honest words for engineers who are tired of pretending they're fine.


Every Sunday morning β€” before your Slack notifications start, before the sprint planning doc lands in your inbox, before the week accelerates β€” you'll find a short letter waiting for you.

It won't tell you how to be more productive. It won't share a "framework" for surviving AI. It won't have a sponsor, an affiliate link, or a growth hack disguised as wisdom.

The Dispatch is a letter from one tired engineer to another. It's about what this moment in software development is doing to us β€” to our sense of craft, our confidence, our ability to think slowly in a world that only rewards moving fast.

Some weeks it's a reflection on something I noticed. Some weeks it's an honest question worth sitting with over coffee. Occasionally it's something small and practical β€” a technique, a reframe, a three-minute exercise that actually helped.

Always under 600 words. Always worth reading before the week starts.

πŸ“¬ Sample issue β€” Vol. 1, No. 3

"The Test You Can't Pass By Typing Faster"

I've been thinking about a particular kind of tiredness that doesn't show up in burnout surveys. It's not exhaustion from too many hours. It's exhaustion from not being sure what you're doing anymore.

A senior engineer I know described it this way: "I used to know when I'd solved a hard problem. There was a feeling β€” this small satisfaction that something difficult was now understood. Now I just... ship things. And I'm not always sure which parts I actually understood."

That feeling β€” that hollowing out of the moment of mastery β€” is one of the subtler costs of working inside AI-accelerated flows. The feedback loops that used to teach us have been compressed or skipped entirely.

The question I want to leave with you this week: What did you understand this week β€” really understand, in your bones β€” that you couldn't have understood without writing it yourself?

β€” This is what The Dispatch sounds like. Thoughtful. Brief. Yours to keep or discard.

What you're signing up for

Not what we think you should be signing up for. What it actually is.

What readers say

We're early. These are real responses from engineers who found The Clearing.

"I've unsubscribed from every newsletter except this one in the last six months. It's the only thing in my inbox that doesn't make me feel like I'm being sold something."

Senior SWE, 9 years in industry

"The Sunday letter is the thing I actually read over coffee now instead of the HN digest. It asks questions I'd forgotten to ask myself."

Staff Engineer, fintech

"I forwarded the third issue to my entire eng team. Three of them cried a little. That's how accurate it was."

Engineering Manager, 12-person team

"Someone finally saying the quiet part out loud β€” that we're all kind of lost right now and that's okay. I didn't know I needed to hear that."

Mid-level developer, 5 years

Get The Dispatch in your inbox.

Every Sunday morning. Under 600 words. No cost, no catch, no confirmation loop.

Recent issues

A sense of what lands in your inbox.

Questions you might have

How often do you send?
Once a week, Sunday mornings (Pacific time). Occasionally an extra issue if something big is worth addressing β€” always clearly labeled. We've never sent more than two emails in a single week.
Is this related to any AI tool or company?
No. The Clearing and The Dispatch have no affiliation with any AI company, toolmaker, or VC-backed startup. We're not anti-AI either β€” we're pro-human. The goal is helping engineers find their equilibrium in an industry moving faster than most humans can comfortably process.
What do you do with my email address?
Send you the letter. That's it. We don't sell it, share it, run retargeting ads against it, or feed it to any analytics platform. Submissions go through Formspree. When you unsubscribe, we delete your record β€” no "are you sure?" emails, no re-subscribe nudges six months later.
I'm an EM / non-IC. Is this for me?
Yes. The Dispatch is for anyone carrying responsibility for technical work in the AI era β€” individual contributors, managers, leads, and technical founders. If you're feeling the weight of what's happening to the craft right now, this letter is for you. About 30% of readers are EMs or above.
Can I share The Dispatch with my team?
Please do. Forward it, drop it in Slack, paste the link in your team retro. If you find something worth sharing, share it. The goal is that the ideas reach engineers who need them β€” not that you feel protective of your inbox.
Will this help with my actual burnout?
Probably a little. The Dispatch won't fix systemic problems at your company or eliminate the pressure to ship faster. What it can do is help you feel less alone in what you're experiencing, give you language for things that are hard to articulate, and β€” on a good Sunday β€” remind you why you got into this work in the first place. For more practical support, see our reading list and our decompression tools.

The thing about AI fatigue is that it's deeply individual and almost universally shared. Everyone in the room is feeling some version of it. Almost no one is naming it. The meetings keep happening, the PRs keep getting reviewed, the velocity charts keep going up β€” and meanwhile something quieter is fraying.

The Dispatch is an attempt to name it. To say: yes, this is hard. Yes, the acceleration is real. Yes, your instincts about your own capacity are probably right. And then β€” very gently β€” to ask what you want to do about it.

You don't have to be in crisis to sign up. You just have to be someone who cares about doing good work and occasionally needs a reminder that good work takes a certain kind of slowness that the industry currently isn't giving you permission to take.

We'll take it anyway. Together. One Sunday at a time.

Join The Dispatch β†’