Dad's Cloud
“Dad, what do you do?”
It was the middle boy who asked. He was sitting at the kitchen table with a worksheet about careers that Mom had assigned as part of their homeschool unit on community. The question was straightforward: What does your parent do for work? Describe their job in your own words.
The oldest had already filled his in: “Dad works on computers.” Clean. Efficient. Done.
The youngest had written: “Dad does stuff on the enternet.” Close enough.
But the middle boy wanted the real answer. The dreamer in him couldn’t settle for the simple version. He needed to understand.
Dad looked up from his laptop, where he was doing the actual work in question. “I’m a Cloud Architect.”
Three boys stared at him.
“I build things in the cloud,” Dad tried.
The youngest looked out the window. The sky was clear. Not a cloud in sight.
“There are no clouds,” the youngest reported.
“Not those clouds,” Dad said. “It’s — okay, come here.”
He pulled a chair over and the boys gathered around his laptop the way they gathered around anything Dad was about to explain — the oldest standing behind, ready to absorb; the middle one leaning in, ready to imagine; the youngest climbing directly into Dad’s lap, ready to touch buttons.
“Don’t touch the keyboard,” Dad said.
The youngest touched the keyboard.
Dad gently moved his hand. “Okay. So. You know how we keep stuff in the barn? Tools, feed, equipment?”
“And the cat,” the youngest said. Tiger was, in fact, in the barn at this moment.
“And the cat. But imagine if instead of keeping all that stuff in our barn, we could keep it in someone else’s barn — a really big barn, far away — and get to it whenever we wanted, from anywhere.”
“That’s dumb,” the oldest said. “What if you need a wrench right now?”
“Well, it’s not wrenches. It’s information. Data. Programs. Instead of keeping them on your own computer, you keep them in the cloud — which is really just a bunch of really powerful computers in big buildings somewhere.”
“Like a warehouse?” the middle one said.
“Exactly like a warehouse. A data warehouse. And my job is to design how those warehouses are organized. Which shelves go where. How to find things fast. How to make sure everything stays safe.”
The middle boy’s face lit up. This was his language — organization, maps, hidden structures. “So you build invisible buildings?”
Dad pointed at him. “That’s actually a really good way to put it.”
“Can you see them?” the youngest asked.
“Not really. They exist as — it’s like blueprints. Diagrams. Code.”
“Show us,” the middle one said.
Dad turned his laptop screen toward them. It showed a diagram — boxes connected by arrows, labels in small text, color-coded systems that flowed into other systems. It looked like a city map drawn by someone who thought in right angles.
The oldest studied it. “That’s a network diagram.”
“When did you learn that?” Dad asked.
“YouTube.”
Dad nodded. Fair enough.
The middle boy stared at the diagram like it was a treasure map. Which, to him, it basically was. “What are the blue ones?”
“Servers.”
“And the green ones?”
“Databases.”
“And the red ones?”
“Security layers.”
“Like guards?”
“Like invisible guards for the invisible building. Yeah.”
The middle boy went quiet. Dad could see the gears turning — the same gears that turned when the kid drew his maps, built his forts, designed the elaborate fictional kingdoms in his notebooks. He was mapping Dad’s cloud the same way he mapped everything else — finding the story in the structure.
Gunner had been lying under the table during this conversation, which was his default position during any family gathering in the kitchen. His understanding of the discussion was limited but earnest.
He’d heard “cloud” multiple times. He knew what clouds were. They were the big white things in the sky that sometimes turned gray and made water fall, which was exciting because water was one of his top five favorite substances.
He looked out the window at the sky. No clouds. But they’d come back. They always came back.
He put his head on his paws and returned to his vigil, occasionally glancing upward through the glass with the patient expression of a dog waiting for the sky to do something interesting.
Tiger, who had come in from the barn and was now on the kitchen counter — a position Mom had banned him from approximately four hundred times with zero success — watched the whole scene.
Tiger understood computers. Not in a technical sense, obviously. But he understood that the glowing rectangle consumed Dad’s attention for hours at a time, that Dad talked to it and it talked back, and that it was somehow connected to food and shelter and the continuation of their current living arrangements. Tiger respected the glowing rectangle in the same way he respected the heater — he didn’t know how it worked, but he knew it was important.
What Tiger did not respect was Dad’s attempt to explain it. The boxes and arrows and color-coded systems were, to Tiger, a transparently overcomplicated way of doing something that cats had solved millennia ago: keeping track of things. Tiger kept track of every food source, escape route, warm spot, and potential threat on the entire property using nothing but his brain. No servers. No databases. No cloud.
Cats were the cloud. Local, distributed, always on.
Tiger looked at the laptop screen, then at Dad, then out the window at the sky that Gunner was watching.
He was deeply unimpressed.
That afternoon, after the school unit was finished and the boys had scattered — the oldest to the woodshop, the youngest to whatever chaos would have him — the middle boy sat on the porch with his notebook.
He was drawing.
It wasn’t the career worksheet anymore. It was something new. A map — but not like his usual treasure maps of the property with X-marks and dotted lines. This was different. This was boxes connected by arrows, color-coded, layered. It looked like Dad’s cloud diagram, except the boxes were labeled things like “Gunner’s Food Bowl,” “Tiger’s Windowsill,” “The Secret Fort,” and “Mom’s Garden.”
He was mapping the family.
Dad came out onto the porch and looked over the boy’s shoulder. He didn’t say anything for a long moment.
“What’s this one?” Dad asked, pointing to a box in the center connected to everything else.
The middle boy had labeled it “Home.”
“That’s the main server,” the boy said. “Everything connects to it.”
Dad sat down next to him. Gunner, who had followed Dad outside because following Dad outside was one of life’s essential activities, lay down at their feet.
“That’s a pretty good architecture,” Dad said.
The middle boy shrugged, but he was smiling. The kind of smile that happens when a kid realizes his dad’s weird job might actually be a little bit cool.
Tiger appeared on the porch railing, because Tiger appeared everywhere. He looked at the notebook, looked at the boy, and jumped down into his lap.
The middle boy kept drawing with one hand and pet Tiger with the other.
Dad watched his son map the family like a network, the dog at his feet, the cat in his lap, the Virginia mountains catching the afternoon light.
He didn’t usually think of his job as anything special. It was technical. It was abstract. It was the kind of work where you built things nobody could see and fixed problems nobody could touch.
But his kid had just turned it into a treasure map.
Maybe that was the best thing about being a Cloud Architect: you built things that were invisible, and if you did it right, people didn’t even notice they were there.
Kind of like being a dad.
Later, at dinner, the youngest submitted his revised career worksheet.
What does your parent do for work?
“My Dad builds invisible buildings in the sky for people to keep their stuff in. He is a Cloud Arkitek.”
Mom graded it with a checkmark and a smiley face.
Under the table, Gunner caught a dropped green bean.
On the counter, Tiger watched the clouds through the kitchen window, still unimpressed.