The Unfinished Manuscript with the Blue Spine

You start writing the book the week after you turn thirty. You buy a Moleskine with a blue hardcover from the Crossword Bookstore at the Phoenix Mall. The first page is about a boy who hears a different version of a nursery rhyme, one with an extra 'baah', and how it makes him feel like something is wrong with the world. You write in the mornings before stand-up, at the Formica table in your kitchen, the smell of filter coffee and the noise of the 7:15 Virar local passing below your building. You fill seventy-three pages.

The project lasts eight months. It ends not with a bang but with a new client from Frankfurt who needs daily syncs at 6 PM your time. The notebook goes into the drawer with your old headphones and expired passports. You forget the boy’s name. You get a promotion, move to a quieter apartment in Khar, buy a nicer coffee machine. The blue spine sits in a different drawer now, behind a tangle of charging cables.

Two years later, you’re on a video call with a junior developer in Pune who’s struggling to explain a bug. He’s flustered, trying to find a metaphor. “It’s like… the code expects the song to have two ‘baahs’, but somewhere it’s getting three,” he says, laughing at his own absurdity. You laugh too, tell him to check the API validation layer. You do not think of the blue notebook. You do not remember the boy who heard the extra ‘baah’ and felt the fabric of his childhood quietly tear.

The developer fixes the bug. You close the ticket.

You never open that drawer again.