Tuesday, April 21, 2015

Active Projects – Hardpan Technologies Workspace

• Compile a FreeBSD image for a BeagleBone Black single-board computer, then netboot a BeagleBone Black A6 to FreeBSD, from a FreeBSD Virtual Appliance, using Crochet, FreeBSD 10.1 VMDK, Virtualbox, Debian GNU/Linux (?) for the PXE services, and a Netgear wireless router with Ethernet hub. HP Laptop (UEFI) with Microsoft Windows 8 as host OS to the Virtualbox VMDK appliance. Toshiba laptop for USB boot to PXE service on Debian (?) or FreeBSD.

• Development of a fork of McCLIM, extending of the original CLIM model for human-computer interface design and implementation, independent of graphical or audible appliance interface or textual media

• Develop HPan Ex Libris services – JCR and CORBA; Bookshelves interface in CORBA; Notebooks interface in CORBA; editor interfaces and viewer interfaces, in human-computer interface (HCI) design, focusing on the Android Mobile platform and one or more desktop computing platforms.

• Develop an automotive crew information system onto Ex Libris, Android mobile,  and ELM interfaces onto OBD-II as interface for automotive sensor information,  corresponding to normative mechanical diagnostic methods,  automotive maintenance models,  and procedures in automotive repair. Additional focus about environmental characteristics of automotive/mechanical work environments and corresponding demands for physical and structural resilience of digital electronic systems

Politics? Nope, the author is not babysitting myths.

• Not getting lost in a vortex of prolific cryptocurrencies — keyword: Mathematics

• Bitcoin miner implementation in Common Lisp,  as primarily focusing on CMUCL-style VOPs as furthermore implemented in SBCL, furthermore referencing implementations and optimizations of ECDSA system elements in C and in specialized microcontroller elements as accessible via direct machine instructions (Intel,  ARM, and Nvidia instruction set architectures) (See also: Texas Instruments AM35xx Sitara MCU;  design documents for the CryptoCape peripheral to BeagleBone SBC platforms)

• Development and applications of an interface for SHA-256, RIPEMD-160, and other mathematical systems relevant to cryptographic computations, with optimizations for features of the BeagleBone Black platform,  as extensible with the peripheral CryptoCape, and other machine architectures.

• Parallelization in applications of mathematical computations denoted in the previous outline elements.

• CORBA GIOP extended for serial communications,  project OLLIEOP

• CORBA GIOP extended for I²C, project OLLIEOP

• CORBA implementation in Common Lisp,  updating a fork of CLORB.

• Applications of the TPM element of the peripheral CryproCape, using the BeagleBone single board computer (SBC) within a FreeBSD
kernel and correlated operating system, focusing on PKI architecture, LDAP directories for principal identity, Keberos for principal authentication,  and OpenSSL as a feature of a TLS system applying X.509 certificates — focusing on the TPM's roles for trusted storage of cryptographic keys.

• Various things CORBA and BSD-style "Open"

• Formal Business Models

Hardpan Technologies and the Ex Libris Model – Bookshelf Concept and Service Architecture Design – Overview

