CLEAN-CODE
در این قسمت از آموزش های کد نویسی تمیز، به مبحث جالب و مشهور Solid رو با همدیگه بررسی میکنیم .
در قسمت اول در مورد Interface Segregation Principle صحبت میکنیم و اینکه چجوری این نکته رو در کدهامون رعایت کنیم .

تعریف :‌ این مبحث میگه شما نباید کلاینت ، یا کلاسی را مجبور به پیاده سازی از متدهایی یک اینترفیس کنید که اصلا چنین فیچری برای این آبجکت تعریف نمیشود و مجبوریم پیاده سازی نشده آنهارا رها کنیم .

#clean_code [010]
#SOLID
#Interface_Segregation_Principle

CLEAN-CODE
در این قسمت از آموزش های کد نویسی تمیز، به مبحث جالب و مشهور Solid رو با همدیگه بررسی میکنیم .
در قسمت اول در مورد Dependency Inversion Principle صحبت میکنیم و اینکه چجوری این نکته رو در کدهامون رعایت کنیم .

تعریف :‌ این قانون به شما میگویید، نباید ماژول سطح بالاتر به ماژول سطح پایین تر مستقیم به هم متصل باشند، در اصل ماژول سطح بالاتر باید به انتزاعی از ماژول صبح پایین متصل باشد .

#clean_code [011]
#SOLID
#Dependency_Inversion_Principle

CLEAN-CODE
در این قسمت از آموزش های کد نویسی تمیز، به مبحث جالب Design Pattern‌ها وارد میشیم .
همین الان بگم شما با یادگیری و استفاده از این دیزاین ها قرار نیست سینیور بشید 😂😂😂 .

#clean_code [012]
#Design_Pattern

CLEAN-CODE
در ادامه مبحث Design Pattern ها به الگو و پترن جذاب و جالب Memento میرسیم .

تعریف :‌ در این الگو قرار است ، وضعیت ها و استیت های قبلی یک آبجکت رو ذخیره کنیم و در صورت نیاز استفاده کنیم، همین وبس 😜 .

#clean_code [013]
#Design_Pattern
#Behavioral_Pattern
#Memento

CLEAN-CODE
در این قسمت از آموزش های کد نویسی تمیز، به مبحث جالب و مشهور Solid رو با همدیگه بررسی میکنیم .
در قسمت اول در مورد Liskov Substitution Principle صحبت میکنیم و اینکه چجوری این نکته رو در کدهامون رعایت کنیم .

تعریف :‌ در تمام سیستم بتوان از کلاس فرزند بجای کلاس پدر استفاده کرد و در این درحالی است که کارایی سیستم مختل نشود .

#clean_code [009]
#SOLID
#Liskov_Substitution_Principle

با سلام خدمت همه دستان عزیز
در این کانال قصد دارم تا نکاتی که چه از سر تجربه چه از سر مطالعه های پراکنده بدست آوردم رو به اشتراک بزارم .
هرکدوم از دوستان نظر، ایده، یا مبحثی که بخوان در مورد اون آموزشی ببیند، بهم اطلاع بدن و اگر بتونم یا بلد باشم سعی میکنم آموزشی که میخوان رو تهیه کنم و قرار بدم تا هم خودشون و هم بقیه بتونن استفاده کنند .
آیدی من :‌ https://news.1rj.ru/str/MrERROR2

CLEAN-CODE
در ادامه مبحث Design Pattern ها به الگو و پترن جذاب و جالب Memento میرسیم .

در این قسمت، پروژه قبلی رو ریفکتور میکنیم و سعی میکنیم بوسیله این پترن بازنویسی کنیم.

تعریف :‌ در این الگو قرار است ، وضعیت ها و استیت های قبلی یک آبجکت رو ذخیره کنیم و در صورت نیاز استفاده کنیم، همین وبس 😜 .

#clean_code [014]
#Design_Pattern
#Behavioral_Pattern
#Memento

CLEAN-CODE
در ادامه مبحث Design Pattern ها به الگو و پترن جذاب و جالب State Pattern میرسیم .

