Added Tips and Tricks.

Signed-off-by: Someshdiwan <[email protected]>

Author: Someshdiwan

Section18ExceptionHandling/src/CustomException.txt

@@ -0,0 +1,26 @@
+Best practices for creating custom exceptions
+There are some basic pointers to keep in mind while creating your own custom exceptions:
+
+Use descriptive names: Naming your custom exception clearly and descriptively helps to communicate the cause of the
+exception to whoever reads your code.
+
+This makes it easier to debug errors and understand what went wrong.
+
+Document your exceptions: This includes adding comments to your code that explain what the exception is for,
+what conditions trigger it, and how it should be handled.
+
+This will make it easier for other developers to understand how to use your custom exceptions in their own code.
+
+Don't overuse exceptions: Only use exceptions for exceptional conditions. Overusing exceptions can make your code harder to read and debug.
+
+Be consistent: Follow a consistent naming and formatting convention for your custom exceptions.
+
+Test your exceptions: This means creating test cases that trigger the exception and verifying that the exception is
+thrown correctly.
+
+Also, test how your code handles the exception, and make sure it reacts appropriately without crashing or causing other errors.
+
+By following these best practices, you can create custom exceptions that are effective,
+easy to use and help improve the overall reliability and maintainability of your code.
+
+So keep these tips in mind as you create your own custom exceptions and happy coding!