Now Loose Those Beasts

I have an itch to look at a piece of some old code (to generate browser forms from entity and ui metadata retrieved from the server).  Without further ado:

createMetaform - Copy

I think there is an essential lesson about asynchronicity in the form of this function. Notice how it flows top to bottom then back up and in. It ends somewhere near the center. In fact, the beasts are loosed right around the golden ratio, if mine eyes do not deceive me.  Notice the sort of unconscious inward mirroring between myth and code. Like as in how the function “nowLooseTheBeasts” takes the retrieved entity, loads it into the generated form, and then injects that into the DOM (the anatomy of that which the user can see) and then updates the UI container (IOW, the present-moment skin of the DOM’s underlying anatomy).

I might say a lot, for there is a lot to say, not only about the code pictured above, but the code in which that code is embedded.  Or again, like my first published draft of this post, I may say very little.

That’s like two attitudes toward code (to say nothing of programming): 1) Condense code like distilling a mathematical equation; 2) Dense code is hard to evolve, rather, use (occasionally) verbose design patterns to create code that is broken apart, light and airy, and easy to rearrange.  (Uh oh, looks like I’ll be saying a lot, since none of this has anything to do with the condensed meaning I first typed out… [but if I say a lot using dense meanings… {you’ll have to keep the resonances humming on your own <I can’t do all the work for you through this flat text |you’ll have to breathe life into the pattern herein distilled>}])  I tend, rather, to practice a mixture of the two.  The code pictured above radiates one face of my meaning.  These words another: mathematical equations obfuscate meaning in one way (symbols, like λεπ, that generalize toward total abstraction) while clarifying it in others (revealing underlying structure via the absence of noise unrelated to that structure).  A third: meaning could be thought of as the field generated by the “flow of consciousness” through an alternation between symbolic equations and concrete substitutions (concrete, in this case, in the form of present perception & past memory).

(I just noticed an interesting thing about my language.  What I interject in parenthesis throughout the sentence is the very material normal writers use to construct their next sentence (or is the material they wisely edited out in the interests of the reader [sorry! {I just don’t know any other way to be authentic.  You see, it’s just what I’m talking about in this blog post, two approaches combined <mysterium coniunctionis?>.  |is the question greater than the period? Yes _I’m going to get off track with all these parantheticals_.|  I’m trying to communicate an insight that consciousness is asynchronous.  And how it is so.  How we have consciousness and then we have everything else.  We naively refer to the “everything else” as if it were a single, unified thing.  The Unconscious.  The Right Brain.  Or whatever other moniker you know it by.  God, maybeven?  But what we really have is a  bounded “self” {bounded by some self-defined body}, some identity, some self-referential field, that creates of itself one “processor thread” {this is a language equation, in a math equation that quoted word may be lambda or epsilon or pi}.  Then it tries to understand “its unconscious” as another single processor thread.  In reality, self-identity necessarily founds all representations of non-self-identities in the non-self itself, which it understands only in the one way: not what I am now; which it understands in only one way: what I am now.  Which means we have a seesawing.  Can you see it sawing away like scissors through too much paper?]).  I wonder if this means our paragraphs diverge in purport?  Perhaps it is a shortening of the distance between meaning?  If so, perhaps one could travel through the noosphere at a faster rate thereby?  One could certainly travel inwards, from top to bottom then back up and in).

All that is to spell out: when you let the mind generate meaning in its own natural, asynchronous way you just may find unexpected resonances as exoteric purposes reveal inner purposes that harmonize with outer purposes esoterically.

Note on the code: To be precise, this is essentially the constructor function (initializer) of the “Metaform” object.  The Metaform exists to construct and manage the lifecycle of a user input form (like a purchase order)  generated by logic that takes in entity metadata (property names, value types, relational attributes, ui actions) and a view outline  (user interface domain specific language) and a view model (entity data to be placed into the UI shell generated by combining the entity metadata with the view outline) (although, sadly, to the careful eye, the code will be seen to not adhere to this [what is effectively an] ideal description in subtle ways that are the result of the code body’s growth in the context of an existing code base).  The embedded functional nature exists for one reason and because of one reason.  It exists for the reason of creating seams along a single of path of logic.  These seams are necessary because the single path of logic has steps that require getting data from the server.  In the browser, in javascript, this is achieved through AJAX; in my case, jQuery.get().  jQuery.get() can be used synchronously (by settings async: false and using the return value of the function call) but this is against the grain in javascript, and in fact, vastly slows down the UI (circa 2012).  For instance, during the time it takes (in this case) to generate a form, if the user wishes to somehow otherwise interact with the UI (such as in selecting a different order to view since the first click was in error and the one below it was meant [these sorts of corrections happen in terms of a fraction of a second]), the user will find the UI unresponsive, jerky, rude.  The “proper” way is to use callbacks.  Callbacks allow the browser to update and respond to UI events while the logical steps wait for server data, which, when it gets returned, is passed on to the callback function to continue stepping through the logic.

Callbacks essentially start to look like the code pictured above and can go to any level of depth, like Shai Hulud through the Dunes of Arrakis.  In fact, callbacks, time travel, wave forms and prophecy are probably all related (by way of some audaciously essential subtlety that worms its way throughout [ie: recursion, reflection, reflexivity, autopoiesis, knowledge, mercuri[o]us, Prometheus, treu {ooze ta say the Dao ain’t sum alien’z Way?  De’briz uv ‘is passin’ ticklin’ da leevz uv’wareness?}]).

Arrakis, among other things, represents Frank Herbert’s understanding of a pattern of reality in which large interconnected systems (organisms, empires, species)  attain a time embedded structural dynamic that tunnels the effect of local events outwards into the wider system, giving disproportionate global effect to local actions and disproportionate global action unto local effect.  Too with time.  You can imagine this “time embedded structural dynamic” to be a whirlpool of events with a boundary that bends and tunnels through space and time like a worm of karma through the events of history.  Except history is a desert through which many such worms wend their way.

Are you keeping up wit’his semantic DJ tap dancing language ‘cross your visual field?  Wondering whether or no to attract a worm to ride  or just keep wormstepping the susurrus of the night.

One thought on “Now Loose Those Beasts

  1. […] call it: Neural Closures.  It’s my design pattern for the day (very like the code pattern in Now Loose Those Beasts, except in that case each step was dependent on the one previous to it before the “beasts […]

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s