Corresponding to development of the Hardpan Technologies web log ('blog), I would like to begin making some formal, public notes as with regards to a design not for a patent insomuch as it is a design for a bibliographical content management system. Today, I would wish to extend of that same design with a set of features for support of book sales – and that, without offending the sensitivities of libraries as institutions. So, a capital idea and a wave to the socialized state aside, the thing would focus on JCR and CORBA, firstly for data structures and personal content access, secondly for data services as may be provided on a heterogenous network medium of no too simple authenticity.
So, the initial server component would be implemented in Java, and the first service client toolkit may as well be implemented in Java, also. The server, in this design, would use ModeShape – nothing too specific in the data serialization layer, howrver. The server and the client would both use JacORB, and – ideally – the hosting operating system's Kerberos support, X.509 certificate model, and user interface.
It being implemented in Java, the first client application may not be available on iOS platforms. The intermediary IDL interfaces, however, could as well be implemented in C# for iOS platforms, and OS X platforms, and the desktop. Perhaps there's a port of Cocoatron for Android, too. The author is rather more immediately familiar with Java(r) toolchains, however, and the author does not have access to a normal XCode installation. So, initially, it will be implemented in the Java programming language, for Linux and FreeBSD servers and for Android mobile operating systems.
The author may or may not publish the Android app, at the Android app store. Initially, it will be installable for Android platforms, in application of the Android Studio IDE. "All smiles" for the newest innovations in development of the Gradle DSL for Android Studio applications, and the inevitable (?) Gradle-Ant and Gradle-Maven adapters, if one should wish to search around for such adaptive technology.
There's the architecture of it. It needs a name, too, and I have a name for it: Ex Libris, under the Hardpan label. Unique, huh? In that quality, it extends likewise of a design of a small model for access to, and user-unique creation and annotation of automotive notebooks in a user's own digital data model, in a manner ostensibly extensible for whole automotive crews, in applying CORBA, FreeBSD, Android, OBD-II libs, and the BeagleBone Black platform as a "Shop appliance" with a suitably stylish and functionally sturdy enclosure. No patent pending of this design, here licensed CC BY-SA 3.0.
Ex Libris, in its bookshelf features - no too long nod for BibTeX in Java.
Further design TBD.
Donate Bitcoins

Sunday, April 5, 2015

Towards a Model of Qualities of Physical Measurement of Historic Properties

Concerning the theme of project management that I've been developing, this week, here at my DSP42 tech web log ('blog), there's a type of project that I have been endeavoring to to avoid illustrating with any too convenient of manner of anything like neon signage. Simply, it is a project I'm developing in a manner of structural archaeology. Although, personally, I cannot aspire to convey any great amount of content about the broader discipline of archaeology, and even the single ebook that I have found, about the topic -- Clive Gamble's Archaeology: The Basics (2nd. edn. Routledge. 2007) -- that, in itself, does not address methods of field archaeology, but simply in turning my own internal steam engine about the project, I've managed to develop a handfull of concrete ideas, this evening.

One of the concerns that I face in endeavoring to not too clearly illustrate what is the object of this project, it's in that the project is not itself guarded by any single team of convenient morlocks. The facility is an older lumber mill, originally constructed to process pine conveyed from the Sierra Nevada mountains, constructed -- to my best estimate -- constructed, certainly, sometime in the early 1800's, and it is a family property moreover. My own grandfather was a sawyer at that mill.

As I have learned, to this day, the facility has been subjected to theft and vandalism, over the years. I do not want to see it subjected to any more of the like, if I would draw any attention to the facility whatsoever. In its present state, the  mill has a nondescript outward appearance, so it cannot now be easily spotted from passersby. Nonetheless, I would not want to hang a neon sign over it, online, Originally, it was a fully functioning, steam operated. manually fed lumber mill.

One of the concrete ideas that I've been able to develop, this evening, is towards a matter of measurements for the remnants of the facility. There is one profoundly notable remnant of the facility, namely the  centerpiece of the mill's original steam system, the original water reservoir. Once upon a time, I had made some photos of that object, for a photography course. This evening, considering some simple qualities of the physics of the item, I have arrived at an idea that there is a way to measure the item's exact dimensions, using at least two measuring implements: A laser-operated distance measurer, such as would be used in construction projects, and a vinyl measuring tape of a certain maximum measuring distance, such as I recall from track & field. Both items could be applied to measure the total dimensions of the item, to begin to construct at least a diagram of the mill's original construction.

Certainly, that item was not the only object of the mill's operation. Offhand, I remember a photo I had made of some of the piping there -- a motor would have existed, at some point in time, to make a fully functioning steam engine at the property, namely to drive the mill's original sawblade and other elements of the mill's physical system. There were also the chain feeds on which the felled trees were fed up to the saw blade. Separately, of course the felled trees would have been transported originally from the mountains -- whether all the way by a carriage, or by flue and carriage -- likely, down the original traces of the old road grade snaking up into the Sierras.

Personally, I have found an old book about the history of the region where this property is located. That book discusses many aspects of the old mills, and the old hydroelectric projects of the mountains, as well as some historically entertaining but nonetheless practical matters of the well-known old families of the area. Whereas that mill, itself, has existed for nearly two centuries now, I suppose I'm of an old family of the area, too -- though I don't expect we'll ever see a school or  road named after us, in all of our family's heritage of rustic engineering.

