Archiv der Kategorie: Clean Code

Methods should do one thing only

Erstellt am November 5, 2017 von oliverfunke

According to the Single Responsibility Principle a class should have one, and only one, reason to change. To same statement is valid for methods. A method should do one thing only and therefore have only one reason to change. Unfortunately … Weiterlesen →

Veröffentlicht unter .NET, C#, Clean Code | Kommentar hinterlassen

Linq vs Loop: Nested Loop

Erstellt am Juli 9, 2017 von oliverfunke

Like in the previous article of this series I want to compare Linq with a classical loop. This time we want to look at the use case to handle data which contains nested data. Again we want to use validated … Weiterlesen →

Veröffentlicht unter .NET, C#, Clean Code, LINQ | Kommentar hinterlassen

Clean Tuples

Erstellt am Mai 28, 2017 von oliverfunke

Depending on the preferences of a developer you may sometimes find a lot of tuples within the source code. Whether this is good or bad practice is another discussion which is not part of this article. Therefore I don’t want … Weiterlesen →

Veröffentlicht unter .NET, C++, Clean Code | Kommentar hinterlassen

Write clean code instead of comments

Erstellt am April 30, 2017 von oliverfunke

Of course comments help to understand code. They are an essential part of the source code. But comments are an addition only. If you want to create readable and easy to understand source code, you have to focus on the … Weiterlesen →

Veröffentlicht unter .NET, C#, Clean Code | Kommentar hinterlassen

Linq vs Loop: Check whether item exists

Erstellt am April 16, 2017 von oliverfunke

Like in the previous article of this series I want to compare Linq with a classical loop. This time we want to look at the common use case to check whether an item exists. Again we want to use validated … Weiterlesen →

Veröffentlicht unter .NET, C#, Clean Code, LINQ | 1 Kommentar

Don’t return null

Erstellt am April 3, 2017 von oliverfunke

If you write a function returning an object instance you have to think about the special cases. This may be error cases or maybe situations where no object instance can be found or created. In such cases you will often … Weiterlesen →

Veröffentlicht unter .NET, C#, Clean Code | Kommentar hinterlassen

Design patterns: Iterator

Erstellt am März 19, 2017 von oliverfunke

An Iterator provides a way to access the elements of an object sequentially without exposing the underlying representation. It is a base Design Patterns which we use permanently. For example a loop over a list is done by using the … Weiterlesen →

Veröffentlicht unter .NET, C#, Clean Code, Design Pattern | Kommentar hinterlassen

Use factory methods instead of overloaded constructors

Erstellt am März 5, 2017 von oliverfunke

If a class can be created and initialized in different ways or by using different kind of values you may often see overloaded constructors. This is a standard way to implement such an object creation but it has a major … Weiterlesen →

Veröffentlicht unter .NET, C#, Clean Code | Kommentar hinterlassen

Linq vs Loop: Simple Query

Erstellt am Februar 26, 2017 von oliverfunke

Within this article and within further articles I want to compare Linq and classical loops. During code reviews you may sometimes hear the suggestion to use language specific features as they will simplify the source code. Such a feature is … Weiterlesen →

Veröffentlicht unter .NET, C#, Clean Code, LINQ | Kommentar hinterlassen

Design patterns: Factory Method vs Abstract Factory

Erstellt am Februar 19, 2017 von oliverfunke

In case a class instance shall be created, developers may give the advice to use a “factory”. This common term isn’t wrong but sometimes it’s better to define the exact type of factory you want to use. So, in this … Weiterlesen →

Veröffentlicht unter .NET, C#, Clean Code, Design Pattern | Kommentar hinterlassen