✔️𝗥𝗲𝗹𝗮𝘁𝗶𝗼𝗻𝗮𝗹 𝗣𝗮𝘁𝘁𝗲𝗿𝗻𝘀 𝗠𝗮𝘁𝗰𝗵𝗶𝗻𝗴

✅ 𝗥𝗲𝗹𝗮𝘁𝗶𝗼𝗻𝗮𝗹 𝗣𝗮𝘁𝘁𝗲𝗿𝗻𝘀 𝗠𝗮𝘁𝗰𝗵𝗶𝗻𝗴 is a feature introduced in 𝗖# 𝟵 that enhances the pattern matching capabilities of the language. Pattern matching is a way to compare values against patterns.

✅ 𝗥𝗲𝗹𝗮𝘁𝗶𝗼𝗻𝗮𝗹 𝗣𝗮𝘁𝘁𝗲𝗿𝗻𝘀 𝗠𝗮𝘁𝗰𝗵𝗶𝗻𝗴 specifically allows you to perform pattern matching based on relational comparisons, such as greater than, less than, greater than or equal to, and less than or equal to comparisons.

✅ It is a 𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 programming technique, which means that it focuses on the evaluation of expressions rather than the control flow of your code.

🔥 𝗔𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲𝘀 𝗼𝗳 𝗿𝗲𝗹𝗮𝘁𝗶𝗼𝗻𝗮𝗹 𝗽𝗮𝘁𝘁𝗲𝗿𝗻𝘀 𝗺𝗮𝘁𝗰𝗵𝗶𝗻𝗴:
◾️ 𝗖𝗼𝗻𝗰𝗶𝘀𝗲𝗻𝗲𝘀𝘀: Relational patterns matching can be used to create more concise and readable code.
◾️ 𝗘𝘅𝗽𝗿𝗲𝘀𝘀𝗶𝘃𝗲𝗻𝗲𝘀𝘀: Relational patterns matching can be used to express more complex conditions.

💡 𝗥𝗲𝗹𝗮𝘁𝗶𝗼𝗻𝗮𝗹 𝗣𝗮𝘁𝘁𝗲𝗿𝗻𝘀 𝗠𝗮𝘁𝗰𝗵𝗶𝗻𝗴 is not always the best solution. Sometimes, it is simpler and more efficient to use the traditional way of checking if an expression matches a certain condition.



𝗧𝗵𝗮𝗻𝗸 𝘆𝗼𝘂 𝗳𝗼𝗿 𝗿𝗲𝗮𝗱𝗶𝗻𝗴 😊

✔️ 𝗨𝘀𝗲 '𝗠𝗶𝗻𝗕𝘆' 𝗼𝗿 '𝗠𝗮𝘅𝗕𝘆' 𝗶𝗻𝘀𝘁𝗲𝗮𝗱 𝗼𝗳 𝗼𝗿𝗱𝗲𝗿𝗶𝗻𝗴 𝗮𝗻𝗱 𝘁𝗮𝗸𝗶𝗻𝗴 '𝗙𝗶𝗿𝘀𝘁' 𝗼𝗿 '𝗟𝗮𝘀𝘁'

✅ LINQ 𝗠𝗶𝗻𝗕𝘆 and 𝗠𝗮𝘅𝗕𝘆 are extension methods in C# that allow you to find the minimum or maximum element in a sequence based on a specified property. They were introduced in .𝗡𝗘𝗧 𝟲.

💡 Simplify LINQ expression by Use 𝗠𝗶𝗻𝗕𝘆 or 𝗠𝗮𝘅𝗕𝘆 instead of ordering and taking 'First' or 'Last'

🔥 𝗧𝗵𝗲 𝗮𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲𝘀 𝗼𝗳 𝘂𝘀𝗶𝗻𝗴 𝗟𝗜𝗡𝗤 𝗠𝗶𝗻𝗕𝘆 𝗮𝗻𝗱 𝗠𝗮𝘅𝗕𝘆:
◾️They are more concise and easier to read.
◾️They are more efficient, as they do not need to sort the entire sequence.
◾️They can be used with any type of sequence, including sequences of objects.



𝗧𝗵𝗮𝗻𝗸 𝘆𝗼𝘂 𝗳𝗼𝗿 𝗿𝗲𝗮𝗱𝗶𝗻𝗴 😊

✔️ 𝗡𝘂𝗹𝗹 𝗖𝗼𝗮𝗹𝗲𝘀𝗰𝗶𝗻𝗴 𝗢𝗽𝗲𝗿𝗮𝘁𝗼𝗿

✅ The 𝗡𝘂𝗹𝗹 𝗖𝗼𝗮𝗹𝗲𝘀𝗰𝗶𝗻𝗴 𝗢𝗽𝗲𝗿𝗮𝘁𝗼𝗿 (??) in C# is used to provide a concise way of handling null values. It's particularly useful when you want to provide a default value when a nullable expression evaluates to null. This operator helps make your code cleaner by reducing the need for verbose null checks and conditional statements.

