<?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 Dmitry Sheiko&#39;s Web Development Blog</title>
    <link>https://dsheiko.com/tags/design-patterns/</link>
    <description>Recent content in Design Patterns on Dmitry Sheiko&#39;s Web Development Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 17 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://dsheiko.com/tags/design-patterns/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>React Design Patterns: A Practical Reference</title>
      <link>https://dsheiko.com/weblog/react-design-patterns-a-practical-reference/</link>
      <pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://dsheiko.com/weblog/react-design-patterns-a-practical-reference/</guid>
      <description>GoF design patterns gave OOP developers a shared vocabulary for recurring structural problems. SOLID gave them principles for evaluating design decisions. React doesn&amp;rsquo;t fit neatly into either framework, but after several years of widespread adoption, its own set of idiomatic patterns has emerged.&#xA;These aren&amp;rsquo;t best practices in the vague sense. They&amp;rsquo;re concrete, named solutions to specific problems that come up repeatedly when building React applications: how to share logic without duplicating it, how to avoid prop drilling, how to split server and client concerns, how to build flexible component APIs.</description>
    </item>
    <item>
      <title>Design Patterns in JavaScript, Python, and Rust</title>
      <link>https://dsheiko.com/weblog/design-patterns-javascript-python-rust/</link>
      <pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate>
      <guid>https://dsheiko.com/weblog/design-patterns-javascript-python-rust/</guid>
      <description>Back in 2011, I wrote a walkthrough of design patterns with PHP and JavaScript examples. PHP and ES5 have aged a lot since then. The patterns have not.&#xA;This article is a companion to the open-source repository design-patterns-for-web-developer, which covers the 5 SOLID principles and 23 GoF patterns with examples in modern JavaScript (ES2020+), Python (3.10+), and Rust (2021 edition). For each topic I show a condensed version of the code and link to the full source.</description>
    </item>
    <item>
      <title>Design Patterns by PHP and JavaScript examples</title>
      <link>https://dsheiko.com/weblog/design-patterns-by-php-and-js-es5-examples/</link>
      <pubDate>Thu, 15 Dec 2011 00:00:00 +0000</pubDate>
      <guid>https://dsheiko.com/weblog/design-patterns-by-php-and-js-es5-examples/</guid>
      <description>After having your project fully tested, deployed and running, it seems the application architecture is pretty good enough. All the requirements met and everybody is happy. But then as it happens, the requirements change and you, all of sudden, find yourself in the time of troubles. It comes out that some modules easier to hack than to modify. Change of other ones brings endless changes in a cascade of dependent modules.</description>
    </item>
  </channel>
</rss>
