Skip to main content

the living snowflake

The definition of what constitutes a living thing is not as cut and dried as many would think. If we define a living thing as something that takes materials from its environment , consumes them to make energy and reproduce themselves, and then excretes waste...then stars are alive and most chemical reactions can also said to be living ones, so how do we distinguish what we familiarly call "life" from ordinary chemical processes. Can we add in the restriction that the interactions must be performed by multicellular organisms to be alive then we have just removed many types of archaic bacteria and viruses from the category of "life" and we know that these organisms are capable of reproducing themselves. Maybe the problem is the question, maybe we have used a much too narrow definition of "life", I propose that instead of defining life in terms of resource utilization and reproduction that we define it in terms of one thing that life does that non life does not. Life has the unique ability to continue to change despite the fact that the required resources for its survival do not, this is the result of the nearly random effects of mutation. All cells are subject to mutation by virtue of their existence on a planet, near a highly radiating Sun. The effects of UV radiation on our cells introduces mutations in the genetic structure of even the smallest organisms and changes over time how those organisms relate to the outside environment. In the billions of years that have elapsed since the first signs of life on Earth, mutation has played its part in the development of increasingly more complex systems from blind chemical processes. The formation of the cell wall is said to arise from the combination of having simple replication molecules trapped insides lipid bodies which naturally, in their mindless acquiesence to conservation of energy, form into spherical shapes. The process of genetic transcription also occurs from the blind chemistry of the simple sugars which are themselves nothing more than energy conservative combinations of elemental molecules like Nitrogen, Oxygen, Carbon and Hydrogen which have known (but probabilistically certain) affinities for bonding and attraction.

In living systems contrary to those of low level chemical systems (reactions) the failure of elements to bond is expressed as an improbability of the occurance coupled with the brevity of the survival of the new species (the atomic scientists word ...not mine!) what is not energy conservative ceases to exist after brief periods. Life on the otherhand persists through mutations and macroscopically results in a materially different system that can then propagate its particular mutation set to its progeny. Viruses do this, the most archaic Bacteria do this, plants and people do this. Stars do not do this, snow flakes do not do this, a catalyzing reaction between two elements or more complex chemicals does not do this. The evolution of what I propose as non life is rigid and fixed once the energy regime for a reaction is set, once oxygen and hydrogen meet under the right temperature and pressure constraints water WILL form. Abberant species of hydrogen/oxygen molecules are probabilistically denied to exist for any important (meaning allowing continued reaction) duration. Similarly, stars are not alive because they do not have the ability to continue their stellar burning beyond the limits of their acquired Hydrogen fuel, the initial mass value or addition of new material does lead to a change in the evolutionary trajectory of the star (will it be a white dwarf? a neutron star or a black hole? or will it go NOVA?) but these changes are precisely predicted ones. Unlike true life, who's evolved state under mutation holds the possibility for highly unpredictable changes in the final entity, particularly after generations of mutation and propagation.

So formerly my proposal for a new definition of "life" is:

Life, any entity that under the process of internal random mutation changes how it interacts with the outside environment from generation to generation despite having at any given moment the resources (even if fixed in quantity) required for its survival.

How's that?

Comments

Popular posts from this blog

On the idea of "world wide mush" resulting from "open" development models

A recent article posted in the Wall Street Journal posits that the collectivization of various types of goods or services created by the internet is long term a damaging trend for human societies.

http://online.wsj.com/article/SB10001424052748703481004574646402192953052.html

I think that the author misses truths that have been in place that show that collectivization is not a process that started with the internet but has been with us since we started inventing things.

It seems that Mr. Lanier is not properly defining the contexts under which different problems can benefit or suffer from collectivization. He speaks in general terms of the loss of the potential for creators to extract profit from their work but misses that this is and was true of human civilization since we first picked up a rock to use as a crude hammer. New things make old things obsolete and people MUST adapt to what is displaced (be it a former human performance of that task or use of an older product) so as to main…

Engineers versus Programmers

I have found as more non formally trained people enter the coding space, the quality of code that results varies in an interesting way.

The formalities of learning to code in a structured course at University involve often strong focus on "correctness" and efficiency in the form of big O representations for the algorithms created.

Much less focus tends to be placed on what I'll call practical programming, which is the type of code that engineers (note I didn't use "programmers" on purpose) must learn to write.

Programmers are what Universities create, students that can take a defined development environment and within in write an algorithm for computing some sequence or traversing a tree or encoding and decoding a string. Efficiency and invariant rules are guiding development missions. Execution time for creating the solution is often a week or more depending on the professor and their style of teaching code and giving out problems. This type of coding is devo…

Live Coding Exercises: How NOT to hire potentially Brilliant Engineers.

I've intimated this view before but, I abhor "live coding" exercises for engineering interviews and will never have them as part of any interview process I conduct. They are simply unrealistic to real world engineering in every possible way, they only test familiarity (or luck) with a tiny subset of solution methods to a specif subset of problems...that you either "nail" or get spectacularly wrong depending on who is observing you.

They are mostly entirely unfair to the candidate on top of the pressure of having a gun under them while coding, only in the most extreme cases is coding under the gun and that's just competitions where the code is far from real world engineering related...so why test for general coding ability with such tests?? Stupid.

I posit, it is significantly more effective to see examples of a candidates finished working code in the form of a project or projects they've created. How long it took some one to get some uber algorithm work…