Bending the Code: A Meal, a Kitchen Wizard, and Why Tacos La Villa Is the Future of Everything
by Eric Becker, Court Jester of Vibe Code | FluidFortune.com
There's a table at Tacos La Villa on D Street in La Verne that has seen more of my half-baked ideas than most of my friends have. It's absorbed the ambient noise of YouTube tutorials, the quiet hum of a homelab stress test, and more than a few moments where a CyberSecurity concept finally clicked while I was halfway through a birria taco. My laptop has been opened here more times than I can count. My nacho order at the counter has been remembered before I finish saying hello. For the better part of the past year and a half, this place has been less a restaurant and more a second office — one that just happens to have significantly better food than anywhere I've ever actually worked.
This is a story about a meal. But it's also, inevitably, a story about code — and about why the two have more in common than you might think.
The D Street Graveyard
Before I get into the food, I need to tell you about the building.
My mother ran a dress shop called Heart of Haute directly across the street from this address for over two years. In that time, I watched three separate restaurants open in the space that is now Tacos La Villa, and I watched all three of them fail. Not slowly, either. They came in, they tried, and they were gone. I don't say that to be grim — it's just the reality of the restaurant industry, and it was the reality of that particular block.
What struck me at the time wasn't the quality of the food at any of those places. The food was generally fine. What was broken was harder to name. The atmosphere felt transactional. The staff seemed indifferent or overwhelmed. There was no sense that the people running the place had thought deeply about who was coming in or why they'd want to come back.
In software terms — and forgive me, this is a habit — those places shipped product without thinking about the user experience. They had the features. They didn't have the vibe.
When Aleja Bautista-Abad and her partner Luz opened Tacos La Villa at that location, something was immediately different. I remember noticing it before I'd even eaten there. The energy was different. The space felt intentional.
What Aleja and Luz Built
Aleja is the head chef and owner-partner of Tacos La Villa. She is, without question, one of the more interesting people I've met in the context of this community, and I say that having crossed paths with a fair number of interesting people along the road that eventually led me to build FluidFortune.
She is what I've come to think of as a Full-Stack Kitchen Wizard. She has the foundational, time-tested culinary knowledge of someone who understands why things work — why meat needs to slow-cook for twelve hours to reach that particular depth of flavor, why a certain green sauce needs the acidity balanced just so, why you don't rush certain things no matter how pressed for time you are. That's legacy knowledge. That's the kind of thing you can't Google your way into overnight.
But she also has something that a lot of people who possess deep technical knowledge sometimes lack: the willingness to throw a wildcard at the wall and see what sticks. The Flamin' Hot Cheeto Burrito on the menu is the clearest example of this. It is, on its face, an audacious concept. It is also completely, deliciously vindicated every single time someone orders it. The Cheeto crunch isn't gimmick for gimmick's sake — it works because everything underneath it is built on a foundation that can support the weight of the experiment.
She is, in the language of the vibe-coding world, someone who knows exactly which rules she can bend without breaking anything.
The Regulars and the Relationships
Part of why I keep coming back — and part of why I think Tacos La Villa has succeeded where others failed — is the staff.
Aleja picks her people the way she picks her ingredients: deliberately, with attention to quality, and with an eye toward how each element contributes to the whole. The people who work here know the product. They know the customers. And perhaps most importantly, they're treated well, which is something you can feel as a diner even if no one explicitly tells you about it.
There's a young man who works the front counter who is one of the better examples of good management I've seen in any industry. He started out in the kitchen. By most accounts, including his own, he wasn't thriving there — not because he lacked skill, but because the back-of-house environment didn't play to his real strengths. What he has is an outgoing personality, a natural ease with people, and a genuine enthusiasm that's hard to fake and impossible to manufacture.
Aleja saw that. She moved him up front.
The thing that makes this story worth telling isn't just that it worked out — it's how it worked out. Because he came up through the kitchen, he's not just a cashier who can smile and take your order. He's a cashier who, if something comes out of the kitchen less than perfect, can take the plate back, diagnose what happened, and actually help fix it. He can translate between the front-of-house experience and the back-of-house reality in a way that most front-desk employees simply can't. He's a full-stack employee, essentially — comfortable in both environments, invaluable in the space between them.
I've seen him in action. It's genuinely impressive.
Aleja and Luz have also been intentional about reaching out to the surrounding community in concrete ways — offering discounts to students at the University of La Verne being one notable example. It's not charity and it's not marketing in the cynical sense; it's an acknowledgment that a restaurant lives or dies based on its relationship to its neighborhood. She's building those connections deliberately, and it shows in the energy of the place on any given afternoon.
The Workstation
On off-days, on lunch breaks, on slow Tuesday afternoons when a project needs thinking-through rather than just executing — this is where I end up.
I've run homelab builds from this table. I've tested remote connections. I've worked through CyberSecurity concepts that were giving me trouble, the kind of slow-burn learning that benefits from ambient noise and occasional interruption. And lately, I've done a lot of what I do at FluidFortune from here: vibe coding, in the truest sense of the term.
For anyone unfamiliar: vibe coding is a term coined by Andrej Karpathy to describe the practice of working with AI tools through high-level natural language — describing what you want rather than manually constructing every line of logic. You're operating at the level of intent and outcome rather than syntax and structure. It's fast, it's iterative, and at its best, it feels less like programming and more like having a very capable conversation about what you're trying to build.
I am, by my own declaration and with zero false modesty, the Court Jester of Vibe Code. I hold this title with pride. It means I bring the ideas, the prompts, the "wouldn't it be interesting if" energy — and I rely on the underlying architecture, whether that's an AI model or a more technically grounded collaborator, to translate that energy into something that actually runs.
As it turns out, this is also a pretty good description of how I collaborate with Aleja.
The Prompt
It started with a conversation.
I'm sitting at my usual table, laptop open, lunch menu half-considered, and I start describing what I want: Chilaquiles, but as nachos. Green sauce. Chile Verde. Two eggs over easy. Crema instead of melted cheese — I want the tang and the cool-down factor, not the gloop. Refried pinto beans. Pico de Gallo. Avocado salsa on top. And light jalapeños, because my stomach has opinions.
That's the prompt. It's a vibe. It's a direction. It's a set of desired outcomes without a fully specified path to get there.
Aleja listened, asked a couple of clarifying questions — the kind of questions that come from genuine culinary knowledge rather than just filling out a form — and started filling in the gaps. The gaps I didn't know existed. How do you manage heat distribution when Crema is your primary dairy component, given that Crema behaves very differently under heat than a melting cheese? How do you keep the chips structurally sound under the weight of beans and egg yolk and Verde sauce while still getting the essence of chilaquiles coating on them? Where does the avocado salsa land in the sequence so it doesn't get cooked into oblivion but still reads as integrated rather than tossed on top as an afterthought?
These are not questions a vibe coder asks. These are questions a kitchen architect answers.
She went to work.
Deployment
There is a particular moment in any collaborative project where the work leaves your hands and enters someone else's, and you just have to trust the process. The oven was running. The components were coming together. I went back to my laptop and waited.
When the dish arrived, it looked exactly like the idea in my head — which is rarer than it sounds. The green chilaquiles sauce had done its work on the chips without collapsing them. The Chile Verde sat heavy and rich in the middle, all that slow-cook depth coming through in the color and the smell of it. The eggs were over easy, yolks intact, waiting. The crema was cool and white against the heat of everything else. Pico up top, avocado salsa draped across it. A modest scattering of jalapeño slices, respectful of the hardware constraints.
I cracked the yolk.
It ran down into the chips and the Verde and the sauce, and it became something new — a golden thread tying the whole thing together, softening the acidity of the green, rounding out the heat, binding the elements without overwhelming any of them. The first bite hit egg, then Verde, then a flash of avocado and green chile, then the crunch of a chip that had somehow stayed a chip through all of this. I loaded a little pico onto the next scoop. Added a jalapeño. The palate, as I told Gemini at the time, screamed in absolute joy.
This is what a successful deployment feels like.
Why It Works (The Part About Bending the Code)
Here is what I want to be clear about, because I think it's the most important thing: Aleja didn't invent a new cuisine. She didn't throw out the rulebook. She didn't "disrupt" anything.
What she did was understand the rules deeply enough to bend them.
Chilaquiles are chilaquiles. There are reasons for every element of that dish going back generations — the way the sauce softens and integrates with the tortilla, the breakfast protein, the balance of acid and fat and heat. Nachos are nachos. There's structural logic to them: the load-bearing chip, the melting cheese that acts as architectural mortar, the toppings arranged to hit multiple notes in a single scoop.
What Aleja did was look at both of those codebases and find the shared logic underneath. She identified that the functional role of melted cheese in a nacho — moisture, fat, a creamy counterpoint to heat — could be performed by Crema in a way that actually enhanced the chilaquiles concept rather than fighting it. She understood that the over-easy egg, rather than being a topping, would become middleware once broken — dynamic, integrating, binding elements that would otherwise sit in separate registers. She managed the chip question by controlling the sauce application: coated in the chilaquiles tradition, but protected enough to carry the nacho load.
None of that breaks the culinary code. It bends it. Precisely, deliberately, and with full knowledge of what the constraints are and why they exist.
This is senior-level work. In any field.
The Bigger Picture
I've been thinking about vibe coding a lot lately — what it's good at, what it isn't, and what it needs to reach its potential. The honest answer is that vibe coding is only as good as the foundation it's built on. A prompt can conjure an idea into the room, but it can't build the room. For that, you need someone who understands load-bearing walls.
The tension between so-called "legacy coders" (the ones who understand the deep architecture, the memory management, the reason certain things are done certain ways) and vibe coders (the ones working at the speed of idea, using AI as a translation layer between intent and output) is real, and it's not going away. But I think the tension is more productive than it is adversarial — or at least, it should be.
Aleja's kitchen, on one particular afternoon over a plate of Chilaquiles Breakfast Nachos, demonstrated this as clearly as anything I've seen. The vibe coder provided the prompt. The legacy-and-vibe hybrid provided the execution. Neither of us could have produced the result alone. I'd have had an interesting concept and no dish. She'd have had a full menu and no Chilaquiles Breakfast Nachos.
When they met in the middle, we got something neither of us anticipated: something new that was also, somehow, exactly right.
Where to Find the Magic
If you're in the La Verne area and you haven't been to Tacos La Villa on D Street, I would encourage you to fix that. Go for the Quesa Birria if you want to understand what I mean about legacy foundations holding up experimental frontends. Order the FH Cali Burrito if you want to taste audacity working in perfect harmony with craft — or if you don't want it flaming hot, take the Court Jester's recommendation: surf 'n turf. That's Carne Asada and Shrimp — a custom order request, but well worth the small additional cost — and if you want to really experience a mind-bending Cali Burrito experience, add nacho cheese to the mix. And if you're feeling adventurous, describe a direction to Aleja and see what she builds with it.
Bring your laptop if you want. A polite ask may get you the wifi password if you need it, but reception is excellent if you have a hotspot already. The atmosphere is warm and the salsa situation is exceptional.
My usual table might be occupied. Find your own.
Eric Becker is the founder of FluidFortune and self-proclaimed Court Jester of Vibe Code. He does most of his best thinking at restaurant tables and encourages others to do the same.