Stefan Koopmanschap has a new post today talking about code reviews and introducing the concept for those not familiar with what they are or their usefulness.

Code reviewing is exactly what it sounds like: It is reviewing code written by another developer. There are different ways of doing this, but in the end it all comes down to having at least one other set of eyes checking any code written before it is released. There’s many reasons for doing code reviews. It can be to prevent security issues, to ensure correct performance of your application, to prevent bugs but eventually it all comes down to the more generic term of ensuring the quality of your application.

He goes on to talk about some of the most common ways to do code reviews, either in something a simple as a pull request out to face-to-face discussions as the code is being introduced. He includes some hints on preparing for the review, steps to perform the review, dealing constructively with the comments made and finally the approval. He talks about who should do the reviewing and how they can still be useful even if you work alone or with a QA department.

If you're relatively new to web development, you might not know exactly what kinds of benefits that using an HTTPS connection might provide. In this new article from the SitePoint PHP blog, Mufleeh Sadique covers some of the basics of HTTPS and gives some reasons why to "go HTTPS" in your applications.

Hypertext Transfer Protocol Secure or Hypertext Transfer Protocol over SSL is used for secure communication over a network, or perhaps more importantly – over the Internet. You would see https:// in the URI and a lock icon in the browser when you access a page that uses HTTPS. [...] If you ever wondered whether and how to go HTTPS with your website, we’ll attempt to clear this up in this article by briefly describing what HTTPS is about, and why and how to implement it.

He's broken the rest of the article up into a few different sections. The first answers the question "why HTTPS" with a few reasons including the most important - encrypted communication. In the second section, he starts showing you how to "go HTTPS" using a self-signed certificate to start. With the certificate installed, he moves into the last part, ensuring your application is always using the HTTPS version and redirecting anything else.

According to this new post from Scott Mattocks today, there's a new article in a new section of the php|archtiect site detailing the evolution of PHP-GTK.

This article is a first in a series of PHP-GTK articles. My goal is to start with PHP developers that have never heard of PHP-GTK and slowly but surely get them to the point where they can develop their own PHP-GTK apps with minimal headaches. Part one of this series doesn’t jump into any development. It simply gives a bit of background. This article explains where PHP-GTK came from and how it can be useful in the real world. As always, I welcom comments, ideas and suggestions, not just about this article but also about future articles that you would like to see written.

The article looks at PHP-GTK from its humblest beginnings (the filesystem functions) out to what it is and what it's used for. There's also a brief discussion of where it's headed as well, including links to a few different resources on the topic.

According to this new post from Scott Mattocks today, there's a new article in a new section of the php|archtiect site detailing the evolution of PHP-GTK.

This article is a first in a series of PHP-GTK articles. My goal is to start with PHP developers that have never heard of PHP-GTK and slowly but surely get them to the point where they can develop their own PHP-GTK apps with minimal headaches. Part one of this series doesn’t jump into any development. It simply gives a bit of background. This article explains where PHP-GTK came from and how it can be useful in the real world. As always, I welcom comments, ideas and suggestions, not just about this article but also about future articles that you would like to see written.

The article looks at PHP-GTK from its humblest beginnings (the filesystem functions) out to what it is and what it's used for. There's also a brief discussion of where it's headed as well, including links to a few different resources on the topic.

From David Ramalho's blog today, he takes a look at not how to write PHP, but how he writes PHP - focusing mainly on the tools he uses, especially Eclipse.

Friends, I’m sure the post would be a heck of a lot funnier if instead of "How" I would write "Why", but I’m sticking to "How" for...now.

He says some about what Eclipse is and how it can be extended, specifically mentioning the PHPeclipse Project.

The PHPeclipse project aims to create a full featured PHP IDE with features like internal PHP parser, debugger, code formatter, outline view, templates and much more.

There are also a foew other tools he mentions: a Subversion plugin, XMLBuddy, and the JSEclipse plugin...

From David Ramalho's blog today, he takes a look at not how to write PHP, but how he writes PHP - focusing mainly on the tools he uses, especially Eclipse.

Friends, I’m sure the post would be a heck of a lot funnier if instead of "How" I would write "Why", but I’m sticking to "How" for...now.

He says some about what Eclipse is and how it can be extended, specifically mentioning the PHPeclipse Project.

The PHPeclipse project aims to create a full featured PHP IDE with features like internal PHP parser, debugger, code formatter, outline view, templates and much more.

There are also a foew other tools he mentions: a Subversion plugin, XMLBuddy, and the JSEclipse plugin...

With a continuation of their previous article, WebReference has posted part two of their "How to Interact with Web Forms" series - an excerpt from the PHP Phrasebook (Sams).

They build on the previous code, showing how to:

• preselect items from a multiple select list,
• process image submit buttons
• checking the mandatory fields
• checking the values of select lists

They wrap it all up with two handy concepts - how to write out your data to a form and send it off in email form to the location of your choosing and working with the files uploaded via a form.

With a continuation of their previous article, WebReference has posted part two of their "How to Interact with Web Forms" series - an excerpt from the PHP Phrasebook (Sams).

They build on the previous code, showing how to:

• preselect items from a multiple select list,
• process image submit buttons
• checking the mandatory fields
• checking the values of select lists

They wrap it all up with two handy concepts - how to write out your data to a form and send it off in email form to the location of your choosing and working with the files uploaded via a form.