Pick-Up | What's Next

Team. We might pick up on the other related projects on this web-history or start some new streams.

Our next project might be the original vision for an open-vm on the JAVA platform, whose label might confuse you. It baffled those who took up the project at Oracle. It is not so much an "open-source" project. It is more so and opening of a platform's application programming interface (API), its packages and libraries, for use by a simple, yet expressive, set of imperatives. This "universal-set" of imperatives would also be applicable on other platform for which an open-vm has been developed.
An open-vm is this, an interpretive architecture that accepts commands such a construct, behave, assign, those for control flow, and etc. plus uses dynamic invocation for accessing the actions available in an API. The CABOOSE product is near what we need for doing such. Remember the Number Theory of Computing. The "number" the describes CABOOSE is near that for an open-vm in JAVA. The development project will start with a "Hello, OPEN-VM" program, once again and evolve. The final product hopefully will be another DIY-Text on the construction of the open-vm pattern.

Enjoy Your Weekend...Keep Coding...Hunt...Peck...Think....

CABOOSE in JAVA by Abraham Vati James [penname]

Team. A do-it-yourself CABOOSE text is available on Amazon. It is a synopsis of the content in this web history, plus a few extra modules. It can be purchased here for 10.00 (US$).

This has been a fun project, in the midst of life's ups and downs. We will be working on some more related projects soon.

A Couple of Birds | One Stone - Epilogue

Team. The primary goal of this web history was outlining and starting an open-source project for a general-purpose controller architecture that could serve as a servlet, web-script, or common gateway process for rapid web application development, when using a type-II model-view-controller architecture. This was done after contacting Oracle's Project Management Office, as part of the JAVA Community Process (JCP), about getting mentorship as a specification lead on JAVA Specification Request (JSR) for such a product. The potential for such a component was discussed at JCP executive committee meeting in early 2014 and the feedback given was that JAVA Server Pages and JAVA Server Faces existed for simplifying servlet construction and this product was not immediately necessary. Yet, Ben Evan, a well-known JAVA champion, suggested that the author of this weblog try starting an open-source project, if it gets a following, Oracle might incorporate a general-purpose servlet in its offerings. In the meantime, they polled the developer community and started an MVC framework offering called Ozark, which has a locomotive engine for its logo.

With concerns about making a quality "well-exercised" JAVA archive for delivery with personal time constraints and realizing that many software developers, including neophytes, are not aware of their potential for developing "impactful" products, the author decided that he would collect some of the more meaning exerts from the history, edit them, and compile a CABOOSE do-it-yourself (DIY) text. This delivers the software, in a form that is as reliable and robust as the reader of the text implements it, plus the promised textbook. The book mentions Ozark, but does not include any of the passages from this web history that provide and example of integrating a CABOOSE-controller with it. 

The textbook much like the weblog, starts with a "Hello-type" sample program, and evolves it until in eight steps until we have a general-purpose web-controller in the form of an JAVA Enterprise Edition http-servlet.

The work is in the process of publishing and should be available on Amazon by August 15, 2018, written under the pen-name Abraham Vati James. If one reads the "appendix", An Unspoken, Unknown, and Uncommon History, one might discern why this name was chosen, with Abraham recorded as the father of nations, "Vati" translating as "father" and "equity" in a pair of Indo-European tongues, and "James Gosling", known as the originator of the first JAVA virtual machine.
The "appendix" might be discounted as "hogwash","poppycock", and "taradiddle", but read it carefully. The goal of it is not jumping any claims, patents or copyrights; it is first a thank you for "I AM THAT I AM" and His rich Mercy and Goodness that has followed the author through many difficult situations, second the fond thanks for the inspiration for producing a sketch of a few "award-winning" idea generated by the author's JAVA muse, a high-school sweet whose favorite movie line and gender neutral name produce the caricature Duke (of Earl), which is his title, and his little known first name, and finally, it is the an expression of the well-known fact, "truth is stranger than fiction".

The text can likely be found on Amazon, in a few days, with a search for "Abraham Vati James", which is a rather unique name. It cost less than most professional engineers spend of lunch at their favorite sandwich shop. It might be work a read.

This web history might be reaching an end of it journey; with a new adventure waiting around the bend where we can pick-up and focus on some of the concepts mentioned briefly herein and not included in the CABOOSE in JAVA by Abraham Vati James text.

