Why I Started Cooking
The story of how a guy who could barely boil water became someone who looks forward to spending Sunday afternoon in the kitchen.
I used to think cooking was something other people did.
Not me — I was the guy who ate the same three things on rotation: pasta with jarred sauce, fried eggs, and whatever takeaway was closest. This wasn't laziness exactly. I just never saw the point of learning something that felt so... high-maintenance.
Then my wife went back to work full-time, and someone had to feed us.
The accidental education
The first few months were rough. I burned things. I under-seasoned everything. I once made a soup so bland my wife politely suggested we "order something" while looking at the bowl with thinly veiled concern.
But somewhere in that fumbling period, something clicked. I started noticing when things went right — when the onions turned golden at exactly the right moment, when the pasta water was salty enough, when the sauce reduced to exactly the right consistency.
It stopped feeling like a chore and started feeling like a puzzle.
What this blog is
This isn't a food blog in the traditional sense. I'm not a chef. I'm not a photographer. The photos here are taken on my phone, usually before I've thought about whether the light is good.
What I am is someone who cooks every day for people I love, who has made a lot of mistakes, and who has learned — slowly, stubbornly — what actually makes food good.
That's what I'm writing down here.