<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>EcmaScript5 on Dmitry Sheiko&#39;s Web Development Blog</title>
    <link>https://dsheiko.com/tags/ecmascript5/</link>
    <description>Recent content in EcmaScript5 on Dmitry Sheiko&#39;s Web Development Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 04 Apr 2013 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://dsheiko.com/tags/ecmascript5/index.xml" rel="self" type="application/rss+xml" />
    <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>
