It would most likely benefit all if the questions/situations/reviews were based on very contemporary (if not forward looking) programming, i.e. the cert would be heavily weighted towards security, state/cookies/sessions, database related, file handling and uploads, and internet/SOAP/CURL.
Maybe a rough categories breakout might look like this: 5 % -- Package(s) and install 5 % -- PHP .ini 15 % -- Security 20 % -- Functions 25 % -- Classes 5 % -- Error Handling 5 % -- RegExp 10 % -- PEAR/PECL 5 % -- Version Control Peter -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of tedd Sent: Wednesday, April 23, 2008 1:17 PM To: NYPHP Talk Subject: Re: [nyphp-talk] About Formalizing an Enterprise PHP and the PHP+Developer Hi gang: It would be nice to be a certified programmer -- I'm certified in other professions and it helps somewhat. However, the problem as I see is two-fold: 1. What's required to become certified (obvious); 2. What are the qualifications of the governing body and its industry's support (not so obvious). First, we need to establish a charter and solicit member participation. Then with numbers comes the authority to establish acceptable and proper criteria for certification. Cheers, tedd -- ------- http://sperling.com http://ancientstones.com http://earthstones.com _______________________________________________ New York PHP Community Talk Mailing List http://lists.nyphp.org/mailman/listinfo/talk NYPHPCon 2006 Presentations Online http://www.nyphpcon.com Show Your Participation in New York PHP http://www.nyphp.org/show_participation.php _______________________________________________ New York PHP Community Talk Mailing List http://lists.nyphp.org/mailman/listinfo/talk NYPHPCon 2006 Presentations Online http://www.nyphpcon.com Show Your Participation in New York PHP http://www.nyphp.org/show_participation.php
