an odd post

A few of you might recall I have other blogs.  This is not that unusual, I know a number of you also find the urge to run more than one blog. Sometimes it makes sense.

One of my other blogs is I Can't Blog. True to its name there are only 22 posts on it and it started back in 2010. It doesn't see much daylight. Maybe I should take it out for a linky game/meme someday.

Anyway I recently posted on it and decided I would do my own "guest" post over here.

Direct from where the font never dries and seldom a comment is written:

now what

The car doesn't start. The clicking chatter from under the hood sounds bad.  Damn it's always something.

More of these "somethings" when you have less of "nothings".

Recursive complaining. Complain and then complain about the feeling of complaining. Your own feedback sucking you into a downward spiral.  Pull out before you crash.

Back in a former life, I made a living coding embedded software. Recursion was a useful but tricky approach to creating applications. You had be cautious of infinite loops.

A system stuck in an infinite might never come back and in some cases could destroy itself (I believe a few windows computers died that way). Intervention by an outside observer/user hitting the power reset was needed.

To keep the software from getting too loopy in it's thinking a hardware watchdog would typically be included in the design. The watchdog needed to be feed (sent a valid signal) within a preset time frame or it would shut down the software. This approach allowed the software to ignore the aid of the watchdog by inserting a feeding within it's loopy routines. In other words ignoring the help of others. I'm fine, I told you. Now go away.

Couldn't everyone benefit from a personal watchdog?

BTW, I was reviewing recursion on wikipedia and discovered that Google included a little "Easter egg" surprise on their search page related to recursion. If you search on main search page for recursion it ask you "Did you mean: recursion." It never ends, does it?