Moffett and Intelligent Self-Interest

Let’s pull up Moffett’s Universe again:


Now watch Robert Wright and think about our intelligence moving from top-left to bottom-right on Moffett’s universe for cooperation to trump conflict.

Formatting PL/SQL like SQL

In going through reams of PL/SQL code it dawned on me that procedural language is often formatted differently than structured query language in the same code sample. I decided to take a shot at formatting procedural language code like SQL and I like the result.

	var1 number(9) 	:= 0;
	var2 number(9) 	:= 0;
	var3 number(9) 	:= 0;
	var4 number(9) 	:= 0;
	var5 number(9) 	:= 0;
	var6 number(9) 	:= 0;
	var7 number(9) 	:= 0;
	var8 number(9) 	:= 0;
	var9 number(9) 	:= 0;
	if 	var1 	= var2
	and 	var3 	= var4
	or 	var5 	= var6
		while 	var1 	< var9
		and 	var2 	is null
		or 	var4 	is not null
			select 	a.col1
			into 	var6
			from 	table1 a
			, 	table2 b
			where 	a.col1 	= b.col1
			and 	a.col2 	= var7
			or 	b.col2 	= var8;

			var1 	:= var1 + 1
		end loop;
	elseif 	var1 	= var2
	and 	var1 	<> var3
	or 	var1 	<> var4
		into 	table3
		( 	col1
		, 	col2
		, 	col3
		( 	var1
		, 	var2
		, 	var3
		var9 	:= 100;
		if 	var4 	is not null
			var8 	:= 100;

Note that I am using ten character tabs throughout the code and formatting and aligning as I would with SQL. I find the conditional structures in the IF and WHILE statements much clearer this way.

*Footnote: I recently used the TOAD formatter command and have found it surpasses my own standard for formatting. If you have TOAD I highly recommend the use of the formatter for all code. The saving in effort for the maintenance people that follow in your development footsteps is well worth it.

formatting plsql like sql formatting plsql like sql formatting plsql like sql

Intelligence is not Behaviour but Prediction

Came across a video of Jeff Hawkins of the Redwood Neuroscience Institute explaining brain theory.


Remember, the above diagram as you view the video. Also think about the Universe of Discourse as explained by James Moffett. The theory has already been hinted at.

The Innovator’s (and SQL’s) Dilemma

Let’s look at Christensen’s four marketing issues again:

  1. Availability
  2. Compatibility
  3. Reliability
  4. Economy

How can this be correlated with SQL? First, data availability is determined by the SELECT statement. You query the database to determine if data that meets search criteria exists. Second, data compatibility is determined by the INSERT statement. Data is accepted if it is within the database structure’s definition. Third, data reliability is determined by the UPDATE statement. Data has to change as the database’s state changes to continue to meet the database’s objectives. Finally, data economy is determined by the DELETE statement. Data that is no longer of use can be removed from the database to free up available resources to achieve cost effectiveness.

  1. Select
  2. Insert
  3. Update
  4. Delete

Christensen’s Innovator’s Dilemma tetrad has provided us with another viewpoint on the SQL tetrad.

Quadrant Theory

Judah Thornewill predicts: “Major online internet useage research firms will record that over 3 billion people in 2025 managed their incoming and outgoing digital information using a graphical user interface based on Quadrant Theory – as described in Marshall McLuhan’s “Tetrad” model in Laws of Media, Ken Wilber’s Holon in Sex, Ecology Spirituality, and R Buckminster Fuller’s Tetrahedral structures in Synergetics.”


I think this is an interesting prediction by someone trying to develop a product based on an unexplained concept. However the project appears to have vanished along with the website. What I plan to glean from it is Ken Wilber’s work. I plan to give it a read.

Concepts and Ontologies

I came across a very interesting paper:  Concepts and Ontologies

Posted in Uncategorized. Tags: , , , . Leave a Comment »