About

Optimal Coder is a blog dedicated to software development, offering insights into coding practices, design principles, and industry challenges. The blog features articles on topics such as book overviews, design patterns, coding advisory and workplace dynamics.

About me

My name is Mirnes Mrkaljevic, currently based in Germany and working as a software engineer in the logistics sector. I am well-versed in C#, with experience in JavaScript and Angular as well. My passion lies in advising and crafting clean, maintainable code that is both easy to understand and extend. I am deeply committed to Test-Driven Development (TDD) and constantly exploring ways to enhance team efficiency and collaboration.

Let’s Connect!

Feel free to reach out, share your thoughts in the comments, follow me on LinkedIn or Email me.

Design Patterns: Strategy

The Strategy Pattern is a behavioral design pattern that defines a family of algorithms, encapsulates each one, and makes them interchangeable. This pattern allows the algorithm to be selected at runtime, providing flexibility in designing software. It’s particularly useful when you have multiple ways of performing a task, and you want to choose the implementation dynamically without altering the client code. When To Use It? You Have Multiple Algorithms or Behaviors. Use it when you have a need for muplitple ways of performing a task, and you want to make these implementations interchangeable. Examples: Different sorting algorithms, payment methods, discount calculations... You Want to Eliminate Conditional Logic. If you find yourself writing large if-else or switch statements to decide which algorithm to use, this pattern can simplify and clean up your code. Examples: A game character with different attack styles You Need Runtime Flexibility. Use this pattern if the ...

Design Patterns: Builder

This is also, like a Singleton , one of the creational design patterns. It provides the way of creating complex objects step by step by simple chaining and every particular step is independent of other steps. Let us dive into the real example of usage. For showing purpose we have created an example in C# which creates simple SQL queries using described pattern. using System; using System.Text; namespace BuilderPatternExample { public interface ISqlQueryBuilder { ISqlQueryBuilder Select(string columns); ISqlQueryBuilder From(string table); ISqlQueryBuilder Where(string condition); ISqlQueryBuilder OrderBy(string columns); string Build(); } public class SelectQueryBuilder : ISqlQueryBuilder { private readonly StringBuilder _queryBuilder; public SelectQueryBuilder() { _queryBuilder = new StringBuilder(); } public ISqlQueryBuilder Select(string columns) { ...

Design Patterns: Singleton

Tyipically the first design pattern most people learn, often wrongly ☺ To give an introduction, we can say that singleton is one of the creational design patterns which ensures only one class instance with single point of access thru entire application. Because it is relatively simple to implement, the Singleton pattern is sometimes misapplied in situations where it is not the most suitable choice. When to use it? Here are the few examples of corrent usage of singleton: Configuration Management Centralized configuration settings for consistent use thru entire application Caching Maintaning Single istance of cached objects for easy and fast acces Logging Ensure unified mechanism to avoid duplication of log files, formats, etc Global State Management Centralized management of the state which is needed to be shared accross the application Resource sharing Thread pools, database connection, I/O operations When not to use it? On the other hand, here are fe...

Optimal Coder

Search This Blog