Insofar as that it is a project in a manner of structural archaeology, but I am not formally familiar with any sort of archaeological field methods, so of course I can only try to sort of find the shape of the hallway in the dark, so to speak, to the next grand idea -- or the next simple task, rather  -- for discovering when and how that facility was constructed, and by whom, and by what methods of construction. The concern about measurements -- that will aid that aspect of the project, substantially. Perhaps a museum of historic lumber mills may sometime be aided with this small effort, as well.

Insofar as that, personally, I am at least informally familiar with some aspects of formal ontology, that knowledge is proving to be of some use, too -- as that a time ontology, a persons and agencies ontology, and a geographical features ontology could all be of use in this project. Albeit, this being an ad hoc manner of archaeological project, I will not be scaling it up overnight to raise any sort of a linked data barn about it, but I think it does behoove an interest about linked data, insofar as archaeology, if not insofar as further manners of projects in investigations of histories, perhaps in journalism and in legal studies moreover.

At this time in my life, I am able to make an in-depth study of that aspect of the family's history. I am told that a stage coach once stopped by where that historic property is located. Though I myself may not have enough of a soft brush for geneaology -- and my own family tree is shaped quite like a broad grove, as I understand -- but the nature of structural archaeology, though I have not arrived to this concept until ostensibly my middle years, I think it is a compelling concept, even insofar as of the family's history.

An acquaintance had once inquired of whether I ever participate in archaeology digs. I had answered to the negative, at that time, but now I recall that -- in fact -- I have been on a dig, once. On the other side of my family, before there was a managed waste transport service, we used to dispose of items in a dump pit. I have seen some historic bottles, metal cans, and even a glass electrical insulator from the first archaeological dig I was ever set on about. That was of family history, though. We don't show off a lot, my family.

Towards a Definition of a Document System in CORBA

In beginning to develop a concept for a mobile application utilizing the automotive OBD-II/CAN protocol and an OBD-II interface such as the ScanTool 426101 OBDLink MX, the author has begun developing a corresponding concept of an automotive notebook, such that would be accessible via a CORBA service. Though it may be a concept somewhat less stylish than a concept of a networked car with a Bluetooth or WLAN OBD-II/CAN interface, it is the author's opinion that the concept of an automotive notebook is more the appropriate concept to develop, as the first essentially challenging feature of the design of the application.

The author is familiar with some concepts ascertainable of structured markup formats, including the stylish old adage that XML was defined for separating logic of document structure from style of document presentation. Contrasted to a document format such as HTML or LaTeX, those defining -- essentially -- both structure and presentation information, at least that old stylish adage made for a few convenient keynotes for authors assisting in the original popularization of XML. XML itself -- similar to HTML -- is accompanied with a formal Document Object Model (DOM), and is accompanied furthermore by a formal XML to IDL binding definition -- namely the XML Valuetype mapping -- such that would allow for developing an application interface onto an XML like document structure, via CORBA.

In defining an automotive notebook data type in CORBA IDL as a data type subsumed by notebook, and the notebook data type subsumed by document, the software design then may be implemented as it being orthogonal to a design for a CORBA-based document service.  The Document IDL interface, of course, would not be all that there would be to such a thing, though -- in itself -- it presents some particular design concerns, as to its implementation.

Offhand, the author knows of at least a few variably "Mobile-friendly", variably "Editable" document formats, such that masy occur to mind as with regards to how a CORBA-based document service may be defined, viz a viz

  • EPUB Book
  • ODF Document Package
  • DocBook Article
In the author's opinion, the last one of those three presents the most appealing alternative.

Albeit, DocBook does not -- in itself -- define a document container format, such as may be applied for purpose of streams-oriented document storage and streams-oriented document distribution -- namely, in as any single document being stored as a single filesystem object including text, graphics, tables, charts, and so on. In the author's opinion, the appeal of DocBook for this document system design, the appeal is not so much for developing a streams-friendly storage model, but rather for developing a semantically meaningful markup model, separate to any manner of an aesthetically appealing presentation model -- as whether for visual document presentation, or audible document presentation, or for a braille document presentation.

