The Flip Side of Removing Technical Debt is Adding Information Value

april

When managing software development, there needs to be an amalgamation phase to convert types and bits into endemes. (- once things are stable). Somewhere between code rewriting, and code refactoring, is code information amalgamation which is adding information value.

The flip side of removing technical debt is adding information value. You can go through programs to remove technical debt. This removes problems. You can also go through programs to extract information structures. This adds value.

Here are some things that can be extracted from code, some to remove problems, some to add value which I found through the Google search “Extracting * from code”:

  • extracting code from code bases [adds value or removes technical debt]
  • extracting a method from code [adds value]
  • extracting a model from code [adds information value]
  • extracting the application architecture from code [adds value]
  • extracting the data from code contents [adds value or removes debt]
  • extracting the model from a code [adds information value]
  • extracting the strings from code [removes technical debt]
  • extracting this data from code [adds value or removes technical debt]
  • extracting abstractions from code [adds information value]
  • extracting action words from source code [adds information value]
  • extracting Algorithms From Code [adds value]
  • extracting Annotations from Code [adds value]
  • extracting API examples from test code [adds value]
  • extracting Authors from Source Code [adds value]
  • extracting automata from code [adds value]
  • extracting candidate fingerprints from code [adds value]
  • extracting code blocks from code [adds value]
  • extracting code metrics from code [adds information value]
  • extracting Colors from Code [adds value or removes technical debt]
  • extracting configuration from code [adds value]
  • extracting content from code [adds value or removes technical debt]
  • extracting data from code [adds value or removes technical debt]
  • extracting Definitions from Code [adds information value]
  • extracting dependencies from code [removes technical debt]
  • extracting descriptions from code [adds information value]
  • extracting design from code [adds information value]
  • extracting documentation from code [adds information value]
  • extracting dynamic behavior from source code [adds value]
  • extracting existing context from code [adds information value]
  • extracting Facts from Perl Code [adds information value]
  • extracting Gold from Legacy Code [adds value]
  • extracting high-level designs from code [adds value]
  • extracting Hybrid Automata from Control Code [adds value]
  • extracting information from code [adds information value]
  • extracting IR tokens from code [adds value]
  • extracting JPF Options from Code [adds value]
  • extracting kernels from code [adds value]
  • extracting knowledge from code [adds information value]
  • extracting meaning from code [adds information value]
  • extracting meaningful metrics from source code [adds information value]
  • extracting measurements from code [adds information value]
  • extracting Messages from Code [adds value]
  • extracting metadata from code [adds value]
  • extracting methods from code [adds value]
  • extracting models from code [adds information value]
  • extracting multi-threaded capabilities from code [adds value or rmvs debt]
  • extracting other relationships from code [adds information value]
  • extracting parallelism from legacy code [removes technical debt]
  • extracting protocol state machine from code [adds value]
  • extracting questions from code [adds information value]
  • extracting relationships from code [adds information value]
  • extracting rules from code [adds information value]
  • extracting secret credentials from your code [removes technical debt]
  • extracting software architecture from code [adds value]
  • extracting source content from code [adds information value]
  • extracting specifications from code [adds information value]
  • extracting specs. from code [adds information value]
  • extracting Speedup From C-Code [adds value]
  • extracting SQL from the code [adds value or removes technical debt]
  • extracting SQL statements from application code [adds value or rmvs debt]
  • extracting state machines from code [adds information value]
  • extracting strings from code [removes technical debt]
  • extracting summary keywords from code [adds information value]
  • extracting type signatures from code [adds value]
  • extracting UML constructs from code [adds value]
  • extracting unnecessary knowledge from code [removes technical debt]
  • extracting Values From Code [adds value or removes technical debt]

I develop Solutions to Business Information Problems

My work seems to follow the following cycle:

+-------------+     +-------------+
| identify    |     | model,      |
| generic     |     | research    |
| business    | --> | & develop   |
| information |     | information |
| problem     |     | solution    |
+-------------+     +-------------+
       ^                   |
       |                   v
+-------------+     +-------------+
| apply       |     | document &  |
| information |     | publish     |
| solution    | <-- | information |
| to business |     | solution    |
| needs       |     |             |
+-------------+     +-------------+

Information Can Support Cloud, Big Data, Mobile, and Social and Be Supported by Them

These five technology foci can support each other in these various ways

cloud    - IT
big data - BI
mobile   - smart phones
social   - Internet
my information - endemes


Using v  |     Big Data            Cloud          My Information         Mobile            Social             
         +------------------+------------------+------------------+------------------+------------------+
         |                  | cloud            | some sort of     |                  |                  |
         |                  | performance      | automated        |                  |                  |
