Until the 30th of September get 30% off any course on Dometrain with code BTS30: https://dometrain.com/?coupon_code=BTS30
Subscribe to my weekly newsletter: https://nickchapsas.com

Become a Patreon and get special perks: https://www.patreon.com/nickchapsas

Hello, everybody. I'm Nick, and in this episode of Code Cop, I will explain why you should be using FirstOrDefault over Find in C# even though people on LinkedIn might tell you otherwise.

Workshops: https://bit.ly/nickworkshops

Don't forget to comment, like and subscribe :)

Social Media:
Follow me on GitHub: https://github.com/Elfocrash
Follow me on Twitter: https://twitter.com/nickchapsas
Connect on LinkedIn: https://www.linkedin.com/in/nick-chapsas

Keep coding merch: https://keepcoding.shop

#csharp #dotnet #codecop

Nick Chapsas

Nick explains why using the Find method over FirstOrDefault in .NET lists can be a misleading practice. He highlights performance comparisons and how optimizations in .NET 9 make FirstOrDefault faster, emphasizing the importance of understanding such nuances to avoid harming code and performance.

Stop Using FirstOrDefault in .NET! | Code Cop #021

People will read the title and stop using FirstOrDefault. :)

The title feels a little bit clickbaity innit

Waaaaaoooo ! We can save micro or nano seconds when finding a person by ID inside an array of 1000 persons…
And during this time, developers do simple SQL queries without indexes that took few seconds 🤣… This is for me a false performance debate this video !

FirstOrDefault is a generic method that can be used on various data-structuers. Saving few nano-seconds won’t matter. If I was working on a domain where every nanosecond saved yielded a value then I don’t think I would be picking C#.