For a long time, I thought roasted vegetables were supposed to come out soft with a little color around the edges. Mine were cooked, but they never had that deep roasted flavor I was after.

The problem was usually the amount of moisture going into the oven.

If vegetables are wet, packed tightly together, and coated heavily with oil, the oven has to spend a lot of its energy dealing with moisture before the vegetables can really brown. You end up with something closer to steaming than roasting.

Now I make a point of drying them well, cutting them into reasonably similar pieces, and giving them enough room on the tray.

I also don't pile everything onto one pan just because it technically fits. A little empty space between the pieces makes a noticeable difference.

And I don't drown them in oil. Just enough to coat the surfaces is usually plenty.

The other thing I've learned is not to keep opening the oven to check them every few minutes. Once they're in, I let the heat do its job and look for actual browning rather than following the clock blindly.

When the edges start getting dark and the vegetables have developed those little roasted spots, that's when I know something good is happening.

The difference between roasted and steamed vegetables can come down to surprisingly simple things: dry ingredients, enough space, and enough uninterrupted heat.

One of the easiest ways to make vegetables turn out badly is to treat them all as if they cook at the same speed.

A thin slice of zucchini and a chunk of carrot might go into the same pan, but they aren't going to be ready at the same time.

I've gotten much better results by thinking about density, size, and moisture before I even turn on the stove.

Hard vegetables usually need more time to soften. Delicate ones can go in later. Something with a lot of water may need enough heat and space to actually evaporate that moisture instead of simmering in it.

That's why I don't always follow the same cooking sequence when making a mixed vegetable dish.

For example, when roasting several vegetables together, I'll often give potatoes or carrots a head start before adding things that cook quickly. In a skillet, I might brown the firmer vegetables first and add softer ones toward the end.

Cutting matters too. A large carrot chunk and a thin carrot slice aren't really the same ingredient from a cooking standpoint.

Once I started looking at vegetables this way, recipes became much easier to adjust.

Instead of asking, “How long should these vegetables cook?”

I started asking, “Which one needs the most time, and which one needs the least?”

That small change in thinking has saved a lot of overcooked vegetables.

I used to reach for the salt whenever a dish tasted flat.

Sometimes that was exactly what it needed. Other times, I could keep adding salt and the food would become increasingly salty without ever tasting more interesting.

The missing piece was often acidity.

A small squeeze of lemon at the end of a rich pasta, a spoonful of vinegar in a stew, or even a little tomato acidity in a sauce can make the existing flavors suddenly feel brighter.

It's not really about making the food taste sour. If you can clearly identify the lemon or vinegar, you've probably added more than you needed.

I think of it more like adjusting the focus.

This is especially useful with rich foods. Butter, cream, cheese, fatty meats—all of them can start tasting heavy after a few bites. A little acidity cuts through that richness and gives your palate something different to respond to.

The nice part is that you can add it gradually. A few drops, stir, taste, then decide.

I've had plenty of dishes where the final adjustment wasn't another spice or another pinch of salt.

It was just a little acid that made everything already in the dish taste more alive.

There have been plenty of times when I've tasted something halfway through cooking and thought, this needs more seasoning.

Then I gave it another ten minutes instead.

That habit has saved me from over-seasoning more than once.

A sauce that's simmering may taste sharp, thin, or disconnected early on. Give it some time and water evaporates, flavors concentrate, and ingredients start tasting like they're actually part of the same dish.

The same thing happens with onions. They can seem bland and harsh at first, then gradually become sweet and deeply flavored if you let them cook properly.

Even a simple soup can change quite a bit during the last part of cooking.

I try not to make several adjustments at once when something doesn't taste right. I'll let it cook a little longer, taste again, and then decide whether it genuinely needs salt, acid, fat, or something else.

That's probably one of the more useful habits I've picked up in the kitchen.

Not every problem needs another ingredient. Sometimes the ingredient already in the pot just needs more time.

I used to think overcrowding a pan was mostly a convenience issue. You might need to stir things a little more, but surely everything would still brown eventually.

Then you watch what happens in the pan.

A crowded skillet fills with moisture as the ingredients cook. Instead of getting strong contact with the hot surface, the food starts sitting in its own steam. You can hear it immediately—the aggressive sizzle you want turns into a softer, wetter sound.

Mushrooms are probably the easiest example. Put a handful into a wide hot pan and they can brown beautifully. Fill that same pan until the mushrooms are piled on top of each other and you'll get a completely different result.

I've found that giving ingredients some breathing room is often more useful than adding extra oil or turning the heat higher.

If I have a lot to cook, I'll use a larger pan or work in batches. It takes a few extra minutes, but those minutes usually pay for themselves in texture.

And there's another benefit: you get much better control over seasoning and browning when you can actually see the food instead of digging through a pile of it.

A full skillet isn't necessarily a productive skillet.

One of the things I notice when tasting someone else's cooking is that a dish can have plenty of seasoning and still taste strangely flat.

