Naming conventions in C# - Time & Space Complexity

Time Complexity: Naming conventions in C#

O(1)

Understanding Time Complexity

We look at how following naming rules affects the speed of writing and reading code.

Does using good names change how fast the program runs?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

public class Person
{
    public string FirstName { get; set; }
    public string LastName { get; set; }

    public void PrintFullName()
    {
        Console.WriteLine($"{FirstName} {LastName}");
    }
}

This code defines a class with properties and a method using standard naming styles.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: There are no loops or repeated operations here.
• How many times: The code runs each statement once when called.

How Execution Grows With Input

Since there are no loops or repeated steps, the time to run does not grow with input size.

Input Size (n)	Approx. Operations
10	About 10 simple steps
100	Still about 10 simple steps
1000	Still about 10 simple steps

Pattern observation: The work stays the same no matter how big the input is.

Final Time Complexity

Time Complexity: O(1)

This means the program runs in constant time, unaffected by input size.

Common Mistake

[X] Wrong: "Using longer or more descriptive names slows down the program's running speed."

[OK] Correct: Naming only affects how humans read and write code, not how fast the computer runs it.

Interview Connect

Understanding naming conventions shows you care about clear code, which helps teams work better together.

Self-Check

"What if we added a loop to create many Person objects? How would the time complexity change?"

Practice

1. Which naming convention is correct for a C# class name?

easy

A. MyClass

B. myClass

C. my_class

D. MYCLASS

Solution

1. Step 1: Understand class naming convention in C#

   Classes in C# use PascalCase, where each word starts with a capital letter and no underscores are used.

2. Step 2: Compare options with PascalCase

   MyClass uses PascalCase correctly. my_class uses snake_case, myClass uses camelCase, and MYCLASS uses all uppercase (incorrect for classes).

3. Final Answer:

   MyClass -> Option A

4. Quick Check:

   Class names use PascalCase = MyClass [OK]

Hint: Classes always start with uppercase letters (PascalCase) [OK]

Common Mistakes:

• Using camelCase for class names
• Using underscores in class names
• Using all uppercase for class names

2. Which of the following is the correct way to name a local variable in C#?

easy

A. localVariable

B. LocalVariable

C. LOCALVARIABLE

D. local_variable

Solution

1. Step 1: Recall local variable naming rules

   Local variables in C# use camelCase, starting with a lowercase letter and no underscores.

2. Step 2: Match options to camelCase

   localVariable uses camelCase correctly. LocalVariable uses PascalCase, LOCALVARIABLE uses all uppercase, and local_variable uses underscores.

3. Final Answer:

   localVariable -> Option A

4. Quick Check:

   Local variables use camelCase = localVariable [OK]

Hint: Local variables start lowercase, no underscores (camelCase) [OK]

Common Mistakes:

• Starting local variables with uppercase letters
• Using underscores in local variable names
• Using all uppercase for local variables

3. What will be the output of the following code snippet?

const int MAX_COUNT = 10;
int maxCount = 5;
Console.WriteLine(MAX_COUNT);
Console.WriteLine(maxCount);

medium

A. Compilation error

B. 10 and 5

C. 5 and 10

D. maxCount and MAX_COUNT

Solution

1. Step 1: Identify constant and variable values

   MAX_COUNT is a constant with value 10, maxCount is a variable with value 5.

2. Step 2: Understand Console.WriteLine outputs

   Console.WriteLine(MAX_COUNT) prints 10, Console.WriteLine(maxCount) prints 5.

3. Final Answer:

   10 and 5 -> Option B

4. Quick Check:

   Constants print their value = 10, variables print their value = 5 [OK]

Hint: Console.WriteLine prints the values, not the names [OK]

Common Mistakes:

• Confusing constant and variable values
• Expecting names to print instead of values
• Thinking naming affects output values

4. Identify the error in the following C# code snippet:

public class exampleClass {
    public int MyProperty { get; set; }
    private int myField;
}

medium

A. Field name should be PascalCase

B. Property name should be camelCase

C. Class name should be PascalCase

D. No errors, code is correct

Solution

1. Step 1: Check class naming convention

   Class names must use PascalCase, but 'exampleClass' starts with lowercase.

2. Step 2: Check property and field naming

   Property 'MyProperty' uses PascalCase correctly; field 'myField' uses camelCase correctly.

3. Final Answer:

   Class name should be PascalCase -> Option C

4. Quick Check:

   Class names = PascalCase, exampleClass is incorrect [OK]

Hint: Class names always start uppercase (PascalCase) [OK]

Common Mistakes:

• Using lowercase for class names
• Confusing property and field naming rules
• Thinking camelCase is okay for classes

5. You have a constant for the maximum number of users and a method parameter for the current user count. Which naming is correct in C#?

public const int max_users = 100;
public void UpdateUserCount(int CurrentUserCount) { }

hard

A. MaxUsers and currentusercount

B. maxUsers and CurrentUserCount

C. max_users and current_user_count

D. MaxUsers and currentUserCount

Solution

1. Step 1: Naming for constants

   Constants use PascalCase, so MaxUsers is correct, max_users is incorrect.

2. Step 2: Naming for method parameters

   Method parameters use camelCase, so currentUserCount is correct, CurrentUserCount is incorrect.

3. Final Answer:

   MaxUsers and currentUserCount -> Option D

4. Quick Check:

   Constants PascalCase, parameters camelCase = MaxUsers, currentUserCount [OK]

Hint: Constants PascalCase, parameters camelCase (start lowercase) [OK]

Common Mistakes:

• Using camelCase for constants
• Starting parameters with uppercase letters
• Using underscores in parameters