Potential Future Goals:

• We still must flesh out CABOOSE in the open-sourced LAMP and the proprietary Microsoft .NET CLI languages.
• We must get a grasp on the Distinct Number Algorithm (DNA) Storage and the (CODECO) Compression and Decompression.
• We have some key work that we must do on the Open VM.
• We still must produce the "boostin" Houston Server as promised, which is a node-based kernel for grid processing, likely more practical and effective than HADOOP has been or will be. 
• We must draft a system artifact trace-ability plan that was part of our early efforts with CABOOSE.
• Also, we must examine how this procedure described early in this web history called the Miller-Kovarik Secondary Method might improve solutions for optimization problems in electronic computing and mathematics. This includes areas such as operations research and artificial intelligence.
• We must draft a practical, extensible crestomathy, rosetta stone index for modern computing, based upon its primitive operations such as writing on standard output and standard error, reading on standard input, file, database, and networking operations, plus many of the elementary data transformation that can occur in a program, when modeled, in terms of Ps and Qs, pre-conditions and post-conditions, plus Ts, transformation-filters.
• And, much, much, more... 

The author will point you in the direction of any new weblog work when it arises....

Hunt...Peck...Think....Keep an Eye Out for Flying Rocks....Do Worry....Be Happy....

On Steep Compression.

Team. We have spoken in the past on this "CABOOSE plus computing idea" weblog about a simple data compression and decompression methodology called DNA ( Distinct Number Algorithm ) Storage. A letter was written the NSF strongly suggesting that they stop wasting money on researching storage techniques using deoxyribonucleic acid and adopt this simpler approach.

While driving this day, a more practical notion of annotating a file with stop symbols for decompression occurred. The file itself is a maker with unique patterns in it. One might take samples of a given size from random parts of a file.

If one had a megabyte that he were compressing, he could sample sixty-four eight byte span and store them. This would be half a kilobyte of information for uniquely identifying the decompressed image. If the compressed image, plus any metadata composed another half kilobyte, the final descriptor for the megabyte would consume a kilobyte.

If this megabyte were the fortieth one in a gigabyte, the kilobyte descriptor would be the fortieth in a compressed description of the gigabyte. Whose final size would be a megabyte. Then, this megabyte, an image of a gigabyte, could be made a kilobyte. The process becomes recursive. So, a reasonable challenge problem for a college computing class would be producing an algorithm, based on the intuition of DNA Storage, that placed a megabyte in a kilobyte. One would imagine that the "top-notch" engineers at Google could draft such a routine in an afternoon.

Weeks from the Presses. CABOOSE is here.

Team. Life became hectic last summer (2017) around this time 07.27.2017. Unhappy with management at Team Software's sister company, a resignation letter was given at this position, the primary one, and a secondary position was placed in a permanent state of limbo on the same day. Living life on financial roller-skates, instead of thick heels, that Maslow's triangle slowly eroded. Employment was found again this Spring and work on CABOOSE resumed. It has evolved. The prototype source and the JAVA archive will remain on-line. Those will be collected and placed in one convenient place. And, a link for a DIY CABOOSE text based on a synopsis of this web-history will be placed on-line. The goal is by mid-August, if work allows. It has been five plus twelve hours days each week.

Also, please forgive the web entry Apologetics Mine. It along with others has been permanently scrubbed. Some rather troubling experiences occurred at VUMC in September 1988, a potential cover for the death of a student-athlete in 1987 plus a medical assault. Plus, the way in which modern medicine has handled the situation is reprehensible. Although Earth, Wind, and Fire's song September is soul-stirring. It is a time of subconscious tension. It shall not be mentioned again in this web history.

Oh, by the way a confusion does marvels for erasing the memory. The pass-codes for this weblog were forgotten. It was unlocked after finding a single item, by chance, that held a security code for a web-host with a recovery e-mail. The point is, take is slowly at work and keep confusion at a minimum. It is costly for everyone.

On the Topic of Value; and Wise Management.

Rush. Rush. Rush. The birth place of the modern information age is the location of the old Gold Rush. Winding roads placed hastily as communities boomed and busted! The rush for wealth mostly likely cost men their lives; and, others simply left a region where they had sufficient resources for surviving, possibly beyond more than they could expect or dream.

