A Task represents completion, not a promise of another thread

First, build a mental model

An async method runs until it reaches an await that must suspend. Its Task represents eventual completion. Awaiting lets the method resume when the result is available; asynchronous work and parallel CPU work are different concepts.

1. Task represents completion without a result; Task<T> also represents a typed result.
2. Calling an async method does not automatically create a dedicated background thread.
3. await observes completion and propagates failure. Blocking with Result or Wait can waste threads and can deadlock in some synchronization contexts.
4. For independent operations, start both then await Task.WhenAll; do not overlap operations that have an ordering dependency.

static async Task<int> ReadScoreAsync()
{
    await Task.Delay(10);
    return 7;
}

Task<int> pending = ReadScoreAsync();
Console.WriteLine("started");
int score = await pending;
Console.WriteLine(score);

1. Start

   The method begins and returns a Task representing its eventual completion.

2. Caller continues

   The caller prints started before it prints the awaited result.

3. Resume

   After pending completes, await yields 7 and the next line prints it.