On the Other Hand… Good Stuff

While I was typing yesterdayʼs whining post about software intrusions hindering my efforts to actually use the computer, I was also eating my lunch. In yesterdayʼs case (actually right now, as I begin this new entry, intending it to auto-post itself tomorrow/today), I was consuming leftovers (a not uncommon practice, alternating with a Romaine salad). Yesterdayʼs deliciosity remained from New Yearʼs Eve* when The Lovely One made one of my favorite dinners (probably my most favorite and the subject of todayʼs post) — her own particular recipe (somewhat modified as time has passed) for Beef Stroganoff.**

Iʼll be kind and post the recipe (almost) right up front.

Janetʼs Outstanding Beef Stroganoff

Ingredients
  • 1 Tablespoon flour
  • 2 teaspoons salt
  • 1 pound beef sirloin (cut into quarter-inch strips — bite sized)
  • 2 Tablespoons butter
  • 1 can sliced mushrooms (I recommend 2 cans)
  • ½ cup onion (half an onion, chopped)
  • 1 clove garlic, minced (or 2 or 3)
  • 2 Tablespoons butter (or margarine)
  • 3 Tablespoons flour
  • 1 Tablespoon tomato paste
  • 1 ¼ cup beef stock or 10 ½ ounces concentrated beef broth
  • 1 cup dairy sour cream (we, of course, use fat-free)
  • 2 Tablespoons dry sherry (My Beloved has started using any dry white wine)
  • 6 ounces noodles (a couple cups of brown or brown-and-wild rice is better)
Procedure
The actual (ancient and much abused — therefore difficult to read) recipe card from My Belovedʼs recipe files

The actual (ancient and much abused — therefore difficult to read) recipe card from My Belovedʼs recipe files

Combine 1 T flour and salt. Coat meat with flour-and-salt mixture, then melt butter in a large skillet. When butter is liquified, add meat and brown quickly on both sides. Add mushrooms, onion and garlic. Cook 3 or 4 minutes or until onions are crisply tender. Remove meat and mushrooms, using a slotted spoon.

Then add 2 T butter to pan drippings and blend in 3 T of flour. Stir tomato paste in rapidly. Stir in cold stock/broth. Cook over medium high heat until thickened and bubbly.

Return meat and mushrooms to skillet. Stir in sour cream and wine. Cook slowly until heated through. Do not boil.

Serve over noodles (cooked, of course) or, better, brown and wild rice. [total prep time = 30-40 minutes, tops]

Lately, after our (for which read: “The Lovely Oneʼs”) tongueʼs awakening to the joys of paprika during the 2011 trip to Budapest, we spice with garlic (more than suggested above), pepper (just bought some Tellicherry black peppercorns, which we ground into the sauce) and both hot and sweet paprika. The paprika is a definite must — makes the dish wonderfully better, richer in taste, slightly more exotic. Sometimes (I donʼt recall right now what we did New Yearʼs Eve) we also add garlic powder and onion powder.

We usually have this dish only once or twice a year, almost invariably in the colder seasons. But it really is wonderful. More than well worth a try.

* Ah, with reference to yesterdayʼs justifiable criticism, the computer permitted itself to ignore the “v” I typed between the capital and lower case “e,” thus not creating “Eve.”

** And I deliberately made beef stroganoff (both above and here) a link so you could check out other, lesser recipes for this wonderful meal.

©2013 John Randolph Burrow, Magickal Monkey Enterprises, Ltd, S.A.

Effing Mountain Lion

FML. My computer cannot keep up with my typing (and although I type relatively quickly, I do not type really, really fast, so anyone would believe that a modern — no, not contemporary, but still modern — computer could keep up with my only-human typing speed; that supposition would be wrong). So what is the problem?