And, the modern computing rush. What does it cost? It cost a contract with services such as ConstantContact, or similar, when samples of valid instructions for doing such, exist on many developer and tutorial sites across the WWW.

Best of all, these cost are minimal. The only detractor is that any Integrated Development Environments connected with the Internet can be monitor, via histories of usage data transmitted,or the possible (unknown-unapproved) transfer of projects. This includes the commercial products which require a fee.

It simply takes the wisdom of searching for something outside one's standard domain of business vocabularies. Learning the few keywords for basic input, output, string processing, numerical computation, and the proper tools for installing, compiling, and evolving the simple utilities needed for performing the same "android-role", or automaton of business function, that might be "tandemish" in its "24/7" accumulation of data, marketing tasks, or other vital role, is, as simple as, taking that extra-hour or so, started at 5:00 AM for a couple of years, so your business or "profit-ability" will exceed that of the "average" one.

So, slowing some, or possibly enjoying an unplanned week or so, which concludes with a swift pivot in technical or work direction, might be more profitable than working at a break-neck pace, unless you are driven by a project manager who will  not permit more than a three minute, lavatory-respite.

Unfortunately, some are that way! And, the saddest fact about modern software engineering teams, certain affiliations permit the rapid career advance of such.

Here is an adaptation a Christian Proverb, "Bob", says the wise time manager, "You are scheduled for your yearly fourteen days, and have fourteen from last year, that are unused, plus five unused personal day." And, spoken in the tone of a "true" businessman, "I'll tell you what, take the next four weeks, and work in a full-Friday every month for the rest of the year; I will make sure that personnel only records the unused time from last year."

This adaptation is a unique one, in that, excessive workdays, with over-flowing dustbins, full of one's lunch and rest period snacks, plus a small case of colas for "alertness" are costly. The increased person-hours of billable time are rapidly diminished by work-quality, employee-absenteeism, and attrition, plus the related cost in hiring, training, and retaining new staff members in a nightmare called an engineering team. This is for the corporation; For the machines ratcheting left and right, striking this key and that, communicating on network portal, phone, wired and wireless, do not the deserve a rest cycle, an oil replacement, and a complete wash and detail. Look, we are not Kenworths, Peterbilts, Freightliners, Contenentals, Trailways, or Greyhounds! We are not that or the "rear-wheel" drive V-8 Fords, first generations Hondas or Toyotas, or any other passenger vehicle with a reputation of reaching 325K+ worth of mileage as a standard-lifetime of a "well-maintained" vehicle in those categories. Plus, the last thing this world needs is more lerts!

This is not a reference about any "specific" personal experience; yet, if metal degrades, will not the tender structures of flesh.

Cracked! Fissured! Leaking! Sinking! Sagging! Red-Roof Rusted!

Team. Does this sound like your favorite in-line four cylinder? You know the one which helped you pay for college, when gasoline reached it's peak in the early millennium. Or, for some of us, it was a struggle paying the $1.63 at the Amoco on the corner of the loop which the "townies" would Scoupe in an early 1990s Hyundai bumping some West Coast rapper, while we all wasted more time than pursuing that costly education which we all still likely undervalue.

Does this sound like those coffee cans you found in your Depression-era grandparent's attic behind a steamer chest, boxes of rations, and old newspapers? You know the ones which had the wheat pennies, buffalo nickels, and other silver coins, plus the bills: ones, five, tens, and twenties from the nineteen thirties, forties, and fifties, and, let us not forget the certificates of stock for a fledgling American Telephone and Telegraph, General Motors, Ford Motor Company, and, of course, Studebaker. You know the coffee cans that let you retire at twenty-one. Yeah, those swags.

Such is the nature of the very foundation of modern computing, It is the equivalent of a new roof-line on the top of a very old structure. A modern remodeling of a very old amphitheatre, one, in which many tragedies, comedies, dramas, plus skits: improvisational, experimental, and fondly-frenetic-frenzied-frantic, played out. Some in front of small intimate audiences, such as that given by a troupe of senior citizen's rendition of a Broadway classic, in the vein of those Grand Olde Players' community productions.

