This is based loosely on Rosolli, but we adapted it somewhat for Midwestern-US tastes, and changed it from a side dish into a main dish. Notice that everything except the apples can be prepared ahead of time, and then you can throw it together quickly when it's time to eat.
5 medium-sized potatoes
7 fresh carrots
3-4 apples
2 medium onions (optional, or substitute a few pearl onions)
3 sprigs of fresh dill (optional, or use dried dill if that's what you can get)
1 lb. chicken breast
1 can (20 floz) chunk pineapple
oil for browning the chicken (I use olive oil)
salt to taste
Wash, cut, and boil the potatoes until done but not soft, and the carrots (separately from the potatoes) until firm. (Do not overcook. Everything in this recipe that is cut up should be cut into bite-sized pieces.) Save some of the water from the carrots.
Cut up the chicken and brown it in a skillet.
Drain everything and let it all cool while making the sauce...
Dipping Sauce / Dressing:
½ cup of the carrot water
1 cup pineapple juice (if there's not enough, top it off with more of the water from the carrots)
¼ cup brown sugar
1½ TBSP cornstarch
1/8 tsp ginger
food coloring (optional; a slight peach/orange tinge looks good; don't overdo it)
Mix the sugar, ginger, and cornstarch together, then stir into the liquids over medium heat, stirring until it bubbles and becomes translucent. Cool.
After making the sauce, slice up the onions, chop the dill, core and cut up the apples, and stir it all together, salting if desired. Serve cold, either drizzling the dressing over the salad or leaving it on the side for dipping.
Variation: Scandinavian Style:
Add 7 fresh beets, boiling them with the carrots. Omit the pineapple and the chicken, and replace the above sauce with a mayo-based dressing. This still won't be authentic rosolli, but closer.
Chicken Veggie Salad
Yahoo: Content? What's that?
I'd like to put forward Yahoo! as my nomination for the Content? What's that? awards. 
(Click the screenshot to view a higher-resolution version.)
With my OS and browser chrome all clipped out of the screenshot, the page area comes to 1542x805, a total of some 1241310 pixels. Trying to be as generous as is anything like reasonable, I estimate the content area as roughly 678x39 = 26442 pixels for the search box area (Yahoo _is_ a major web search engine, so IMO this counts), something like 401x213+286x40+131x26 = about 100259 pixels for the TODAY article, plus a somewhat more arguable 500x170 = 85000 pixels for the news headlines (which could easily be considered intrasite links, but I'm trying to be magnanimous), a total of about 211701 pixels of content, roughly 17% of the total page area. For such a major site (Alexa rank: 4), this is an embarrassingly low number, IMO.
Cherry Cake
This is a variant I developed. There's a plum cake recipe that's been a favorite in my family for decades, and I've always wondered about using other fruits. I've been experimenting with peaches, but they're juicier and not as strong a flavor, so that recipe needs more adjustments before it's ready for general consumption. Update: I've since made progress on that.
But the cherry variant turned out great on the first try. In fact, I think I might like it better than the plum. Here's the recipe.
1 quart home-canned pitted pie cherries
1.5 cups sugar
3 eggs
1/4 cup oil
1/2 cup milk
1 tsp vanilla
1 tsp almond extract
2.5 cups flour
1 tsp soda
1 tsp cinnamon
For the glaze:
juice from the cherries
1/2 cup sugar
2 TBSP cornstarch
Drain the cherries, reserving the juice for the glaze. Run the cherries through the blender long enough that you can't tell where one cherry leaves off and the next starts.
In a mixing bowl, combine cherries, sugar, and eggs. Beat until foamy, then mix in the oil, milk, vanilla, and extract.
Stir the dry ingredients together then mix them into the wet mixture. Pour into a (greased and floured) Bundt or angelfood cake pan. Bake at 350F for 50-60 minutes. Cool for about ten minutes, then invert onto a plate. Spoon the glaze over the top while both are still hot.
To make the glaze, combine the juice, sugar, and cornstarch in a saucepan. Boil gently, stirring, until translucent.
Beginning to Understand
I think I may be beginning to understand the Japanese writing system. This worries me, because it's not the sort of thing you really expect to understand. Ever.
There's a bit of necessary background information: I have a Spaced Repetition System, that I use for memorizing vocabulary and stuff. I've had it for, oh, about a year now I guess.
The SRS is cool because it makes review automatic. How it works is, for every active card it tracks two things: when is it due to be looked at next (due date/time), and how long is that since the previous time (repetition interval). When you get a card right without any trouble and click the "Correct" button (after showing the answer to check yourself), it increases the interval geometrically and requeues the card based on the new interval. If you have trouble remembering but do get it, you can click "Difficult", and the interval stays about the same. If you don't quite get it, but almost, "Close" will shorten the interval a bit, and if you just plum forgot or missed outright, there's a button that will cut the interval down to a fraction of its former value. There's also an "Easy" button that increases the interval by a couple orders of magnitude. Anyway, the normal state of affairs, once you get your multipliers tweaked to match your personal learning rate, is that *most* of the time you remember the card and click the "Correct" button, with the result that the interval climbs from minutes to hours within the first couple of days, then from days to weeks, and it just keeps climbing from there. The better you know a card, the longer you can go and still know it.
New cards are introduced as necessary based on how far apart your active cards are spaced. You can also dequeue a new active card any time you want, if you just feel you're ready for a new one, and there's a review-only mode that never gives you any new ones. But usually I just let it give me new ones when it thinks I'm ready. Cards that aren't active yet have a "cue number" that controls the order in which they are introduced.
I've got a number of different kinds of things in the SRS: English words, Hebrew words, Japanese characters and words, Bible verses, geography, US Constitutional amendments, whatever I want to memorize that breaks up into bite-sized pieces. I spend roughly half an hour a day using it, broken up into 5-10 minute segments here and there.
So here's the story: months and months ago, I put the word 七曜表 into my SRS. Since I didn't yet know two of the three characters used to write it, I gave it a cue number higher than either of them. At the time I was putting in a bunch of words just so there'd be something there to dequeue whenever I needed it. I then promptly forgot about the word until it came up.
You also need to know that in the Japanese writing system, each character has multiple possible "readings" (pronunciations). There are also a couple of different major *kinds* of readings, "on" readings and "kun" readings being the important ones for most purposes. In my SRS, I always list on readings before kun readings, and they show up in a different color, so *hopefully* I'm getting at least a general sense of which is which. In my SRS I list the readings in kana (the portion of the Japanese writing system that's strictly phonetic in nature, which makes it perfect for pronunciation guides). Here, however, I shall attempt to render these pronunciations in a manner that will make sense for English speakers, on the theory that some of the people reading this might not know kana.
So anyway, as of a couple of days ago I've now reached the point where I've studied all three of the characters used to write this word. 七 can be pronounced either "she-chee" or "na-na" and means seven. 曜 is "yo" (with the o held for two beats; a rare character with only one major reading) and its basic meaning is day, as in day of the week. The third character, 表, is one that I only started studying a couple of days ago and am still reviewing multiple times per day. It has three major readings. The first one is unspellable in English; the traditional transliteration would be "hyo", but you're going to want to make that two syllables, and it's only one: the "hy" is a blend. (The y sound is pretty much the *only* blend-forming phoneme in the Japanese language. They don't really have l or r, and they don't form blends with s or z or w.) Oh, and the "o" is held for two beats. The character can also be read "oh-moe-tay" or "ah-dah-wah-sue". (That "d" is not exactly a normal d. It's a lateral alveolar flap consonant, often transliterated as "r". It sounds sort of like "l", only different. It's closer to d than r. If you know Spanish, it's said to be more like a Spanish r than it is like an English r.) This character carries the idea of displaying or showing or expressing something or making an annotation the concept of a surface or table. (Oops, got it mixed up with another character I'm still learning.)
So the card comes up, and I look at it, and I guess based on its structure that I should be using the on readings, so I come up with "she-chee-yo-hyo" (with each o held for two beats) as my best-guess pronunciation. Then I think about the meaning. Seven-day display? Showing seven days? What, a calendar or something?
And then I clicked the "show answer" button, and... wow. Both my pronunciation guess and my meaning guess were dead-on. That's... weird. Normally when a new card is first dequeued, I expect to get it at least partly wrong the first three or four times I see it, until I finally start getting it pounded into my thick skull. But this one... well, it just sort of made sense.
And that's a major milestone. Because when I first started studying the Japanese writing system, I did not think any part of it (well, other than the kana) would ever make any sense.
Zeke
Someone asked to see a photo of Zeke (my mom's dog), so I'm posting up this one, which was taken a couple of months ago, when he was about a year old. The photo was taken by my sister.
A Screenshot for the UI Hall of Shame
Okay, I'm a reasonably intelligent guy, so I was able to figure out what I need to do, but one could be excused, upon a straightforward reading of these messages, from concluding that the goal is impossible to reach due to conflicting requirements. I can't install AD until after I run adprep, but I can't run adprep until after AD is installed (which is what will make this computer a domain controller). What? Gah.
Now working on a serif font design.
Actually, perhaps serif
is an inadequate term for this level of decoration.
Anyway, I was playing with design ideas for a serif typeface, and after a few rounds of messing around, this is where I landed for the first glyph, a lowercase a.
Update: After doing the next couple of characters, I realized that the a is too tall: I inadvertently designed it to the cap height. That probably means that the character would need to be redesigned if I decide to go ahead and finish the font.
Thoughts? Is this worth turning into an entire typeface?