This is the last article related to the set of SOLID project principles. The DIP principle is the most useful of all in terms of its relevance to the creation of strong classes and good architecture of the whole system.
The principle relates to two main aspects of object-oriented programming. First of all, it highlights the importance of correlation between the classes with the same parent. Secondly, it helps to understand correctly the essence of object-oriented programming and virtual mechanisms, which support the process.
As you may know we were asked to develop system for attendees of Economic Forum 2020. One of the client’s main requests was to allow mobile applications, communicating with main server, to read only the data that has been changed since last reading.
Have you ever seen a class method in your project, the core of which would be one line only: throw new NotImplementedException()? Is this the right solution? Could such a code cause an issue?
That is the second article from the series about SOLID principles. This time I should give you more details about the Open-Closed Principle. The element of software should be locked for modification but open to extension. Uncle Bob himself used to say: “Good architecture reduces the amount of modified code to the absolute minimum. Ideally to zero”.
SOLID principles are regarded as one the best practices in programming. We hear about them all the time. Unfortunately, it seems to me that these rules are often misunderstood. I’ll try to present them in the series of five articles, one article for each rule.
There are many articles describing how to write a good test. But the question is how to create a good data test? I will show an example, different from what you may have ever read.
The requirement of one of the applications we were creating was to allow the files to be stored in the cloud. Such a solution may prove to be particularly useful in case of a limited client or server resources or the need for easy access to all files stored in the application. In the following article I will present a solution for connecting .NET application with Google REST API.
This is the second article from the series about how to improve your .NET application that uses Entity Framework. In this lesson I will show you how to reduce the number of connections and queries sent to database when updating database. I will show you a few good practices in some common cases. Let’s start.
In this article I will first explain how the queues work and in the second part we will install Symfony, messenger component and rabbitMQ and we will create a simple project example of product order basket in the store.
The world is changing faster than ever before, and especially IT world. As software developers and engineers we should „sharpen our saw” not only to be better and better but also to be on a roll with new technologies, frameworks and libraries. The same as athletes who keep in shape and train harder to get better, faster and stronger (yup, I like Daft Punk), we should train ourselves.
This is the first article from the series about how to improve your .NET application which uses Entity Framework. I will show you some simple tips that will boost your application. I hope that many advices you will find here can be used in any other ORM or even any other programming language. First of all let’s see how the majority of applications work.