The Use Case Pattern is a way of organizing the business logic of an application into a set of use cases. Each use case represents a specific action that a user can perform within the system. For example, in an e-commerce application, a use case might be “Place an Order” or “View Order History”. The…
Category: Uncategorized
Single Responsibility Principle (Clean Architecture)
When talking about patterns, almost everyone can name the SOLID pattern (Single Responsability, Open/Close, Liskov Substitution, Interface Segregation and Dependency Inversion). The Single Reponsibility is one of the most important principle for clean code but it’s also very important for clean architecture. Let’s explore this The SRP states that a class should have one, and…
How to use Feature Flags in Blazor
Feature flags are a way of controlling the availability and behavior of features in your application without changing the code. They can help you with testing, experimentation, and gradual rollout of new functionality. Blazor is a framework for building interactive web UIs using C# and .NET. In this blog post, I will show you how…
Migrating an Old .NET App Using Unsupported Tech: A Step-by-Step Guide
In today’s rapidly evolving tech landscape, it’s quite common to find yourself in a situation where you need to migrate an old .NET app that relies on unsupported technologies. While this can be a daunting task, with careful planning and implementation, it’s possible to breathe new life into your application. Also, pay attention that tech…
Infrastructure as Code and source controle
For those who don’t what is this about, Infrastructure as Code is a set of files when executed with the right tool, will create resources such as storage account, databases, virtual network etc. It is mostly associated with the cloud. As I’ve been working lately with Terraform, I really enjoyed it and I thought it…
Tensions between teams due to rivalry
Communication and collaboration between teams, while essential to a working company is sometimes very difficult for many reasons. There may be valid grounds for tension but it is never beneficial for the company. What to do when this happens? Team rivalry This is a very common and a difficult one to solve. Rivalry can be…
Creativity vs knowledge
In IT, we tend to privilege knowledge and we test the hire candidates accordingly. What do they know about object oriented programming, authentication and security, frameworks and languages. While this has merit in itself, is it enough? Knowledge is indeed important as for any candidate, there musy be things to know. If you hire a…
Single responsability vs Interface segregation
I stumbled upon a Reddit post forwarding an article about how single responsability and interface segregation would be essentially the same. I obviously disagreed but by reading the comments, it appeared that the differences between the two aren’t that clear for some Let’s start with the single responsability. It means that a class has one…