Skip to main content

Avastu's Ideation Series: Multi-Mapped Cycle Convergence Theory

This is a small representation, still in draft of something that I will be working on in my free time. You all know how much free time this "slave-to-his-own-hippocampus" has ;-)

Anyways, first of all my approach is exploratory. It is even adventurous research approach since it has research intent to define the roadmap for the next generation. I have taken and done a lot of research on what I read about (Kondratieff) and am spending a lot of time on what I am proposing (Startup and Civilizational).

What I am proposing:

  • Startup/Re-startup Cycles - 30 years: These are software companies that have emerged and if they have been around for 30 years then they have a fair chance to take a shot at their re-birth. Call it deconstruction, re-structuring or even the latest fad "transformation". Bottom line is if they are able to adopt a suitable "surf-to-shore" strategy, they can ride on this multi-mapped wave to the next successful level, which I have often called in other articles as "cylindrical verticalization". Simply said: The next stage. More detailed explanations will follow in later articles.
  • Civilizational Prosperity Cycles - 300 years: This is one of those typical tidal cycles that don't happen that often but they do govern the life and death of successful companies and nationsin an event of a natural market/economic slowdown or purely "prosperity shift". My hypothesis comes from my observations of typical 300 (more or less) years cycles that I studied about India. There is a lot to learn from civilizations like India, especially U.S since its nearly 300 years cycles are up, meaning, it can take on that slope if it effectively collaborates and learns from India. U.S is making a lot more headway with India than we may have seen from European nations in the 15 - 18th century. So U.S has a great opportunity to take on the proverbial plank and go with the "surf-to-shore" strategy and get on to the next level. More detailed explanations on this cycle will come later.
  • Kondratieff cycles - 50 years: This you have heard from me several times and all the credit goes to Kondratieff but it is very inspirational to me in many ways. It certainly is one of the primary layes to that multi-mapped wave as we approach the death of traditional IT and move on to "conceptual/ideation age". We have bigger and complex puzzles to solve. What we today identify or even diagnose as a disorder in our children is in fact the foundation of what will help them raise to that challenge of emerging and acting as true conceptual leaders.
So here's the draft of the waves, it'll change often as our explorations dig more data:

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op