daal wrote:
What is difficult is that even Big and Not Big depend on sente and followup.
The difficulty of figuring out sente was the main reason, IMHO, the go programmers failed to come up with a good evaluation function in four decades of collective effort. If they had, I doubt if today's bots would be using winrates.

However, humans understand the concept of sente, if fuzzily. Sente is important for evaluating local positions, because after a sente is played with sente, the resulting position has the same value as the initial position, and is easier to count. If you start with evaluating local positions, you will develop your sense of sente.

Quote:
One question though: How would you go about deciding between a sente move and a big gote move?
There's good news and bad news. Let's start with the bad news.
Bad news 1). You may want to save the sente for a ko threat.
Silver lining. If you are even thinking about playing the sente, that is probably not the case.
Bad news 2). You can only be sure that the big gote is right if it is quite big. Using the common way of counting — which I do not recommend, but which you probably are already using — the gote normally has to be bigger than both the sente move plus its threat.
Silver lining. A gote that big has probably already been played.
Now for the good news.
Good news 1). If you are not saving the sente as a ko threat (probably the case) and the threat of the sente is bigger than the big gote, so that your opponent should answer the sente, play the sente.
Good news 1a). That is very likely to be the case.
These are the basics. If we consider the rest of the board, other considerations apply.
There is a rule of thumb about doubling the size of a sente (using, cough, the common way of counting) in order to compare it with a gote. This actually applies to reverse sente. You can normally save a sente to use as a possible ko threat until just before your opponent will play the reverse sente. That's why it is useful for sente, as well.