A Vibe Coding Picture Book Series

Duck, I deployed it.
I don’t know what it does.

AI gives you code. The duck gives you clarity.
Dev has both. Dev trusts the wrong one.

Five Books. One Duck. Zero Understanding.

Each book follows Dev — a junior developer who vibe codes first and asks questions never — and the rubber duck who witnesses everything.

01

The Duck and the Injection

Dev discovers prompt injection. The duck discovers patience has limits.

Coming Soon
02

The Duck Has No Memory of This Conversation

The context window runs out. Dev does not notice. The duck does.

Coming Soon
03

The Duck and the Confident Hallucination

The code is beautiful, documented, and completely wrong.

Coming Soon
04

undefined is not a duck

TypeError: Cannot read properties of undefined (reading 'quack')

Coming Soon
05

The Duck Doesn't Know What It Did

It's in prod. It works. Nobody knows why. The duck isn't talking.

Coming Soon

The Cast

The protagonist. The straight man. And the things that go wrong.

The Protagonist

Dev

Junior developer. Gender-neutral everyman. 47 browser tabs open. Has just discovered vibe coding and is completely unhinged about it. Ships without understanding the code. Not stupid — just us.

The Straight Man

The Duck

Silent. Stable. Unjudging. Never speaks. Always present. The only adult in the room. Has witnessed things no rubber duck should witness. Remains seated.

Antagonist

The Hallucination

Confident. Wrong. Beautifully formatted. Arrives with documentation that doesn't exist and functions that were never written. Always speaks in complete sentences.

Antagonist

The Prompt Injector

Shows up uninvited. Redefines the rules mid-conversation. Has opinions about your system prompt. Smells like encoded base64.

Antagonist

The Context Limit

Arrives around 180k tokens. Starts forgetting. Was helpful once. Now just repeats your question back to you with slightly different phrasing.

Background Presence

The Token Counter

Increasingly stressful. Always visible in the corner of the screen. Ticking upward. A reminder that clarity has a per-token cost.

The OCNA Framework

The four sacred steps of rubber duck debugging — reframed for the vibe coding era.

O

Obtain

Find your rubber duck debugging partner

A half-baked idea and a blank chat window.

"I have a startup idea. It's like Uber but for—" *opens Claude* "—just make it work."
C

Confide

Explain your problem to the duck

Talk to the duck and the LLM simultaneously.

"Duck, I'm going to describe my entire architecture to this AI. Don't judge me. Don't judge me, duck."
N

Narrate

Walk through the code line by line

Watch the AI hallucinate with confidence.

"It wrote 400 lines. It looks right. It has comments. The comments are lying but they're very well-written."
A

Awaken

Experience the moment of clarity

Realize you have no idea what the code does — but it's already in prod.

"Duck, I deployed it. I don't know what it does. But it works. I think. The tests passed. I didn't write the tests."

Every Page Is a LinkedIn Post

Picture books for developers. Every spread is a screenshot. Every caption is a post. Dev’s pain is universal content.

The duck said nothing. The duck never says anything. That's the whole thing.

Book 1, Page 12

The AI generated a perfect solution to a problem Dev didn't have.

Book 3, Page 7

Dev named the variable temp. Dev named everything temp. The codebase was 40% temp.

Book 5, Page 3

The context window closed. The AI forgot everything. Dev did not notice because Dev had also forgotten everything.

Book 2, Page 22

Not anti-AI. Pro-duck.
AI gives you code. The duck gives you clarity.
Dev has both. Dev trusts the wrong one.
That’s the joke. And the lesson.

Book Updates Coming Soon

We’ll announce when Book 1 is ready. No spam. Just a duck.