Others, such as the joint revelation of the aggregation of the infinitesimals, those infinitely small units within a space, of one of more dimensions, that produces a measure of the area under a curve or volume with a bounded region of a surface. That joint revelation accompanied the tangential grasp of curvature and its normal in perpendicular juxtaposition. Those incidental insights which left one of the inclination that either one or each of Newton and Liebnitz both absconded with an apple scone, a draught of tea, and a draft of some conceptualization or another, one likely as old as the sands of distant shores.

Dramatic enough. Over-blown. Can a frivolous flourish be added! Maybe, it might be accompanied by a silky "pocket-square" and embroidered, floral, paisley, regimental four-in-hand, half or full Windor, or natty, knotted bow, possibly one of Mo's.

Yea, a tenuous trumping of triteness upon tin tinseled trumpets! A clear clownish "cleek" of clarions! That "wordsmithed" high note that causes cat squalls! That is the nature of mathematics.

It is often clouded and cloaked, with so many Merlinish smokes, mists, mirrors, and thin fish-lines puppeteering the formal logical deductions, reductions, and simplification, that little of any meaningful value filters out which deducts, reduces, or simplifies the "over-weaning and overbearing" nature of the "spirit of intellectual egoism" plaguing "mathematics".

Is that a pompous paradoxical parody perfect per a presumed paradisaical plane of pondering called a pensive propositional philosophic perfectimum of Peano? Yeah, Porky sp..sp..sp..spit it out! That is all folks!

In short simplicity, mathematicians often confuse themselves. Shrouding simple concepts in strange notations and over-exacting vocabularies, those within the world of mathematics have on many occasions left themselves as confused as a freshman learning assembler during the earliest days of computing degree programs. That "froshmore", who revisited a "link-edited" programming assignment devoid of any comments during the doldrums of a drunken summer session and asked, "What purpose does the label "xajr" serves", he, was steeped in baffling befuddlement.

With this stream on meaningless vacuous statements presumed factual and supporting some "hand-waving" propositions and penetrative profound premises that common-sense obviates, one should say, "Yeah, sound like a typical proof in some math class or another. The one that caused swelling in your tear ducts." And, your instructor believed that you were moved by the depth and elegance of his didactic dialogue. Did someone say Tylenol 4 and might we use the door?

Truth being, as stated in the last web-post, computing is incredibly new. Those mind-expanding feats, which bewilder the majority of us in this age, are the most immediately apparent results in a fledgling field. This infuriates some who are amazed at Merlin's seeming levitation act in "pneumatic platform-boots", especially when explained by one of those "monkeys" for whom it is said that such will destroy the profitability of the industry, if it becomes possible that they might work among its "geniuses". Yet, it never crosses one mind that this definition of "Napier, Jacques" is an implicit description of all who are not "well-versed" in modern computing, albeit spoken by a characteristic group, whether spoken with a Francish flair or Southern slur.

And, it should be emphasized that the collection of fallen fruit, although gourd-sized, is not an phenomenal feat. It might require renting a crane for collecting the resulting haul, mostly financial, but it does not necessitate hiring NASA or Space X so one might snag the produce of the top of this tree of man's knowledge.

But, the primary concept and goal in this message of sandwiched ideas is that the very foundation of modern computational theories that support electronic computing, the eons of mathematical thought, some lost in antiquity and clay pots buried in numerous region this world that have been raided in attempts at erasing many countries histories and legacies, is flawed and fallible. It needs a complete re-engineering run, with a mixture of greenfield insights. Yet, modern egos, economic liabilities, the "unwise" exaltation of men of this and past eras, sensibilities is the spirit of haughty misplaced malapropisms such as, "rationalism hath destroyed more economies and wrought unchecked campaigns of genocide that halteth naught with the dawn of a new millennium!", these in the most unending and unwieldy of fragment phraseology stay the horse-sense that says, "review of past landscapes is prudent in the avoidance of future pitfalls" Dem gators bight!

Pardon the "aquamarine" colloquialism, Dora! Ain't a 'thang' wrong with a swamming swim, onceth and a while!


When one builds on a foundation of sand, one cannot expect that the structure will stand the test of eternity. With such said, placing an organization's long-term future stability and growth on such would be unwise. It does not matter how well-packed the sand might be. It can shift! In fact, it will liquefy with a sufficient influx of groundwater. So, we shall compute electronic internationale; Lord willing and the creek does not rise! Pardon the "gatorism" from an American peninsula.