Software Astrology

• 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 -

• 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 -

• Days of possible critical problems: 5, 14, 24
• Days of unfortunate computation: 10, 20, 27
• Days of good enough software behaviour: 3, 11, 22, 25, 29
• Fault-free days: 8, 18, 25

- Dmitry Vostokov @ SoftwareAstrology.com -

• Days of possible critical problems: 4, 23, 31
• Days of unfortunate computation: 8, 19, 26
• Days of good enough software behaviour: 6, 24
• Fault-free days: 2, 10, 21, 29

- Dmitry Vostokov @ SoftwareAstrology.com -

• Days of possible critical problems: 3, 11, 21, 30
• Days of unfortunate computation: 7, 17, 26
• Days of good enough software behaviour: 19, 28
• Fault-free days: 5, 14, 24

- Dmitry Vostokov @ SoftwareAstrology.com -

• Days of possible critical problems: 7, 15, 25
• Days of unfortunate computation: 1, 11, 20, 29
• Days of good enough software behaviour: 3, 13, 23
• Fault-free days: 9, 18, 27

- Dmitry Vostokov @ SoftwareAstrology.com -

• Days of possible critical problems: 3, 11
• Days of unfortunate computation: 7, 15, 26
• Days of good enough software behaviour: 5, 13, 23
• Fault-free days: 9, 18, 28

- Dmitry Vostokov @ SoftwareAstrology.com -

This is a short summary of behavioural and structural characteristics for modules, products and systems built during Winter time:

• Follow the large picture
• Tend to be dominant components ruling process and kernel space. Often initiate process space reformation
• Flexible data manipulation
• Interface acceptance
• Frequently the source of creativity

During Winter, software constructors live in expectation of coming Spring, less active, more conscious with internal aspects of their being and this channels into code construction and then into built modules, products and systems. Build activities, design of expressible and powerful UI and marketable features are diminished during this period. Some old components are even face possibility to enter the end of their life cycle.

Computational life cycles also have their winter periods, called χ-Winter (from χειμώνας, Greek) which might not coincide with the same physical periods due to the lag time of channeling. There can be one to many correspondence between one physical winter period and χ-Winter periods with some boundary overlapping due to the presence of Riemann surfaces (*) in computational space-time.

(*) Riemann surfaces are manifold representations of multivalued functions that explain side effects of many computational algorithms when doThis() function gives several unexpected results instead of the expected one.

- Dmitry Vostokov @ SoftwareAstrology.com -

• Days of possible critical problems: 2, 11, 19, 29
• Days of unfortunate computation: 7, 15, 23
• Days of good enough software behaviour: 5, 13, 21, 31
• Fault-free days: 9, 17, 26
• Days of customer grievance: 1, 2, 4, 6, 11, 12, 20

- Dmitry Vostokov @ SoftwareAstrology.com -