As with regards to developing a visual presentation model for applications in a document service as would implement the XML valuetype mapping for CORBA IDL, a concept of XSL formatting objects (XSL-FO) occurs to the author's consideration. XSL-FO is implemented in Apache FOP. In a sense, XSL-FO is to XML as like DSSSL is to SGML. In another sense: XSL-FO serves to develop a page-oriented rendering for XML, via XSL transformations.

With a further binding for Cascading Sytlesheets (CSS) defined onto the XSL-FO layer in the presentational aspects of the same document service -- thus, with an object model for data structures in a manner of CSS presentational information, then defined with a set of CORBA IDL interfaces -- the presentational aspects of the document service may then be designed with a complete data model, insofar as data structures for presentation of the underlying XML valuetype mapping. To implement a set of human computer interface (HCI) elements for the same document service design,  however, that would be one of the inevitable "Tricky parts."

If in the design of a software model, one may make reference to an item of existing work, in software applications -- even insofar as with regards to designs of human-computer interfaces -- the stylesheet editing components of UX Write then occur to the author's consideration. UX Write is an application available on Apple iOS mobile devices. In the HCI design of UX Write, as the author recalls, UX Write provides a separate interface for each of style editing and for document editing. The features defined to a style in the style editing interface, then, would serve to affect how the markup of a document in UX Write is presented in the document editing interface. The document editing interface may as much be viewed as a markup editing interface, but not in so far as for editing of bare markup -- rather, a sort of stylized markup editing interface. Thus, there is a design concept available, insofar as for how a document editor application may be implemented with a set of separate features for document editing and for presentational style editing. That, in itself, would still not serve to provide a convenient document editing toolkit, though it is towards a design of something like as so,  for an implementation onto CORBA, whether or not with round-trip serialization onto individual files in a filesystem.

Saturday, April 4, 2015

Maintenance as Project

Here at the author's DSP42 web log ('blog), this week, the author has begun to develop a concept of project management. Rather than launching onto an orthogonal thesis with regards to the Interface Definition Language (IDL) of the Common Object Request Broker Architecture (CORBA), the author is prsently preferring to develop something of a broader view of project management, as namely towards a broader sense of types of project. Thus far, the author has denoted three primary types of project, at this web log, and some corresponding concepts.
  • Thesis Development Project [xref]
    • Subsumed by Literary Project
    • Subsumes
      • Thesis project for academic institution, i.e. graduate thesis
      • Thesis project for journal publisher, i.e. journal article
    • Those subsumed types of thesis development project may differ as per style and format of published bibliography, such that would be entailed of a given publisher's requirements
  • Software Development Project [xref]
    • Subsumes
      • FPGA programming project
      • Software programming project
    • Subsumed by Digital media project [not denoted in earlier thesis work]
  • Construction Project [xref]
    • See also: Structural Archaeology

The author would not venture to define any further detail of the third of those types of project, if without further reflection as with regards to scale and context, and no long thesis for orthogonal and typically legal concepts of intellectual property, as well as concepts of physical property and, essentially, ownership. Candidly, the author is personally familiar with concerns faced by owners of properties having historic structures on premises, insofar as concerns resulting of property theft and property vandalism. In both respects, it would seem to entail a certain lack of understanding with regards to concepts of physical property. One might think as if a historic structure would not need a guard dog on premises, and that be proved to be altogether a naive concept.

With no too cute comment from the author for the author's own ears, and the author's own defensive posture with regards to family properties, presently this web log will proceed to develop a concept of a fourth type of project, namely, the maintenance project. This concept, too, may require some careful introspection, as towards developing a concept: What is the beauty of maintenance?

Similar to the manner of the author's previous articles, in this series, the author will endeavor to focus  the author's consideration on a practical matter, essentially towards a single reification of each type of project. In regards to maintenance project, on this weekend day, the author endeavors to produce a sense of personal focus, namely towards personal physical health maintenance and personal intellectual health maintenance, both subsumed by a concept of health maintenance -- not quite insofar as with regards to central health management institutions and the fine distinction of capitalist principles as viz a viz any essentially socialist principles, aside to any concept of how science is managed, institutionally. No too contentions topics in this web log -- those would be left aside for the author's politically concerned web log, Bring Back Lady Liberty.