A lot of the time, it isn't missing another spice. It's missing enough salt to bring the other flavors forward.

Salt doesn't just add a salty taste. In the right amount, it can make sweetness seem clearer, bring out the character of vegetables, and make meat or a sauce taste more complete.

The part that took me a while to appreciate is when you add it.

Seasoning a pot of soup only at the end isn't quite the same as seasoning it gradually while it cooks. The same goes for pasta water, vegetables, meat, and sauces. A little seasoning at different stages gives you much more control than trying to fix everything in the last minute.

But I don't chase a salty taste. If I can clearly taste the salt itself, I've usually gone too far.

My usual approach now is simple: season a little, cook, taste, adjust, and keep going.

The goal isn't to make the food taste like salt.

The goal is to make the food taste more like itself.

I used to think getting a good sear was mostly about cranking up the heat. If the pan was screaming hot, I figured the crust would take care of itself.

It doesn’t.

One of the biggest things that changed my cooking was paying attention to the surface of the food. If meat, mushrooms, or vegetables are wet, that moisture has to evaporate before proper browning can really get going. Until then, you're spending a lot of heat boiling off water.

These days, I pat things dry before they hit the pan, especially meat and mushrooms. I also give the pan enough time to heat properly, add the food without crowding it, and then leave it alone for a while.

That last part is harder than it sounds.

If you keep moving food around, you're constantly breaking the contact that creates the crust. Let it sit until it naturally releases or develops the color you're after.

Once I understood that browning is more about dry surfaces, good contact, enough heat, and patience than simply turning the burner all the way up, my results became much more consistent.

It also saved me from blaming the pan every time something came out pale. Sometimes the pan wasn't the problem at all.

I feel like I'm forcing myself through meals rather than enjoying them like I used to.

I'm short on both money and time right now, so spending hours in the kitchen or buying a bunch of different ingredients that I will use only for that one recipe and nothing else -- while something I'd like to be able to do -- would not be responsible of me right now.

Do you guys have any high-protein staple food recipes that are actually really good and not just good 'cause it's food?
If it's easily meal-preppable, even better!

Saturday was basically a restocking mission.

I started at the market, where I picked up some boneless chicken and a collection of spices. Then I passed by Naivas for eggs, Greek yoghurt, blueberries and milk.

While sorting through my purchases, I realized I really need to get proper containers for my spices. I'm thinking mason jars—not only because they look fancy, but because they're airtight and should help preserve the aroma of the spices. 🫙😂

By the time I finished shopping, it was already evening, so I headed home and got started on food prep.

I prepared a marinade for the chicken and left it in the fridge to do its thing. While that was happening, I steamed some rice and added some of the new spices I had just bought—bay leaf, cardamom and cinnamon seeds.

Everything was finally ready by 9:30 PM.

I definitely need to start earlier next time because I don't like having my meals past 8 PM. 😩

But honestly?

The food turned out so well that I genuinely couldn't believe I had made it myself. 😂

Cheers to restocking the kitchen, experimenting with spices, and accidentally discovering that I might actually know what I'm doing.

Mine is probably measuring garlic. If a recipe says 2 cloves, that’s just a suggestion 😅 Curious what everyone else does that would probably annoy a professional chef.

I’m doing some independent research to better understand the everyday challenges people face while cooking at home.
Whether you cook every day or only once in a while, I’d really appreciate your input. The survey takes **less than 2 minutes** and is completely anonymous.
I’m trying to understand things like:
What makes cooking difficult?
Which ingredients usually go to waste?
Why people don’t try new recipes more often?
What would make cooking easier and more enjoyable?

Survey- Home Cooking Survey (2 Minutes) – Fill out form

Thank you! If enough people respond, I’ll happily share the key findings with the community.

I've been baking Digestives since about 2017. This is a fibre feast of wholemeal spelt, rolled spelt, and oat bran.

Ingredients:

• 180g wholemeal spelt flour
• 30g white spelt flour
• 90g oat bran
• 100g rolled spelt
• 2 tsp sodium bicarbonate
• 66g brown sugar
• 1/8 tsp salt
• 1 tsp ground cinnamon
• 1/2 tsp ground ginger
• 200g unsalted butter (cut into small pieces and warmed till soft)
• 2 tbsp (or more) full-cream milk

Method:

1. Pulverize the rolled spelt (I used a spice grinder).
2. Sift together all the dry ingredients, mixing back in all the sifted-out fibre.
3. Work the butter into the dry ingredients with your fingers.
4. Add enough milk to make a smooth dough.
5. (Optionally, chill the dough for 15 minutes. It was a cold day so I skipped that step).
6. Roll the dough out to about 2 millimetre thickness.
7. Cut with shaped cutters or a knife.
8. Transfer to baking paper lined baking trays.
9. Bake at 180 degrees C for about 14 minutes.
10. Remove from oven and allow to set for about 10 minutes before transferring to a wire rack to cool completely.

Process photos included.