PFCongres 2013
13 - 14 Sep 2013 at Cursus- en vergadercentrum Domstad

Thanks for all the feedback folks, it's very useful - glad to see some of you already using Codeception, that's by far the best feedback possible - you were inspired enough to try it!

Good talk, speaker seemed a little inexperienced but did very well. Would have liked to see a little more info about other serialization options and not focus only on his own library, I don't feel like I have enough context to choose based on what was presented.

Very good talk, learned a lot, very well presented. Could perhaps use some better editing about what content to include in the time frame, I felt like there was very powerful features that couldn't be discussed because the speaker ran out of time.

Disorganized as hell and could have used more code samples. However, it was extremely funny and enjoyable, was a nice change of pace from other talks. The content could definitely use polish and depth though, perhaps the speaker needs more practice runs?

For a spur of the moment talk, this was very well done. Lots of audience interaction and some great info. If this were on the main stage, I'd like a little bit deeper content, perhaps about higher level documentation like architecture and use cases.

A nice introduction to ZF2 and some very usefull tips, but you could have been more ambitious. I mean, i like your aproach for a small application one is working on alone, but what if you have a large application constantly being developed by a team of developers? It seems to me your aproach would require to stop regular development until porting is finished, or are you going to keep up with processing the changes from regular development while porting?

A more ambitious and less risky alternative could be to extend the existing application step by step to work on ZF2 while it remains fully functional on ZF1. This is done by one or two developers while maintenance by the regular team continues on the same code base. Porting will require a lot of choices between making adaptations on the application level, wrapping ZF2 components with a ZF1 compatible adapters or the other way around, whatever is the least work given the existing code and target design (Yes, you need to make a plan first).

When erverything works on both platforms you can go into production on ZF2. Once producton is stable on ZF2 you can remove ZF1-targeting code and confugurations that er no longer required. Finally port the rest of the application code to work without adapters on ZF2.

I did something like this with my applications when porting from PHP4 to PHP5: the 1.x versions of the phpPeanuts.org framework worked on both platforms for several years while the applications where ported one by one to run on PHP5. Then in a much shorter period each of them was ported to the PHP5-only 2.0 version of the framework.

I admit this would be a lot more work with ZF because of the bigger API and structural changes, requiring more wrapping etc., but i bet it can be done. It may cost more for the IT department (but probably less then trying to keep up with changes from regular development), but will be much less disruptive to the business then stopping regular development, so the orinization as a whole may be better off, including finacially. Furthermore, the team that does regular development gets time to learn ZF2 step by step instead of having to make a big leap of knowledge (and faith). Finally, if the porting project takes a bigger effort then estimated, you can take more time without the project failing completely (which would leave the application stuck on ZF1). And i bet it could result in another very interesting talk ;-)

I'm with Erika: This was my talk of the day as well. Hadn't seen / heard it on ProTalk.me yet (I know it's listed there). Luckily.
Excellent and energetic talk, well-balanced between humor and serious information.

Interesting talk, especially liked how you stated the actual issue and requirements of the solution. I'm not fully convinced this is THE tool I'd pick to solve such a problem, but it definitely is an option.

Good talk, good pace. The tool itself was completely new from me, but because it was well explained I was able to follow all steps. This tools seems quite useful as it integrates testing various domains. Will definitely look into this!

For me it felt like the slides were not adjusted to the audience. Would've loved to have a little more insights in the SVG format and perhaps some practical cases. The same holds for canvas by the way.