My last season behind the kettle corn
A fall at Richardson Adventure Farm making kettle corn, keeping it stocked, fielding questions I have no business answering, and handling people who've clearly had a few. It's also my last season before college.
Most of what I write here is about servers, auth engines and things that live behind a login page. This one smells like sugar and hot oil.
Every fall I work kettle corn at Richardson Adventure Farm. I make it, and I handle the operations side: keeping it stocked in stores so it's there when people want it. I don't work the register. On paper, my job is everything that happens before a bag ends up in someone's hands.
On paper.
In practice, if you're standing next to a giant steaming kettle in the middle of a fall farm, wearing the work hoodie, you are not "the kettle corn guy." You are the guy. Information desk, lost-and-found, tour guide, therapist, and occasional bouncer. Nobody told me that part in training.
The job I signed up for
Let's start with the part I actually know how to do.
Kettle corn is simple in the way most hard things are simple. Oil, kernels, sugar, salt, heat, stirring. That's the whole recipe. The trick is everything around the recipe:
- Timing. It goes from perfect to burnt in a few seconds. Sugar doesn't give you a rollback. You watch it, you listen to it, and you pull it at the right moment, not one moment later.
- Consistency. The first batch of the morning and the last batch of a packed Saturday should taste the same. That only happens if you do the same steps in the same order every single time, especially when you're tired.
- Stock. A quiet weekday and a sold-out October Saturday are completely different loads. Stock for the weekday and you're out by noon on the weekend. Checking levels before they hit zero is way easier than scrambling once a store is already empty and people are asking for it.
With my IT and DevOps background, it took about one busy weekend to realize I'd walked into a production environment. Swap "batch" for "deploy" and "shelf" for "server" and half of this is a DevOps talk.
But production environments don't usually walk up to you and ask where the bathroom is.
Questions I am not qualified to answer
Here's something I didn't expect: standing near something interesting makes people assume you know everything. A kettle, a work hoodie, and a little bit of steam give you an authority you absolutely have not earned.
It isn't just the hoodie, either. The uniforms are red. That means anyone wearing red is fair game, on shift or not. So here's a free tip: don't wear red to a place where the uniforms are red. Come out on your day off in a red shirt and you'll be giving directions to the bathrooms within ten minutes. It's the fastest way to get asked questions I know of.
Over a season, I've been asked:
- Where the bathrooms are. (Fair. I eventually learned this one.)
- Where the bathrooms are, again, by the same person, twenty minutes later.
- How long the corn maze takes. I have no idea. I have never once finished it during a shift, because I am at the kettle.
- Whether the corn in the maze is the same corn in the kettle corn. Respect the curiosity. I genuinely don't know.
- What time "the thing" starts. Which thing? They also didn't know. We both stood there and thought about it.
- Where their car is.
- Where their kid is. (This one I take seriously. You find a staff member who can actually help, right away.)
- Whether I can break a fifty. I don't touch the money. I'm the guy stirring sugar.
- Whether kettle corn is "a healthy snack." I'm not going to lie to you while holding a paddle covered in sugar.
My early instinct was to guess, because saying "I don't know" felt like failing the job. Bad idea. A confident wrong answer about where something is sends a whole family on a fifteen-minute walk in the wrong direction, and they will come back to tell you about it.
So I adopted the same rule I use everywhere else: "I don't know, but here's who does" beats a confident wrong answer every time. Point them to someone who works that part of the farm, a map, or the info area. That's not dodging the question. That's routing it correctly.
Anyone who's done help desk work just nodded.
The after-dark crowd
Now, the part everyone actually asked me to write about.
As the day goes on, the crowd changes. The morning is families, strollers and grandparents. By evening, some groups have clearly been enjoying themselves for a while before they wander over to the smell of sugar. Most of them are great. A few of them become characters.
There's a whole taxonomy:
- The Philosopher. Wants to talk about popcorn on a deeper level. Why it pops. What it means. Whether we're all, in a sense, kernels. This person will stay for a while.
- The Expert. Has made kettle corn once, at home, in 2014, and has notes. Mostly about how I'm stirring wrong.
- The Negotiator. Believes the price is open for discussion. I don't set the price. I don't even take the money. This does not slow the negotiation down.
- The Best Friend. Has decided, within thirty seconds, that we go way back. Tells me about their week. Introduces me to their friends by name, a name that isn't mine.
- The Kettle Inspector. Wants to get closer to the kettle. Much closer. This is where I stop being chill.
Most of it is harmless and honestly kind of funny. Someone tried to order kettle corn "extra crispy, light on the sugar, hold the salt." Someone else asked me, with complete seriousness, if I owned the farm. I'm the guy stirring the sugar. The hoodie just means I work here, not that I'm in charge of it.
What actually works
You figure out pretty quickly that you can't win an argument with someone who's had a few, and you shouldn't try. A few things that work way better:
- Stay friendly, stay boring. Calm and slightly dull is the most de-escalating energy there is. Nothing to push against.
- Redirect, don't debate. "You're stirring it wrong" doesn't need a rebuttal. "Ha, maybe! Fresh batch comes out in a couple minutes" moves everyone along.
- Know where the line is. Joking is fine. Getting near the kettle is not. That thing is extremely hot, and hot sugar sticks. Being clear and direct about safety isn't rude, it's the job.
- Don't be a hero. If someone is getting genuinely out of hand, that's not mine to solve alone. Grab staff or security, let the people whose job it is handle it, and go back to stirring.
Most people are great
For every rough interaction there are dozens of good ones: kids watching the kettle like it's a magic trick, people who come back every year and remember the smell before they remember the name of the farm, and someone who buys a second bag on the way out because the first one didn't survive the drive to the parking lot.
It's ops, but louder
I keep coming back to how much this job feels like the rest of my work.
The kettle is the system. The stock is capacity planning. The questions are support tickets, half of them for a different department. The drunk guy explaining popcorn physics is an incident, and the response playbook is the same: stay calm, don't escalate, protect what matters, and hand it off to the right person when it's above your pay grade.
The difference is that there's no dashboard. You find out the system is healthy because people walk past, smell it, and come back for a bag.
What I take back with me
A season of this makes me better at the screen stuff. You learn to respect the boring parts: the restock, the checklist, the prep before the rush. Nobody notices them when they're done right, and everybody notices when they're not.
You also get really comfortable saying "I don't know." That's a skill a lot of people in tech could use more of.
And it's a good reset. After a day of building auth flows and arguing with configs, standing over a kettle making something people are genuinely happy to get (while someone explains to me that I'm doing it wrong) is a nice change of pace.
Practice for the classroom
I'm heading to college to major in secondary education, and the longer I worked this job, the more it felt like practice for that.
Think about what a shift actually involves:
- Answering the same question many times without getting short with anyone. Every person asking where the bathrooms are is asking for the first time, even if you're hearing it for the fortieth. That's a teacher's whole day.
- Explaining something simply while you're busy doing it. "Why does it pop?" while I'm mid-batch is basically a lesson with no prep time.
- Saying "I don't know, let's find out." A good teacher doesn't fake an answer. Neither should the kettle corn guy.
- Reading a crowd. Knowing when a group is fine, when it's getting rowdy, and when to step in calmly before it turns into a problem. Swap the drunk adults for a room of teenagers on a Friday afternoon and it's not that different.
- Staying calm when someone is testing you. The Expert and the Negotiator are good training for any student who wants to see how far they can push.
I didn't take this job to prepare for teaching. It just turned out to be pretty good prep anyway.
Signing off from the kettle
This was my last season. College is next, so I won't be back behind the kettle next fall.
I'm going to miss it more than I expected: the smell, the rhythm of a good batch, the regulars, and even the 9 p.m. philosophers. Thanks to everyone at Richardson for a great run, and to everyone who bought a bag, asked me a question I couldn't answer, or told me I was stirring it wrong.
If you're out there next year and you grab a bag of kettle corn, someone else made it. Be nice to them. And maybe don't wear red.
The bathrooms are that way. I know that one now.