Nice breakdown explaining why properties, tuples, etc. are useful.

Properties in particular are often misunderstood with the "Just use fields" crowd, which is unfortunate. Kotlin, in my view, got it right by making properties built-in behavior with member-level val and var declarations. Brilliant design choice. Kotlin also leverages properties as state abstraction to make lazy values and delegation extensions of this built-in behavior. Would be awesome if C# would follow Kotlin's example:

Using tuples for multiple return values is also an underused strategy. Although I think C# should extend var coverage to method return types for this, that or provide a separate keyword for it, like manifold's auto (Java):

private auto GetSpawnPoint(Vector3 inputPosition)
{
    Vector3 position = new Vector3(inputPosition.x, 0, inputPosition.z);
    Quaternion rotation = Quaternion.Euler(0, 180, 0);

    return (position, rotation);
}