Milad Naseri In remembrance

𝐑𝐞𝐜𝐨𝐫𝐝 𝐯𝐬 𝐂𝐥𝐚𝐬𝐬 𝐢𝐧 𝐂#: 𝐖𝐡𝐞𝐧 𝐭𝐨 𝐔𝐬𝐞 𝐄𝐚𝐜𝐡? Sometimes we need to define types that don’t contain complex behavior and are simply meant to hold data. These are often referred to as 𝐏𝐎𝐃 (Plain Old Data) types. Implementing such types with a regular class can become repetitive: you define fields, write a constructor, assign parameters to fields, and sometimes even implement equality members. This adds unnecessary boilerplate when all we need is a clean data container. 𝐖𝐡𝐲 𝐑𝐞𝐜𝐨𝐫𝐝𝐬? C# introduced records to solve exactly this problem. Records are designed specifically for data-holding scenarios and are extremely concise to write. By default, they are immutable, meaning once an instance is created, its properties cannot be changed. If you attempt to modify one, the compiler will warn you. This immutability is a major advantage—especially in multi-threaded applications, where preventing unexpected data changes helps avoid concurrency issues and makes the code more reliable. 𝐈𝐧 𝐒𝐮𝐦𝐦𝐚𝐫𝐲: If your type is intended primarily to store data rather than behavior, records are often the ideal choice: Less boilerplate More readable code Built-in value-based equality Safe, immutable design (great for multi-threading) 𝐁𝐚𝐬𝐞𝐝 𝐨𝐧 𝐦𝐲 𝐞𝐱𝐩𝐞𝐫𝐢𝐞𝐧𝐜𝐞… From what I've seen in real-world projects, records work especially well for: 𝐃𝐓𝐎𝐬 / 𝐕𝐢𝐞𝐰𝐌𝐨𝐝𝐞𝐥𝐬 𝐃��𝐦𝐚𝐢𝐧 𝐌𝐨𝐝𝐞𝐥𝐬 Do you know other scenarios where records shine? Share your thoughts in the comments—I’d love to hear your perspective! #dotnet #csharp #programming #softwareengineering #step2 #cs_internship #csharp https://lnkd.in/d38X4Qep

5

I see detractors frustrated why their causes have been unsuccessful and the Iranians' cause has gathered global momentum. Of course Iranians have the right for a free and safe life. But the difference is that this group is culturally aligned with education, success and achievement. They might be your excellent engineering colleague, your prof or your boss. Well, this is how you effect change!

3