تعریف :‌ اگر هر وقت در یک آبجکت، بر اساس استیت و وضعیتی که اون آبجکت داره ، قراره کارهای خاصی انجام بشه یا نشه، بدونین میتونین از این پترن استفاده کنین .

#clean_code [015]
#Design_Pattern
#Behavioral_Pattern
#State_Pattern

CLEAN-CODE
در ادامه مبحث Design Pattern ها به الگو و پترن جذاب و جالب State Pattern میرسیم .

تعریف :‌ اگر هر وقت در یک آبجکت، بر اساس استیت و وضعیتی که اون آبجکت داره ، قراره کارهای خاصی انجام بشه یا نشه، بدونین میتونین از این پترن استفاده کنین .

#clean_code [016]
#Design_Pattern
#Behavioral_Pattern
#State_Pattern

CLEAN-CODE
در ادامه مبحث Design Pattern ها به الگو و پترن جذاب و جالب Strategy Pattern میرسیم .

تعریف :‌ اگر احتمالا داخل یک پروژه ، یه متد دارین که شروط بسیار زیادی داره و بر اساس شروط داده ها و محاسباتی که داره انجام میده تغییر میکنن، این پترن فیت کار شماس 🥳😅😜 .

#clean_code [017]
#Design_Pattern
#Behavioral_Pattern
#Strategy_Pattern

CLEAN-CODE
در ادامه مبحث Design Pattern ها به الگو و پترن جذاب و جالب Strategy Pattern میرسیم .

در این قسمت، طراحی قبلی خودمون رو ریفکتور میکنیم و سعی میکنیم بوسیله این الگو، طراحی زیبا و بهتری داشته باشیم .

تعریف :‌ اگر احتمالا داخل یک پروژه ، یه متد دارین که شروط بسیار زیادی داره و بر اساس شروط داده ها و محاسباتی که داره انجام میده تغییر میکنن، این پترن فیت کار شماس 🥳😅😜 .

#clean_code [018]
#Design_Pattern
#Behavioral_Pattern
#Strategy_Pattern

CLEAN-CODE
در ادامه مبحث Design Pattern ها به الگو و پترن جذاب و جالب Iterator Pattern میرسیم .

تعریف :‌ اگر قرار باشه یک شئی رو بسازیم که کار کالکشن هارو انجام بده، بهتر براش یک Signature خاص بسازیم تا درصورت تغییر نوع کالکشن زمین گیر نشیم 😐😢.

#clean_code [019]
#Design_Pattern
#Behavioral_Pattern
#Iterator_Pattern

سلام دوستان .
توی این مقاله یه روش جالب برای ولیدیشن قرار دادم . بد نیست بخونید .
اگر DDD کار میکنید و Value object هارو میشناسید ولی خوب نمیتونید موجودیتشون رو درک کنید، این مقاله میتونه بهتون کمک کنه که درک بهتری پیدا کنید .
خیلی سادس ولی ایده پشتش خیلی جالبه .
https://www.linkedin.com/pulse/parse-dont-validate-mohammad-taghi-khademi-kzxxf/?trackingId=Y%2B2l62ieR9yYnaDvrIFo7w%3D%3D

🚀 Brain bytes: Unlock the Power of .NET!

🧠 Today’s Byte: What is CLR (Common Language Runtime)?

---

### 🛠 What is CLR?

The CLR is the backbone of the .NET ecosystem. It powers every .NET application, handling the complex tasks developers often worry about, such as memory management, security, and program reliability.
With CLR, your code runs in a managed environment, making .NET applications robust and scalable.

Sample:
When you run a .NET app, the CLR automatically manages your program’s memory so you don’t have to worry about allocation and freeing up space.

---

#### 🧠 Memory Management

Expert Insight:
Manual memory management can cause leaks and crashes. CLR automates allocation and deallocation, using a garbage collector that tracks object lifetimes and cleans up unused memory, letting developers focus on business logic, not infrastructure.

Sample:

string name = "Brain bytes";

The CLR allocates and manages the memory for this string. When it’s no longer needed, it is cleaned up automatically.

---

#### 🛡 Security

Expert Insight:
CLR enforces strict security boundaries. It uses Code Access Security (CAS) and permissions to ensure that your application—and any third-party libraries—cannot overstep their rights. This minimizes risks from malicious code or accidental misuse.

