AutoMapper: Find Usages
AutoMapper is a popular .NET library for automating object-to-object mapping. It allows developers to easily map objects between different types, reducing the amount of boilerplate code required for data transfer and transformation. But it's easy to miss data flow using AutoMapper because it's not immediately obvious where the mapping is happening. For example, you want to know where a specific property is set, but the IDE says "Usages were not found".
I thought about this problem and came up with a solution.
Collections search
During interviews, we often hear — or say ourselves — that searching in an array is slower than in a hashtable. Some might even recall that array search has linear complexity, or O(n), while a hash table has constant complexity, O(1). But does this hold true in practice? What if there are situations where searching in an array turns out to be faster? Let's not rush to conclusions.
Dapper: How caching can be harmful
Dapper is a popular library that allows mapping objects from a database to C# types. Unlike Entity Framework, it is not a full-fledged ORM, but it is very popular due to its minimalism. In this article, I will explain how the default behavior can lead to a significant increase in memory consumption.
String of Digits
A popular task is to check if a string contains only digits. For example, you need to check if the user entered the correct phone number, index or a tax code of an organization. There are several ways to solve this task, which differ in their efficiency. Let's take a look at the most popular ones.
Any() vs Count: part 2
In Part 1, we compared Any() and Count methods for different collections and proposed optimization approaches.