We created this collaborative space for sharing checklists that help ensure software quality, guide you through crisis and other helpful stuff for devs 

You might not sign up for all of them (particularly those around classes and inheritance), but these ‘Uncle Bob’-inspired tips might help you think more about how you name things and structure your code. 

This video is for the Observer pattern in the behavioral category with a JobPosting example for the Persian language developers. 

6 types of code you shouldn't have inside your .NET controllers 

PM>Install-Package DNTFrameworkCore
PM>Install-Package DNTFrameworkCore.EntityFramework
PM>Install-Package DNTFrameworkCore.Web
PM>Install-Package DNTFrameworkCore.Web.EntityFramework

[Route("api/[controller]")]
public class
    TasksController : CrudController<ITaskService, int, TaskReadModel, TaskModel, TaskFilteredPagedQueryModel>
{
    public TasksController(ITaskService service) : base(service)
    {
    }

    protected override string CreatePermissionName => PermissionNames.Tasks_Create;
    protected override string EditPermissionName => PermissionNames.Tasks_Edit;
    protected override string ViewPermissionName => PermissionNames.Tasks_View;
    protected override string DeletePermissionName => PermissionNames.Tasks_Delete;
}

Automating .NET Core Services with PostSharp and Aspect-Oriented Code 

More DI: The Real Power of Decorators 

Rewrite a legacy application using DDD, TDD, .NET and CoreDdd library 

Clean Code concepts adapted for .NET / .NET Core 👍