A Week of Biryani in Atlanta: Notes from the Kitchen and the Counter

Monday evening, standing in the kitchen after work, I was tearing open a bag of basmati rice when the thought hit me. Let's go all in on biryani this week. If I made one meal a day myself and bought the other, then recorded the differences, I figured I'd learn something. Working in IT support, you internalize this pretty quickly: the key to problem-solving is "change one variable at a time." I wanted to apply the same logic to cooking.

Monday, Tuesday: Establishing a Baseline

On Monday I followed a Hyderabadi biryani recipe to the letter. I marinated chicken thighs in yogurt, turmeric, chili powder, and garam masala for two hours, parboiled the rice to about 70%, and layered everything up. It was edible, but nothing to write home about. The rice was slightly overcooked, and the spice aroma didn't seem to penetrate the meat. I left notes the way I'd write a troubleshooting log. Symptom: overcooked rice, weak flavor. Probable causes: rice boiling time, marinade duration.

On Tuesday I stopped by an Indian restaurant over in Decatur. I ordered the lamb biryani, and the moment the lid came off, saffron and rosewater hit me. Every grain of rice was distinct, and the meat fell right off the bone. The gap between this and my Monday version was so obvious it actually made me happy. At least now I knew what the target state looked like.

Wednesday, Thursday: Adjusting Variables

Wednesday, I extended the marinade from two hours to six. I boiled the rice for exactly five minutes and pulled it out right away. I also fried the onions not just to brown, but until they turned a deep reddish-brown. It took a while, but that turned out to be the biggest single change. The sweetness released as the onions caramelized balanced out the heat of the spices. A definite upgrade over Monday.

Thursday I found a restaurant on Buford Highway. I ordered a vegetable biryani with potatoes, carrots, and cauliflower. For it to have that much depth without meat, I figured it came down to generous ghee and whole spices. Cardamom, cloves, and cinnamon sticks were tucked in among the grains of rice. When I got home I added a note: "Try adding whole spices to the water when boiling the rice."

Friday, Saturday: Combining and Failing

Friday, incorporating Thursday's note, I added four cardamom pods, three cloves, and half a cinnamon stick to the rice water. I also doubled the grated ginger in the marinade. Best result of the week. A subtle spice aroma rose from the rice, and the chicken was seasoned all the way through. First time I've been impressed by my own cooking, which, honestly, caught me off guard.

Saturday, riding high on confidence, I pushed things too far. I decided to try coconut milk and mixed it into the yogurt marinade, and the result was disastrous. It wasn't biryani anymore. It was some kind of thing where rice sat on top of coconut curry. In IT terms, it was like pushing an untested patch to a system that was running just fine. The lesson was clear, but the trash can said it for me.

Sunday: Restoring the Friday Recipe

After Saturday's failure, on Sunday I restored the Friday recipe exactly as it was. I wanted to confirm it was reproducible. Thankfully, I got nearly the same result. Five minutes for boiling the rice, at least six hours of marinating, onions fried to reddish-brown, whole spices in the rice water. Those four were the key parameters of my biryani.

As I ate dinner, I felt the urge to organize the week's notes into a Python script. Simple stuff: put the recipe variables and satisfaction scores into a dictionary, then pull out which combination scored highest. I actually wrote it, and when a fifteen-line script spit out the Friday and Sunday combination as number one, I had to laugh. The code just confirmed what I already knew.

Over the course of the week: five pots of homemade biryani, two bowls of restaurant biryani. There's still leftover raita and pickled onions in the fridge. Monday's lunch is already decided.