A Story of the No‑AI Brotherhood
By 2026, using AI at work had become quietly dangerous in some teams—not because of policy, but because of an unspoken code: don’t mess with the no‑AI brotherhood, no matter what the boss says.
The Setup
Maya had just been promoted to senior analyst at a mid‑sized logistics firm outside Atlanta. Her new manager, Daniel, was pro‑AI: he wanted the team to use copilots for drafting reports, summarizing meeting notes, and triaging customer emails. On paper, that was the company line. In practice, the team ran on something else.
The “brotherhood” wasn’t formal. It was a cluster of long‑tenured staff who prided themselves on doing everything “by hand.” They mocked AI users in side chats, rolled their eyes in meetings, and made little jokes about “prompt monkeys” and “copy‑paste consultants.” It felt harmless at first—until it wasn’t.
The First Warning
Maya’s first mistake was efficiency. She used an AI assistant to turn a messy Teams transcript into a clean summary before a client call. The summary was good. The client was impressed. Daniel praised her in the team channel.
That evening, in the unofficial Slack, someone posted a meme: a cartoon of a worker feeding prompts into a black box labeled “AI,” with the caption, “When your entire job is Ctrl+C, Ctrl+V, and hope.” A few people reacted with laughing emojis. One senior analyst, Raj, added: “Careful, some of us still believe in actual work.”
Maya laughed it off. But the next day, during a stand‑up, Raj “joked” that maybe they should start measuring “prompt count per report” as a KPI. The room chuckled. Daniel didn’t say anything.
The Escalation
Over the next few weeks, the harassment sharpened.
- In a design review, someone “accidentally” shared their screen with a chat window open where an AI had been asked, “How to pretend you’re working when you’re not?” The chat was clearly fabricated, but the implication landed.
- When Maya presented a well‑structured deck, a colleague muttered, “Bet an LLM wrote half of this,” loud enough for others to hear.
- In the team’s meme channel, a deepfake‑style image started circulating: Maya’s face photoshopped onto a stock photo of a person asleep at a keyboard, with the caption, “AI doing the heavy lifting again.”
It wasn’t just mockery anymore. It was a signal: you’re not one of us.
The Unspoken Rule
The brotherhood’s power came from informal influence. They controlled:
- Who got looped into high‑visibility projects.
- Whose work was double‑checked “for quality.”
- Who was quietly left out of pre‑meeting huddles where real decisions were made.
If you used AI openly, you were marked. If you used it in secret and got caught, you were labeled dishonest. The rule was simple: don’t mess with the no‑AI brotherhood, no matter what the boss says.
Even Daniel, who officially supported AI adoption, hesitated to confront the group. He knew they could make life difficult for anyone he “protected.” He framed it as “team culture” and urged Maya to “be sensitive” about how she used tools.
The Breaking Point
The turning point came during a quarterly review. Maya’s metrics were strong: faster turnaround, fewer errors, higher client satisfaction. But in the calibration meeting, several brotherhood members raised “concerns”:
- “Her work feels… generic.”
- “I’m not sure how much of this is really hers.”
- “We should be careful about promoting a style that relies on AI.”
No one said the word harassment. But the message was clear: your competence is suspect because you use AI.
After the meeting, a senior colleague pulled Maya aside and said, almost kindly: “Look, just… don’t make a show of it. Use it if you must, but don’t talk about it. Don’t let Daniel put you up as an ‘AI success story.’ You’ll make enemies.”
That was the unspoken rule, spoken at last.
The Choice
Maya had three options:
- Go quiet. Use AI in secret, never mention it, and try to blend in.
- Push back. Document the behavior, report it as harassment, and risk being labeled a troublemaker.
- Leave. Take her skills somewhere that didn’t treat tool use as betrayal.
She chose a fourth path, risky but deliberate.
She asked Daniel for a structured pilot: a two‑week experiment where the team would use AI on a specific, low‑risk task, with clear success criteria like time saved and rework reduced. She framed it not as “AI vs no‑AI,” but as “let’s measure what actually helps the work.”
At the same time, she quietly documented incidents: dates, messages, screenshots of the memes and the deepfake‑style image, and notes on who said what in meetings. She didn’t send them to HR yet. She just made sure the record existed.
The Confrontation
When the pilot ended, the data was unambiguous: the AI‑assisted workflow cut drafting time by 35% with no drop in quality. Daniel presented the results to the broader team.
The brotherhood pushed back hard. “This is just speed over craft.” “Next we’ll be judged on prompt count.” “Some of us still care about real analysis.”
Maya spoke up, calmly:
“I’m not asking anyone to worship AI. I’m asking that we stop punishing people for using tools that help. If the issue is quality, let’s talk about quality. If it’s about identity—‘real workers don’t use this’—then that’s not about work. That’s about exclusion.”
She didn’t mention the documentation. She didn’t need to. The shift in the room was subtle but real. A few younger analysts nodded. One senior member, previously silent, said: “Maybe we’re making this more cultural than it needs to be.”
The Aftermath
Nothing changed overnight. The brotherhood didn’t dissolve. But the temperature dropped.
- The meme channel went quiet on AI‑shaming posts.
- People stopped making “prompt monkey” jokes in meetings.
- A couple of analysts started asking Maya, privately, how she set up her workflows.
Daniel, emboldened, updated the team’s working agreement to explicitly state that using approved AI tools was acceptable, and that mocking or ostracizing colleagues for tool use would be treated like any other form of workplace harassment.
Maya kept her documentation in reserve. She knew that if the harassment escalated again—especially if it involved fabricated content or deepfake‑style attacks—she could take it to HR with a clear record.
The Real Rule
The story’s core wasn’t really about AI. It was about belonging.
In some workplaces, the unspoken rule had become: you don’t mess with the no‑AI brotherhood, or you’re dead meat. But the counter‑rule, slowly emerging, was this: using tools to do better work shouldn’t cost you your dignity, your reputation, or your place in the team.
Maya’s victory wasn’t that everyone suddenly loved AI. It was that the team began to separate craft from tribe—and that using AI stopped being a social crime.
(AI-generated)
. Good if you don't want any vibecoded ports I guess. I've been pretty open about it as well not gonna cosplay as an actual developer.