💎 𝗖𝗹𝗲𝗮𝗻 𝗖𝗼𝗱𝗲
✔️ 𝗡𝘂𝗹𝗹 𝗖𝗼𝗮𝗹𝗲𝘀𝗰𝗶𝗻𝗴 𝗢𝗽𝗲𝗿𝗮𝘁𝗼𝗿

✅ The 𝗡𝘂𝗹𝗹 𝗖𝗼𝗮𝗹𝗲𝘀𝗰𝗶𝗻𝗴 𝗢𝗽𝗲𝗿𝗮𝘁𝗼𝗿 (??) in C# is used to provide a concise way of handling null values. It's particularly useful when you want to provide a default value when a nullable expression evaluates to null. This operator helps make your code cleaner by reducing the need for verbose null checks and conditional statements.

🔥 𝗔𝗱𝘃𝗮𝗻𝘁𝗮𝗴𝗲𝘀 𝗼𝗳 𝘂𝘀𝗶𝗻𝗴 𝘁𝗵𝗲 𝗻𝘂𝗹𝗹 𝗰𝗼𝗮𝗹𝗲𝘀𝗰𝗶𝗻𝗴 𝗼𝗽𝗲𝗿𝗮𝘁𝗼𝗿:
◾️ 𝗖𝗼𝗻𝗰𝗶𝘀𝗲 𝗖𝗼𝗱𝗲: It reduces the need for writing lengthy null-checking code, resulting in more compact and clear expressions.
◾️ 𝗥𝗲𝗮𝗱𝗮𝗯𝗶𝗹𝗶𝘁𝘆: The operator is well-known among C# developers, so it improves the readability of your code by providing a common and recognizable pattern.
◾️ 𝗔𝘃𝗼𝗶𝗱𝗶𝗻𝗴 𝗗𝘂𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻: It eliminates the need to repeat the same null-checking logic throughout your codebase.
◾️ 𝗗𝗲𝗳𝗮𝘂𝗹𝘁 𝗩𝗮𝗹𝘂𝗲𝘀: It's particularly useful when you want to provide default values for nullable variables.



𝗧𝗵𝗮𝗻𝗸 𝘆𝗼𝘂 𝗳𝗼𝗿 𝗿𝗲𝗮𝗱𝗶𝗻𝗴 😊

✔️ 𝗥𝗲𝘁𝗵𝗿𝗼𝘄𝗶𝗻𝗴 𝗘𝘅𝗰𝗲𝗽𝘁𝗶𝗼𝗻𝘀

✔️ 𝗥𝗲𝘁𝗵𝗿𝗼𝘄𝗶𝗻𝗴 𝗘𝘅𝗰𝗲𝗽𝘁𝗶𝗼𝗻𝘀

❌ Exceptions should not be explicitly rethrown because it can lead to loss of information about the original exception. When an exception is thrown, it creates a stack trace that records the call stack at the point where the exception was thrown. This stack trace can be helpful for debugging the exception.

✅ The preferred way to handle an exception is to catch it and then take some action to resolve the problem. This could involve logging the exception, displaying an error message to the user, or taking some other corrective action. If the exception cannot be resolved, it should be rethrown, but without specifying the exception explicitly. This will preserve the original stack trace information and make debugging easier.

💡 When you want to wrap the exception in a different exception type. In this case, you should create a new exception object and then throw that object. Do not simply rethrow the original exception object.


𝗧𝗵𝗮𝗻𝗸 𝘆𝗼𝘂 𝗳𝗼𝗿 𝗿𝗲𝗮𝗱𝗶𝗻𝗴 😊

✔️𝗦𝘄𝗶𝘁𝗰𝗵 𝗘𝘅𝗽𝗿𝗲𝘀𝘀𝗶𝗼𝗻

✔️𝗦𝘄𝗶𝘁𝗰𝗵 𝗘𝘅𝗽𝗿𝗲𝘀𝘀𝗶𝗼𝗻

🕯 The 𝘀𝘄𝗶𝘁𝗰𝗵 𝘀𝘁𝗮𝘁𝗲𝗺𝗲𝗻𝘁 has been part of C# since its early versions. It allows you to evaluate an expression against a series of case values and execute code blocks based on the matched case.
Each case value must be a constant value that is known at compile-time. After a case block is executed, you usually need to include a break statement to exit the switch statement.

💡 The 𝘀𝘄𝗶𝘁𝗰𝗵 𝗲𝘅𝗽𝗿𝗲𝘀𝘀𝗶𝗼𝗻 was introduced in C# 8 as a more concise and expressive alternative to the traditional switch statement. It allows you to assign a value to a variable based on the value of an expression.
In a switch expression, you use the => syntax to specify the value to assign if the expression matches a certain case. The _ is a discard symbol and is used as the "default" case.

✅ Both the 𝘀𝘄𝗶𝘁𝗰𝗵 𝘀𝘁𝗮𝘁𝗲𝗺𝗲𝗻𝘁 and the 𝘀𝘄𝗶𝘁𝗰𝗵 𝗲𝘅𝗽𝗿𝗲𝘀𝘀𝗶𝗼𝗻 are used for similar purposes, the switch expression offers more concise syntax and greater flexibility for pattern matching and value assignment, making it a more powerful tool for modern C# development.


