<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: 5 Tips To Speed Up PHP Development</title>
	<link>http://phpit.net/article/5-tips-to-speed-up-php-development/</link>
	<description>PHPit has dozens of PHP articles, codesnippets and FAQ's.</description>
	<pubDate>Wed, 21 May 2008 02:16:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Steve</title>
		<link>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-8840</link>
		<pubDate>Tue, 25 Jul 2006 17:51:29 +0000</pubDate>
		<guid>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-8840</guid>
					<description>Frameworks are good. But make sure you select one that you are comfortable with. Don't just follow the pack.</description>
		<content:encoded><![CDATA[<p>Frameworks are good. But make sure you select one that you are comfortable with. Don&#8217;t just follow the pack.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: WC</title>
		<link>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-7401</link>
		<pubDate>Wed, 12 Jul 2006 11:07:48 +0000</pubDate>
		<guid>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-7401</guid>
					<description>1)  Publishing your source code does -not- make it more vulnerable.  Bad coding does.  Publishing bad code only makes it easier to find the loopholes.

2)  Extending a framework is easier than writing the whole thing from scratch.

3)  Licenses can't change on the current version of a module.  Future revisions, yes, but not the current one.  Update of -anything- can break your code.  That's life.  It's still a -lot- faster to fix the new problem than write everything from scratch.

The programming market is changing.  Speed of code is not nearly as important as it used to be, and speed of creating code is much more important.

There will always be jobs for 'reinvent' people, but the current market trend is towards 'reuse' people.</description>
		<content:encoded><![CDATA[<p>1)  Publishing your source code does -not- make it more vulnerable.  Bad coding does.  Publishing bad code only makes it easier to find the loopholes.</p>
<p>2)  Extending a framework is easier than writing the whole thing from scratch.</p>
<p>3)  Licenses can&#8217;t change on the current version of a module.  Future revisions, yes, but not the current one.  Update of -anything- can break your code.  That&#8217;s life.  It&#8217;s still a -lot- faster to fix the new problem than write everything from scratch.</p>
<p>The programming market is changing.  Speed of code is not nearly as important as it used to be, and speed of creating code is much more important.</p>
<p>There will always be jobs for &#8216;reinvent&#8217; people, but the current market trend is towards &#8216;reuse&#8217; people.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: makro</title>
		<link>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-6622</link>
		<pubDate>Thu, 06 Jul 2006 17:54:10 +0000</pubDate>
		<guid>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-6622</guid>
					<description>I partially agree with the author BUT i have to say, that many Frameworks as well as Scripts have various downsides, which could well slow down the development process in the long run:

1.) Licenses: What to do if you used a script / framework under GPL (free) and want to go commercial?
-     You have to publish all of your code, what in turn makes the whole application vulnerabe, because everyone can see your source.

2.) Functions: What if you depend on a framework and some day need to implement functionality, which the framework does not provide.

- You have to rewrite the app or extend the framework itself. All your changes are like to be lost after a applying a Framework (sourcecode) update.

3.) Modules: So you use modules for your framework to speed up development, huh? 

- Many bad things can happen to your app: Sourcecode of every module you use is public (vulnerable).
- Licenses can change, can be tricky or expensive.
- Updates of the framework can break the module.
....

There are many other concerns on this topic but they would be out of scope of this posting.

For my work as freelance programmer and systems professional i always "reinvented" the wheel and this is what i got:

Thin, fast, reliable, "personal" and secure Applications or Daemons.
No other solution than the tailored one can really do what you (or the customer) want to do it.
Frameworks and CMS are often slow, unsecure and offer all-singing-all-dancing stuff, you really will (probably) not need.

I always said: Quality overrules Quantity.

If more Programmers and Companies would get the point of this statement, there wouldnt be so much, really much, crap pieces of software out there. 
Additionally, speeding the development process (which includes analysis and design AND testing / debugging) has negative effects on the income of the developer and the financial expectations of your customers. This is where relationships between development, open source, closed source, marketing and so on come into view and covering these here would be FAR BEYOND the scope of the article and this posting.

It always is hard for the worker when the market exploits his industry.

