Should parameter names describe their object type?

I'm unsure whether parameter names should describe their object types or if shorter, more concise names are preferable. Consider the following two method signatures: public void PrintPoint(MyVeryCustomPoint point) { Console.WriteLine($"X: {point.X}, Y: {point.Y}, Z: {point.Z}"); } Versus: public void PrintPoint(MyVeryCustomPoint myVeryCustomPoint) { Console.WriteLine($"X: {myVeryCustomPoint.X}, Y: {myVeryCustomPoint.Y}, Z: {myVeryCustomPoint.Z}"); } Since this is a very simple demonstration, using the first version looks better. But the second approach improves clarity by making the parameter’s type more explicit. In the end I wonder if it is good practice to include types in parameter names like the second one for sake of consistency? I’m looking for general conventions or standards, rather than a specific use case. I work on a complex application where some methods/endpoints use the first approach, while others use second one without a clear pattern, so I wondered if it would be worth to standardize this.

Mar 10, 2025 - 08:57

I'm unsure whether parameter names should describe their object types or if shorter, more concise names are preferable.

Consider the following two method signatures:

public void PrintPoint(MyVeryCustomPoint point)
{
    Console.WriteLine($"X: {point.X}, Y: {point.Y}, Z: {point.Z}");
}

Versus:

public void PrintPoint(MyVeryCustomPoint myVeryCustomPoint)
{
    Console.WriteLine($"X: {myVeryCustomPoint.X}, Y: {myVeryCustomPoint.Y}, Z: {myVeryCustomPoint.Z}");
}

Since this is a very simple demonstration, using the first version looks better. But the second approach improves clarity by making the parameter’s type more explicit.

In the end I wonder if it is good practice to include types in parameter names like the second one for sake of consistency?

I’m looking for general conventions or standards, rather than a specific use case. I work on a complex application where some methods/endpoints use the first approach, while others use second one without a clear pattern, so I wondered if it would be worth to standardize this.