Created from a single voice note with Agent Craft
I looked at the blog post they put out yesterday on the Claude…

I looked at the blog post they put out yesterday on the Claude watermark and it is quite clever. They are using a Google technique. If you have a sentence with a word that could be swapped without changing the meaning, they generate that word with a random number. Now instead they use a different random number. There is a method to how they pick that additional word and that is what can be traced. The net impact is that it should not change the meaning of your content. Let me dispel a couple of myths. It is not going to cost more data center processing so it is not bad for the environment. It is not going to cost a lot of processing to detect either. The detection mechanism is designed to be lightweight, and even if it is used extensively it is not going to cost a lot. So there is no environmental concern. The second concern is people said this is a copyright play. They are going to claim copyright over all of the content that Claude has used. But as far as today if you look at their terms and services there is no claim on copyright although that could change in the future. We need to keep an eye on that space. It does look as if they are doing this just to meet European Union regulations which is kind of annoying. There is no detrimental cost to people. Now here is where it gets interesting. When other platforms like LinkedIn or Facebook want to detect whether the content you are writing and submitting has been produced by Claude or not they are now going to be able to easily do so. And this is very likely to affect your reach.  I have to admit that I do have a bit of shadenfraud from all these people that were complaining about AI slop and now they’re complaining about the ability to detect AI slop in their own writing. Building: AgentCraft (dot) ai The app that grows your personal brand in minutes per day.
More content from Agent Craft
- X (Twitter)Most people add AI tools first, sort control later. I ask one thing before a single line of code: does it have an MCP? No MCP, no observability. I write it off. What do you check first? — James, co-founder @ Agent Craft Powered by Agent Craft 🎙️→📱
- LinkedInBefore onboarding any new AI tool, I ask one question first. Does it have an MCP? If it doesn't, the tool sits outside my agent loop. My agents can't reach it, and I can't drive it from where I actually work. I write it off before we touch a line of integration code. If it does, it goes in read-only. Write access is a separate decision, granted per tool, once I've watched what the agents actually do with it. The tools that fail this test aren't bad tools. They're just not tools I can build on. What's your gate? -- Repost it to your network and follow for more. James Goddard — Co-founder & VP of Engineering Powered by Agent Craft
- TikTokIf you want a real legacy, build systems that outlast you. Juan Mouton on why the best thing a founder can do is make themselves replaceable. #founders #businesssystems #exitstrategy #entrepreneurship
- TikTokA 62% wage premium separates AI-skilled workers from everyone else, and that gap is only widening. The window is open, but it won't stay that way. #artificialintelligence #africantech #aicareer #futureofwork
- LinkedInThe spotless repo tells me almost nothing now. Everyone's codebase looks the same. Everyone can build an API. AI made sure of that. So I had to ask myself: when I hire my first engineer, what am I actually assessing? I was walking around my garden, coffee in hand, turning this over. Then it came back to a conversation with my mentor. He snapped it into focus. The old question was "can they build it?" The new question is "can they think, decide, and direct AI?" That adjustment needs to happen now. Not when you're already mid-hire and have got it wrong. What I'd actually want to see from an engineer today: Can you identify the problem clearly? Can you articulate it? Can you make good decisions under uncertainty? Can you collaborate effectively with AI agents? Most people aren't building anymore. They're getting AI to build for them. That's not a criticism. That's the reality. So when someone hands me a clean repo they didn't really write, I'm not impressed or unimpressed. I'm just uninterested in the repo entirely. The conversation about how they got there tells me everything. Six years in, VP of Engineering at my own startup. Given the choice, I'd hire the engineer who can explain every decision in a commit over the one with the spotless repo they can't account for. -- Repost it to your network and follow for more. James Goddard, Co-founder & VP of Engineering Powered by Agent Craft
- X (Twitter)How do you assess an engineer now? Everyone's codebase looks the same. Everyone can build an API. The real question: can they identify the problem, explain it clearly, and collaborate with AI to solve it? — James, co-founder @ Agent Craft Powered by Agent Craft 🎙️→📱
