To have an infinitely large application there can be no limits on the number of
lines of source code, on the database size, or on the size of the data
structures. I have removed the limitations on the lines of code in an
application, I will now work on removing all limitations on the size of the
database and the data structures.
An English language description of any application: Security, layout, forms,
dialogs, resources, database, navigation, content management. Navigation
includes bar menus, popup menus, tree menus, trees, directories.
Make Years of Development reduced to Man Months
Man Months to Man Weeks
Man Weeks to Man Hours
Man Hours to Man Minutes
Man Minutes to Man Seconds
Man Seconds to Involuntary response software
Each phase the development of software robots gets me closer to my final goal of
infinitely large applications with no limitations, zero development time, and no
I can get rid of these dependencies by having the system maintain and manage
Permanent storage for logic
A network diagramming system for the editing and management of all resources.
As application become larger and more complex the management of logic and related information structures must be handled with absolute precision.
This system controls the logic and the flow of information
all sub-systems as a single unit. There is just one system with the information and
logic that is accessed globally. This gives us the ability to use any of the logic
and access any information, in the complete system, from any other part.
This diagramming system is a place to store all the logic and
information that a company will use. If we are ever to get to an infinitely
large application size, the permanent storage and access to logic, parameters,
setup, data structures, and databases must be maintained by the system itself,
with it knowing everything it can about itself.
For humans this gives us a way to known what, where
and how the system works, and to make changes at any
time that is: fast, accurate, accountable and with 100% confidence.
Software Logic Management
Writing more code does not make for better software systems
The creation of Logic is a manual process
Speed of access is the primary objective, but should not
The requirement for logic is constantly changing
All software logic is constructed from five instructions:
MOVE, SHIFT, COMPARE, JUMP, and SUBTRACT
Software Logic cannot be shared
The domain of Software Logic is the human, hardware,
software, and literature needed to complete the task
A hardware solutions should be considered first; "we
need more/better direct access to hardware..."
The science of controlling software development effort by
allowing change to facilitate improved systems
I spend 90% to 95% of my development time learning someone else's logic. The
concept of Software Robots is to code 100% of the logic into a self contained
software module so I do not need to know anything about it's logic to use the
The following two compilers are being developed as a natural language
extension to "computer". This will provide full language support for all
robots by having a core reduction table with outputs to multiple
test cases, since they themselves are robots with their own unique language
tied to the natural language interface that can accommodate variations that
is required by each robot.
Software development with no limits. Produce an infinite number of statements without adding complexity.
Program once, use everywhere. Logic: security, I/O, forms, dialogs, schedule,
shared across all applications. Programming that is accumulative and permanent.