MWaseemZakir's platform  covers topics related to software development, technology trends, and coding tutorials. Through articles, tutorials, and personal anecdotes, MWaseemZakir offers insights into programming languages, development frameworks, and best practices in software engineering. Readers can learn about software design principles, development methodologies, and emerging technologies to enhance their coding skills and build high-quality software applications.

Waseem .NET Newsletter

This post provides clean code tips for .NET developers, focusing on giving meaningful names, avoiding null returns, keeping class and method sizes small, not reinventing the wheel, and using appropriate tools or IDEs. It also offers practical examples and suggestions for better coding practices in .NET projects.

EP 66 : Clean Code Tips for .NET Developers - Part I

Whenever you’re ready, there are 2 ways I can help you:

I’m sorry, but advising to throw exception over returning null when a user is not found?
With the reasoning that returning null can lead to exception if someone try to access a property? Well yes, and throwing exception WILL lead to exception, for something that is an expected outcome?
That’s all I needed to read to know to stay away from this article

m following you on linkedIn. Your contents are very helpful. Keep it up.