<?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: Rapid development programming frameworks</title>
	<atom:link href="http://www.inetinteractive.com/blog/rapid-development-programming-frameworks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.inetinteractive.com/blog/rapid-development-programming-frameworks/</link>
	<description></description>
	<lastBuildDate>Wed, 09 Nov 2011 20:02:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Aaron Forgue</title>
		<link>http://www.inetinteractive.com/blog/rapid-development-programming-frameworks/comment-page-1/#comment-49</link>
		<dc:creator>Aaron Forgue</dc:creator>
		<pubDate>Mon, 14 Apr 2008 14:03:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.inetinteractive.com/blog/development/rapid-development-programming-frameworks/#comment-49</guid>
		<description>Michael,
I totally agree with your disdain towards the &quot;jack of all trades&quot; approach. However, I feel that you can have the best of both worlds.

Once you have honed your PHP (or language of choice) skills and know the language through-and-through, the next logical step is to create a structured process or workflow for developing applications. Having a structured system allows your code to remain consistent over several projects (increasing maintainability) and also allows for reuse of common code (eliminating the coding redundancy). This can be accomplished either by creating your own framework or adopting a third party framework that you are comfortable with.

Whichever path you choose, I wholeheartedly agree that a thorough understanding of your chosen language is an absolute requirement before diving into any type of framework.</description>
		<content:encoded><![CDATA[<p>Michael,<br />
I totally agree with your disdain towards the &#8220;jack of all trades&#8221; approach. However, I feel that you can have the best of both worlds.</p>
<p>Once you have honed your PHP (or language of choice) skills and know the language through-and-through, the next logical step is to create a structured process or workflow for developing applications. Having a structured system allows your code to remain consistent over several projects (increasing maintainability) and also allows for reuse of common code (eliminating the coding redundancy). This can be accomplished either by creating your own framework or adopting a third party framework that you are comfortable with.</p>
<p>Whichever path you choose, I wholeheartedly agree that a thorough understanding of your chosen language is an absolute requirement before diving into any type of framework.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Kilday</title>
		<link>http://www.inetinteractive.com/blog/rapid-development-programming-frameworks/comment-page-1/#comment-39</link>
		<dc:creator>Michael Kilday</dc:creator>
		<pubDate>Thu, 10 Apr 2008 19:30:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.inetinteractive.com/blog/development/rapid-development-programming-frameworks/#comment-39</guid>
		<description>I&#039;d rather just learn something like Php inside and out, rather than Php -and- a Php framework on top of it. I personally prefer being very good at a few things opposed to being pretty good at many things. This is my perspective as a freelance coder wanting the offer clients everything and the kitchen sink when they ask for it.</description>
		<content:encoded><![CDATA[<p>I&#8217;d rather just learn something like Php inside and out, rather than Php -and- a Php framework on top of it. I personally prefer being very good at a few things opposed to being pretty good at many things. This is my perspective as a freelance coder wanting the offer clients everything and the kitchen sink when they ask for it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