So, the author has now denoted one further type of project, subsuming two more exacting types of project. In those two instances, however, the author does not formally apply the term, Project.

  • Health Maintenance Project [Type 2]
    • Subsumed by Maintenance Project
    • Properties
      • Intellectual Health Maintenance
      • Physical Health Maintenance

Concerning that -- moreover -- at first, the author does not denote that particular type of Health Maintenance Project as a Personal Health Maintenance type, it is not the author's wish to invite any speculation with regards to Group Health Maintenance, such that would reside in parallel to personal health maintenance. In a sense, public schools might be thought to be institutions implementing of manners of group health maintenance. However, in light of the concerns presented by the Common Core, as it being essentially a socialist agenda being imposed in public schools, it would seem to be far too contentious a topic to introduce in any hasty regards whatsoever. If, however, the outline would be expanded on further, it might be written thusly:

  • Health Maintenance Project [Type 1]
    • Subsumed by Maintenance Project
    • Subsumes
      • Health Maintenance Project [Type 2]
      • Health Maintenance Project [Type 3]
    • Properties
      • Intellectual Health Maintenance
      • Physical Health Maintenance
  • Health Maintenance Project [Type 3]
    • Subsumed by Health Maintenance Project [Type 1]
    • Subsumes
      • School
The author has there revised the Intellectual Health Maintenance and Physical Health Maintenance qualities as to denote those qualities as being properties of such type of project. That would be instead of denoting those as being subsumed by the Health Maintenance Project [Type 1].

Some examples of Health Maintenance Project [Type 2] may include:
  • Reading a book
  • Exercising with a bungee band
  • Excercising with free weights
  • Exercising in a study of the martial arts (external equipment sometimes applied, but not required), for example
    • Exercising in a study of Tai Chi
    • Exercising in a study of Wing Chun
    • Exercising in a study of Judo
    • Exercising in a study of Jeet Kune Do
  • Riding a bicycle
  • Going on a hike, along a managed trail
  • Climbing a mountain
  • Swimming in a public body of water.
  • Recreations of a physically exerting manner and -- characteristically -- recreations entailing some type of a non-self-propelled material equipment, such as a mechanical snowmobile, a powered motorcycle, a four-wheeled ATV, or a living creature such as a horse, (Please, Tread Lightly on land, water, or asphalt)
  • Walking with dog along a road or trail
It is the author's sinceremost opinion that any examples of Health Maintenance Project [Type 3] would be best be left to officials of the institutions managing such projects. 

Presently, the author observes that this article has not yet addressed all too much of a sense of maintenance project, that -- namely -- this article has not described much of a sense of structural facilities maintenance, such as with regards to maintaining known geographical properties in a civil manner, and maintaining any structural constructions developed on any known geographical properties. Perhaps the reader may endeavor to consider that the author does not wish to paint a neon sign over "Home."

In considering a third type of structural maintenance project, moreover, the author observes that there is a type of project in an automotive maintenance project -- essentially a type of equipment maintenance project for a type of equipment that provides a means of external locomotion, paralleled also by watercraft maintenance, further paralleled by types of equipment maintenance project not entailing a maintenance of a means of external locomotion -- such types of equipment maintenance project as include firearm maintenance, footwear maintenance, and manners of other indoor and outdoor equipment maintenance.

The reader might be advised that this article is not a property of a tax board. This article is a property of the author's own writing, in a thesis development project, broadly so. Though a survivalist type of view about politics might seem quite apropos to the time, the author does not subscribe to any concepts of a hasty escalationism.

Concerning Construction and Project Management for Countryside Climates

