On the PHPDelusions.com site there's a post that compares the functionality of mysqli to PDO and looks at the differences in their overall usability.

By no means I am going to say that mysqli is worse than PDO. Mysqli is an excellent extension, with many specific features. But it's just not intended to be used directly. To make it usable, one have to always wrap it into a helper library, to reduce the enormous amount of code that otherwise have to be written by hand.

[...] But for the average PHP/MySQL user, standard APIs are the only known methods for database interaction. Thus they tend to use both extensions right in the application code, without any intermediate wrapper around. For such a use PDO is an indisputable winner, and I'll show you why.

The post then breaks it down into sections comparing the functionality between the two database access methods:

• Named placeholders
• General inconvenience in binding
• Getting single column value
• Getting multiple rows
• Binding unknown number of parameters
• Compatibility

Of course, all the inconveniences above could be overcame by a good wrapper. This is why if you choose mysqli, you definitely have to use one.

On the latest episode of the Full Stack Radio podcast host Adam Wathan sits down with Jeffrey Way of the Laracasts website for an interview.

In this episode, Adam talks with Jeffrey Way of Laracasts about learning, object oriented design, testing, API usability, and whole bunch of other stuff.

You can listen to this interview either through the in-page audio player or by downloading the mp3 directly. If you enjoy the episode, be sure to subscribe to their feed to get the latest episodes as they're released.

Francois Zaninotto has a recent post looking at something every developer should consider when creating their applications - especially the libraries that might be used by other developers: code usability.

Usability guidelines can sometimes be of use in awkward places. I try to apply them to source code. [...] Of course, coding guidelines are there to make the code easy to read by everyone. But code usability goes somehow beyond. Let's see some of the differences.

He compares good versus bad code in a few different areas:

• Bad Code Comments
• Split Up Code
• Cleanliness
• New Conventions
• Listen To User Feedback

Each item is described, some including code examples to help make them more clear. Be sure to check out the comments for more good suggestions.

Justin Carmony has written up a new article about something every developer (and/or development business) struggles with when hacking away at their code - keeping what the clients want in mind.

Why does it seem so hard to deliver quality products to clients? Sometimes it feels like clients either don’t appreciate quality, or they have their priorities all mixed up. [...] These seems rather obvious, but in-fact many developers get caught up in quality and then are totally surprised when their clients aren’t happy. Why? Because as developers we notice and respect quality a great deal more than suitability.

Part of the problem is that clients don't care about the quality behind the scenes. Most of the time, they just want to see results and don't really care how it was done. He focuses on one thing that can really help you in dealing with these clients - keeping up with that their needs are, not just assuming. This includes a few more specific tips:

• Meet the Client
• See the Need
• Open Communication
• Frequent Client Feedback
• Usability Testing

The Zend Developer Zone has posted part seven of their series covering the development of an Ajax chat application. This time,. they're focusing on some of the final touches - usability improvements.

To start we need to make the chat messages automatically refresh at fixed intervals without requiring user input. We will also add a small message to let the user know when a background request is active. To finish up we remove the necessity of using the "Say It!" button to submit new chat messages.

They show how to make the chat window refresh at an interval (rather than manually), how to have the application tell the user it's doing something (like "loading"), and adding a keypress event to handle the user pressing the enter key to send off their message.

The Zend Developer Zone has posted part seven of their series covering the development of an Ajax chat application. This time,. they're focusing on some of the final touches - usability improvements.

To start we need to make the chat messages automatically refresh at fixed intervals without requiring user input. We will also add a small message to let the user know when a background request is active. To finish up we remove the necessity of using the "Say It!" button to submit new chat messages.

They show how to make the chat window refresh at an interval (rather than manually), how to have the application tell the user it's doing something (like "loading"), and adding a keypress event to handle the user pressing the enter key to send off their message.

From Cclair.nl, there's a new post sharing some code that's been created in an effort to make a "more modern CAPTCHA".

"ModernCaptcha" is a simple script in order to prevent spam in a very user friendly way. In a few words, your visitors don't have to type some characters as you see on the most websites, the verification is made by choosing the company name belonging to the logo that is show.

It's an interesting approach, but, as one reader pointed out, bots has a one in five chance of guessing correctly. That's way less than with a more standard image manipulation CAPTCHA method. I'm not sure I'd want to use it on my sites, but it might be good for a smaller site.

There's a demo of the end result and a download of the latest version as well as some limited support provided in the comments of the post.

From Cclair.nl, there's a new post sharing some code that's been created in an effort to make a "more modern CAPTCHA".

"ModernCaptcha" is a simple script in order to prevent spam in a very user friendly way. In a few words, your visitors don't have to type some characters as you see on the most websites, the verification is made by choosing the company name belonging to the logo that is show.

It's an interesting approach, but, as one reader pointed out, bots has a one in five chance of guessing correctly. That's way less than with a more standard image manipulation CAPTCHA method. I'm not sure I'd want to use it on my sites, but it might be good for a smaller site.

There's a demo of the end result and a download of the latest version as well as some limited support provided in the comments of the post.

On the Shadow Fox Network today, they've posted parts one and two of their look at building a better blogging system.

In part one, they talk about things where all good projects should start - with the planning and what it will take to get the project done. This includes the structure of the application, the usability, and the extensions you'll want to use.

Part two goes a step further into the planning stage by looking specifically at the design and usability of the application. They start with the base HTML and add some styling and images to make it easier to use.

On the Shadow Fox Network today, they've posted parts one and two of their look at building a better blogging system.

In part one, they talk about things where all good projects should start - with the planning and what it will take to get the project done. This includes the structure of the application, the usability, and the extensions you'll want to use.

Part two goes a step further into the planning stage by looking specifically at the design and usability of the application. They start with the base HTML and add some styling and images to make it easier to use.