<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: Friday Dopamine Dump</title>
	<atom:link href="http://piotrpasich.com/friday-dopamine-dump/feed/" rel="self" type="application/rss+xml" />
	<link>http://piotrpasich.com/friday-dopamine-dump/</link>
	<description>PHP, Symfony, Design Patterns</description>
	<lastBuildDate>Fri, 08 Sep 2023 13:45:00 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.0.38</generator>
	<item>
		<title>By: mheki</title>
		<link>http://piotrpasich.com/friday-dopamine-dump/#comment-87</link>
		<dc:creator><![CDATA[mheki]]></dc:creator>
		<pubDate>Mon, 26 Jan 2015 16:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://piotrpasich.com/?p=2684#comment-87</guid>
		<description><![CDATA[Then I would keep the code simple and not introduced a legacy one in above examples. 
That might confuse those who want to start with phpspec :-/]]></description>
		<content:encoded><![CDATA[<p>Then I would keep the code simple and not introduced a legacy one in above examples.<br />
That might confuse those who want to start with phpspec :-/</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Piotr Pasich</title>
		<link>http://piotrpasich.com/friday-dopamine-dump/#comment-85</link>
		<dc:creator><![CDATA[Piotr Pasich]]></dc:creator>
		<pubDate>Fri, 23 Jan 2015 10:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://piotrpasich.com/?p=2684#comment-85</guid>
		<description><![CDATA[I can totally agree with you. But the time is nearly over, so I decided to move on. This exercise is also for me as a writer - do it in one hour.]]></description>
		<content:encoded><![CDATA[<p>I can totally agree with you. But the time is nearly over, so I decided to move on. This exercise is also for me as a writer &#8211; do it in one hour.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mheki</title>
		<link>http://piotrpasich.com/friday-dopamine-dump/#comment-84</link>
		<dc:creator><![CDATA[mheki]]></dc:creator>
		<pubDate>Fri, 23 Jan 2015 10:26:00 +0000</pubDate>
		<guid isPermaLink="false">http://piotrpasich.com/?p=2684#comment-84</guid>
		<description><![CDATA[Nice article Piotr. We do code katas in our company. I have to agree with you - it requires a lot of discipline to do it everyday.

I found one issue in your post. The way we do TDD is: make it red, make it green, refactor.

So in your Price example, after the first failed test, I would create the easiest solution to make it pass. Then I would create a new example such as `it_throws_when_price_is_not_numeric()` and after failure, implement your `throw new LogicException(&#039;Price should be numeric&#039;);`
That way I make a very small steps to achieve the final result.


One more thing: when you finish code kata, you should erase your work ;-)]]></description>
		<content:encoded><![CDATA[<p>Nice article Piotr. We do code katas in our company. I have to agree with you &#8211; it requires a lot of discipline to do it everyday.</p>
<p>I found one issue in your post. The way we do TDD is: make it red, make it green, refactor.</p>
<p>So in your Price example, after the first failed test, I would create the easiest solution to make it pass. Then I would create a new example such as `it_throws_when_price_is_not_numeric()` and after failure, implement your `throw new LogicException(&#8216;Price should be numeric&#8217;);`<br />
That way I make a very small steps to achieve the final result.</p>
<p>One more thing: when you finish code kata, you should erase your work <img src="http://piotrpasich.com/wp-includes/images/smilies/icon_wink.gif" alt=";-)" class="wp-smiley" /></p>
]]></content:encoded>
	</item>
</channel>
</rss>