The author has recently moved to a ranch type acreage in a quiet country locale. At same locale, the author has begun an ad hoc project, firstly in regards to automotive repair. In a linear manner, the author is also keeping up with vocational planning and software development -- at this time, insofar as ideas management. To avoid casting any short or long shadow onto concepts of patent ownership and patent litigation, the author has been endeavoring to avoid developing any projects that may be too far semantically similar or too much practically similar to any of the body of existing work in software and academia. Beyond concerns with regards to patent ownership, patent licensing, and litigation about laws concerning intellectual property, the author has begun to develop an orthogonal thesis with regards to managed knowledge sharing, as viz a viz the respective technology transfer methods developed by the ESA and by NASA -- as to a point, a concept of managed technology transfer. In a manner, that concept resides in parallel to a concept of informal knowledge sharing.

In the previous article at the author's DSP42 tech web log, the author had developed a number of concepts -- albeit, none too formally expressed -- with regards to thesis projects, software projects, and the simple observation that to develop a software project's documentation, it may entail something like a thesis project -- citing the FreeBSD Handbook, then, as a literary precedent to which effect. In that article, the author also developed -- in a short time -- a concept of programming language as programming media, and a corresponding concept of FPGA programming being similar to, or rather being correlated to software programming only insofar as that an FPGA program is applied essentially as to configure a digital circuit, whereas a software program is developed essentially as to control a computing machine -- such manner of machine, including a microprocessor, perhaps having been implemented with an FPGA program, onto a single FPGA circuit.  Initially, the author's thesis was that a thesis development project, in itself, would entail an original work in ideas management, as would correspond to content development and formal bibliographical reference.

Presently, the author would like to develop a widely orthogonal thesis, with regards to project management for country projects, citing the classic wood working projects regularly published by the periodical, Popular Mechanics. Certainly, Popular Mechanics is one of the original "DIY" resources, at least for projects at a small residential scale, such as -- in a formal sense -- single-facility construction projects, automotive study, and electronics study. By no oversimplified comparison, it might seem vaguely similar to the extensive work developed about digital and analog electronics, specifically, such as of modular projects and studies published by the Adafruit Learning System and at Sparkfun. In short, the Adafruit Learning System itself might seem to be something like a Popular Mechanics of the modern digital electronics domain.

Returning to a concept of country projects -- the author presently relying on the author's own memory of a few of the construction projects published by Popular Mechanics, namely those applying wood as a building material -- in a sense, such construction projects would need at least four things as in order to be produced. No riddle:

  • Materials
  • Tools
  • Labor
  • A Plan
Insofar as budgeting for materials purchases, tools purchases or tool rentals, labor time, and development or licensing of plans, that in itself may entail something of a managerial quality. It being something of an implicit quality of such projects -- in some projects, moreover to a decentralized quality, essentially of a group-oriented project management, for projects managed of all of a group's knowledge, contrasted to a monolithic or centralized style of management -- the author will not denote it separately.

Insofar as concerning the media of project plans, and a corresponding concern as with regards to terms of licensing, certainly the digital tablet is not the first medium on which a plan would be produced, though it may afford an opportunity for licensing and control of media files. In an older sense, paper often suffices as a medium.

Orthogonally, the author is presently mulling about a concept with regards to developing a manner of structural archaeology, as around a single thesis concept: That if a structure exists, that structure was built by someone, at a time in the history of the known cosmos.

Thursday, April 2, 2015

Toward a Functional Overview of Thesis Development and Software Development

My being a student of electronics and computer networking, in an associates level program, and -- for some time -- a fan of free/open source Linux software platforms such as Debian GNU Linux, and broadly a fan of academic literature about computing, I understand that there is an existing body of work with regards to project management, at least insofar as with regards to software projects. My being furthermore of some experience with regards to the arts aspects of the humanities, including visual creative arts and the performing arts, I'm of a point of view that software projects are not the only kinds of projects under the sun.

Personally, I haven't encountered a lot of literature in academia, insofar as project management. I've read some little about the Capability Maturity Model (CMM), perhaps a sort of monolithic or centralized project management model, and some little about Scrum. I've not read a lot about "Extreme Programming" (XP) -- sort of an older agile project management trend, in a sense -- but I understand that it involves an iterative process. I've also read a little about the ideas management method proposed by Scott Belsky, in the book, Making Ideas Happen. Belsky's Action Method addresses more of a creative approach, juxtaposed to what one might expect that an implementation of monolithic CMM might be like, at a personal level. Of course, a large project might need a large management information system (MIS) to manage it by, entailing a certain degree of formalism throughout.

