In the 3rd part of the series we’ll see how to create asynchronous steps in the pipeline with TPL Dataflow. We’ll also see a new implementation using the Disruptor-net library.
Logging is a big part of software development for many years now. This guide is a bird’s eye view of modern solutions for logging in .NET space.
One of the most important concepts in modern programming is Exceptions. They were introduced in the 60’s with LISP and eventually made their way to practically all modern programming languages. This article is an extensive guide to dealing with exceptions in Visual Studio.
In the First Part of the series, we talked about the Pipeline Pattern in programming, also known as the Pipes and Filters design pattern. In this part, we’ll see how to implement such a pipeline with TPL Dataflow.
The Pipeline pattern is a powerful tool in programming. The idea is to chain a group of functions in a way that the output of each function is the input the next one. The concept is pretty similar to an assembly line where each step manipulates and prepares the product for the next step.
I’ve been developing software for 10 years now. Every now and again I wonder what it is that makes me tick. What’s the element that makes me come to want to go work in the mornings. In other words, what is it that motivates us as software developers?
Don’t know about you, but I’m obsessed about performance. I’ve gathered a list of 10 best practices on dealing with performance problems, starting with when you need to deal with them at all.
LINQ is terrible to debug. We have no way of knowing what goes on inside that query. We can see the input, we can see the output, but that’s about it. What happens when something goes wrong? Do we just stare at the code, trying to get some kind of insight? There’s got to be a better way…
Extension methods are awesome, right? They are probably most widely used in the LINQ feature. But when should we use them? And when shouldn’t we? Let’s talk guidelines.
Poor memory management can hurt performance in many ways. One such effect is called GC Pressure. This article will show 8 techniques to minimize GC pressure, and by doing so, improve performance.
One of the most commonly used patterns in software development is Caching. It’s a simple, yet extremely effective concept. The idea is reuse of results. When performing a heavy operation, we will save the result in said cache
I’d like to tackle an old dilemma: Class instantiation. Which pattern do you use to create a class? Do you always use a new statement? Do we still need to use Singleton or Factory? Should we always use dependency injection? How about static classes, are they truly evil?