<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pattern on Dimitri Laaraybi</title>
    <link>https://www.dimitrilaaraybi.com/tags/pattern/</link>
    <description>Recent content in Pattern on Dimitri Laaraybi</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 26 Jul 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.dimitrilaaraybi.com/tags/pattern/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Reducing dependencies with the IServiceUtils&lt;T&gt; pattern</title>
      <link>https://www.dimitrilaaraybi.com/blog/serviceutils/</link>
      <pubDate>Sat, 26 Jul 2025 00:00:00 +0000</pubDate>
      <guid>https://www.dimitrilaaraybi.com/blog/serviceutils/</guid>
      <description>&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;&#xA;&lt;p&gt;In many C#/.NET applications, business services rely on common dependencies like logging, mapping, time management, or database repositories.&lt;br&gt;&#xA;Injecting these repeatedly into every service can lead to boilerplate code, inconsistency and less room for dependancies with relevant business logic value.&lt;br&gt;&#xA;Another drawback of this is that potential code scanners like Sonar could eventually raise some rules errors when some of your constructors injects too much parameters (which is the case by default in Sonar C# rules, 7 max allowed 😉). And this rule break could potentially block your quality gate ❌&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
