Re:How to write GOOD code? WTF? (Score 1)

As you seem to be seeking a reputation as some kind of authority on PHP, might I suggest you adopt a more considered approach, and use less intemperate language?

It's not clear that you actually know what spaghetti code is. I was already writing structured code when Djikstra's seminal article "Goto consider harmful" was first published.

Many Aliro classes exist in their own files, others are logically grouped. This is an implementation and convenience issue. A whole chapter of my book discusses the complex questions to do with XHTML generation.

Only three lines of Aliro code exist outside classes and functions, and the latter are used only where it is inescapable. By and large, the core classes are tightly logically focussed, such as aliroSession which, amazingly, deals with sessions. Not all of the code in Aliro is at the same level of development - it is a practical project that has a history and antecedents.

Your own published views suggest that you are in danger of embracing a too technical conception of OO that undermines the benefits. And I think you place too much reliance on the widely misunderstood notion of patterns. I give reasons for my view in my book, rather than just making arrogant assertions.

Incidentally, I find it hard to take seriously a PHP expert who can write a line like:
if($feedContent && !empty($feedContent)):

I'm interested in constructive discussion, even if it is critical of my published work. But this isn't remotely constructive, nor even well informed.