PHPDeveloper.org

Aaron Jorbin's Blog: Commit: The Story of Writing a WordPress Patch

Mon, 09 Aug 2010 12:57:17 -0500

For those that have considered contribute back to the WordPress project but weren't sure what the experience might be like, you should check out this helpful post from Aaron Jorbin with his story.

Hanging out in the #WordPress irc channel or on the wp-hackers mailing list, a question that comes up from time to time is '�How do I get a bug patched'�. I recently had a patch committed, so I thought I would detail the process from start to finish to help others get an idea of the process.

He shares three lessons he learned during the experience - make it easy for non-coders to see the change, getting suggestions from other developers on the patch and realizing that sometimes, a small change in one place can break other things too.

Smashing Magazine: Lessons Learned from Maintaining a WordPress Plugin

Mon, 02 Aug 2010 11:08:05 -0500

On Smashing Magazine today there's a new article from Joost de Valk about some of the things he learned from maintaining a WordPress plugin - one to help easily track your site via Google Analytics.

Recently I released a WordPress plugin for Google Analytics that adds a tracking code and dozens of various pieces of meta data to blogs. Since the release of version 4, I've updated it 6 times, to the point where it's now at version 4.0.6. In this article I would like to share with you my experiences in maintaining this and other WordPress plug-ins and common good practices that I've distilled from that work.

He breaks it up into a few different categories:

Website and Account Configuration
Versioning Option Arrays
Don't Release Too Soon
Know Which Version People Are On
URLs in WordPress
Writing to the Root Directory
Rethink Your Filters
Never Assume

Matrin Rusev's Blog: Building a PHP Framework - Lessons Learned

Thu, 26 Feb 2009 12:02:32 -0600

If you're thinking of trying your hand at creating your own PHP framework, you might want to check out this post from Matrin Rusev about some of the lessons he learned (the hard way) about framework construction.

After using Codeigniter, CakePHP and Zend Framework for a while I decided to build my own framework. I wanted to include some features that I couldn't find the way I like them in none of the projects I tested. These are some lessons I learned the hard way. I hope you'd find some useful tips for your software projects.

The post looks a a few different topics - doing good planning before development starts, using third-party libraries, planning out the syntax the components inside of your framework will use, how to handle debugging and two tools you can use to benchmark the end result.

Deasil.com: Lessons to be learned from PHP

Sat, 12 Jan 2008 20:04:00 -0600

In a new post to the blog at deasil.com, they talk about some of the lessons they see that can be learned from PHP and how it works/is packaged up.

PHP, though, came along with a breakthrough idea - mod_php was an everything in one install. Unlike mod_perl, mod_php gave you a programming language, templating language and extension all in one.

He advocates the PHP language developer's decisions to include everything into the core of the language which (while maybe not the best of decisions) has made PHP into one of the most practical development languages and has helped to make it one of the most popular and widely used languages on the web.