<?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: 5 Tools Every PHP Developer Should Master</title>
	<atom:link href="http://blog.calevans.com/2009/02/09/5-tools-every-php-developer-should-master/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.calevans.com/2009/02/09/5-tools-every-php-developer-should-master/</link>
	<description>Lint I find in my mind&#039;s belly-button.</description>
	<lastBuildDate>Sun, 29 Aug 2010 06:47:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com" />
	<atom:link rel="hub" href="http://superfeedr.com/hubbub" />
		<item>
		<title>By: Steven</title>
		<link>http://blog.calevans.com/2009/02/09/5-tools-every-php-developer-should-master/comment-page-1/#comment-64448</link>
		<dc:creator>Steven</dc:creator>
		<pubDate>Mon, 06 Apr 2009 05:35:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.calevans.com/?p=409#comment-64448</guid>
		<description>@Milan

On the contrary, I believe the Unit testing can actually be your life-saver on real projects with defined deadlines et all, especially when specs are a-changing !

The unit tests will help you identify issues in the code logic whenever you change implementation, so it&#039;ll help you. 

I do agree with Cal and others here that it&#039;s overkill and way too resource-consuming to use it on a mere prototype. Not version 1 though....</description>
		<content:encoded><![CDATA[<p>@Milan</p>
<p>On the contrary, I believe the Unit testing can actually be your life-saver on real projects with defined deadlines et all, especially when specs are a-changing !</p>
<p>The unit tests will help you identify issues in the code logic whenever you change implementation, so it&#8217;ll help you. </p>
<p>I do agree with Cal and others here that it&#8217;s overkill and way too resource-consuming to use it on a mere prototype. Not version 1 though&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Milan</title>
		<link>http://blog.calevans.com/2009/02/09/5-tools-every-php-developer-should-master/comment-page-1/#comment-63367</link>
		<dc:creator>Milan</dc:creator>
		<pubDate>Tue, 17 Mar 2009 12:32:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.calevans.com/?p=409#comment-63367</guid>
		<description>I completely agree with you Cal. Unit testing can be a really bad idea when the specs keep changing. In real life this happens way to often.</description>
		<content:encoded><![CDATA[<p>I completely agree with you Cal. Unit testing can be a really bad idea when the specs keep changing. In real life this happens way to often.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: abcphp.com</title>
		<link>http://blog.calevans.com/2009/02/09/5-tools-every-php-developer-should-master/comment-page-1/#comment-63360</link>
		<dc:creator>abcphp.com</dc:creator>
		<pubDate>Tue, 17 Mar 2009 11:21:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.calevans.com/?p=409#comment-63360</guid>
		<description>&lt;strong&gt;5 Tools Every PHP Developer Should Master &#124; Postcards From My Life...&lt;/strong&gt;

Over the past nine years of having fun with PHP, began to see that there are five categories of tools that I rely on more than any others. Sure, I’ve got a code beautifier, a standards checker, and a hand full of hand-written scripts I use for variou...</description>
		<content:encoded><![CDATA[<p><strong>5 Tools Every PHP Developer Should Master | Postcards From My Life&#8230;</strong></p>
<p>Over the past nine years of having fun with PHP, began to see that there are five categories of tools that I rely on more than any others. Sure, I’ve got a code beautifier, a standards checker, and a hand full of hand-written scripts I use for variou&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Md Emran Hasan</title>
		<link>http://blog.calevans.com/2009/02/09/5-tools-every-php-developer-should-master/comment-page-1/#comment-63359</link>
		<dc:creator>Md Emran Hasan</dc:creator>
		<pubDate>Tue, 17 Mar 2009 11:16:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.calevans.com/?p=409#comment-63359</guid>
		<description>A good read which touches the most important tools in a concise, yet powerful writeup. 

Regarding the IDE thing, I&#039;ve been using NuSphere PHPEd for around 2 years now and it has been my good friend throughout the time. Like the Komodo you mentioned, it doesn&#039;t force the project thingy and boosts all my fav features including a nifty terminal window.

About the Unit testing, do you think it&#039;s best to first start writing the tests with personal projects instead of writing them for the projects in the job (assuming your company doesn&#039;t force you write unit tests at work) ? 

Thanks everybody!</description>
		<content:encoded><![CDATA[<p>A good read which touches the most important tools in a concise, yet powerful writeup. </p>
<p>Regarding the IDE thing, I&#8217;ve been using NuSphere PHPEd for around 2 years now and it has been my good friend throughout the time. Like the Komodo you mentioned, it doesn&#8217;t force the project thingy and boosts all my fav features including a nifty terminal window.</p>
<p>About the Unit testing, do you think it&#8217;s best to first start writing the tests with personal projects instead of writing them for the projects in the job (assuming your company doesn&#8217;t force you write unit tests at work) ? </p>
<p>Thanks everybody!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Integritylance</title>
		<link>http://blog.calevans.com/2009/02/09/5-tools-every-php-developer-should-master/comment-page-1/#comment-62905</link>
		<dc:creator>Integritylance</dc:creator>
		<pubDate>Sun, 08 Mar 2009 14:46:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.calevans.com/?p=409#comment-62905</guid>
		<description>Excellent find, I will make a note to mention it on our site.</description>
		<content:encoded><![CDATA[<p>Excellent find, I will make a note to mention it on our site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PHPSP.org.br &#187; Blog Archive &#187; 5 coisas que um programador PHP precisa</title>
		<link>http://blog.calevans.com/2009/02/09/5-tools-every-php-developer-should-master/comment-page-1/#comment-62112</link>
		<dc:creator>PHPSP.org.br &#187; Blog Archive &#187; 5 coisas que um programador PHP precisa</dc:creator>
		<pubDate>Tue, 17 Feb 2009 09:06:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.calevans.com/?p=409#comment-62112</guid>
		<description>[...] eles já se consideram programadores, e logicamente, as coisas não funcionam bem assim. Inspirado num post do Cal Evans (se você nunca ouviu falar nesse nome, google-for-it ! agora!) em que ele diz 5 ferramentas que um [...]</description>
		<content:encoded><![CDATA[<p>[...] eles já se consideram programadores, e logicamente, as coisas não funcionam bem assim. Inspirado num post do Cal Evans (se você nunca ouviu falar nesse nome, google-for-it ! agora!) em que ele diz 5 ferramentas que um [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AppBeacon</title>
		<link>http://blog.calevans.com/2009/02/09/5-tools-every-php-developer-should-master/comment-page-1/#comment-61965</link>
		<dc:creator>AppBeacon</dc:creator>
		<pubDate>Sat, 14 Feb 2009 01:36:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.calevans.com/?p=409#comment-61965</guid>
		<description>&quot;Active State realizes that every file is not a project and that a developer should only have to use a project when they actually want a project.&quot;

I couldn&#039;t agree more.  I left Komodo to try out Aptana, NetBeans, even IntelliJ and several others.  Almost to a T, they can&#039;t open an individual file from another source for quick editing.  Project this, project that.

Give me a break.  Sometimes, you JUST need to EDIT.</description>
		<content:encoded><![CDATA[<p>&#8220;Active State realizes that every file is not a project and that a developer should only have to use a project when they actually want a project.&#8221;</p>
<p>I couldn&#8217;t agree more.  I left Komodo to try out Aptana, NetBeans, even IntelliJ and several others.  Almost to a T, they can&#8217;t open an individual file from another source for quick editing.  Project this, project that.</p>
<p>Give me a break.  Sometimes, you JUST need to EDIT.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Plush</title>
		<link>http://blog.calevans.com/2009/02/09/5-tools-every-php-developer-should-master/comment-page-1/#comment-61874</link>
		<dc:creator>Jim Plush</dc:creator>
		<pubDate>Wed, 11 Feb 2009 17:37:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.calevans.com/?p=409#comment-61874</guid>
		<description>Hey Cal, 
I saw the headline on my rss aggregator and I thought it was going to be some crappy write up saying smarty is a must know. Glad to see it was actual a worthwhile article. When I first came to Panasonic their web team&#039;s idea of source control was zip files with a &quot;master&quot; owner. yikes!</description>
		<content:encoded><![CDATA[<p>Hey Cal,<br />
I saw the headline on my rss aggregator and I thought it was going to be some crappy write up saying smarty is a must know. Glad to see it was actual a worthwhile article. When I first came to Panasonic their web team&#8217;s idea of source control was zip files with a &#8220;master&#8221; owner. yikes!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tarique Sani</title>
		<link>http://blog.calevans.com/2009/02/09/5-tools-every-php-developer-should-master/comment-page-1/#comment-61858</link>
		<dc:creator>Tarique Sani</dc:creator>
		<pubDate>Wed, 11 Feb 2009 09:25:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.calevans.com/?p=409#comment-61858</guid>
		<description>Hey Cal, thanks for the reply and you need not be so defensive :D 

I fully agree with Unit test after M1 and specs do indeed change   

/me sighs, leaves the spec changing rant for some other time and bookmarks this page to show to clients</description>
		<content:encoded><![CDATA[<p>Hey Cal, thanks for the reply and you need not be so defensive :D </p>
<p>I fully agree with Unit test after M1 and specs do indeed change   </p>
<p>/me sighs, leaves the spec changing rant for some other time and bookmarks this page to show to clients</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: markux</title>
		<link>http://blog.calevans.com/2009/02/09/5-tools-every-php-developer-should-master/comment-page-1/#comment-61857</link>
		<dc:creator>markux</dc:creator>
		<pubDate>Wed, 11 Feb 2009 09:06:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.calevans.com/?p=409#comment-61857</guid>
		<description>The best ERD tool is SQLYog http://www.webyog.com/en/sqlyog_feature_list.php (but only for mysql)

I use seagull framework that it&#039;s an application framework (ready to use with a db schema, user handle, autenthication, permission e menu nagivation fully customizable from admin panel).</description>
		<content:encoded><![CDATA[<p>The best ERD tool is SQLYog <a href="http://www.webyog.com/en/sqlyog_feature_list.php" rel="nofollow">http://www.webyog.com/en/sqlyog_feature_list.php</a> (but only for mysql)</p>
<p>I use seagull framework that it&#8217;s an application framework (ready to use with a db schema, user handle, autenthication, permission e menu nagivation fully customizable from admin panel).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