Sample:

using System.IO;

File.ReadAllText("C:\\Windows\\system.ini"); // Will fail if your app lacks permission

Unauthorized access triggers a SecurityException, protecting the system.

---

#### ⚡️ Exception Handling

Expert Insight:
Instead of cryptic error codes, CLR provides a structured exception model. Developers write resilient code with try-catch blocks, ensuring that unexpected events are caught and handled gracefully, improving user experience and program stability.

Sample:

try
{
    int[] arr = new int[2];
    Console.WriteLine(arr[5]); // Out of bounds!
}
catch (IndexOutOfRangeException ex)
{
    Console.WriteLine("Oops! Array index error: " + ex.Message);
}

CLR catches the error and allows you to recover or inform the user.

---

#### 🗑 Garbage Collection

Expert Insight:
Garbage collection is a hallmark of managed environments. CLR’s garbage collector frees memory from objects no longer in use, preventing leaks and fragmentation. This leads to efficient, long-running applications without manual cleanup.

Sample:

void CreateObjects()
{
    var tempObj = new object();
} // tempObj is no longer used after this method

CLR’s garbage collector reclaims memory for tempObj automatically.

---

### 👨‍💻 Sample C# Code

using System;

class Program
{
    static void Main()
    {
        Console.WriteLine("Hello from CLR Managed Code!");
    }
}

Sample Explanation:
This program prints a message. Behind the scenes, CLR ensures memory is managed, exceptions are handled, and security policies are enforced.

---

### 🔍 How CLR Works

