<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Presentation on Pal Hargitai Personal Blog</title>
    <link>https://palhargitai.eu/tags/Presentation/</link>
    <description>Recent content in Presentation on Pal Hargitai Personal Blog</description>
    <generator>Hugo -- 0.152.2</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 12 Oct 2012 20:54:28 +0000</lastBuildDate>
    <atom:link href="https://palhargitai.eu/tags/Presentation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>An approach to splitting functionality</title>
      <link>https://palhargitai.eu/post/2012-10-12-an-approach-to-splitting-functionality/</link>
      <pubDate>Fri, 12 Oct 2012 20:54:28 +0000</pubDate>
      <guid>https://palhargitai.eu/post/2012-10-12-an-approach-to-splitting-functionality/</guid>
      <description>&lt;p&gt;Perhaps a disclaimer first, I haven&amp;rsquo;t found this in textbook, although I wouldn&amp;rsquo;t be surprised if it were. It&amp;rsquo;s actually an explanation I used on a job to explain how splitting responsibilities would help them in their &lt;a href=&#34;http://en.wikipedia.org/wiki/Development,_testing,_acceptance_and_production&#34; title=&#34;Development, testing, acceptance and production&#34;&gt;DTAP&lt;/a&gt; environment. It&amp;rsquo;s a loosely defined way of looking at some responsibilities of some facets with respect to &lt;a href=&#34;http://en.wikipedia.org/wiki/Software_testing&#34; title=&#34;Software testing&#34;&gt;testing&lt;/a&gt; and &lt;a href=&#34;http://en.wikipedia.org/wiki/Software_deployment&#34; title=&#34;Software deployment&#34;&gt;deployment&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