Greetz,
makro</description>
		<content:encoded><![CDATA[<p>I partially agree with the author BUT i have to say, that many Frameworks as well as Scripts have various downsides, which could well slow down the development process in the long run:</p>
<p>1.) Licenses: What to do if you used a script / framework under GPL (free) and want to go commercial?<br />
-     You have to publish all of your code, what in turn makes the whole application vulnerabe, because everyone can see your source.</p>
<p>2.) Functions: What if you depend on a framework and some day need to implement functionality, which the framework does not provide.</p>
<p>- You have to rewrite the app or extend the framework itself. All your changes are like to be lost after a applying a Framework (sourcecode) update.</p>
<p>3.) Modules: So you use modules for your framework to speed up development, huh? </p>
<p>- Many bad things can happen to your app: Sourcecode of every module you use is public (vulnerable).<br />
- Licenses can change, can be tricky or expensive.<br />
- Updates of the framework can break the module.<br />
&#8230;.</p>
<p>There are many other concerns on this topic but they would be out of scope of this posting.</p>
<p>For my work as freelance programmer and systems professional i always &#8220;reinvented&#8221; the wheel and this is what i got:</p>
<p>Thin, fast, reliable, &#8220;personal&#8221; and secure Applications or Daemons.<br />
No other solution than the tailored one can really do what you (or the customer) want to do it.<br />
Frameworks and CMS are often slow, unsecure and offer all-singing-all-dancing stuff, you really will (probably) not need.</p>
<p>I always said: Quality overrules Quantity.</p>
<p>If more Programmers and Companies would get the point of this statement, there wouldnt be so much, really much, crap pieces of software out there.<br />
Additionally, speeding the development process (which includes analysis and design AND testing / debugging) has negative effects on the income of the developer and the financial expectations of your customers. This is where relationships between development, open source, closed source, marketing and so on come into view and covering these here would be FAR BEYOND the scope of the article and this posting.</p>
<p>It always is hard for the worker when the market exploits his industry.</p>
<p>Greetz,<br />
makro
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Kevin</title>
		<link>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-1774</link>
		<pubDate>Wed, 17 May 2006 06:11:26 +0000</pubDate>
		<guid>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-1774</guid>
					<description>I would have to disagree with the part that says: Don't re-invent the wheel. This is a very limited way to tell php programmers, as being lazy and not promoting development. Yes you can customize those scripts, but why do that when you have to ability to code your own. Who cares if it takes a little while, atleast it can be a very good learning tool. But I do have to say people new to php could use one of those, but don't discourage ones who are able to code their own CMS, or whatever.</description>
		<content:encoded><![CDATA[<p>I would have to disagree with the part that says: Don&#8217;t re-invent the wheel. This is a very limited way to tell php programmers, as being lazy and not promoting development. Yes you can customize those scripts, but why do that when you have to ability to code your own. Who cares if it takes a little while, atleast it can be a very good learning tool. But I do have to say people new to php could use one of those, but don&#8217;t discourage ones who are able to code their own CMS, or whatever.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: SN</title>
		<link>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-636</link>
		<pubDate>Thu, 23 Feb 2006 01:39:28 +0000</pubDate>
		<guid>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-636</guid>
					<description>I have been using a framework not mentioned in the tips called &lt;a href="http://zoopframework.com" rel="nofollow"&gt;Zoop Framework for PHP&lt;/a&gt;. It has really helped me productivity wise. Thanks for your tips. Additionally I have been using &lt;a href="http://quanta.kdewebdev.org/" rel="nofollow"&gt;Quanta&lt;/a&gt; myself as an Editor. It doesn't have a windows port, but runs great on linux and macOSX, is free, and has an Intellisense like feature.</description>
		<content:encoded><![CDATA[<p>I have been using a framework not mentioned in the tips called <a href="http://zoopframework.com" rel="nofollow">Zoop Framework for PHP</a>. It has really helped me productivity wise. Thanks for your tips. Additionally I have been using <a href="http://quanta.kdewebdev.org/" rel="nofollow">Quanta</a> myself as an Editor. It doesn&#8217;t have a windows port, but runs great on linux and macOSX, is free, and has an Intellisense like feature.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Luk</title>
		<link>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-567</link>
		<pubDate>Thu, 09 Feb 2006 19:41:19 +0000</pubDate>
		<guid>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-567</guid>
					<description>For me the best editor is Notepad++</description>
		<content:encoded><![CDATA[<p>For me the best editor is Notepad++
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Matt Kaufman</title>
		<link>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-164</link>
		<pubDate>Tue, 22 Nov 2005 08:04:53 +0000</pubDate>
		<guid>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-164</guid>
					<description>I have a license that I bought for Zend IDE, and I actually prefer (and use) jEdit over it .. it's far faster and has a great set of plugins that can be added in very easily: http://jedit.org</description>
		<content:encoded><![CDATA[<p>I have a license that I bought for Zend IDE, and I actually prefer (and use) jEdit over it .. it&#8217;s far faster and has a great set of plugins that can be added in very easily: <a href='http://jedit.org' rel='nofollow'>http://jedit.org</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dennis Pallett</title>
		<link>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-14</link>
		<pubDate>Fri, 28 Oct 2005 14:12:32 +0000</pubDate>
		<guid>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-14</guid>
					<description>I don't really like PHPDoc type of comments myself. I find them really annoying, and it really clutters up my PHP files. I'd rather have the documentation seperate.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t really like PHPDoc type of comments myself. I find them really annoying, and it really clutters up my PHP files. I&#8217;d rather have the documentation seperate.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Spajus</title>
		<link>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-13</link>
		<pubDate>Fri, 28 Oct 2005 09:34:00 +0000</pubDate>
		<guid>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-13</guid>
					<description>There's no alternative for speeding up things to Zend Studio. Code coloring is a must for even a text viewer nowadays. And you should use PHPDOC type of comments, not //some thing ones...</description>
		<content:encoded><![CDATA[<p>There&#8217;s no alternative for speeding up things to Zend Studio. Code coloring is a must for even a text viewer nowadays. And you should use PHPDOC type of comments, not //some thing ones&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Daniel</title>
		<link>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-12</link>
		<pubDate>Thu, 27 Oct 2005 00:37:37 +0000</pubDate>
		<guid>http://phpit.net/article/5-tips-to-speed-up-php-development/#comment-12</guid>
					<description>I too use PHP Designer 2005.  It is very handy, especially when you download the interpretor (http://www.php.net/downloads.php).  The interface shows the includes and classes in a tree so you can see the layout.  Also has the code coloring for HTML, CSS, XML, PERL, JS, VB, C# and even SQLs.  As stated in the beginning of this article, I used to be one of the 'notepadders'. :)  I must admit though... Not having to count lines to find an error (with wordwrap turned off) is worth a lot to me!!  Great article, Thanks much!</description>
		<content:encoded><![CDATA[<p>I too use PHP Designer 2005.  It is very handy, especially when you download the interpretor (http://www.php.net/downloads.php).  The interface shows the includes and classes in a tree so you can see the layout.  Also has the code coloring for HTML, CSS, XML, PERL, JS, VB, C# and even SQLs.  As stated in the beginning of this article, I used to be one of the &#8216;notepadders&#8217;. :)  I must admit though&#8230; Not having to count lines to find an error (with wordwrap turned off) is worth a lot to me!!  Great article, Thanks much!
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
