It's been a few days since CICONF and this is my first chance to get my thoughts together after a few busy days. In all I am extremely pleased with the event, and so far I have seen nothing but positive feedback on the #ciconf hash-tag and not heard any complaints. Winner!

He goes through both days of the conference - Friday and Saturday - describing things from his perspective (an organizer), some of the speakers that presented and some of the evening activities.

I created my profile on monster.com on a Monday and made it public that night. The following Tuesday morning my telephone went nuts and my email inbox blew up with recruiters reaching out with positions that I was "perfect for". Over the course of the next week and a half (not including weekends) I spent 10-12 hours a day receiving and returning phone calls, and reading and responding to emails from recruiters.

He received calls from all over the country as well - "apparently experienced PHP developers are in short supply". He points out a few things he found interesting about the search like the fact that unit testing was never listed as a requirement (or even a "plus") in descriptions, only a few descriptions talked about memcache and that PHP wasn't the language over half of the employers were looking for.

He also shares a few hints for those looking for jobs right now, things to add to your resume or look for as far as skills most in demand:

• Have experience with frameworks
• Joomla was very commonly being used so being familiar with it is definitely a plus
• Have sample code to show your coding skills
• There's more to the world then PHP

Our fourth episode is all ready for your listening pleasure. In this exciting episode we focus on "The Conference Experience" and discuss why programming conferences are so important to developers. Chris talks about why CodeMash was so awesome and the awesome talks full of awesomeness that he attended. Ed talks about his own experiences with speaking and attending conferences, complete with a total derail by Chris on why a certain conference rubbed him the wrong way. Oh yeah, you also find out our opinions on what constitutes a "well-written PHP application". I'm sure you will be surprised by our answers.

You can either listen to this latest episode either via the in-page player or you can download the mp3 directly.

A friend of mine who is a big supporter of Symfony told me to give Symfony1 a shot. Off course I was skeptical since I knew less about symfony1 than I did on Zend_Tool. That, plus the fact we needed to autoload, bootstrap and get two frameworks up and running simultaneously. What could possibly go wrong! Conclusion: I've got my tool up and running about a 45 minutes later...

He talks about the process he went through to download, setup and configure the framework and start using a "task" to create a simple executable script. He also briefly compares Symfony1 to Symfony2, noting that SF2 is a bit more "out-out-of-the-box friendly" than SF1. The overall experience was a positive one, though. You can find out more about Symfony1 here and Symfony2 here.

I'm talking about people trends and community and HOW. WE. CONNECT. I decided to start old school stylie, and looked up the word 'community' in the dictionary. [...] So community literally means to give gifts to and among each other. Which in turn means my community is a group of people who welcome and honor my gifts, and from whom I can reasonably expect to receive gifts in return.

They go on to talk about the three key elements any good community relies on - the people that make it up, the places they meet (real or virtual) and the "things" that bring them together.

If I could make a single plea to every researcher, academic, economist and reporter it would be to stop counting us and start communicating with us. Learn more about where, why, and how our communities form, and why they're so important to us (even when they don't make us any money).

If you're not already involved in a local user group or haven't attended a conference, it's an experience completely different than sitting behind the keys, hacking day to day. PHP.net has a list of both PHP conferences and upcoming events - find one near you and make plans to attend. You'll be glad you did!

For those who don't know what an advisory board is, conference organizers get loads of proposals and need help deciding who should speak. So they ask others in the industry to provide some feedback. It was quite a learning experience.

He talks some about the "speaker backlash" that comes from being rejected, a lack of professionalism in some submittors and some basic (common sense) recommendations like:

• fill out the form completely, even if you don't think it's all useful
• start locally and then move up. A major conference isn't the place to try out your speaking first-shot
• whet the board's appetite - make them want to hear more about the topic or come up with something new
• share your unique experience with the technology
• use sites like Joind.in, Meetup and SlideShare to your advantage

I hadn't been using Doctrine for a while and decided to pick it up two weeks ago, as we wanted to see if we can implement it for our CMS at our office. So I setup a clean installation of the zend framework (1.11.9) and tried tried to implement Doctrine. The main goal was to see if we can reverse engineer existing databases and then start doing some queries.

There were three things he found in the process that caused a few issues:

• A confusing set of terms and features that weren't explained well enough to know their use
• Getting things like autoloaders working with the Zend Framework to make things work well together
• A potential bug with the "name" property on an object and some automatic namespacing Doctrine tries to do

There are already a lot of resources available on the Internet. I have looked at various configurations, like for example the 'bisna' project from Guilhere Blanco. But I keep saying that it's really difficult and has a steep learning curve. Doctrine 1.2 was really simple. Doctrine 2.x is a lot more difficult to get into.

I like to classify these mistakes into three broad groups: cock-ups (or screw-ups in American English), errors and oversights. A cock-up is when you stare blankly at the screen and whisper "Oops": things like deleting a database or website, or overwriting three-days worth of work, or accidentally emailing 20,000 people. Errors cover everything, from simple syntax errors like forgetting a } to fatal errors and computational errors.

Included in his list are things like:

• Leaving Debug Mode On
• Turning Debug Mode Off
• Wrong Variable Type
• 1p Errors

Examples of each are included with both code and descriptions as well as "lessons learned" to help you not make the same mistakes in your applications.

In this day and age, everyone uses the internet for finding new jobs or to find a new employee, but more and more I sense that it's all turning into one big mess. This blog post is devoted to all those people contacting me because they have the best job position. [...] I know it's a tough market out there, lot's of competition and so many technologies and skills to keep track off. I know, but it is [you, the recruiter's] business! You decided to dive right into the job chaos, so don't cry if you have to do a bit of work. Do you think we just turn on the computer and it writes code itself ? You do your job, I do mine.

He points out a few specific times a recruiter has sent emails about a "direct hire position" that needs filling immediately or a Java developer (when, clearly, Michelangelo is a PHP developer). He also points out to recruiters that, despite what they may think, they're almost never the only one getting in contact about the same job.

if you're out looking for a new PHP job, go check out the community itself. Most of us have a list of companies with PHP job vacancies or we have a shortlist of trustworthy, understanding recruiters that have touched base with the PHP community and won't let you down once you sign up.

Today I've passed the Zend Framework Certification exam and with that I can finally close my new years resolution for 2010: doing 12 (tech related) exams in 2010. So I've seen a lot of exams, good ones and bad ones and I want to share with you my experience by creating a top-5 of must-have certifications for PHP programmers...

He suggests that certifications are a good way to prove your knowledge to others like customers or colleagues. He talks about the exams and certifications he's taken this year (20 of them) and some of the things he's learned along the way:

• Like unit-testing, mocking is everything.
• Failing is not a shame
• Don't do what I do, unless you know what you are doing.
• The top-5 of certifications that every PHP should have (according to me)