About Rincaza

I trained in a community-college pastry program and then spent two years decorating cakes for a grocery bakery, which teaches you speed and what actually sells at 4 p.m. I still bake that way at home: weights when they matter, cups when they do not, and no step that exists only to look fancy in a photograph.

I write desserts that fit after a normal dinner — a skillet cookie, a loaf cake, a pan of bars — not weekend projects unless I label them as such. If a frosting can be done with a whisk, I will not send you looking for a paddle attachment.

I started writing recipes after five years of getting home from an office job at 6:30 with a fridge full of ingredients and no plan. The dinners that actually got made were the ones that used one pan, stayed under 35 minutes, and did not send me back out for a specialty sauce. That is still the filter I use.

I test timings with a phone timer on the counter, not from memory. If a recipe says 20 minutes, it is 20 minutes on a home stove with a 12-inch skillet, not a restaurant flat-top. When a step can be skipped on a Tuesday, I say so.

I learned to cook over fire because the first apartment I rented after college had a broken oven for eight months. A kettle grill and a cheap instant-read thermometer taught me more about doneness than any oven ever did. I still use both, and I write temperatures you can check, not "cook until done."

I care about carryover heat, lid-on versus lid-off, and the difference between a gas grate and charcoal. If a recipe of mine works under a broiler as well as on a grill, I say so, because not everyone has a backyard.

I have cooked vegetarian at home for twelve years, not as a brand, as a grocery bill and a habit. The recipes I write start with the vegetable that is actually in season or already in the crisper — cabbage, sweet potatoes, a tired bunch of kale — and build a meal around it instead of treating it as a side.

I am particular about texture. Overcooked beans and watery zucchini are how people decide they "don't like" a vegetable. I write the doneness cues I wish I had when I started: how the edge should look, how it should smell, when to pull it off the heat.

I spent three years buying produce for a neighborhood grocer, which is a polite way of saying I learned to tell a ripe peach from one that will be floury by Thursday. I still shop that way. A recipe is only as good as the tomato, the chicken thighs, or the bunch of cilantro you start with.

When I write a recipe I say what to look for at the store — the cut, the ripeness, the fat cap — and what to do with the rest of the ingredient so it does not sit in the crisper until you throw it out.

I cook for two and freeze for later, because I would rather wash one pot on Sunday than five during the week. I scale recipes with that in mind: what doubles cleanly, what does not, and which parts you should leave unassembled until the night you eat them.

I keep a running note of what lasted in my freezer and what turned watery after a thaw. Those notes become the storage lines on the recipes I publish. If a sauce splits when reheated, I tell you how to bring it back, or I tell you not to freeze it.

I live in a one-bedroom with a 24-inch range and four burners I do not trust equally. I cook almost everything in a 12-inch cast-iron skillet because I do not have the cupboard space for a Dutch oven and a sheet pan army. That constraint is useful: if a dinner cannot be done in one pan, I usually rewrite it until it can.

I keep a short pantry — canned tomatoes, chicken stock, rice, eggs, onions — and I build recipes from those first. If you need a garnish that exists only in a specialty shop, I leave it optional.

I cooked on the line in two small restaurants in Portland for six years before I started writing recipes for a living. The thing I kept explaining to new cooks is the same thing I explain here: why you rest the meat, why the pan has to be hotter than you think, why salt goes on before the sear and not after.

I am less interested in a long ingredient list than in the two or three moves that decide whether the dish works. If a recipe of mine has a "don't rush this" note, it is because I have rushed it and watched it fail.

I cook for a household of four in a kitchen that is 10 feet wide. School nights, leftover lunches, and a Sunday pot that has to stretch to Monday are the jobs I write for. I do not assume you have a stand mixer or a second oven.

Most of my recipes start as something we actually ate last week. I write down the quantities after the fact, then cook the dish again from those notes so the published version matches what a tired person can follow, not what I improvised the first time.

I batch-cook on Sundays because I work irregular hours and I will not cook from scratch at 9 p.m. The recipes I publish are the ones that hold: chili that is better on day two, a grain salad that does not turn to mush, chicken that reheats without drying out.

I date containers and I write fridge and freezer times I have actually used, not the optimistic ones on the back of a package. If something does not reheat well, I say so and I do not pretend it is a meal-prep recipe.