Day 173 - The Machine Talks to the Machine

March 30, 2026

Main Theme

Being busy is not the same as making progress.

Key Topics

The difference between busyness and progress
Low-impact tasks vs. meaningful work
The illusion of productivity
Aligning actions with goals
Evaluating how time is spent

Key Lessons

Activity alone doesn’t guarantee progress.
Busy work can distract from meaningful priorities.
Progress comes from focused, high-impact actions.
Clarity of goals helps guide better decisions.
Regular evaluation prevents wasted effort.

Reflection Questions

What tasks make you feel busy but not productive?
Are your daily actions aligned with your bigger goals?
Where could you shift focus to create real progress?
How can you better evaluate your time and effort?

Episode Transcript

Guy Reams (00:00.578)
This is day 173, the machine talks to the machine. I received a design document from a vendor last week. It was supposed to be their work. Within seconds, I could tell it came from an AI. And not from a good prompt either. The whole thing felt hollow. So I did something I'm still trying to understand. I fed their document into an AI tool, asked that AI tool to critique the work, and sent those critiques back to the vendor.

They replied with an email that was also clearly AI generated. I responded by running their email through an AI tool and sending that reply back. Now we are in this strange loop where machines are talking to machines and I am just the poor guy in the middle clicking the send button. A few days earlier, the same thing had happened with an employee. They sent me a request. The language was flat and generic in an unmistakable way.

I stared at it for a moment and thought, do I respond with an AI generated reply? What is the proper ethic here? I honestly do not know. This is actually pretty funny in a way that also makes me a little uneasy. We are in this weird middle layer right now. A good percentage of the population has never used an AI tool. Then there are those of us who do. Among those who do, some have access to really powerful and expensive tools or have built their own, like myself.

and most are using free tools. This gap is real and it's widening fast. We used to talk about the digital service, digital divide that we created back in the advent of computers. I wonder if that conversation is suddenly much more topical now. I keep thinking about what happens when the default mode of communication becomes a machine writing to another machine. When I send feedback and get a response, I want to know a person actually read it.

Thought about it, maybe even felt something. I want to know they care enough to put their own words on the line. When that stops happening, something breaks in this relationship. Trust maybe? Or just a basic assumption that we are both actually trying? When the default mode of communication becomes a machine writing to another machine, something is breaking in this relationship. I do not have a clean answer yet, but I know that I do not want to keep playing this game where I am stuck in the middle.

Guy Reams (02:29.262)
between two algorithms. So here's what I'm gonna try. The next time I get an email or a document that feels like it came from nowhere, I'm going to ask a simple question. Did the quick brown fox actually jump over the lazy dog? Or perhaps, what is the airspeed velocity of an unladen swallow? Actually, now that I understand context and how it impacts large language models, I could deliberately bypass context completely. Ask a question like, is the answer to this question no?

Or to be really fun, give me a one word answer that explains everything in detail. Not as an accu-jus, accu-usation, just as a check-in. Maybe that starts a different conversation. Maybe it does not. But at least it puts a human question back into the loop. Maybe I'll start there and see what happens.