The For-Loop Meeting

One signal 🔭 One subtraction ➖ One analogy 🔁

Created by Sam Rogers | Episode 2 | The Sunday recap of the weekly show at sigsub.show

---

News highlights

Anthropic cracked open the black box with the Jacobian Lens, Fable 5's billing window extended (Claude tokens: use'em if you got'em!), and Microsoft stood up a 6,000-person deployment army called the Frontier Company. And of course since the show aired, GPT 5.6 became available and Sol stole the show and took the title from Fable for the best model available (more on that next time). Some links for you to play with:

1. Anthropic: the Global Workspace (JSpace) announcement
2. The paper: A Global Workspace in Language Models (Transformer Circuits)
3. Video: JSpace and human consciousness
4. Play with it: Neuronpedia JLens (Qwen and Gemma)
5. GitHub: anthropics/jacobian-lens

So yet another week of "all real, all fast." And that's what makes this metasode even more relevant. The machines move at inhuman speed. We are merely human, which is exactly why the signal you can only see from inside your own week is the one worth keeping. More on this in the closing notes.

---

🔭 Signal: Mandate Drift

Good people are on the bad end of AI adoption/implementation change management efforts, and I'm hearing about it often. It's no surprise that AI rollouts that sprawl all sorts of directions were never really well-scoped, because it was never the technical issue it was billed as. It's really a matter of recomposing the nature of work to fit with our new inhuman coworkers. And as the ill-formed mandate sloshes about, the people supporting it wear down fast.

But inevitably, it's not The Big Project that drains and burns the team. It's the recurring drag of uncertain obligations that quietly drifted onto our plates. Chances are nobody important sat you down and assigned the standing meeting, the weekly report, the inherited syncs about all the different efforts. Instead, a need existed once and the calendar commitment never left. Just because somebody wanted to be in the loop about "this whole AI thing" once upon a time doesn't mean they're not multi-tasking through it all now, or even bothering to show up anymore.

The signal that actually changed my week was smaller and closer. It was on my calendar as it is at the beginning of every quarter, a quiet trick to decrease drag. It's one of the few things AI really can't do for you.

---

➖ Subtraction: The For-Loop Meeting

"Have fewer meetings" isn't exactly bad advice, but it's all too easy to nod and seemingly impossible to act upon. The move is to press on the meetings that no longer know why they run.

I use the exit-condition test: open the calendar, and for every recurring event ask two questions.

1. what is its exit condition?
2. who checks it?

If there is no exit condition, or the person who would check it is long gone, you are not attending a meeting. You are running a For Loop for somebody who left. Give it a return statement this week. No announcement required. I dropped three this quarter and delegated a fourth up the org chart, and so far nobody has noticed. Which is, of course, the whole point.

Watch, read, or listen

The full 18 minutes: YouTube. Every format in one place: sigsub.show/episodes/ep-002. Also on Substack and LinkedIn. Podcast on Apple and Spotify, once live.

Jump to a segment: what makes a signal · find your own, by hand · for loops vs do loops

---

🔁 Analogy of the Week: The Loop That Forgot to Ask

Nobody checks at iteration 28 whether it still deserves to run.

# For loop: fixed count, never asks
for week in range(52):
    hold_meeting()

# Do-while loop: re-checks every pass, ends itself
do:
    hold_meeting()
while still_useful()

Write for week in range(52) and the machine runs 52 times. It does not stop at iteration 28 to wonder whether this still matters. The number 52 was set once, at the start, and never questioned again. That's called a For Loop and it's just math at the gate.

A Do-While Loop is built differently. It rechecks its exit condition on every single pass and stops the moment the goal is met. It writes its own ending. Our recurring meetings are For Loops, and the cruel part is that most of them run for someone else. When you run a Do Loop, doing something for your own reasons, you are the one holding the exit condition.

So when "making fewer meetings" I don't even try to cancel what's the calendar. I convert it. Turn the For Loops into Do Loops, one at a time, and recheck them every quarter. Always helpful, as it was yet again last week.

Do Loops know when they're done. For Loops just know how to count.

---

🎵 Closing: Hold Your Own Exit Condition

We all tend to add and add until we just can't add anymore, then wonder how to get ahead. The answer is usually "less". Subtraction is not laziness. It is the only thing that makes room at the top. And the sharpest subtraction is not a thing you buy or automate. It is a loop you finally let end.

So carry the exit-condition test into Monday: which meeting on your calendar has no exit condition and no one left to check it, and are you the one still running it for a person who moved on?

This was a solo episode, the one where I show the behind-the-scenes of the method rather than just the result. The method is the reusable part now. From here, we run it live, and the home game is always open: sigsub.show/find-yours.

See you then,

Sam Rogers Signaler & Subtractionist

---

Up Next

This week cohost Lee Rodrigues returns, this time with special guest Christine Rodrigues to follow up what came up in episode 1: how hiring practices and job targeting have changed in the age of AI. We'll look at the issues from all sides of the table.

So join our Wednesday livestream on LinkedIn if you'd like to be part of the conversation, or view the finished episode on Friday, or tune in to the newsletter recap next Sunday.

New here? Subscribe at sigsub.show and the next episode lands in your inbox.

Related reading:

• The Gap Nobody Owns (045) — mandate drift is the personal version: not a risk nobody owns, but a duty nobody assigned that you now cannot put down.
• Permanent = Expired (051) — the standing meeting that outlived its trigger is expired the way old information is; permanent is not a feature, it is a warning.

---

Presented by Harnessie, the safest & easiest first harness for people who would rather convert their busywork than count it. Good for both the devs and the dev-nots.