I never planned to write about food. If you’d told me back at the end of 1999, when I was getting out of the Marines, that I’d one day run a cooking blog about vegetarian family dinners, I’d have laughed. Back then, dinner was whatever was fast and filling, and “vegetable” mostly meant the lettuce on a burger.
After the Marines, I found my way into IT. Today I’m a Senior Technical Analyst doing hardware support in healthcare, which means I spend my days keeping the machines running so the people taking care of patients don’t have to think about them. It’s a job built on troubleshooting: something’s broken, figure out why, fix it without making anything else worse. Turns out that’s a pretty good description of family cooking too.
My wife and I live in Sylva, North Carolina, tucked into the mountains, along with our dog Charlie, who supervises every meal from the kitchen floor. Our kids are grown and out on their own now. But the story of this blog really starts back when they were still at home.
The night dinner got complicated
When our youngest, Jaden, was 12, they announced they were going vegetarian. Mostly because they didn’t like the idea of hurting animals, and partly because some of their friends had made the same choice.
I’d love to tell you I handled it gracefully. I didn’t. My first response was the classic: “My house, eat what I cook.” And for a while, that’s exactly what happened. Jaden ate the side dishes. Every night. Potatoes, a salad, maybe some green beans, while the rest of us had the full plate.
Then one night I looked down at the table and really saw it. Everyone else had a complete dinner, and Jaden had a plate of sides. Not a meal, just whatever happened to be next to the meal.
So I tried cooking two separate dinners. That didn’t last. Two pans, two timelines, twice the dishes, and by the time everything was done I was worn out and dinner was late. It was hard, it was time-consuming, and it wasn’t something I could keep up night after night.
Fixing it like a tech problem
So I did what I do at work. I looked at the problem and asked: what’s the smallest change that solves it without breaking everything else?
The answer was to stop cooking two dinners and start cooking one that splits. Build a shared base (the sauce, the grains, the roasted vegetables, the seasoning), then branch at the very end. A little meat goes into some bowls, beans or tofu go into others. Same meal, same table, same conversation.
That’s the method I now call Base and Branch, and it’s the backbone of everything on this blog.
Where we are now
Jaden kept going on their own path: vegetarian, then pescatarian, then fully vegan by the end of high school. These days they’re in college, they love to cook, and when we visit, they cook for us. That still gets me.
Somewhere along the way my wife and I changed too. We eat mostly vegetarian and vegan now, with meat only once in a while. Nobody forced it. Years of Base and Branch dinners just showed us how good vegetable-forward food can be.
I’ve always liked being in the kitchen (I even went through a homebrewing phase), but I never expected the kitchen to change my family the way it did.
Why One Table Kitchen?
Because the goal was never to turn anyone vegetarian. It was to keep everyone at one table.
If your kid just told you they’re done eating meat, or your household is a mix of eaters, I’ve been where you are. I wrote a couple of books about it, My Kid Went Vegetarian, Now What? and The Flexitarian Kitchen Planner, but this blog is where I’ll share the everyday recipes and lessons as they come.
Pull up a chair. There’s room at the table.
Get a Free Week of Base and Branch Dinners
Seven weeknight dinners that split into plant-based and traditional, plus a shopping list for the whole week. Free, straight to your inbox.
