Embracing Complexity

This is a collection of information that seems important. Most of this is from a LinkedIn post by Tony Seale.

This is not about creating complex things. This is about looking at things as a system. This is about embracing and managing the complexity.

A kluge is a term from the engineering and computer science world, it refers to something that is convoluted and messy but gets the job done.  Anyone can create something that is complex.  Anyone can create a kludge.  But it is hard work to create something that is simple and elegant.

It takes hard work to create something that is simple.  Not simplistic, simple.  Simplistic is dumbing down a problem in order to avoid complexity.  Simple is about embracing complexity, but then understanding the complexity and then hiding complexity from users.

Simplistic is dumbing down a problem in order to make the problem easier to solve.  Simplistic ignores complexity in order to solve a problem which can get you into trouble.  Simplistic is over-simplifying.  Simplistic means that you have a naïve understanding of the world, you don't understand the complexities of the world.  Removing or forgetting complicated things does not allow for the creation of a real world solution that actually work.

Simple is something that is not complicated, that is easy to understand or do.  Simple means without complications.  An explanation of something can be consistent with the real world, consider all important subtleties and nuances, and still be simple, straight forward, and therefore easy to understand.

Per the Law of Conservation of Complexity; inherent complexity cannot be removed from a system, but the complexity can be moved.  Is the platform dealing with the complexity, or the software application, or the user of the software application?

Irreducible complexity is explained as follows: A single system which is composed of several interacting parts that contribute to the basic function, and where the removal of any one of the parts causes the system to effectively cease functioning.

So for example, consider a simple mechanism such as a mousetrap.  That mousetrap is composed of several different parts each of which is essential to the proper functioning of the mousetrap: a flat wooden base, a spring, a horizontal bar, a catch bar, the catch, and staples that hold the parts to the wooden base.  If you have all the parts and the parts are assembled together properly, the mousetrap works as it was designed to work.

But say you remove one of the parts of the mousetrap.  The mousetrap will no longer function as it was designed, it will not work.  That is irreducible complexity: the complexity of the design requires that it can't be reduced any farther without losing functionality.


An area of knowledge can be characterized in a spectrum with two extremes.  This article calls the two ends of the spectrum "kind environments" and "wicked environments":
  • Kind area of knowledge: Kind environments, characterized by clear rules, repetitive patterns, and unchanging tasks. Specialists whose jobs are at risk fall under this category.
  • Wicked area of knowledge: Wicked environments, characterised by obscure data, no rules, constant change, and abstract ideas. Generalists who can adapt and excel across different skillsets fall under this category.

Comments

Post a Comment

Popular posts from this blog

Relational Knowledge Graph System (RKGS)

Image
Relational Knowledge Graph System (RKGS) is an interesting idea that combines the relational paradigm and the knowledge graph paradigm.  This documentation, Why RKGS , explains the idea. This gets even more interesting with the notion of "relational AI".  RelationalAI is described as follows by the company of the same name, Relational.ai : “RelationalAI is a cloud-based relational knowledge graph management system, with state of the art probabilistic processing and declarative reasoning at scale to make developing Data Applications a superpower for your business.” This notion of knowledge graphs represented in relational databases fits into my belief that knowledge graphs have two aspects: the expression SYNTAX and the logic of what is expressed or SEMANTICS. While the LOGIC of a knowledge graph is always the same regardless of technical syntax used to express that logic; there are many, many different technical syntaxes that can be used to represent a knowledge graph. There
Read more

Graph Hairball

Image
Knowledge graph system logic, the "things" and "relations between things" that  graph theory calls "vertices" (a.k.a. nodes, points, entities, things) and "edges" (a.k.a.  links, lines, relations, associations), looks like a big graph hairball as some people call it an example of which you can see here: Why?  This common view of a graph is because there has to be some "general view" of the information provided by the graph.  This is just like a general view of the information within a relational database is a table ; a set of ROWS and COLUMNS for exactly one table at a time. So what is interesting is that with a graph database the default view is everything in the graph of knowledge.  Whereas the default view of everything in a relational database is one table at a time. Further, it does not really matter whether the information that populates your knowledge graph comes from, say, CSV files, Excel, JSON, XBRL, RDF, PROLOG or whateve
Read more

PLATINUM Business Use Cases, Test Cases, Conformance Suite

Image
A brick wall is made of exactly two things: bricks, mortar. But a brick wall created by a master craftsman, or mason, and a brick wall created by a “weekend warrior” with no knowledge of masonry will be very different. Master craftsmen are created and that process takes time and effort. This blog post is a first prototype that brings several things together into one useful resource for business professionals.  It pulls together the human readable information of the Showcase of Reports   and the machine readable information of the Conformance Suite of XBRL-based Financial Reports Prepared using the Seattle Method .  Then, I want to incorporate the information found in these PLATINUM XBRL-based Financial Report Examples . The three resources can be useful and used independently; but they are even more useful when used together.  Business professionals really could not care a less about the technical details of getting some result that they want.  But technical professionals need to under
Read more