<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Design-Patterns on Osmar Petry</title><link>https://osmarpetry.dev/tags/design-patterns/</link><description>Recent content in Design-Patterns on Osmar Petry</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 15 Jan 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://osmarpetry.dev/tags/design-patterns/rss.xml" rel="self" type="application/rss+xml"/><item><title>Design Patterns</title><link>https://osmarpetry.dev/blog/design-patterns/</link><pubDate>Wed, 15 Jan 2025 00:00:00 +0000</pubDate><guid>https://osmarpetry.dev/blog/design-patterns/</guid><description>&lt;h2 id="presentation-intent"&gt;Presentation Intent&lt;/h2&gt;&#10;&lt;p&gt;Prepare the presentation with a clear script of intentions.&lt;/p&gt;&#10;&lt;p&gt;Explain how to read the book and how, by recognizing similar patterns, you create connections between them and discover different perspectives on the same problem. In some cases, this leads to other ways—or better ways—to apply a different pattern.&lt;/p&gt;&#10;&lt;p&gt;Another pattern can sometimes feel very similar to the one you are reading. The point is to think beyond the current chapter and compare intent, structure, and trade-offs.&lt;/p&gt;</description></item><item><title>Domain-Driven Design: Tackling Complexity in the Heart of Software</title><link>https://osmarpetry.dev/blog/ddd/</link><pubDate>Wed, 15 Jan 2025 00:00:00 +0000</pubDate><guid>https://osmarpetry.dev/blog/ddd/</guid><description>&lt;p&gt;Domain-Driven Design (DDD) is a software design approach that focuses on modeling complex systems based on the real-world domains or concepts they represent. The aim is to tackle complexity in the heart of software by aligning the development process with the business domain, using a common language, and creating models that capture the behavior and relationships of the system. DDD emphasizes the importance of designing software around the concepts and processes of the business domain, rather than just technical implementation. It encourages communication and collaboration between the development team and business stakeholders, and promotes the use of models as the primary driver for design decisions. The end result is a software solution that better reflects the needs and requirements of the business domain, and is more maintainable, scalable and adaptable over time.&lt;/p&gt;</description></item></channel></rss>