The infamous chiclet-keyboard (with the inimitable Gwen Hernandezʼs incredibly useful Scrivener for Dummies right there, close to hand when needed.

The infamous chiclet-keyboard (with the inimitable Gwen Hernandezʼs incredibly useful Scrivener for Dummies right there, where it always resides, close to hand when needed).

Well, up front I should admit that I donʼt lways hit every key precisely (particularly on this damnable chiclet Bluetooth keyboard*). For example, that missing “a” in the previous sentenceʼs “always” is probably not the fault of the computer but of this user (of course, the spelling-correction feature is underlining the defective “lways” — both above and in this parenthetical insertion, but I intend to post this initial message for 2013 just as my computer — and I — create[s] it, more or less**; likewise, if I adntʼ mad Typinator change m regular mistyped “setnence” to sentence, that ould have remained wrong as well). I also, as suggested already, have a horrible tendency toward typos — dyslexic fingering that creates jumbled words with letters misordered, some of which I have programmed to get corrected*** (as noted above), some not. Both kinds, however, stir up Mountain Lionʼs intrusive correction suggester (putting up a blue suggestion of what I presumably was supposed to mean to type below the active word onscreen), which although helpful once in a blue moon, usually serves merely to slow down the computerʼs response to the continuation of my typing (which I guess could be resolved, at least somewhat, if I watched the screen and not my fingers/keyboard — as if that will happen at this very late stage in my typing life). Thus, third, I should acknowledge that I myself have created many intrusions into the ordinary typing process, some (if nch) my help to slow down th computerʼs acceptance and display of my maladroit dgitsʼ dance across the excruciatingly tiny keys.****

So some of my curet problems must be ascribed simply to me. (That boldfaced bit of idiocy is an automatic correction, believe it or not, for current!)

I missed BehavioralInjector_64 using 83.3 percent of the RAM by less than a second before the screencapture camera clicked. Drat.

I missed BehavioralInjector_64 using 83.3 percent of the RAM by less than a second before the screencapture camera clicked. Drat.

On the other hand, and that other mitt is the thrust of todayʼs post, none of this was a problem before I “upgraded,” witlessly, moronically, to Appleʼs system 10.8.2, the savagely unready-to-be-released Mountain Lion. (I know I have moaned about this Windoze-like***** set of programming incompetence already, but… ) I have begun to discover that the problem seems to reside with the vast number of processes that think whatever unimportant background activity (like updating Spotlight or too-frequently backing up to Time Machine or whatever mds and mdworker, among too many other gnomically-named bits of coded nuisance, keep attempting to do behind my back, without my permission) is more important than the actual task at which I am genuinely at work (meaning that my typing or program-opening or whatever comes a distant third to whatever other disk-grinding busy-nesses are happening about which I do not care). And I am not the only one.

Some of the worst offenders are processes from programs I have installed (namely Syncoveryʼs totalitarian backup agent and Intego VirusBarrierʼs horrible BehavioralInjector — whether underscore32 or _64, the former being the more dictatorial and domineering). However, using Activity Monitor, I can quit those processes (usually — sometimes it takes ten or fifty quits to get BehavioralInjector to stay absent/inactive). Appleʼs own intrusions are not so user-friendly. Furthermore, that aforementioned spinning beachball has really gotten irritatingly omnipresent!

And that, my friends, is why I keep not getting much done. (Amusingly — and I intend that word literally, etymologophiles — these processes donʼt interfere with getting online. Much — see beachball reference above.)

Maybe now, with as few issues in the most recent paragraphs as there were, I can get back to work on important fiction (really).

* Really, Apple? You couldntʼ make a real keyboard that connects wirelessly? Really…

** The less being that whatever I noticed was wrong when I finished, I boldfaced. (And I wonʼt comment on what I may know were my own issues and what the fornication-worthless software/hardware permitted to be wrong.)

*** Another standard correction, which the computer currently finds nearly impossible to handle adequately is the transformation of straight apostrophes to curly typographerʼs apostrophes (and since I cannot get PopChar to function today — more computer trauma, I guess — I canʼt show a straight one). What happens is: all too often the apostrophe gets inserted after the final s in a possessive (I am coming to think because of the ridiculously slow and intrusive correction-suggester); several examples have occurred in todayʼs post.

**** That would translate as: “some (if not each) may help to slow down the computerʼs…” (Hmmm… you can tell that these footnotish interjections were created down here as I wrote because with these, too, the number of errors decreases with time. Interesting?)

***** Shall we enumerate every Microsoft Windows nonimprovement since XP (and most before)?

Did anyone get the punning initial acronym? Apple… ? (Itʼs not my life that I was addressing.)

©2013 John Randolph Burrow, Magickal Monkey Enterprises, Ltd, S.A.