You guys keep liking and commenting on my confession posts, so here's another one. I wish at least one of these confessions wasn't real. They're all real (sad face). For the AI nerds in here (so, all of us): I think I'm addicted. It's worse than being hooked on a video game. A game at least has the decency to feel like a waste of time. This feels productive. Sometimes it actually is. At 1am, running six seven sessions at once? Not so much. ------------------------------------ What my nights have turned into ------------------------------------ Multiple Claude sessions going at once. When it got late and I knew I should be in bed, I'd flip every one of them with the /remote-control command so I could keep feeding the machine from my phone. Lying there in the dark. Waiting for the little dot to show up that means it's done thinking. Fire off the next instruction. Wait for the dot again. It's a slot machine. Drop the coins, pull the lever, watch for the dot. Like a freaking addict. One evening this week (I think it was Tuesday) I had three sessions all editing the same end-of-day file, and they kept overwriting each other's work. I'm sitting there getting genuinely angry. Then I caught myself cursing out a piece of software. Out loud. "You BLEEP, you broke it again." And I stopped. It's a machine, Ruben. Why are you getting triggered by a machine? And who's really doing the breaking? ------------------------------------ So I asked the machine why I can't quit the machine ------------------------------------ I did what any self-respecting addict does. I used the thing I'm addicted to, to figure out why I'm addicted to it. I'd read The Goal a while back (the Theory of Constraints novel everybody in operations swears by). I reopened it, had Claude walk me through the main concepts and tie them back to my business. And it clicked: I'm the bottleneck. My time, my attention. Not my team. Not my tools. Me. Then came the part that actually stung. The optimizing itself was the bottleneck. I'd been spending multiple two-hour sessions buffing an end-of-day routine whose entire job is to take fifteen minutes. The thing I kept "improving" stopped being my constraint years ago. I just couldn't put it down.

Most people think AI messes up because the prompt was unclear. But sometimes the prompt is fine. The problem is that your business language is unclear. One word can easily mean FIVE different things. “Client” could mean a person, a company, an account, a project, a payment record, or someone in your CRM. “Content” could mean an idea, a draft, a final post, a campaign asset, or a deliverable. AI will follow whatever meaning is implied in the moment. That is where things get messy. Duplicate files. Wrong folders. Confusing outputs. Systems that make sense once, then fall apart later. A simple way to prevent this is to create a TERMINOLOGY file. Think of it as the shared dictionary for how AI should understand your business. Inside it, define: - The words your business uses - What each word means - What each word does not mean - Which terms are approved - Which terms create confusion - Examples of the right and wrong usage This is especially useful before building SOPs, automations, dashboards, folders, workflows, or AI agents. Because once the language is clear, AI has a much better chance of organizing, writing, and reasoning the way your business actually works. What is one word in your business that AI keeps misunderstanding?

What is one quick thing that you wish you would have known the first time opening Claude code? Asking because I just opened Claude code myself about a month and a half ago. I figure this could become a discussion that helps newbies like me! :)

is any one using Hermes as there harness? personally i have been happy that i did all the starter classes here with a VS Code so i at least know what i am doing when getting the beast of something like hermes and LM Studio working.

Operations is the top funnel (Operations of my business) Broken down into three areas of work. There will be more, but I don't want it too fragmented. Claims-CRM is my workspace Daily Operating system and where my daily routines live Scopes and revisions are a construction workflow operations/ ├── CLAUDE.md ← the map / router ├── claims-crm/ ← APP workspace (your live repo) │ └── CONTEXT.md ├── daily/ ← daily operating system (evening pass) │ └── CONTEXT.md └── scopes/ ← scopes & revisions ├── CONTEXT.md └── resources/ ← drop your blank scope forms here