What is code design? At what stage of software development process he comes out? What benefits to maintain a good code design? Many questions with relatively simple answers, I’m sure that there are many developers, like me, who practice it without much awareness about the theory.

Many programming languages have reference types and value types with some differences in concept between them, but here we will ask about how this works in C#, and also how these concepts are related to immutability and side effects (code smell).

Another post about code smells today talks about Inconsistency the principle of inconsistency is simple and doesn't generate much discussion, although it is crucial to maintain consistency it can end up creating a big dilemma, which is to remain consistent at any cost or allow yourself to be inconsistent to add meaningful improvements incrementally.

By far the most challenging task for an experienced software developer is to come up with good names for the things he creates classes, instances, variables, methods and so on. But the concern for expressive names leads us to exaggerations that end up making the code difficult to read due to excessive expressiveness. For this reason let`s explore a little about what clean code says about it.

Feature envy code smell is a much more common code smell than it sounds and is sometimes overlooked by even the most experienced developers. Here I will try to convince you of the benefits to your code if you avoid it, some of them are readability, better attribution of responsibilities, encapsulation, immutability and in some cases help with some SOLID concepts like Single Responsability Principle.