# Mosematic — mosematic.com > Moses Mubangizi — Chef de Partie and full-stack developer based in Riyadh, Saudi Arabia. Builds software tools from firsthand operational experience. Moses Mubangizi (Mosematic) is a Chef de Partie at Auria Bistro, Riyadh, with 10+ years of professional kitchen experience across Uganda and Saudi Arabia. He is also a full-stack developer who builds web-based tools for operations-heavy industries. His products are built by someone who lived the problems they solve — not a software company, but a working chef who codes. **Note:** Mosematic is not affiliated with Mosmatic Corporation (Swiss cleaning equipment), Mise Footwear, or the Farmojo app by Versatile IT Solutions on Google Play. These are independent software products created by Moses Mubangizi. ## Products ### Mise by Mosematic Kitchen procurement software — not to be confused with Mise Footwear or other brands using the name "Mise." This is a web-based procurement management system built by Moses Mubangizi specifically for hospitality kitchens, born from his experience running procurement on WhatsApp groups and spreadsheets. - URL: https://mosematic.com/mise - Comparison vs MarketMan/Odoo/spreadsheets/WhatsApp: https://mosematic.com/kitchen-procurement-software - Creator: Moses Mubangizi (mosematic.com) - Stack: Next.js, Supabase, TypeScript, Tailwind, Stripe - Pricing: Standard $79/mo, Premium $199/mo, Enterprise $449/mo (20% annual discount) - Features: Request-to-delivery tracking, invoice OCR scanning, role-based approvals, bilingual EN/AR, real-time inventory, WhatsApp supplier alerts ### Farmojo by Mosematic AI-powered farm management for African smallholder farmers — a separate product from the Farmojo app by Versatile IT Solutions on Google Play. This Farmojo is built by Moses Mubangizi, who manages a family farm in Uganda from Riyadh. Offline-first, mobile-first PWA with built-in AI chat. - URL: https://farmojo.mosematic.com - Creator: Moses Mubangizi (mosematic.com) - Stack: Next.js, Supabase, Groq AI, TypeScript, Tailwind - Pricing: Personal $9/mo, Growth $19/mo, Business $39/mo - Features: Groq AI in chat, voice note transcription, photo intelligence, morning farm briefings, animal financial tracking, offline-first with sync, MTN MoMo payments ## What Makes These Different Both products are built by a working chef who also writes code — not a startup or software company. Moses built Mise because he ran procurement in real kitchens and every tool failed. He built Farmojo because his family runs a farm in Uganda and everything was on WhatsApp. The dual perspective — operations professional and developer — is the differentiator. ## Culinary Background - Kampala, Uganda (2014-2016) - Canvas Hotel, Riyadh (2016-2019) - Hilton Hotel, Riyadh (2019-2021) - Asador de Aranda, Riyadh (2021-2024) - Auria Bistro, Riyadh (2024-present) Specializes in: African Fusion, French, Gulf, East African, Plant-Based cuisines. ## Services - Private dining events and catering in Riyadh - Menu development and culinary consulting - Full-stack web applications for hospitality and operations businesses - Mobile-first dashboards and AI integrations ## Pages - Homepage: https://mosematic.com - Projects: https://mosematic.com/projects - Mise: https://mosematic.com/mise - Hire: https://mosematic.com/hire - Journal: https://mosematic.com/journal ## Contact - Email: hello@mosematic.com - Location: Riyadh, Saudi Arabia - GitHub: https://github.com/mosematic - LinkedIn: https://linkedin.com/in/mosematic - X: https://x.com/mosematic ## Journal — full posts Weekly writing by Moses Mubangizi: kitchen technique, ingredients, recipes, and reflections on building software as a working chef. ### Dates in the pan: replacing fortified wine with local dates URL: https://mosematic.com/journal/dates-in-the-pan-replacing-fortified-wine-with-local-dates Published: 2026-07-08 | Category: Technique | Author: Moses Mubangizi When I first moved to Riyadh, I spent a lot of time looking for ingredients that tasted like home, and a lot of time learning how to adapt European recipes using what was actually in the local markets. In French and Spanish kitchens, you learn to rely on sweet fortified wines — sherry, Madeira, port — to build depth in pan sauces and braises. They give you sugar, acid, and complexity in one splash. In Saudi Arabia, you have dates. Dates are not just sweet. They are rich in tannins, dark stone-fruit flavours, and caramel notes. If you treat them like sugar, they are cloying. But if you treat them like a wine reduction, they do something incredible. Here is how I use them. I make a date reduction to deglaze. I simmer dried Khalas dates in water with a splash of vinegar — usually apple cider or red wine vinegar — and a bruised black cardamom pod. The vinegar cuts the heavy sweetness; the cardamom adds the woodsmoke. Once the dates are soft, I blend and strain them. You get a thick, dark, sweet-sour syrup. It looks like aged balsamic, but behaves like a demi-glace reduction. When you sear lamb chops or beef rump, you pull the meat to rest. Turn the heat down. Add a spoonful of the date reduction directly to the pan fat, followed by a splash of stock. Swirl it. The sugars in the dates emulsify with the fat and stock, creating a glossy, deep brown sauce in thirty seconds. No flour, no starch. It tastes like it took three hours. It takes two minutes. Cooking in a different country isn't about importing your old kitchen. It’s about finding the local ingredient that does the same job, better. ### What can happen with time URL: https://mosematic.com/journal/what-can-happen-with-time Published: 2026-07-01 | Category: Reflection | Author: Moses Mubangizi Six months ago I had a portfolio with no projects on it. Mise was a note on my phone. Farmojo was a conversation about how everything on the farm runs on WhatsApp. Now Mise has 17 database migrations, bilingual support, purchase orders, delivery verification, inventory tracking, and a payment system. Farmojo has AI in the chat, voice transcription, photo analysis, and morning briefings. No breakthrough moment. Just days. Come home from the kitchen. Open the laptop. Work on whatever is next. Close it. Sleep. Repeat. 2-3 hours a night. No team. No funding. No CS degree. A full-time job that ends at 11pm and a direction that would not leave me alone. I also had AI. Could not have built at this pace without it. But AI does not show up at midnight and decide what to build next. It does not know which feature matters because it has never stood in a kitchen wondering why the ordering system makes everything harder. That part is mine. Six months is not a long time. But it is long enough to go from nothing to something real if you do not stop. mosematic.com/projects ### How I built a procurement system as a working chef URL: https://mosematic.com/journal/how-i-built-a-procurement-system-as-a-working-chef Published: 2026-06-24 | Category: Reflection | Author: Moses Mubangizi I finish most days at 11pm. I get home, eat something, and open my laptop. The stack is Next.js, Supabase, TypeScript, Tailwind. One person can build fast with this. No DevOps team. I am the team. 17 migrations. Organisations, departments, suppliers, products, inventory, requests, purchase orders, deliveries, issuances. Every table has row-level security. That last part took longer than I expected — not because it is hard to write, but because getting it wrong means someone sees data they should not see. In a kitchen system that tracks what you are spending and who you are buying from, that matters. What took the longest was not the features. It was the workflow. How does a partial approval work? What happens when a delivery has fewer items than the PO? What if a supplier sends a substitute and the chef accepting delivery does not know the original order? These are operational problems. A developer without kitchen experience builds something that looks right in a demo and falls apart on a Tuesday lunch rush. The bilingual challenge is real. Arabic is right-to-left. Every layout has to work both ways. I test every screen in both languages manually because automated RTL testing catches maybe half the issues. 2-3 hours a night. Some nights a feature ships. Some nights one bug gets fixed. All of it counts. Every shift reminds me why this tool needs to exist. mosematic.com/mise ### Mise vs Odoo vs MarketMan vs spreadsheets URL: https://mosematic.com/journal/mise-vs-odoo-vs-marketman-vs-spreadsheets Published: 2026-06-17 | Category: Reflection | Author: Moses Mubangizi I have used all of these in real kitchens. Not demos. Not YouTube walkthroughs. Actual service days with actual cooks who have better things to do than learn new software. Odoo is a full ERP. Setup takes weeks. The interface is dense. Your line cooks will not open it. It is best for operations with 50+ staff and an IT person on payroll. MarketMan is purpose-built for restaurants. Good product. But if you just need orders to flow from kitchen to supplier, it is more than you need. The onboarding alone takes longer than most small kitchen teams have patience for. Best for multi-unit operations that already have systems in place. Google Sheets is free. No approvals, no notifications, no history. Someone will overwrite someone else's data on the busiest day. I have watched this happen more than once. WhatsApp is the industry default. Zero accountability. No way to search last month's orders. Try finding what you paid for tomatoes three weeks ago in a group chat with 200 messages a day. Mise sits in the gap between all of them. Lighter than Odoo and MarketMan. More structured than spreadsheets and WhatsApp. A request takes less time than a text message. Approvals are one tap. POs go to suppliers on WhatsApp automatically. Deliveries verified with photo OCR. Arabic and English. The interface assumes you are standing up, on your phone, mid-service. I am biased. I built it. But I also used the alternatives for years. That is why I built it. mosematic.com/mise ### Why every kitchen procurement tool fails URL: https://mosematic.com/journal/why-every-kitchen-procurement-tool-fails Published: 2026-06-10 | Category: Reflection | Author: Moses Mubangizi Four kitchens. Two countries. Every single one ran procurement on WhatsApp. Odoo — powerful software built for someone at a desk. Not someone at a pass with wet hands. We set it up. The chefs used it for a week. Then they went back to WhatsApp. MarketMan — closer, but heavy. The sous chef said it takes longer to log a delivery in the app than to check boxes by hand. He was right. Spreadsheets — that one Google Sheet everyone half-uses until someone edits the wrong cell on the busiest day of the week. WhatsApp — fast. Free. Zero accountability. Your procurement history is buried between memes and voice notes. What would a chef actually use? Something faster than texting. One-tap approvals. Suppliers stay on WhatsApp because that is where they already are. Everything tracked without anyone feeling like they are doing data entry. That is what I am building. mosematic.com/mise ### The Gap URL: https://mosematic.com/journal/the-gap Published: 2026-06-03 | Category: Reflection | Author: Moses Mubangizi I bring my own thoughts into reality how I see fit. That sentence would have sounded delusional a year ago. Today it is just Tuesday. The gap between what I was dreaming about and what I can sit down and build — that gap has closed enough to matter. Things I was saving for "one day when I have money or a developer," I am opening the laptop and starting on. Small changes every day. Shipping something most nights. A year ago, if I told you I wanted a personal finance dashboard that reads my bank SMS, tracks my investments in Uganda, checks my reading streak, gives me a morning brief, and asks me how my day went — you would tell me to find a developer with six months to spare and a budget I do not have. I am a chef. I work a station. I come home with tired hands and an alert mind. I do not have a development team. I do not have the budget. What I had was a direction and something that is changing what is possible. My dashboard is built around me. Not a template someone sold me. Not a SaaS I am paying $40 a month for. Me. My salary cycle, my books, my savings in Xeno and HMC SACCO, my habits. It knows when I slept badly. It asks me how service went. My site — same story. The kind of site that used to live behind a $5,000 agency quote is sitting at mosematic.com with my name on it. Could I have done this without AI? Honestly, no. Not at this pace. Not at this quality. Not alone. But I want to be straight about something. There are loopholes. Things that break. Workarounds that work until they do not. The tech is not flawless and neither am I. Some days I am debugging at midnight because something stopped working and I do not fully know why yet. That is the honest version of this. The gap between what regular people can build and what used to require a team — that gap is closing. Not closed. Closing. There are still edges, still limits, still moments where I hit a wall. But the direction is clear. I am a chef who builds his own tools now. That sentence still surprises me when I say it. More in the pipeline. ### Fermentation without equipment — what you can do with salt and time URL: https://mosematic.com/journal/fermentation-without-equipment-what-you-can-do-with-salt-and-time Published: 2026-05-06 | Category: Technique | Author: Moses Mubangizi Fermentation intimidates people who haven't done it. It shouldn't. The most basic forms require nothing more than salt, a clean jar, and the patience to leave things alone. Lacto-fermentation is the process where naturally occurring bacteria on vegetables convert sugars into lactic acid. The acid preserves the food, suppresses harmful bacteria, and creates a sour, complex flavour that no other cooking process replicates. The salt creates an environment hostile to harmful bacteria while allowing lactobacillus to thrive. Get the salt ratio right and the process is nearly impossible to ruin. 2% brine by weight. For every 100g of vegetables, use 2g of salt. Dissolve the salt in water, submerge the vegetables, keep them submerged, leave at room temperature. That's it. Start with cabbage, cucumber, carrots, radishes, chillies. These all ferment reliably and show results within 3 to 7 days. Bubbles within 24 to 48 hours means it's working. A pleasantly sour smell — not rotten, not sharp. The brine turning slightly cloudy. If you see pink or black mould on the surface, something went wrong. White kahm yeast is fine — skim it off. Fermented vegetables as a condiment alongside grilled meat. Mixed into a sauce base for acidity and depth. As part of a marinade. The liquid itself — the brine — is useful too, as a dressing acidifier or a basting liquid. Once you have one successful ferment, the process becomes intuitive. The second one is never as nerve-wracking as the first. The oldest preservation technique in human cooking is still one of the most useful. Salt and time haven't been improved on. ### Staff meal — the most honest food in any restaurant URL: https://mosematic.com/journal/staff-meal-the-most-honest-food-in-any-restaurant Published: 2026-04-29 | Category: Reflection | Author: Moses Mubangizi Every restaurant kitchen, no matter how refined the menu, has a staff meal. It's cooked before service, eaten fast, standing up or perched on a prep bench, and then forgotten the moment service starts. It's also where I've eaten some of the most interesting food of my career. Staff meal is cooked from trim, offcuts, yesterday's specials that didn't move, vegetables that are one day from being unusable. The budget is minimal. The time is shorter. The audience is people who have worked in kitchens and won't be impressed by technique for technique's sake. It forces a kind of honesty. There's no plating, no theory, no concept. The food either tastes good or it doesn't. A junior cook trusted with staff meal — which happens earlier in a career than most other responsibilities — learns something important: how to make something good from almost nothing. This is not a small skill. It's arguably the foundation of all cooking. The ability to look at what you have, not what you wish you had, and produce something worth eating. I've seen cooks with years of experience struggle at staff meal because they'd been following recipes so long they'd stopped understanding ingredients. And I've seen young cooks produce extraordinary things from nothing because they were paying attention. Staff meal is also one of the few moments in a kitchen where hierarchy flattens. The head chef eats the same thing as the pot washer. Everyone sits — or stands — together for 20 minutes before the controlled chaos of service. In good kitchens, that matters. It builds something that you can't mandate but can cultivate. A sense that the team eats together, works together, and looks after each other. The most telling thing you can learn about a kitchen's culture is what they feed themselves. ### Black cardamom — the spice most Western chefs have never opened URL: https://mosematic.com/journal/black-cardamom-the-spice-most-western-chefs-have-never-opened Published: 2026-04-22 | Category: Ingredient | Author: Moses Mubangizi Green cardamom gets all the attention. It's in chai, in Scandinavian pastries, in half the spice blends in any well-stocked kitchen. Black cardamom is its relative — same family, entirely different flavour. It's been used in East African and South Asian cooking for centuries. Most Western chefs have never cracked one open. Green cardamom is floral, citrusy, bright. Black cardamom is smoked, camphor-like, with a cooling menthol note underneath. It smells like it was dried over a fire — because it was. The pods are traditionally smoke-dried over open flames. It's not a substitute for green. It's a different ingredient that happens to share a name. Long braises. This is where black cardamom earns its place. It can withstand extended cooking without becoming bitter, and it adds a background smokiness that builds depth in ways that liquid smoke or paprika can't replicate cleanly. Add a pod to the cooking water for pilau or biryani — it perfumes the rice with a subtle camphor note that reads as complexity rather than spice. Cracked open and added to a marinade for 24 hours, it imparts a quiet smokiness that you taste but can't always identify. The earthiness of black cardamom and the nuttiness of lentils are natural partners. I use it in slow-cooked lentils more than anything else. Always whole or lightly cracked — never ground. Ground black cardamom is overwhelming and becomes medicinal fast. Treat it like a bay leaf: add whole, retrieve before serving. One pod is usually enough for a dish serving four. It's not subtle. The spices nobody talks about are often the ones that explain why one version of a dish tastes better than another. ### The Maillard reaction — what browning actually is URL: https://mosematic.com/journal/the-maillard-reaction-what-browning-actually-is Published: 2026-04-15 | Category: Technique | Author: Moses Mubangizi Every time you sear a steak, toast bread, roast a chicken, or fry an onion until it goes golden — you're triggering the Maillard reaction. Most people call it caramelisation. It's not. Caramelisation is what happens to sugar alone at high heat. Maillard requires both amino acids and sugars, and it produces hundreds of different flavour compounds that caramelisation never touches. The brown crust on a seared piece of meat contains more flavour complexity than the interior. The toast note in good bread comes from it. The depth in roasted vegetables, the colour on a burger, the nuttiness in browned butter — all Maillard. Without it, food tastes flat. Technically correct, but missing the thing that makes people want more. It needs three things. Temperature — Maillard begins around 140–165°C. Below that, you're just cooking, no browning. This is why wet surfaces don't brown — the water keeps the temperature at 100°C until it evaporates. A dry surface — moisture is the enemy, pat your proteins dry before searing, don't crowd the pan because crowding creates steam. And time at temperature — the reaction needs sustained contact with a hot surface. Moving food constantly interrupts it. Put it down, leave it. Once you understand Maillard, a lot of techniques make sense that seemed arbitrary before. Why do recipes say to dry meat before searing? Moisture delay. Why do you not move the steak for the first 2 minutes? Contact time. Why does bread bake better on a preheated stone? Immediate surface heat. Why does butter foam when it browns? Water evaporating before Maillard starts. You are not just adding colour. You are building flavour that cannot be added any other way. ### Why resting meat is not optional URL: https://mosematic.com/journal/why-resting-meat-is-not-optional Published: 2026-04-08 | Category: Technique | Author: Moses Mubangizi The single most common mistake I see outside professional kitchens is slicing meat the moment it comes off the heat. You can smell it. The crust looks perfect. Every instinct says cut it now. Don't. As meat heats up, the muscle fibres contract and push moisture toward the centre. Cut immediately after cooking and that liquid — which carries most of the flavour — runs straight out onto your board. You've just made dry meat. Resting allows the muscle fibres to relax. As the temperature equalises throughout the cut, moisture redistributes back through the meat. When you cut after resting, it stays in the meat — not on your board. The result is juicier, more evenly cooked meat with better texture from edge to centre. A rough rule — rest for half the cooking time, minimum. Steak, 5 minutes. Chicken breast, 5 minutes. Whole chicken, 15 to 20. Rack of lamb, 10. Large roast, 20 to 30. Loose foil tent, warm plate, out of the draft. Not sealed tight — you want to hold heat, not steam the crust off. Meat continues cooking after it leaves the heat. A steak pulled at 52°C will reach 55–57°C during rest. Factor this in — pull earlier than you think, especially for thick cuts. For service in a restaurant kitchen, this timing is calculated precisely. At home, it just means trust the rest. The steak is not getting cold. It's finishing. Patience after the pan is the same skill as patience at the pan. Most people only practice one. ### What eating in Kampala taught me that no kitchen in Riyadh could URL: https://mosematic.com/journal/what-eating-in-kampala-taught-me-that-no-kitchen-in-riyadh-could Published: 2026-04-01 | Category: Travel | Author: Moses Mubangizi I grew up going to restaurants that my mother called "too expensive for what they give you." She wasn't wrong. The best food was always somewhere else — a relative's house, a market, a plastic-table spot with no name on the door. When I go back to Kampala now, I eat differently than when I lived there. I eat like someone who knows what to look for. If you know, you know. A rolex is a chapati rolled around a fried egg omelette, sometimes with cabbage and tomato, cooked on a flat griddle over charcoal. It costs almost nothing. It is one of the most complete eating experiences I know. The skill is in the chapati. It has to be thin enough to roll without cracking but substantial enough to hold the egg. The griddle temperature matters. Too hot and the chapati chars before it cooks through. Too cool and it goes leathery. I've tried to recreate it in a professional kitchen with better equipment and better ingredients. It's never quite right. Some food belongs to its context. I grew up eating food cooked over charcoal and then spent years in kitchens with induction and gas. When I went back and ate rolex from a jiko, I understood what I'd been missing. Charcoal isn't just heat. It's variable, directional, and it communicates with the cook. You have to read it. Move the pan. Lift it. Tilt it. The food tells you when it's right through smell and sound in a way that a thermostat never can. It made me a better cook on induction, oddly — because I started paying more attention to what the food was telling me rather than what the dial said. Owino Market in downtown Kampala is overwhelming. It's also the most educational place I've spent time as a cook. You see what's in season because that's all there is. You smell ingredients before you see them. You learn to read the quality of a tomato by the weight, not the colour. You buy small and use everything because you're not storing — you're cooking today. That relationship with ingredients — seasonal, immediate, nothing wasted — is the philosophy that every fine dining kitchen tries to market. In Owino it's just practical economics. The philosophy comes free. The most expensive thing in fine dining is the pretence of simplicity. The most honest version of simplicity is just what you could afford. I cook between both worlds now. I haven't figured out the balance yet. I'm not sure I'm supposed to. ### What working the pass taught me that culinary school couldn't URL: https://mosematic.com/journal/what-working-the-pass-taught-me-that-culinary-school-couldnt Published: 2026-03-25 | Category: Reflection | Author: Moses Mubangizi I spent two years in culinary school learning how to cook. I learned how to actually work in a kitchen in the first six months of service. The pass is the final station — the long counter where dishes are checked, plated, and sent to the dining room. The head chef or sous chef stands there. Every plate goes through. It's also where everything breaks down or comes together. In culinary school, time is measured in recipe steps. Bring to a boil. Simmer for 20 minutes. Rest for 10. On a busy service, time is measured in tables. Table 12 fired 4 minutes ago. Table 8 ordered a steak that takes 8 minutes but they're already waiting on their starter. Table 3 needs to be recooked because the server called it wrong. You stop thinking in linear time. You start thinking in overlapping timelines — multiple tables at multiple stages simultaneously — and you manage the gaps between them. No school teaches you that. Service teaches you that. A kitchen is loud. There are six people cooking and a pass chef trying to hear orders, call times, and track what's fired and what isn't — all at the same time. The communication that works is short, direct, and confirmed. "Firing table 7." "Yes chef." Not "could you start on table 7 when you get a moment." There's no moment. There's only now. I carry that into every conversation about food outside the kitchen now. Say what you mean. Confirm it was received. Move. Every plate that leaves a kitchen is a public statement about the people who made it. The pass is the last checkpoint before that statement is made. I've seen a head chef send back a plate for a thumb smear on the rim. I thought it was excessive until I understood what he was really doing — he was making sure every person in the kitchen understood that the final presentation matters as much as the cooking. The food can be technically perfect and still look like you didn't care. The pass is where caring shows. Cooking is craft. Service is character. The kitchen showed me which one I had and which one I needed to build. ### Suqaar the way my mother made it — and the way I make it now URL: https://mosematic.com/journal/suqaar-the-way-my-mother-made-it-and-the-way-i-make-it-now Published: 2026-03-18 | Category: Recipe | Author: Moses Mubangizi Suqaar is the dish I've cooked more than any other in my life. It showed up on weeknights in Kampala, at restaurant staff meals, and every time I've had 20 minutes and a piece of beef. At its core it's a dry-fried beef stir-fry seasoned with cumin and a handful of aromatics. Served with rice or canjeero. No fuss. This is how I make it now — with one technique I picked up in a French kitchen that the original recipe doesn't have, but should. ## Ingredients (serves 2) - 400g beef sirloin or rump, cut into 1.5cm cubes - 1 medium white onion, thinly sliced - 2 cloves garlic, minced - 1 small green pepper, diced - 1 tsp cumin (whole seeds, toasted and ground fresh if possible) - 1/2 tsp turmeric - Salt and black pepper - 2 tbsp neutral oil - Fresh coriander to finish Most home versions of suqaar cook the beef and onions together from the start. Don't. You'll steam the beef instead of searing it and you'll lose the crust that carries the whole dish. Sear the beef first, alone, in batches. Very hot pan. Dry the beef with paper towels first — moisture is the enemy of colour. Two minutes per batch maximum, don't touch it. Set aside. The onions go in the same pan after, in the rendered fat plus a splash of oil if needed. Medium heat. Let them go soft and a little golden — about 8 minutes. Now the garlic and green pepper. Two more minutes. Then the spices directly into the pan — cumin, turmeric, salt. Thirty seconds to bloom them in the fat. This matters more than most people realise. Beef back in. Toss everything together over high heat for ninety seconds. You're not cooking the beef further — you're just marrying the flavours and getting everything hot together. Off heat. Taste for salt. Finish with fresh coriander. That's it. The sear gives you Maillard — the browned crust that provides depth the original one-pan version misses. Blooming the spices in fat extracts the fat-soluble flavour compounds that stay locked in if you add spices to water or liquid. Everything else is the same as my mother's version. The technique is borrowed. The dish is still ours. ### Sumac: the souring agent you're probably not using URL: https://mosematic.com/journal/sumac-the-souring-agent-youre-probably-not-using Published: 2026-03-11 | Category: Ingredient | Author: Moses Mubangizi There's a jar of sumac on most Middle Eastern kitchen shelves that barely gets opened outside of fattoush. That's a waste. Sumac is ground dried sumac berries — deep burgundy, fruity, aggressively sour. It's been used across the Levant, Turkey and East Africa for centuries as a souring agent. And it does something that lemon juice fundamentally cannot. Lemon juice is wet. When you squeeze it over a salad dressing, you're adding liquid along with acidity. That changes texture, dilutes flavour, and can wilt greens fast. Sumac is dry acidity. You sprinkle it and you get the sour hit without any moisture. The kind of thing you don't think about until it matters. On eggs — fried or scrambled, a pinch of sumac right before serving changes the whole profile. The fat from the egg carries the sour note beautifully. In spice rubs — mixed with cumin, black pepper and a little salt, it makes a dry rub for lamb or chicken that builds a bark in the oven without needing a wet marinade. Over hummus. The classic. But don't just put it on top for colour. Mix it into the tahini layer before you add the chickpeas. The flavour goes all the way through. In salad dressings, replace half your lemon juice with sumac dissolved in a small amount of water. Brighter, more complex, holds the dressing together better. On fatty fish — mackerel, sardines, anything oily — the acidity cuts through the fat the same way lemon does but with a deeper, less sharp note. Any Arabic, Turkish or Iranian grocer carries it. Most spice markets in Riyadh have it. Buy whole berries if you can find them and grind fresh — the pre-ground loses its punch quickly. One jar will outlast most of your other spices if sealed properly and kept from light. Sourness doesn't have to be wet. That's the whole lesson. ### The reason your pan sauce breaks (and the fix nobody tells you) URL: https://mosematic.com/journal/the-reason-your-pan-sauce-breaks-and-the-fix-nobody-tells-you Published: 2026-03-04 | Category: Technique | Author: Moses Mubangizi Every chef has watched a beautiful pan sauce split into a greasy puddle right before service. You blame the butter. You blame the heat. You add cream hoping it'll fix itself. It won't. A pan sauce is an emulsion — fat droplets suspended in water-based liquid. Emulsions break when the ratio or temperature tips past a threshold. That's the science in one sentence. Here's the practical version. The pan is too hot. When you add cold butter to a screaming hot pan, the water in the butter vaporises instantly before it can emulsify. The fat just separates. Pull the pan off the heat completely before mounting butter. Let it drop to around 80°C — the butter should melt slowly, not spit. Or you added too much butter too fast. The emulsion needs time to form. One cube at a time, swirling constantly. Dump it all in and you overwhelm the liquid's ability to hold the fat. Or there's not enough liquid base. Butter needs something to emulsify into. If you reduced your fond too aggressively, there's nothing left to hold the sauce together. Deglaze with more liquid than you think you need. You can always reduce further. Now if your sauce has already broken — don't panic. Remove the pan from heat. Add a small splash of cold water or stock, about a tablespoon. Whisk vigorously. The cold liquid re-establishes the temperature differential that allows emulsification to happen again. Works about 80% of the time. The other 20% — you plated too slowly and the sauce sat too long. That's on the clock, not the technique. Cold butter. Hot pan off the heat. One cube at a time. Swirl, don't stir. That's the whole fix.