1️⃣ Write .NET code (C#, VB.NET, etc.)
2️⃣ Compile to IL (Intermediate Language)
3️⃣ CLR loads IL
4️⃣ JIT compiler turns IL into machine code
5️⃣ CLR manages execution (memory, security, etc.)

Sample:
You write C# code and compile it—your code becomes IL. When you run your app, the CLR takes care of turning IL into native code for your computer.

---

### 🌟 Why CLR Rocks

- Your app runs anywhere .NET does
- CLR automates security & memory
- You get stable, efficient programs

Sample:
You can deploy your .NET app on Windows, Linux, or macOS without worrying about the underlying hardware—CLR makes it all possible!

---

💬 Want more tech insights?
Join & share: [Brain bytes](https://news.1rj.ru/str/brain_bytes)

#DotNet #CLR #CSharp #Programming #CodeNewbie #TechExplained #BrainBytes

🧠✨ Brain bytes
Channel: t.me/brain_bytes

# Programming Paradigms vs Programming Model

## 1) What Is a Programming Paradigm?
A programming paradigm is a conceptual style or philosophy for thinking about problems and structuring solutions in code.
It answers questions like:
- How do we view data? (objects, pure values, sequences, events)
- How do we express behavior? (methods, functions, queries, handlers)
- How do system parts interact? (method calls, message passing, events, streams)

Paradigms guide how you mentally model the domain. They are about “How should I think and organize?” not about specific syntax.
Examples: Imperative, Object-Oriented (OOP), Functional, Declarative, Event-Driven, Asynchronous, Reactive.

## 2) What Is a Programming Model?
A programming model is the concrete set of language mechanisms, runtime behavior, keywords, and APIs that let you implement one or more paradigms.
In C#, the programming model provides:
- OOP constructs: class, interface, abstract, virtual, override
- Functional/declarative tools: LINQ (Where, Select, query syntax), lambdas, delegates (Func<>, Action), expression trees, record types
- Asynchronous constructs: async, await, Task, ValueTask, CancellationToken
- Event-driven features: event, EventHandler, delegates
- Memory/execution semantics: managed runtime, garbage collection, value vs reference types

In short:
Paradigm = conceptual lens (thinking model)
Programming model = toolbox + mechanics enabling that lens

---

## 3) Major Paradigms with C# Examples

### A) Imperative Paradigm
Focus: Explicit step-by-step instructions and mutable state.

int sum = 0;
int[] numbers = { 3, 5, 7, 9 };
for (int i = 0; i < numbers.Length; i++)
{
    sum += numbers[i];
}
Console.WriteLine(sum);

Characteristics: loops, assignments, control flow (if, for, while).

---

### B) Object-Oriented Programming (OOP)
Model the world as objects combining state + behavior.

public class Car
{
    public string Brand { get; }
    public int Speed { get; private set; }

    public Car(string brand, int speed)
    {
        Brand = brand;
        Speed = speed;
    }

    public void Accelerate(int amount) => Speed += amount;
    public override string ToString() => $"{Brand} => {Speed} km/h";
}

var car = new Car("BMW", 120);
car.Accelerate(30);
Console.WriteLine(car); // BMW => 150 km/h

Core concepts: Encapsulation, Inheritance, Polymorphism, Abstraction.

Polymorphism example:

public abstract class Shape
{
    public abstract double Area();
}

public class Circle : Shape
{
    public double Radius { get; }
    public Circle(double r) => Radius = r;
    public override double Area() => Math.PI * Radius * Radius;
}

public class Rectangle : Shape
{
    public double Width { get; }
    public double Height { get; }
    public Rectangle(double w, double h) { Width = w; Height = h; }
    public override double Area() => Width * Height;
}

Shape[] shapes = { new Circle(3), new Rectangle(4, 5) };
foreach (var s in shapes)
    Console.WriteLine(s.Area());

---

### C) Functional Style (in C#)
Emphasis on pure transformations, minimized mutation, composability.

int[] numbers = { 3, 5, 7, 9 };
int sum = numbers.Aggregate((a, b) => a + b);

var squaredEvens = numbers
    .Where(n => n % 2 == 0)
    .Select(n => n * n)
    .ToList();

Console.WriteLine(sum);
Console.WriteLine(string.Join(", ", squaredEvens));

Traits: Lambdas, LINQ pipelines, declarative transformations, easier testing.

---

### D) Declarative Paradigm
Describe WHAT you want, not HOW to iterate.

var products = new[]
{
    new { Name = "Laptop", Price = 45000 },
    new { Name = "Mouse", Price = 400 },
    new { Name = "Monitor", Price = 9000 },
};

var expensive =
    from p in products
    where p.Price > 5000
    orderby p.Price descending
    select p.Name;

Console.WriteLine(string.Join(" | ", expensive));

You specify filters and projections; LINQ decides iteration strategy (and can translate to SQL via EF Core).

---

### E) Event-Driven Paradigm
Flow controlled by events rather than sequential commands.

public class Button
{
    public event Action? Click;
    public void OnClick() => Click?.Invoke();
}

var button = new Button();
button.Click += () => Console.WriteLine("Button clicked!");
button.OnClick();

Used in UI, messaging systems, reactive pipelines.

---

### F) Asynchronous Paradigm
Handle I/O or long-running tasks without blocking threads.

public async Task<string> FetchAsync()
{
    using var http = new HttpClient();
    return await http.GetStringAsync("https://example.com");
}

var data = await FetchAsync();
Console.WriteLine(data);

Combines async/await with Task for clearer concurrency.

---

### G) Reactive (Optional Extension)
Treat data as streams (e.g. with IObservable): react declaratively to change over time.

---

## 4) How C# Programming Model Enables These Paradigms

| Paradigm | Model Elements (C#) |
|---------------|---------------------|
| Imperative | loops, mutable locals, branching (if, switch) |
| OOP | class, interface, abstract, virtual, override, access modifiers |
| Functional | lambdas, delegates (Func<>, Action), LINQ, record types |
| Declarative | LINQ query syntax, attributes, expression trees |
| Event-Driven | event, delegates, EventHandler, UI frameworks |
| Asynchronous | async, await, Task, CancellationToken, ValueTask |
| Reactive | observables (via libraries), continuation chains |

C# is multi-paradigm: mix domain modeling (OOP) + data transformations (functional/declarative) + async I/O + events.

---

## 5) Choosing a Paradigm (Quick Guide)

| Situation | Best Fit |
|-----------|----------|
| Rich domain entities, lifecycle | OOP |
| Data querying/filtering | Declarative (LINQ) |
| Composable transformations, testability | Functional style |
| UI interactions, user input | Event-Driven |
| Network / file / database latency | Asynchronous |
| Simple noscripts / procedural tasks | Imperative |
| Live data streams / continuous updates | Reactive |

Often you combine several in one solution.

---

## 6) Summary
Paradigm = How you think and structure the solution conceptually.
Programming Model = The language/runtime mechanisms enabling those structures.
C# provides a unified model supporting multiple paradigms seamlessly.

---

## 7) Glossary (English Term + Persian Meaning)

| Term | Persian |
|------|--------|
| Programming Paradigm | پارادایم برنامه‌نویسی / سبک مفهومی |
| Programming Model | مدل برنامه‌نویسی / مکانیزم اجرایی |
| Imperative | دستوری |
| Declarative | اعلامی / деклараتی |
| Object-Oriented (OOP) | شیءگرا |
| Encapsulation | کپسوله‌سازی |
| Inheritance | ارث‌بری |
| Polymorphism | چندریختی |
| Abstraction | انتزاع |
| Class | کلاس |
| Object | شیء |
| Method | متد |
| State | حالت |
| Functional Programming | برنامه‌نویسی تابعی |
| Pure Function | تابع خالص |
| Side Effect | عارضهٔ جانبی |
| Immutability | تغییرناپذیری |
| Lambda Expression | عبارت لامبدا |
| Delegate | نماینده (تابع اشاره‌ای) |
| LINQ | چارچوب کوئری یکپارچه |
| Query Syntax | نحوهٔ نگارش کوئری |
| Expression Tree | درخت بیان |
| Event | رویداد |
| Event-Driven | رویدادمحور |
| Asynchronous / Async | ناهمگام |
| Concurrency | همزمانی |
| Task | وظیفهٔ ناهمگام |
| CancellationToken | توکن لغو |
| Record | رکورد (نوع دادهٔ مختصر) |
| Virtual | مجازی (قابل بازنویسی) |
| Override | بازنویسی |
| Abstract | انتزاعی |
| Interface | اینترفیس / قرارداد |
| Reactive | واکنشی |
| Multi-Paradigm | چندپارادایمی |
| API | رابط برنامه‌نویسی کاربردی |
| Design Pattern | الگوی طراحی |
| Refactoring | بازآرایی کد |
| Maintainability | نگهداشت‌پذیری |
| Scalability | مقیاس‌پذیری |
| Deferred Execution | اجرای مؤخر |
| DSL | زبان دامنه‌محور |
| Idempotent | ایدمپوتنت (تکرار بدون تغییر نتیجه) |

---

## 8) Tags
#programming #paradigm #programming_model #CSharp #OOP #Functional #Declarative #LINQ #Async #EventDriven #Reactive #DotNet #SoftwareDesign #CleanCode #BrainBytes #Architecture #Coding #Developer

# 🚦 ASP.NET Core Routing Unlocked – Your App’s GPS!
Channel: [t.me/brain_bytes](https://news.1rj.ru/str/brain_bytes)

---

## 🎯 What is Routing? (Professional Overview)
Routing is the backbone of an ASP.NET Core web application.
It connects incoming URLs to specific pieces of your code, called endpoints (like controller actions or pages).
When a user sends a request, routing ensures it lands exactly where it should, making your app organized, scalable, and user-friendly.

---

## 🪁 Simple Definition
Think of routing as a GPS for your web app.
It reads every URL a user enters and guides it to the right controller and method, just like a GPS takes you to the correct address!

---

## 💡 Practical Example

Let’s build a practical “Product Details” feature:

### Program.cs (Routing Setup)

var builder = WebApplication.CreateBuilder(args);
builder.Services.AddControllersWithViews();
var app = builder.Build();
app.UseRouting();
app.UseEndpoints(endpoints =>
{
    endpoints.MapControllerRoute(
        name: "default",
        pattern: "{controller=Home}/{action=Index}/{id?}");
});
app.Run();

### ProductController.cs

using Microsoft.AspNetCore.Mvc;

public class ProductController : Controller
{
    // Handles URLs like /Product/Details/5
    public IActionResult Details(int id)
    {
        var product = new Product { Id = id, Name = "Sample Product", Price = 99.99M };
        return View(product);
    }
}

### Product.cs (Model)

public class Product
{
    public int Id { get; set; }
    public string Name { get; set; }
    public decimal Price { get; set; }
}

### Views/Product/Details.cshtml

@model Product

<h1>Product Details</h1>
<p>Id: @Model.Id</p>
<p>Name: @Model.Name</p>
<p>Price: $@Model.Price</p>

---

## ☑️ Key Points & Best Practices
- Use clear and simple route patterns.
- Prefer attribute routing for precise control.
- Always check route parameters (e.g., confirm id exists).
- Avoid overlapping or ambiguous route patterns.
- Organize endpoints logically for maintainability.
- Test routes with sample URLs to ensure proper mapping.

---

## 📚 Important Terms & Meanings

- Routing: Maps URLs to the right endpoint (controller/action/page).
- Controller: Receives requests and sends back responses.
- Action: Method inside a controller handling a specific route.
- Endpoint: The final target for a request in your app.
- Route Pattern: URL template to match and direct requests.
- Parameter: Data passed via URL, like id in /details/5.
- Attribute Routing: Routes defined directly on methods/classes using annotations.
- Convention-based Routing: One general template for all routes.

---

## 🏷 Telegram Tags
#AspNetCore #Routing #DotNet #brain_bytes #WebDevelopment #PracticalCode #FAQ #Glossary

---

🔥 For more practical lessons: [t.me/brain_bytes](https://news.1rj.ru/str/brain_bytes)

# 🧩 ASP.NET Core Middleware—Your App’s Request Pipeline, Explained!
Channel: [t.me/brain_bytes](https://news.1rj.ru/str/brain_bytes)

---

## 🎯 What is Middleware? (Professional Overview)
Middleware in ASP.NET Core refers to small components that process HTTP requests one after another as they travel through your application.
Each middleware can inspect, modify, or handle a request—or let it continue to the next middleware in the pipeline.

Every web app in ASP.NET Core is made of a sequence of middleware components, creating what’s known as a “request pipeline.”
You decide what middlewares to use, their order, and how they interact with each request and response.

---

## 🪁 Simple Definition
Think of middleware as checkpoint stations at an airport.
Every request passes through them one by one, getting checked, tagged, or changed before reaching its final destination!

---

## 💡 Practical Example

Let’s build a simple middleware pipeline:

### Program.cs

var builder = WebApplication.CreateBuilder(args);
var app = builder.Build();

// Middleware 1
app.Use(async (context, next) =>
{
    Console.WriteLine("Middleware 1: Before");
    await next();
    Console.WriteLine("Middleware 1: After");
});

// Middleware 2
app.Use(async (context, next) =>
{
    Console.WriteLine("Middleware 2: Before");
    await next();
    Console.WriteLine("Middleware 2: After");
});

// Terminal Middleware
app.Run(async context =>
{
    Console.WriteLine("Terminal Middleware: Handling request");
    await context.Response.WriteAsync("Hello from ASP.NET Core Pipeline!");
});

app.Run();

Order of Execution:
- Request enters Middleware 1, then passes to Middleware 2, and finally to the Terminal Middleware.
- Responses flow back in reverse: Terminal → Middleware 2 → Middleware 1.

---

## ☑️ Key Points & Best Practices
- Middlewares execute in the order they are added in your code.
- The first middleware added is the first to run, and the last is the terminal handler.
- Each app.Use middleware should call await next() to pass control.
- Omitting next() makes that middleware the terminal one (it ends the pipeline).
- Order is crucial! For example, add authentication before authorization.
- Keeping middleware logic short and focused makes it easier to manage and test.

---

## 📚 Important Terms & Meanings

- Middleware: A building block of the request pipeline that handles or transforms HTTP requests/responses.
- Pipeline: The sequence of middleware components through which each request travels.
- app.Use(): Adds a middleware to the pipeline, allowing continuation (next()).
- app.Run(): Adds a terminal middleware, ending the pipeline.
- Request: Information sent by the client to your server.
- Response: Information your server sends back to the client.

---

## 🏷 Telegram Tags
#AspNetCore #Middleware #DotNet #brain_bytes #WebDevelopment #BestPractices #Glossary #FAQ

---

🔥 For more hands-on lessons: [t.me/brain_bytes](https://news.1rj.ru/str/brain_bytes)