php|tek aims to be the conference of reference for PHP enthusiasts and professionals. As such, it features technical talks on topics that range from programming paradigms to internals development, all aimed at an audience comprised of beginners and professionals alike.

This year's theme is "$build->deploy->scale();"'"a nod to PHP's growing role in the rapid development of Internet applications of all sizes, from small to massive, covering a wide array of PHP-related topics. Regardless of the subject, we are partial to talks that tackle a specific issue in a thorough way, with a very pragmatic slant. Remember, attendees will come to the conference with the intent of learning something that they can take home and use in their daily lives'"they are not necessarily interested in why things work, but they are definitely interested in how they work.

Speakers get free access to the conference, some travel assistance (not completely paid for), and compensation for each of the talks given. Instead of havaing specific tracks of talks, they're opting for a "tag-based" approach, applying as many tags that fit to the talk.

To submit your talk ideas, send them off to proposals@phparch.com and include the usual contact info as well as a title, synopsis, audience level, talk type, and topics included in the presentation.

php|tek aims to be the conference of reference for PHP enthusiasts and professionals. As such, it features technical talks on topics that range from programming paradigms to internals development, all aimed at an audience comprised of beginners and professionals alike.

This year's theme is "$build->deploy->scale();"'"a nod to PHP's growing role in the rapid development of Internet applications of all sizes, from small to massive, covering a wide array of PHP-related topics. Regardless of the subject, we are partial to talks that tackle a specific issue in a thorough way, with a very pragmatic slant. Remember, attendees will come to the conference with the intent of learning something that they can take home and use in their daily lives'"they are not necessarily interested in why things work, but they are definitely interested in how they work.

Speakers get free access to the conference, some travel assistance (not completely paid for), and compensation for each of the talks given. Instead of havaing specific tracks of talks, they're opting for a "tag-based" approach, applying as many tags that fit to the talk.

To submit your talk ideas, send them off to proposals@phparch.com and include the usual contact info as well as a title, synopsis, audience level, talk type, and topics included in the presentation.

If you just can't get enough information on the Zend Framework and are looking for a good overview of where it's come from and where it's going, you should check out the latest issue of php|architect magazine with the cover article from Mike Naberezny.

In the article, I begin by introducing Zend's motivations for creating a framework and how it relates to their PHP Collaboration Project. More information on these topics can be found on the Zend Framework website. I then dive into a tutorial where I take a business scenario and show how the components included in the Zend Framework can be put to work.

The article demonstrates a workflow where invoice data is retrieved from a web service, an invoice in PDF format is then built from that data, and finally the resultant file is emailed to a customer. The components Zend_XmlRpc_Client, Zend_Pdf, Zend_Mail, and Zend_Search_Lucene are explored along the way.

You can purchase both a print and electronic (PDF) copy directly from the php|architect site - no need to subscribe and a single issue only costs $3.50 USD.

If you just can't get enough information on the Zend Framework and are looking for a good overview of where it's come from and where it's going, you should check out the latest issue of php|architect magazine with the cover article from Mike Naberezny.

In the article, I begin by introducing Zend's motivations for creating a framework and how it relates to their PHP Collaboration Project. More information on these topics can be found on the Zend Framework website. I then dive into a tutorial where I take a business scenario and show how the components included in the Zend Framework can be put to work.

The article demonstrates a workflow where invoice data is retrieved from a web service, an invoice in PDF format is then built from that data, and finally the resultant file is emailed to a customer. The components Zend_XmlRpc_Client, Zend_Pdf, Zend_Mail, and Zend_Search_Lucene are explored along the way.

You can purchase both a print and electronic (PDF) copy directly from the php|architect site - no need to subscribe and a single issue only costs $3.50 USD.

In his latest blog post, Jeff Moore adds a bit more background to his column in the newest issue of php|architect covering "dependency injection".

The June issue of PHP Architect is out. My column this month is on dependency injection, a topic which I've been warming up to lately.

First there was CORBA. Then insane complexity of CORBA was supplanted by the intolerable complexity of EJB. Influenced by an agile mindset and the power of Unit testing, a group of java programmers began to construct simpler alternatives to EJB. Thus, the inversion of control frameworks were born. Martin Fowler came along, clarified and renamed the pattern dependency injection. This activity has originated in the Java world, but the pattern applies in PHP as well.

It is heartening to see an industry solve a problem over the course of a decade, moving from complex vendor driven middle-ware to simple patterns. The thing I like most about DI is how dead simple it really is.

He goes on to say that Fowler's article on the topic is a "must read" for anyone who will even be looking into dependency injection. He also mentions two issues he has with most of the other introductions - the examples they use and the "over-emphasis on the container".

His goal in writing this month's column was to help to avoid some of those problems while still keeping it relevant and easy to understand.

In his latest blog post, Jeff Moore adds a bit more background to his column in the newest issue of php|architect covering "dependency injection".

The June issue of PHP Architect is out. My column this month is on dependency injection, a topic which I've been warming up to lately.

First there was CORBA. Then insane complexity of CORBA was supplanted by the intolerable complexity of EJB. Influenced by an agile mindset and the power of Unit testing, a group of java programmers began to construct simpler alternatives to EJB. Thus, the inversion of control frameworks were born. Martin Fowler came along, clarified and renamed the pattern dependency injection. This activity has originated in the Java world, but the pattern applies in PHP as well.

It is heartening to see an industry solve a problem over the course of a decade, moving from complex vendor driven middle-ware to simple patterns. The thing I like most about DI is how dead simple it really is.

He goes on to say that Fowler's article on the topic is a "must read" for anyone who will even be looking into dependency injection. He also mentions two issues he has with most of the other introductions - the examples they use and the "over-emphasis on the container".

His goal in writing this month's column was to help to avoid some of those problems while still keeping it relevant and easy to understand.