[Welcome to Sensei's Library!]

StartingPoints
ReferenceSection
About


Paths
SequencingQuestions

Referenced by
Kikashi
FocalPoint
Press
BasicTechniquesOfGo
OrderOfPlay
KanazawaProblem52...
OngoingGame1
Premature
EnglishGoTerms/Di...
KikashiSenteDiscu...
AttachCrosscutCor...
DoubleExtensions
BlackSheepRengo2003
ForcingMoveMisund...
PushingBattlesInJ...
PushingBattleAndC...
KanazawaProblem88...
KanazawaProblem88...
34PointHighApproa...
34PointWithParall...

 

timing
Path: SequencingQuestions   · Prev: Tejun   · Next: Tewari
  Difficulty: Expert   Keywords: Strategy

While it is clear that the timing concept in Go is well worth a node, for the sake of backlinks alone, it isn't so clear what to put here.

Tactical timing

[Diagram]
Which order?

After these joseki plays, Black will play the atari moves at a and b - in some order. Which is correct?


[Diagram]
Bad timing (7 connects)

If Black gets the timing wrong, as here, White can exploit the presence of W2 to make a net on the outside with W8. Now BC is misplaced. We assume that Black connects the ko, since there are no ko threats in the opening.


[Diagram]
Correct timing

Black should play the other atari first. In this case White's chance at resistance with c next gives Black an outside ponnuki. White cannot get a good result that way.



Strategic timing

Some aspects:

  • Go is ruled by minimal play - play something only because it is required - so timing is 'recognition of necessary plays'. According to this, 'urgent points before big points' is the master proverb.
  • The idea of a probing type of strategy is to get commitment from the opponent first; and then decide timing and choice of direction.

Theoretically speaking, perhaps the game divides up as game temperature model, plus real timing issues which aren't just a question of sente sidetracks.

Charles Matthews



Path: SequencingQuestions   · Prev: Tejun   · Next: Tewari
This is a copy of the living page "timing" at Sensei's Library.
(OC) 2004 the Authors, published under the OpenContent License V1.0.