Big Data |        ><        | optimization     | generation of    |                  |                  |
         |                  |                  | endemes and      |                  |                  |
         |                  |                  | endeme sets?     |                  |                  |
         +------------------+------------------+------------------+------------------+------------------+
         | leveraging the   |                  | 1. better endeme | 1. faster        | security         |
         | cloud for large  |                  | comparison       | applications     | authorization    |
Cloud    | scale computing, |        ><        | 2. easier user   | through local    | and identity     |
         | such as big      |                  | application      | hosting          | centralization   |
         | data analytics   |                  | development      | 2. data storage  |                  |
         +------------------+------------------+------------------+------------------+------------------+
         | 1. what to do    | helping people   |                  | 1. real time     | 1. Attention     |
         | with results when| in some way in   |                  | collaboration?   | management,      |
My Info- | you get them and | how to use the   |        ><        | 2. texting       | 2. Mutual user   |
rmation  | 2. data source   | cloud            |                  | content          | alignment and    |
         | integration      |                  |                  | understanding    | discovery        |
         +------------------+------------------+------------------+------------------+------------------+
         |                  |                  |                  |                  | continuous       |
         |                  |                  |                  |                  | connection       |
Mobile   |                  |                  |                  |        ><        | to social        |
         |                  |                  |                  |                  | entities         |
         |                  |                  |                  |                  |                  |
         +------------------+------------------+------------------+------------------+------------------+
         |                  |                  | 1. Endeme set    |                  |                  |
         |                  |                  | development wiki |                  |                  |
Social   |                  |                  | 2. tagging-info  |                  |        ><        |
         |                  |                  | conversion       |                  |                  |
         |                  |                  |                  |                  |                  |
         +------------------+------------------+------------------+------------------+------------------+

Metadata Endeme Set

Here is an endeme set for various common kinds of metadata:

ABCDEFGHIJKLMNOPQRSTUV|
----------------------+
A]C-                  |A. creator/artist/The person or organization who created the content
[B]  -G-      -P-     |B. bundle/product/group/part of/album/collection
 [C]             -ST- |C. classification/taxonomy/topic/subject/class/genre/Content TypeTree/type
A-[D] -H- -LM-O- -S-  |D. orientation/direction/Aspect ratio/height/width/length/size/duration/magnitude
   [E]                |E. Encoding/compression/bit rate
    [F]          -S-  |F. format/schema
     [G]           -U-|G. GUID, Unique identifier,universal id
  -D- [H]     -P--S-  |H. Provider/distributor/The organization who provides and distributes the content/Host/server/source/publisher
       [I]  -NO-  -T- |I. item/track/ordinal/number
 -CD-   [J]      -S-  |J. jurisdiction/domain/scope/coverage
         [K]      -T- |K. keywords/tags/subject
          [L]         |L. language
  -D-      [M]N- -S-  |M. description/narrative/summary/comment/meaning/definition
          -L[N]   -T- |N. name/title/label
 -C-         [O]-R-   |O. copyright/owner/legal owner/rights/Provenance
 -C-      -L-O[P]     |P. place/location created/modified/location shown
                      |Q. 
                [R]   |R. rating/parental rating/Item Star Rating
A-             -R[S]T-|S. shown/target or intended audience/recipients
  -D-             [T] |T. date and time/creation/modify date time
             -OP--T[U]|U. usage/platform/operating system/technology context
   D       -M-  -R- [V|V. Milestone/Version/revision/draft
----------------------+
ABCDEFGHIJKLMNOPQRSTUV|

TA    creation date time
TV    modification date time
PA    location created
PV    location modified
PS    location shown

‘Information’ has a sucky namespace. Use these keywords for searching on the subject of Information.

The word ‘Information’ has a terrible namespace. Here are some keywords for searching for information about the subject of Information.

Information Keywords:

Information Could be Used to Handle Islands of State

The original object oriented idea of islands of state is best handled at Level 4.

Since we don’t yet have adequate level 3 constructs this wi9ll not happen practically until level 3 is built and level 4 is built on top of level 3.

To get around the object oriented ‘hierarchy’ – avoiding object orientation:
– ORM style programming
– Stored Procedures
– UI Frameworks

Object Orientation is really for building frameworks, not applications.
object oriented vs functional programming -> data structure oriented vs data operation oriented programming.

Organizing data structures and operations can be done at level 4. Level 4 can handle various data organization schemes. Can level 4 handle various operation organization schemes? I suspect so and I hope so, but I don’t have enough experience with operation oriented (functional) programming to tell.

A similar question: can level 4 handle aspects?

Object orientation’s problems:
– hierarchy
– fields
– function/operation location