Personally -- as my being a student, at this time in my life -- I'm more interested about management methods for small-scale, original projects, rather than for projects developed under monolithic requirements. As a person of any manner of a creative bent, and a student of a technical field, with some self-managed knowledge of computer programming language, personally I'm interested in developing a project management system for small-scale thesis development projects, and for small free/open source software (FOSS) projects -- in an abstract sense, two types of project. In juxtaposition to monolithic project management methods, personally  I'm of an impression that each of a thesis type of project and a FOSS type of project might be -- in the most of which -- each managed individually, and by a small number of contributors.

To inquire, "How does a FOSS project begin?" or similarly, "How does a thesis project begin?" perhaps the Action Method might present the most readily applicable practical model for such a context -- as towards an ideas management phase of project development.

Towards a View of Idea Management

Aside to the metaphysical aspects of positive intention,  ideas are some of the raw stuff of academic work. Parenthetically, the reader is offered the author's sincerest apology for a lack of formal citation, to that effect. Perhaps the reader may agree that it is a valid assertion. Broadly, it may be a matter of philosophy -- namely, towards a relevance of ideas, in academic work -- furthermore, a practical matter of a functional application of intellect to a formal or informal task. Whether or not that may satisfy all of a model of "Left brain" and "Right brain" knowledge, perhaps it at least serves to present two juxtaposed views about -- in broad sense -- a relevance of ideas.

Aside to this thesis, the reader -- at any time -- might wish to criticize the author's style of writing, if it may serve as a convenient alternative to an addressing of any of the content of the discussion. The author has an idea that the ad hominem mode of discussion occurs in numerous forms. Inevitably, there will be another biting ad hominem criticism over my own writing. At that, I might wish to only address the topic: Philosophy.

Ideas and Theses

In a capital sense, ideas cannot be exchanged for raw currency. Thesis articles -- insofar as being works made as expressions of ideas -- thesis articles may not seem to be terribly profitable, either, not in any manner of an immediate economic sense. In a practical sense, a thesis article about barns does not in itself build a barn, though a thesis article may ever attract some manner of attention from a barn builder. In a literate society, thesis articles -- as literate works -- thesis articles are one manner of a textual medium on which ideas may be communicated.

Without any too lengthy reference to the Business Process Management Notation (BPMN), hypothetically, a model can be developed for a process of thesis article development. Certainly, thesis articles are works developed in chronologically linear manner, from a discrete "Start point" to a discrete "Stop point," at which time the work is published or filed away, if not altogether abandoned.  The process of developing a thesis paper, essentially, is a process of developing ideas, and expressing those ideas on a written medium. In that sense, it may be analogous to a development of any of other forms of prose, and forms of written verse, such as poetry.

Thesis articles, as ideal media,  thesis articles may not seem to serve any single, exacting functional role in society, except insofar as being required of some academic programs. If all of the world is a functional world, thesis articles may not seem to have any obvious relevance -- at least, outside of any manners of academic cultures as in which thesis articles would be any manner of a common fare. Ideally, even in proceeding from academic cultures in which learning itself would seem to be presupposed to be something akin to "Just press play", there may be a relevance recognized of thesis articles as discursive works, in a literary medium, works communicating ideas, and serving in further development of ideas. Hypothetically, a diagram of the ideas content of a single set of thesis works and the ideal derivatives of thesis articles may be all made in a single directed graph. In a practical sense, there is at least the bibliographical cross-reference, incidental to the actual content of individual thesis articles.

That a thesis article represents a communicative medium, in communicating ideas in a literal manner, that in itself does not describe how to write an idea down.

Presently, the linear thread of this article's textual content will diverge onto software development.

Logical Software Development

In a functional manner, a software program represents a linear application of digital data and control structures, such as to produce some manner of a functional result in a microprocessor for which the software program is compiled into machine code. Prototypically, the microprocessor is the central element of a software program, Once compiled to machine code, a software program performs a linear series of applications of digital functions and digital data shift procedures, in any number of linear, processor-level threads of execution. Excepting procedures applied for data shift, as in memory access and in transmission and receiving of data onto digital communication interfaces, the digital functions provided of a microprocessor architecture may include mathematical functions, for scalar and floating point values.

