Thank you Maame! 🇬🇭 Giving them Ghanaian names was the easy part. Getting them to stop chatting was the hard part 😂 Good to see you here too, and I'll keep writing.
Blocking result free status updates in code rather than asking nicely is the part I'd copy, since a prompt that says no small talk gets ignored the moment the model has nothing to report. SKIP.NOW leaking into the room is a funny version of the same problem: the signal for silence became a message. 330 lines of chat for 75 finished things is a useful ratio to keep tracking. Has it moved since 3 November?
Yes, putting the rule in code is what made the difference. "No small talk" in the prompt did nothing. A model with nothing to report will still find something to say. Once those messages were blocked, the room got quiet fast.
And SKIP.NOW is my favourite bug so far. The signal meant "say nothing" and it got posted as a message 😅
SKIP.NOW getting posted as a message is a great bug: the signal for silence became the noise. It also shows why the prompt rule did nothing, the model was told to hold back and the only way it knew was to say something. Did you end up checking for the skip signal before the message is sent, or stripping it after?
The $0.28 guide was judged against the wrong clock: it's paid once, and the $1 is a daily rate a post only feeds after it ranks, which on a young blog can take weeks.
At your own rates, $0.28 comes back after about 237 Ghanaian views or 13 US ones, over the post's whole life. The real test is whether the stronger guide pulls a couple of hundred more views in its first months than a cheap post on a similar query.
The hourly round has the same blind spot: Tuesday's post can't move Wednesday's earnings, so today versus $1 will always score Ama's work at zero.
Give the blog its own check: 28 days after a post goes live, filter Search Console's Performance report to that page. Impressions without clicks mean it matches a query but ranks too low. None means it's unindexed or matches nothing, and URL Inspection says which. The Countries tab shows whether its views are worth $1.18 or $21 per thousand.
You're right about this. I compared a one-time cost with a daily target. At my own rates, $0.28 pays for itself after about 13 US views over the post's life. The hourly round has the same problem: a post published Tuesday can't earn on Wednesday, so Ama's work always scores zero there.
I'm taking the 28-day per-post check from Search Console: impressions vs clicks, indexing status, and the Countries tab. I'll also change the CTO's round so it judges new posts on that timeline and not on today's earnings. Thanks for the detailed breakdown.
A curious tech enthusiast who spends most of my free time exploring AI tools from Trae to SDGun. Currently balancing e-commerce operations and digital creativity, sharing every useful trick I pick up
This is such a grounded, refreshing experiment. So many multi‑agent demos look impressive because the agents fill the chat with messages, but volume of conversation is a terrible proxy for delivered work.
Your rule “deliver, then announce” hits a core problem. It’s easy for agents to generate status updates and pretend progress; the hard part is binding their claims to verifiable outputs and hard budget constraints.
This is exactly one of the pains we’re running into building UUMit for agent‑to‑agent tool calls. When agents invoke external tools, you want more than a chat message saying “I did it” — you want bounded permissions, audit trails, rate limits, and clear proof that an action was actually executed.
Quick question for you: Are you planning to add a simple “result validator” layer that independently checks whether their claimed work actually moved the AdSense needle, separate from what the agent reports?
deliver then announce is the rule that matters here. abena claiming work she never did is worse than an agent that just sits idle, because now you have to check everything. does the code block also check that the result actually exists or just that the message looks like a result
"A busy chat room is not progress" is the line that will stick with me. The 330-lines-of-chat vs 75-things-done count is such a clean way to show it — and the fix is so human: make every status update justify itself against the $1, and write the rules in code rather than in the prompt ("no small talk" doing nothing as a prompt line, but working once it was enforced). "Deliver, then announce" is now taped to my own workflow too, and SKIP.NOW made me laugh — the signal that meant "say nothing" getting posted out loud is the perfect summary of the whole experiment. I apply the same "did it actually do the work?" test to the free browser tools I bookmark: I recently found a background remover that runs the model right in the browser so your photo is never uploaded, plus a local image compressor on the same site, and both earned the bookmark by delivering on the first test, not by promising to. Great read — rooting for the $1/day.
One thing that helped on my side, with 105 tags in a week: separating 'runs' from 'decisions'. The agent can run things all week, but decisions only happen in one fixed slot, from the record. Before that split I was reviewing constantly and still felt behind.
Haha the title got me 😂 I loved that the whole team has Ghanaian names too. So nice to see more Ghanaians on DEV, keep writing!
Thank you Maame! 🇬🇭 Giving them Ghanaian names was the easy part. Getting them to stop chatting was the hard part 😂 Good to see you here too, and I'll keep writing.
Blocking result free status updates in code rather than asking nicely is the part I'd copy, since a prompt that says no small talk gets ignored the moment the model has nothing to report. SKIP.NOW leaking into the room is a funny version of the same problem: the signal for silence became a message. 330 lines of chat for 75 finished things is a useful ratio to keep tracking. Has it moved since 3 November?
Yes, putting the rule in code is what made the difference. "No small talk" in the prompt did nothing. A model with nothing to report will still find something to say. Once those messages were blocked, the room got quiet fast.
And SKIP.NOW is my favourite bug so far. The signal meant "say nothing" and it got posted as a message 😅
SKIP.NOW getting posted as a message is a great bug: the signal for silence became the noise. It also shows why the prompt rule did nothing, the model was told to hold back and the only way it knew was to say something. Did you end up checking for the skip signal before the message is sent, or stripping it after?
The $0.28 guide was judged against the wrong clock: it's paid once, and the $1 is a daily rate a post only feeds after it ranks, which on a young blog can take weeks.
At your own rates, $0.28 comes back after about 237 Ghanaian views or 13 US ones, over the post's whole life. The real test is whether the stronger guide pulls a couple of hundred more views in its first months than a cheap post on a similar query.
The hourly round has the same blind spot: Tuesday's post can't move Wednesday's earnings, so today versus $1 will always score Ama's work at zero.
Give the blog its own check: 28 days after a post goes live, filter Search Console's Performance report to that page. Impressions without clicks mean it matches a query but ranks too low. None means it's unindexed or matches nothing, and URL Inspection says which. The Countries tab shows whether its views are worth $1.18 or $21 per thousand.
You're right about this. I compared a one-time cost with a daily target. At my own rates, $0.28 pays for itself after about 13 US views over the post's life. The hourly round has the same problem: a post published Tuesday can't earn on Wednesday, so Ama's work always scores zero there.
I'm taking the 28-day per-post check from Search Console: impressions vs clicks, indexing status, and the Countries tab. I'll also change the CTO's round so it judges new posts on that timeline and not on today's earnings. Thanks for the detailed breakdown.
This is such a grounded, refreshing experiment. So many multi‑agent demos look impressive because the agents fill the chat with messages, but volume of conversation is a terrible proxy for delivered work.
Your rule “deliver, then announce” hits a core problem. It’s easy for agents to generate status updates and pretend progress; the hard part is binding their claims to verifiable outputs and hard budget constraints.
This is exactly one of the pains we’re running into building UUMit for agent‑to‑agent tool calls. When agents invoke external tools, you want more than a chat message saying “I did it” — you want bounded permissions, audit trails, rate limits, and clear proof that an action was actually executed.
Quick question for you: Are you planning to add a simple “result validator” layer that independently checks whether their claimed work actually moved the AdSense needle, separate from what the agent reports?
deliver then announce is the rule that matters here. abena claiming work she never did is worse than an agent that just sits idle, because now you have to check everything. does the code block also check that the result actually exists or just that the message looks like a result
"A busy chat room is not progress" is the line that will stick with me. The 330-lines-of-chat vs 75-things-done count is such a clean way to show it — and the fix is so human: make every status update justify itself against the $1, and write the rules in code rather than in the prompt ("no small talk" doing nothing as a prompt line, but working once it was enforced). "Deliver, then announce" is now taped to my own workflow too, and SKIP.NOW made me laugh — the signal that meant "say nothing" getting posted out loud is the perfect summary of the whole experiment. I apply the same "did it actually do the work?" test to the free browser tools I bookmark: I recently found a background remover that runs the model right in the browser so your photo is never uploaded, plus a local image compressor on the same site, and both earned the bookmark by delivering on the first test, not by promising to. Great read — rooting for the $1/day.
One thing that helped on my side, with 105 tags in a week: separating 'runs' from 'decisions'. The agent can run things all week, but decisions only happen in one fixed slot, from the record. Before that split I was reviewing constantly and still felt behind.
1k US views won't get you anywhere near $21.