Defensive consistency as dissection of a live frog

I spent some time this weekend further clarifying the Waterken Server
code, trying to make it more easily audited. As I was pulling things
apart and reworking the layout, it occurred to me that the exercise
was similar in ways to the high school biology exercise of dissecting
a frog, but where you have to somehow keep the frog's heart beating.
Like with the frog, the goal is to lay things out so as to be readily
viewed and understood, but you don't have the luxury of omitting
complexity necessary to the living frog, or application. Quite often
it seems you end up pulling up on one bit and twisting it around to
see if there are any feasible cross-section views.

Anyways, I got a little chuckle out of the analogy and thought others might too.

--Tyler

-- 
The web-calculus is the union of REST and capability-based security:
http://www.waterken.com/dev/Web/

Name your trusted sites to distinguish them from phishing sites.
https://addons.mozilla.org/firefox/957/