Archive for September, 2009

Creative cooking on half a brain

Friday, September 4th, 2009

Bwrgh. I can’t brain this evening.

Hmm. I should do dinner. What should I do?

What did I have for lunch? Rice, salmon teriyaki and edamame. I should avoid things like that.

Hm. And I just had a croissant for breakfast. Low veg day. I should do something with veg.

Oh, there’s an onion squash still on the counter. Squash is a vegetable. I should do that.

Chop chop chop. Hm. What do I do with it? Well, it’s nice and hollow, I should put something in it.

Needs a starch? Does it? I’ve had a fair bit today and have snacked, so maybe not.

Yeah, it needs a starch. but what? No rice. Had that for lunch. I have bread. Can I use that? No. I don’t feel like bread.

Ooh. I’ve not done polenta in a while. Would that work as a stuffing? Yes it would. Mmm. Polenta. Start the squash roasting and I’ll put some polenta on the stove to bubble away.

Wow, this dish has like no protein.

Oh, hey, pistachios. Let’s shell those and put them in the dish.

Man, shelling these is a lot of work.

Hmmm. What else can I put in this?

Cheese. I have cheese. That turkish cheese. kefa…teria? kefalotyri. like parmesan, only not.

Apparently also not turkish. Oh well.

This isn’t sounding very vegetabley, is it?

What else can I do?

Oh, I have tomato passata left. Tomatoes are a vegetable.

No, they’re not a fruit, they’re a vegetable dammit.

Hm. These squash are smaller than I thought. I can’t fit all the polenta I made in there. And there are more pistachios than I thought. Oh well, still room for a little tomato.

It’s more of a sauce than a vegetable ingredient anyway…

Now add the cheese.

Cool. I’ve made little pizzas on top of the squash.

I like pizza.

Now to wait.

So much waiting…

Waiting…

Waiting…

Ooh, food.

Hmm.

I think next time I’ll save creativity for when I’ve got a working brain.

It’s all the same, really

Tuesday, September 1st, 2009

Daniel Lemire wrote a post recently comparing one of Paul Graham’s essays on startups with the process of doing research.

It reminded me of a book I read recently, and an observation I made on it. The book was 101 things I learned in architecture school, and the observation was that half the advice applied just as well to software development as it did to architecture. I find this is often true: At the general level, good advice is very portable.

Here are some excerpts:

61. Less is more

Minimalism is not something that’s hard to find in software design (or at least software design as we want it to be instead of the endless feeping creaturism that it often turns out as). Particularly epitomized by the Unix philosophy of “Do one thing, and do it well”.

62. Less is a bore

On the other hand, there’s a reason we’re not all still living in the command line…

32. The most effective, most creative problem solvers engage in a process of meta-thinking, or “thinking about the thinking.”

Good advice anywhere, but particularly so in software development where there’s so much capability for abstraction.

81. Properly gaining control of the design process tends to feel like one is losing control of the design process

There’s a good chunk of explanatory text in the book about this one, which I’m not going to reproduce here. In short, this is about not becoming prematurely wedded to ideas and embracing the uncertainty needed for finding the right solution.

17. The more specific a design idea is, the greater its appeal is likely to be

Tools for solving everyone’s problems tend to be tools for solving no one’s problem.

90. Roll your drawings for transport or storage with the image side facing out

Ok. Maybe not this one…