Skip to main content

Wanna-Be Chef: Cheap Cheese Bean Casserole

Not every geek hits it rich with just the right algorithm and moves to Miami when he (or she!) retires at 35. I am not among that group, or any group near it. Cutting budgets can mean crappy food while you work. Cheap and quick recipes can be useful. At the very least, some way to mix up the usual stuff with a minor twist can at least make the daily drudge a bit more acceptable, for the moment.

This is my recipe for what I call Cheap Cheese Bean Casserole.

Ingredients:
  • 1 Cup Baked Beans (I prefer Bush's Maple Cured)
  • 1 Slice Chedder Cheese
  • 2 Beef Hotdogs (Cheese Dogs work well here)
  • 1/2 Cup Slightly Crushed Saltine Crackers
The instructions are dirt simple but the result is delicious, filling, and perfect on a cold day. Cut up the hotdogs and add to the beans. Cover with the chedder cheese and evenly cover the entire bowl with the crackers. Microwave on medium for 2:30. The cheese will melt into the beans, the crackers will be protected from the sauses and remain crisp. The result is great for five minutes and probably a collective $2 dollar price tag.

Later this week I'll post about the results and recipe for my attempt at flame grilled, beef stuffed bell peppers. Also, I'll talk about why on earth I'm writing about cooking and posting recipes on a tech blog, so stay tuned for that!
Labels:

Comments

Post a Comment

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operat...
1 comment
Read more

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful...
1 comment
Read more

How To Teach Software Development

How To Teach Software Development Introduction Developers Quality Control Motivation Execution Businesses Students Schools Education is broken. Education about software development is even more broken. It is a sad observation of the industry from my eyes. I come to see good developers from what should be great educations as survivors, more than anything. Do they get a headstart from their education or do they overcome it? This is the first part in a series on software education. I want to open a discussion here. Please comment if you have thoughts. Blog about it, yourself. Write about how you disagree with me. Write more if you don't. We have a troubled industry. We care enough to do something about it. We hark on the bad developers the way people used to point at freak shows, but we only hurt ourselves but not improving the situation. We have to deal with their bad code. We are the twenty percent and we can't talk to the eighty percent, by definition, so we need to impro...
4 comments
Read more