<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Roland's Blog</title>
    <description>This blog is my personal repository of discoveries, learnings, and technological exploration. It serves as a portfolio for my future self, documenting the ever-evolving journey through technology.</description>
    <link>https://rolandpop.com/</link>
    <atom:link href="https://rolandpop.com/feed.xml" rel="self" type="application/rss+xml"/>
    <language>en-us</language>
    <item>
  <title>Enhancing Software Architecture with CQRS</title>
  <link>https://rolandpop.com/blog/cqrs/</link>
  <guid>https://rolandpop.com/blog/cqrs/</guid>
  <pubDate>Mon, 06 May 2024 00:00:00 GMT</pubDate>
  <description>This article explores how integrating CQRS with the Mediator pattern enhances software architecture. CQRS separates read and write operations, while Mediator facilitates communication between components without direct dependencies. Together, they enable developers to build scalable, adaptable systems with enhanced modularity and maintainability for modern software development challenges.</description>
</item>
<item>
  <title>Layered Architecture</title>
  <link>https://rolandpop.com/blog/layered-architecture/</link>
  <guid>https://rolandpop.com/blog/layered-architecture/</guid>
  <pubDate>Sat, 02 Mar 2024 00:00:00 GMT</pubDate>
  <description>Explore the layers of .NET Clean Architecture, a refined evolution of traditional Layered Architecture. Emphasizing the Dependency Rule, this approach organizes entities, use cases, adapters, and frameworks, ensuring a one-directional flow. While offering benefits like maintainability and testability, caution is advised to prevent undue complexity.</description>
</item>
<item>
  <title>Dependency Inversion Principle</title>
  <link>https://rolandpop.com/blog/solid-dip/</link>
  <guid>https://rolandpop.com/blog/solid-dip/</guid>
  <pubDate>Tue, 06 Feb 2024 00:00:00 GMT</pubDate>
  <description>Dependency Inversion Principle (DIP) in SOLID emphasizes designing flexible and maintainable software by promoting high-level modules that depend on abstractions rather than concrete implementations. This principle encourages the use of abstract interfaces, composition over inheritance, and explicit constructor listings to manage dependencies effectively. DIP fosters a modular and adaptable codebase, enabling developers to enhance system resilience and ease of maintenance.</description>
</item>
<item>
  <title>Interface Segregation Principle</title>
  <link>https://rolandpop.com/blog/solid-isp/</link>
  <guid>https://rolandpop.com/blog/solid-isp/</guid>
  <pubDate>Sun, 04 Feb 2024 00:00:00 GMT</pubDate>
  <description>The Interface Segregation Principle (ISP) emphasizes simplicity by discouraging unnecessary dependencies in interfaces. This principle ensures code clarity, maintains future resilience, and reduces the risk of complications associated with surplus functionality. By recognizing and addressing ISP violations, developers can streamline interfaces, leading to robust and maintainable software foundations that precisely cater to user needs. Embracing ISP promotes a happy coding experience!</description>
</item>
<item>
  <title>Liskov Substitution Principle</title>
  <link>https://rolandpop.com/blog/solid-lsp/</link>
  <guid>https://rolandpop.com/blog/solid-lsp/</guid>
  <pubDate>Sun, 28 Jan 2024 00:00:00 GMT</pubDate>
  <description>This blog post delves into the Liskov Substitution Principle (LSP) within SOLID software development. Highlighting the importance of seamless substitution of subtypes for their base types.</description>
</item>
<item>
  <title>Open Closed Principle</title>
  <link>https://rolandpop.com/blog/solid-ocp/</link>
  <guid>https://rolandpop.com/blog/solid-ocp/</guid>
  <pubDate>Sat, 27 Jan 2024 00:00:00 GMT</pubDate>
  <description>This article delves into the Open Closed Principle (OCP) in SOLID software development. It underscores the significance of allowing classes to be open for extension while closed for modification, promoting code that is easily extendable, reduces bugs, and minimizes impact on dependent code. The OCP, when applied alongside other SOLID principles, enables developers to create adaptable, maintainable, and bug-resistant code.</description>
</item>
<item>
  <title>Single Responsibility Principle</title>
  <link>https://rolandpop.com/blog/solid-srp/</link>
  <guid>https://rolandpop.com/blog/solid-srp/</guid>
  <pubDate>Sun, 21 Jan 2024 00:00:00 GMT</pubDate>
  <description>This article explores the Single Responsibility Principle (SRP) within the SOLID principles of software development, emphasizing the importance of assigning a single responsibility to each class to achieve clean, maintainable, and adaptable code.</description>
</item>
  </channel>
</rss>