makekite
Original Story · Young Adult Ages 12–15 (Older Reader) ⏱️ 4 min read

Callum and the Coding Club Mistake

A story about accountability, backups and teamwork.

Illustration: A laptop shows lines of code.

Press Listen to hear the story, and tap any sentence to start from there.

🪙 Free tools to help you fly higher at makekite.com

The voice is a computer voice from your own device. We choose an Australian woman's voice when your device has one, and you can pick another from the list.

The coding club had spent two months on its app. It was a game that taught young children about recycling, with animated bins and a cheerful soundtrack. They planned to enter it in the state schools’ competition on Saturday. It was Thursday night, and everything was nearly done.

Callum, who was fourteen, was the team’s lead programmer. He stayed up late to fix a small bug. He was tired, and he typed a command quickly. He thought it would tidy the folders. He pressed enter. A line of text scrolled by, and the screen went blank.

His stomach dropped. He reopened the project folder. It was empty. He had run a command that deleted everything. His heart hammered. He tried to undo it, but there was no undo. He searched the recycle bin. Nothing. Two months of work was gone.

He sat frozen for several minutes. His first thought was to hide it. Maybe he could rebuild it overnight, and nobody would know. But he knew that was impossible. And he knew that hiding would only make it worse. He picked up the phone.

He called his teammate Nisha. “I have done something terrible,” he said. He told her the whole story. There was a long silence. Then Nisha said, “Okay. Do we have a backup?” Callum gulped. “I do not think so.” She sighed. “Let me check my laptop.”

A moment later, she gasped. “I synced the project to my cloud storage on Tuesday,” she said. “It is two days old, but it is there.” Callum nearly cried with relief. “You are a lifesaver,” he said. “I should have made a backup. This is my fault.”

The next day, the club met at lunchtime. Callum stood up. “I deleted the project,” he said. “I am sorry. I should have been more careful.” The others looked shocked, then relieved when they heard about Nisha’s backup. “We lost two days,” said Nisha. “Let us rebuild them.”

Together, they worked all afternoon and evening. Callum rewrote the lost code, and the others retested each level. On Saturday morning, the app was ready. They entered it in the competition, and it won second place in its category.

Afterwards, Callum set up an automatic backup system for the club. He made a rule on the wall of the computer lab. “Save often. Back up twice. Say sorry early.” The mistake had cost them two days, but it had taught them for life.

✨ Key Takeaways

  • Owning up to a mistake quickly helps the team find a solution.
  • Backups protect hard work from accidents.
  • Teamwork can turn a disaster into a success.

💬 Questions for Discussion & Reflection

  • What mistake did Callum make?
  • How did his team respond?
  • What can you do to protect your work or files?

Print a story writing planner →

makekite.com · © 2026 makekite.com, for personal and classroom use