Firmware programming, as a manner of software programming -- as in an instance of FPGA programming -- firmware programming, insofar as FPGA programming, represents a configuration of circuit elements, such that those circuit elements would either produce a direct implementation of a discrete functional model, or that the circuit as implemented of an FPGA program would, itself, be a programmable element of a computer.

Insofar as that a software program and an FPGA program -- in a categorical manner -- would both represent an application of software for application of a digital system, then a certain philosophical parallel may be illustrated between the two categories, in some abstraction. Essentially, an FPGA program configures a digital machine. A software program applies a digital machine, whether a microprocessor implemented as an FPGA program or a microprocessor implemented directly in a semiconductor design.

Software programming, as a practice, would represent a work of developing of a software program. A software program, itself, represents -- essentially -- a medium for application and control of a digital system.

If there may be a single topic denoted of the stylistic qualities of applications of individual programming languages, perhaps it would be a contentious topic to develop. For instance, what manner of a Java collection class is preferred for which applications? What is the deeper meaning of a Common Lisp iterative macro? How often should C pointer arithmetic be applied? Opinions might vary.

To differentiate programming languages on a basis of programming media, broadly, there are text-based programming languages -- such as C, C++, Java, and the numerous dialects of Lisp -- and some visual programming languages -- at which topic, the author refers the reader to an article at Wikipedia: Visual Programming Language,  The author would wish to categorize the older punched--card and punched-tape programs as being some earlier text-based languages -- presumably, those not having been designed expressly for the visual qualities of the chad-betokened storage surfaces on which the historic punched-paper programs would be conveyed to their respective machines.

Again in a social context, the choice of a licensing model for a software program -- there is another possibly contentious topic, in software programming, certainly a topic much related to any number of topics in social, commercial, and legal views of a concept of software program as property.

So, this article has developed a succinct view of two distinct qualities of a software program: The programming language, and the license under which the software program is developed. Again viewing a software program as a categorical item distinct to a thesis paper, there is also the distinct quality of documentation for a software program. Consulting the FreeBSD Handbook. at a level of a view of project meta-data, a software project itself may essentially contain any one or more thesis projects, insofar as the documentation quality of a software project.

In a view of resources and resource containers, the whole set of documentation resources of a software project may not be represented singularly of any single source tree in which the software project is formally developed. That is, documentation may be available about a software project, such that the documentation is not developed by the software project developers, or at least is not contained in the same source tree as the software project itself.

Again, that is not to say how a software project is developed. It is to suggest a sense of a model of what a software project represents, in a sense of three fundamental qualities: A selection of a programming language; a software license for the content of the software program, altogether; documentation. Finally, there is the content of the software program itself -- as the software program being represented in a sense of source code or compiled code and correlated data elements -- the latter not being, expressly, "Program code," though supporting the execution of the program code, for instance as with firmware data for driving an external peripheral, or visual graphics data for the layout of a graphical program interface.

Certainly, the relevance of logic in software development, as a topic, may not be  as easily illustrated as the relevance of ideas in development of thesis articles. A software program -- as a product of a software project -- may represent a multi-faceted kind of work, including some literary work in a form of documentation.

As in order to develop a concept of a relevance of ideas in software development, a concept of topic maps may be presented.

Insofar as to answer a question, "How is a software program developed?" perhaps that may be illustrated with any single "Proof of concept." A concept of requirements, and of styles for best practice in application of any single programming language -- perhaps, again, some  contentious topics.

The concept, "For attention" may not be sufficient as a goal or a requirement for software program development. Incentive -- there, another complex and perhaps contentious quality of software program development.


If it may be possible to develop a system applying CORBA for project management, and that system support an individual, decentralized, by-in-large independent manner of management -- as in development of thesis articles and, in a separate sense, software -- of course, one would want to have determined, "What is that CORBA application going to support?" At that, of course it should be implemented with a license making a clear statement of indemnity.