🤔 Which one do you prefer?


𝗧𝗵𝗮𝗻𝗸 𝘆𝗼𝘂 𝗳𝗼𝗿 𝗿𝗲𝗮𝗱𝗶𝗻𝗴 😊

✔️ One Dot Per Line

✔️ One Dot Per Line

✅ "One dot per line" is a principle of writing clean code in C# (and other programming languages) that suggests breaking chained method calls and property accesses onto separate lines, placing each dot on a new line. This helps to enhance code readability and maintainability by making the code structure clear and easier to follow.


✅Advantages of using "One dot per line" approach:

- Improved Readability: By placing each dot on a separate line, the code becomes more readable, especially when dealing with long chains of method calls or nested property access.

- Reduced Horizontal Scrolling: Code lines become shorter, reducing the need for horizontal scrolling while reading the code, which is often considered less pleasant and harder to follow.

- Easier Debugging: With each method call or property access on a separate line, it becomes easier to set breakpoints and debug specific parts of the code.

- Easier Code Review: The code becomes more structured, making it easier for colleagues to review and provide feedback on the code.


✅The "One dot per line" rule is a useful coding practice that can help to improve the readability, maintainability, and overall quality of your code.


Thank you for reading 😊

✔️ C#: Exceptions should not be thrown in finally blocks

✔️ C#: Exceptions should not be thrown in finally blocks

✳️If an exception is already being thrown within the try block or caught in a catch block, throwing another exception in the finally block will override the original exception. This means that the original exception’s message and stack trace will be lost, potentially making it challenging to diagnose and troubleshoot the root cause of the problem.


✳️Here are a few reasons why throwing exceptions from finally blocks is discouraged:

- Masking the original exception: If an exception is thrown in a finally block, it can overwrite the original exception that caused the try block to exit. This can make it harder to debug the actual cause of the problem, as you won't have access to the original exception information.

- Unpredictable behavior: When an exception is thrown from a finally block, it may interfere with the exception handling mechanism itself. For example, if the catch block outside the finally block handles the exception, throwing another exception from finally will disrupt the expected control flow.

- Resource leaks: The primary purpose of a finally block is to release resources or perform cleanup tasks. If an exception is thrown from the finally block, these cleanup operations may not be completed, leading to resource leaks or inconsistent program state.


✳️Instead of throwing exceptions from finally blocks, it's better to handle exceptions appropriately within the try, catch, and finally blocks. If an exception occurs in the finally block, it's usually best to log the error or take some alternative action to ensure proper cleanup without disrupting the main exception handling flow.


Thank you for reading 😊

✔️ C#: Replace if statement with Null Conditional Operator

✔️ C#: Replace if statement with Null Conditional Operator

✳️The null conditional operator, also known as the null propagation operator or the safe navigation operator, is a feature introduced in C# 6.0 that allows you to write cleaner and more concise code when dealing with potentially null reference types.

✳️The null conditional operator is represented by a question mark followed by a period (?.) and is used to access members or invoke methods on an object that may be null. If the object is null, the expression returns null instead of throwing a null reference exception.

✳️Checking for null is probably what you do quite often, for example, to prevent a null reference exception when invoking properties. Using if-statements for numerous null checking makes code cumbersome and lengthy.

✳️The null conditional operator allows checking one or more expressions for null in a call chain, which is called null propagation. Such a notation can be written in a single line whereas a number of if-else statements typically occupy many lines.


💡In the comments I attached an example in JavaScript: Replace if statement with Optional chaining.


✳️ Can you make the example cleaner ? Do you have any other suggestions?

Thank you for reading 😊

✔️ Avoid else after return

✔️ Avoid else after return

✳️ This principle is a guideline in clean code development that suggests avoiding the use of an else statement immediately after a return statement in a function or method.

✳️ When a return statement is encountered in a function, it immediately exits the function and returns control to the calling code. Any code following the return statement within the same block will not be executed. In many cases, including an else statement after a return is redundant and can be safely removed.

✳️ Following the "Avoid else after return" principle helps in writing cleaner, more maintainable code by simplifying control flow and improving code readability.

✳️ In the attached image, an example of how to apply this principle.

❌ Bad: Violates the "Avoid else after return" principle.

✔️ Good: Refactoring the code, the else clause have been eliminated.

💡 Short: The conditional operator (? :) is used to directly return either "Pass" or "Fail" based on the condition. This eliminates the need for an if-else statement.

✔️ Function names should say what they do

✔️ Function names should say what they do

Function names should be clear and descriptive, providing a clear indication of what the function does. This makes it easier for other developers to understand the purpose of the function without having to read through the implementation details.

This is important because function names serve as a form of documentation and make it easier for other developers to understand the purpose and behavior of the code.

Following this principle helps make your code more readable, understandable, and maintainable.

Thank you for reading 😊

✔️ Use searchable names

We will read more code than we will ever write. It's important that the code we do write must be readable and searchable. By not naming variables that end up being meaningful for understanding our program, we hurt our readers. Make your names searchable.

Using searchable names means that variable, function, and class names should be clear and unambiguous so that other developers can easily understand what they do.

Thank you for reading 😊