New answers tagged organization
Okay, to make this easier to digest, I'm going to do this is a whole w/ sub parts. Square brackets donote optional parts Basic recipe: <quantity> <ingredient>[, <preparation>][, "divided"] Quantity: ( <number> [<qualifier>] [<units>] )+ Ingredients: [<brand-name>] [<preparation>] <item> ... now, you might notice that ...
This is an exercise in data modeling, more so than cooking. What you are describing is the design of your database. You are on the right track. You will want to consider how many of each of the fields you need to have. For example: Quantity - Unique [there will be exactly one of these] Quantity unit - Unique [exactly one] Brand - Unique [optional] ...
The raw potato will definitely cook through. If you cooked the potatoes first, they would be almost devoid of texture by the time they cooked a second time in the oven - you'd have something more akin to mashed-potato pastries on your hands. You might want to think about sweating the onions first, though. Sweating them would drive-off some of their ...
both can cook properly if baked long enough. For example, when preparing fried potato pancakes, they contain raw potatoes and onions as well.
Top 50 recent answers are included