#header-inner {background-position: right !important; width: 100% !important;}


Programmer's 6 - Tiered path to Victory.


i'll share & elaborate if / as i am ready, perhaps rearranging.

(work in progress for as long as neccessary).


Path to Victory:

1. 'Know the Code, Know the Bug'.

the most ambitious of programmer's ways, in my opinion.

an apex of the programmer's ability but can be practiced even by beginners.

... if they dare.

basicly, You have the code, You have the bug (something wrong, an error) to fix, fix it.

anything permitted, learn and / or hack if neccessary.

all of consequences still hold.

... the main bug is Your Ego.

2. 'Know the Problem, Know the Code'.

take responsibility, but strictly adhere to standard programming methods, no 'politics', no 'foul play' etc.

understand 'the problem to solve', understand 'the code'.

plan 'solution' including tiers 3 - 6.

implement and / or debug 'the code' if neccessary.

3. 'Know the Risk, Know Your Way'.

list (write) all of the risks You can, discussing / brainstorming with Your team as well.

try to solve most risky (dangerous) problems at first, perhaps by writing software prototype.

if solution is too inefficient or costly, do not hesistate to cancel 'the whole' of a project.

proceed with tier 4 as well.

4. 'Know the Cost, Know the Time'.

it's basicly all of the simpler solutions (tiers 5 & 6).

try to include the cost (budget, perhaps more) & time limit in planning.

try to learn how to assess how much the tasks will take You to complete them, even if it's almost impossible to do this properly.

it's safe to give Yourself / Your team extra time to reduce stress.

5. 'Know the Problem, Know the Way'.

at this tier, You can start to learn as You have spare time.

otherwise it's tier 6, do not experiment too much but when You are sure, propose solutions.

6. 'Know the Team, Know the Way'.

know who's the boss, know who is responsible for what in your team, follow orders strictly while helping the team as You can.

See also, if You wish: 6 - Tiered path to Victory.


Tactical Programmers.

i think that 'tactical programmers' - programmers who employ problem solving tactics are more efficient at doing their work, and should earn more.

this struggle costs them sanity.

See also: Know Yourself, Know Enemy, Know the Code, Know Enemy?.

'Know the Code, Know the Bug'.



Military tactics are the science and art of organizing a military force, and the techniques for combining and using weapons and military units to engage and defeat an enemy in battle.

In contemporary military science tactics are the lowest of three planning levels:

(i) strategic,
(ii) operational,
(iii) tactical.

The highest level of planning is strategy, how force is translated into political objectives, by bridging the means and ends of war.

The intermediate level, operational level, the conversion of strategy into tactics deals with formations of units.

In the vernacular, tactical decisions are those made to achieve the greatest, immediate value, and strategic decisions are those made to achieve the greatest, overall value, irrespective of the immediate results of a tactical decision.

Source: Wikipedia.


Orders Encoding.

First we enumerate units - give names to each of units.

Alpha - forces leading attack,
Beta - forces securing Alpha Team,
Delta - forces guarding back.

Alpha-Alpha - alpha unit of alpha unit (subgroup).

Then we enumerate orders - give aliases to each of possible orders (serialize).

attack - 1,
hold position - 2,
secure - 3/unit.

then we can say for example: (alpha-1; alpha-beta-2), beta-3/alpha, delta-2.

most specific suborders have priority.

this means:

1. alpha unit attacks, except for beta group of alpha forces which holds position.
2. beta unit secures alpha unit (all orders hold according to their priority, in this case unit secures alpha forces as it was prepared before).
3. delta unit holds position.

then we can encrypt this information & send.

for example, as this can be elaborated as anyone wishes.

i think this can be combined with objects selection in Stitie Space (see: Stitie Machine 1.1 'Sunsail'), and perhaps can be part of 'Ola AH' Programming Language 's semantics & syntax... will experiment with Stitie Machine 1.2 'Satellite' if/when i can.

Taunt Tactic.

it's about making opponent to attack our forces.

it's moving enough of proper forces to a certain position to pose a danger to opponent's positionality or important units.

this move can be elaborated into an ambush lure or if opponent won't react - into positional victory, probably more.


Fast - Start Tactics.

it's about starting fast with small force while bolstering (improving) defenses.

then we retreat to protected location, luring opponents into an ambush.

it's useful when opponent has more offensive forces, and we have better defenses.

to reduce numbers before their forces start to be real threat (reinforcements, alliances etc).