That Place

Summer broke on the backs of children,
even though swings performed miracles
and breezes sang psalms.

For that summer, from the outskirts
of some far off even whimsical place
came the low resolute moo of a dragon.

A child, of course, could not recognize that fabled moo
or the serpentine tail close to her feet,
wound up among the thistle and milkweed
like a hose.

Nor for that matter could she recognize
the starry white bone left upright in the sandbox
like some remarkable claw
or shovel.

Not when the sun was out and games continued.
Certainly not when there was summer love
and rootbeer.

But at dusk when the fog crept in,
thick and sweating,
suggesting some kind of burning far off,
down over there,

(where someone once saw two eyes

– pale as October moons –


a child could know the meaning
of fall.

And that August, two weeks before school began,
some children went down to that place

and they never came back.

— Mark Z. Danielewski (from “House of Leaves”)

Kershaw Blur; Crazy Clearance Prices!

Kershaw Blur; Crazy Clearance Prices!

Kershaw has recently upgraded their popular (and excellent) Blur line of knives to use the newer, and also popular, S30V steel blades.

The upgrade leaves a lot of older stock floating around though, and Amazon is selling the older silver, plain-edge versions for only $31! 

Sometimes when you order knives from Amazon, you don’t get the exact version described. In this case, you DO get to chose the blade style and color (I wish ALL their knife sales had that option).  

You don’t get to choose the exact steel though, so it’s a bit of a crap-shoot. At different points in time, Kershaw has made the Blur in 440A, 420HC, Sandvik 13C26N, and Sandvik 14C28N. 

Mine ended up being a 420HC version, but it really shouldn’t matter too much. All of those steels are solid mid-grade choices, and all are plenty good enough for an every day carry knife… especially one that only costs $31! 

Fail Loop

This gem is part of a code (C#) example that we got from a vendor recently. This exact same pattern appears multiple times in the example.

It stands out because it does manage to work correctly…

using (FileStream rdr = new FileStream(contentInfo.FullName, FileMode.Open, FileAccess.Read, FileShare.ReadWrite))
{                    {
    index = 1;
    while (true)
        long offset = (index - 1) * chunkSize;
        long remaining = contentInfo.Length - offset;
        if (remaining < 1) break; // Stop processing, at the end of the file

        // stuff that doesn't ever touch the index variable