Fiodar Sazanavets

I am a Microsoft MVP and a lead/senior software engineer with over a decade of professional experience. I primarily specialize in .NET and Microsoft stack. I am enthusiastic about creating well-crafted software that fully meets business needs. Throughout my career, I have successfully developed software of various types and various levels of complexity in multiple industries. This includes a passenger information management system for a railway, distributed smart clusters of IoT devices, e-commerce systems, financial transaction processing systems, and more. I have also successfully led and mentored teams of software developers. I enjoy sharing my knowledge with the community. This motivates me to mentor aspiring developers and create educational content, which includes blog posts, technical books, and online courses. My books include "SignalR on .NET 6 - the complete guide", "The battle hardened developer", and "The easiest way to learn design patterns".

Why you need dependency inversion in C#

Knowing a programming language doesn’t make you a software developer. Absolutely every software developer who works with any object oriented language need to be familiar with SOLID principles.For those who are new to programming and doesn’t yet know what those principles are, SOLID is an acronym, which stands for the following: Single responsibility principle Open-closed […]

Why you need dependency inversion in C# Read More »

Importance of interface segregation principle in C#

If you are a software developer primarily working with object-oriented programming languages, you absolutely must be familiar with SOLID principles. Nothing will help you to write clean code as much as SOLID principles would. For those who aren’t yet familiar with what SOLID principles are, here is the list: Single responsibility principle Open-closed principle Liskov

Importance of interface segregation principle in C# Read More »

Liskov substitution principle in C#

Every programmer who works with object-oriented programming languages absolutely must know SOLID principles, which are the following: Single responsibility principle Open-closed principle Liskov substitution principle Interface segregation principle Dependency inversion principle In this article, we will cover Liskov substitution principle. I will explain why this principle is important and will provide an example of its

Liskov substitution principle in C# Read More »

Why open-closed principle is important

SOLID design principles is something that every software developer must know, especially if the developer mainly uses object oriented programming paradigm. SOLID is an acronym. For those who aren’t familiar with the term, this is what it stands for: Single responsibility principle Open-closed principle Liskov substitution principle Interface segregation principle Dependency inversion principle In this

Why open-closed principle is important Read More »

Why you must use single responsibility principle

Every software developer who uses object-oriented programming languages needs to be familiar with SOLID software design principles and know how to apply them in their daily job. For those who aren’t familiar with what they are, SOLID is an abbreviation that stands for the following: In this particular post, we will focus on the first

Why you must use single responsibility principle Read More »

The ways in which Skillshare is better than Udemy

Udemy is a very well-known online learning platform. It contains thousands upon thousands of courses, covering any subject imaginable. And this is why many people go there to improve their professional skills. As a software developer, I have used Udemy quite a lot, both as a student and as an instructor. I have published a

The ways in which Skillshare is better than Udemy Read More »