December 24th, 2009
As The Year 2012 approaches and beliefs in its transformative significance in December intensify we would like to point out that from the number representation perspective 2012 is 7DC in hexadecimal notation and it means:
7 December Crashes
Cosmic events in that year may dramatically influence Software as well. Considering our dependence on software products Seven December Crashes in major software centers of the World may exacerbate natural disasters and impede monitoring and rescue efforts.
- Dmitry Vostokov @ SoftwareAstrology.com -
Posted in Deep Meaning, Horoscopes on Software, Predictions, Software Eschatology | 1 Comment »
November 29th, 2009
- Days of possible critical problems: 5, 13, 23
- Days of unfortunate computation: 9, 17, 28
- Days of good enough software behaviour: 3, 11, 29, 30
- Fault-free days: 7, 15, 26
- Dmitry Vostokov @ SoftwareAstrology.com -
Posted in Horoscopes on Software | No Comments »
October 26th, 2009
- Days of possible critical problems: 7, 16, 26
- Days of unfortunate computation: 3, 12, 20, 30
- Days of good enough software behaviour: 5, 14, 22
- Fault-free days: 1, 9, 18, 28
- Dmitry Vostokov @ SoftwareAstrology.com -
Posted in Horoscopes on Software | No Comments »
October 1st, 2009
- Days of possible critical problems: 2, 10, 19, 30
- Days of unfortunate computation: 6, 14, 25
- Days of good enough software behaviour: 8, 17, 27
- Fault-free days: 4, 12, 22
- Dmitry Vostokov @ SoftwareAstrology.com -
Posted in Horoscopes on Software | No Comments »
September 3rd, 2009
Faces, Faces, InterFaces:


- Dmitry Vostokov @ SoftwareAstrology.com -
Posted in Dialognomy | No Comments »
August 31st, 2009
Extending channeling to user interfaces. From the domain of Physiognomy to the new discipline:
Dialognomy or Dialognomics
From “dialog” and Greek “gnomon” (’interpreter’). Assessment of a computer program behavioural characteristics and internals from its user interface appearance.
More to come.
- Dmitry Vostokov @ SoftwareAstrology.com -
Posted in Definition, Dialognomy, New Words | No Comments »
August 31st, 2009
- Days of possible critical problems: 5, 13, 22
- Days of unfortunate computation: 9, 18, 26
- Days of good enough software behaviour: 2, 11, 20, 29
- Fault-free days: 7, 16, 24
- Dmitry Vostokov @ SoftwareAstrology.com -
Posted in Horoscopes on Software | No Comments »
July 25th, 2009
- Days of possible critical problems: 9, 18, 26
- Days of unfortunate computation: 4, 13, 22, 31
- Days of good enough software behaviour: 6, 15, 24
- Fault-free days: 1, 11, 20, 29
- Dmitry Vostokov @ SoftwareAstrology.com -
Posted in Horoscopes on Software | No Comments »
July 4th, 2009
- Days of possible critical problems: 3, 11, 20, 30
- Days of unfortunate computation: 7, 16, 25
- Days of good enough software behaviour: 9, 18, 27
- Fault-free days: 5, 14, 23
- Dmitry Vostokov @ SoftwareAstrology.com -
Posted in Horoscopes on Software | No Comments »
June 17th, 2009
The Day of Heap Expansion
Modules, products or systems built on December 15 compute big. Their expansive algorithms run free into wilderness. Few limitations exist for their code because it knows how OS works, but once they are on top of the list they don’t know how to keep staying there. December 15 components need to learn how to be satisfied at various resource levels and security restrictions. They do their best in computation when they care about other modules and do not interfere with other processes and threads. Products built on December 15 are liked by many customers. When they see them compute they feel good with their easy and open interfaces. December 15 modules from financial products are open to exploits and have vulnerabilities discovered with depends.exe. They are usually not concerned with such matters and can be sometimes computationally fatalistic, destined to loose data but can restart instead of hanging on exception. Thoroughly compute with all possible checks and then move to another step of their algorithm is the safest thing for them. Modules, products or systems built on December 15 may overestimate resources available for them and overlook deterioration symptoms so various external checks are recommended during their normal computational life span. Training is mandatory for their troubleshooters. Data restrictions are not necessary unless insisted by a security engineer. Running on open platforms is advised for December 15 systems.
DLL, SYS and EXE born on this date:
usrxcptn.dll Fri Dec 15 08:33:42 2006
PCIWNT.SYS Tue Dec 15 19:46:09 1998
AegisP.sys Thu Dec 15 10:31:20 2005
srv.sys Mon Dec 15 21:42:35 2008
Weaknesses: Unrealistic expectations of available resources. Blind messaging.
Strengths: Well-linked modules. Cheerful sounds.
Advice: Don’t have a condescending attitude towards customers. Learn to deal with security constraints. Remember that heap can contract too.
- Dmitry Vostokov @ SoftwareAstrology.com -
Posted in Build Date Astrology | No Comments »