Skip to main content

perception ticks your personal clock

"the more you know, the less there is to find out, the less there is to find out the slower you learn new things, imagine a unit of learning as perceived by you being constant as time goes by life surprises you less and what does happen is spaced out in your experience over longer periods of time, thus a given number of events (significant learning ones that bring new knowledge) is perceived to be spaced out as well and there you go, time contracting with age.

Just a theory. ;)"

This was the answer I provided to the question , "Is time speeding up as we get older or is it me?".

It was the first thing I thought about to answer as it was a question posed as a status message by a friend of mine on Facebook. However, thinking a bit more about it, there might be some legs to it. The main evidence comes from recent work that shows that the human perception of time can be changed by the environmental situations that we find ourselves in , and thus the level of stress that we may be undergoing. Studies have been done that show that when individuals are experiencing exciting actions , like bungie jumping or parachuting, their reported measurement of time extends beyond the actual time, thus their perception of each moment speeds up. This aligns with the statement above, as new or important sensory experiences from moment to moment are spaced out in closer time intervals our perception of what is critical in time is also speeded up and our reported time stretches beyond the actual time. If on the other hand , novel experiences are few and far between, it makes sense that important events stretch out over real time and thus leading to a perceived contraction. (between important events)

The biological mechanism seems to be locked in particular parts of the brain responsible for setting a global timer of sorts, but since these regions are modulated by neurotransmitter activity which can be modified by sensory experience, then the biological timers tick rate (our perception) varies as well.

Some interesting links:


Popular posts from this blog

Highly targeted Cpg vaccine immunotherapy for a range of cancer


This will surely go down as a seminal advance in cancer therapy. It reads like magic:

So this new approach looks for the specific proteins that are associated with a given tumors resistance to attack by the body's T cells, it then adjusts those T cells to be hyper sensitive to the specific oncogenic proteins targeted. These cells become essentially The Terminator​ T cells in the specific tumor AND have the multiplied effect of traveling along the immune pathway of spreading that the cancer many have metastasized. This is huge squared because it means you can essentially use targeting one tumor to identify and eliminate distal tumors that you many not even realize exist.

This allows the therapy for treating cancer to, for the first time; end the "wack a mole" problem that has frustrated traditional shot gun methods of treatment involving radiation and chemotherapy ...which by their nature unfortunately damage parts of the body that are not cancer laden but …

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…

AgilEntity Architecture: Action Oriented Workflow

Permissions, fine grained versus management headache
The usual method for determining which users can perform a given function on a given object in a managed system, employs providing those Users with specific access rights via the use of permissions. Often these permissions are also able to be granted to collections called Groups, to which Users are added. The combination of Permissions and Groups provides the ability to provide as atomic a dissemination of rights across the User space as possible. However, this granularity comes at the price of reduced efficiency for managing the created permissions and more importantly the Groups that collect Users designated to perform sets of actions. Essentially the Groups serve as access control lists in many systems, which for the variable and often changing environment of business applications means a need to constantly update the ACL’s (groups) in order to add or remove individuals based on their ability to perform certain actions. Also, the…