The attitude of these pattern junkies doesn't work with me. *I* will decide whether or not I will use a particular design pattern, and *I* will decide how I implement it. This usually means that I don't use design patterns at all, and those that I do use are implemented in my own unique way. Because of this I am widely regarded as a maverick, a heretic and an outcast by those who consider themselves to be "proper" OO programmers.

Comments in the Reddit post talk about DI not being a "silver bullet", how it "empowers polymorphism" and how design patterns should not be done for the same of using design patterns

It's quite obvious that the state of Joomla! is not one of stability, as evidenced by recent threads on the Joomla! Bug Squad. Threads such as Help in admin menu, Thanks but no thanks, and The purpose and tone of the bug squad list all demonstrate that there is a severe rift between the leadership and the community, and within members of the community as well. Simply put, now is not the time for the Joomla! community, especially the volunteers of the Joomla! Bug Squad, to fall apart.

In his opinion, the Joomla community can't continue to function like this without causing the project to collapse under itself. Pushing away the new developers just wanting to help and putting egos ahead of good contributions only hurts things.

The Joomla! Project CAN NOT go on in this state. Chasing away the volunteers will not do anything productive. Putting your own ego before the collective Joomla! ego will not do anything productive. Not having an open mind will not do anything productive. And being overly offended by the use of a certain term by a non-English speaker certainly will not do anything productive. Change needs to happen.

With the rise of PHP developer as career, many are trying to get their share in the pie. Lately I've met a number of developers who have worked for more than one/two years in developing PHP applications in various companies and they consider themselves as "senior" developers.

Key things to keep an eye out for are the "more talk, less code" they tend to do and the lack of dedication to the tasks at hand. These bad developers then follow up with the typical blame to the junior developers, noting that it was them being difficult that caused all of the "real" problems.

So far I've always thought false would evaluate to 0 when used in a computational context. Turns out that this isn't always the case.

His code example tries to check is a false value is greater than or equal to a negative number. The result, however (despite the thinking that false is a zero value) turns out to be false.

I randomly stumbled upon this when arguing with Mariano today if setting Model::recursive to 'false' has the same effect as setting it to '-1'. Turns out that cake uses a statement like this: if ($recursive > -1) in the core which in turn makes -1 and false do exactly the same thing.

Yesterday I released Suhosin 0.9.17 in response to a bug report by Ilia Alshanetsky and some crash problems with PHP 4 that were reported during the last weeks.

The issue dealt with a method to "bypass the hard_memory_limit of Suhosin due to a bug in PHP" that could result in memory consumption up into the gigabyte range for a single script. The patch takes care of the issue by not allowing negative memory_limit settings, preventing the problem from happening.

Personally I haven't tested ext/filter. I should no doubt be shot like a rabid dog for daring to post about this for that reason alone. Commenting idly without any knowledge of an extension is obviously illegal somewhere, possibly China.

He notes that some of the comments (the more inflammatory ones) were a bit out of place, and that feedback about issues has its place - not in major public view. He worries that the negative comments will cast a negative shadow on the extension and that the "back and forth" that's a result of it only serves to cause more trouble than it's worth.

To start off right, you need to know how the service works and what kind of methods you'll need to access it. They show a simple connection to the service as well as two functions to mark something as spam and to mark it as non-spam (or 'ham' as he calls it). He also links to their development page and to the WordPress plugin that performs the same action.