Call for webinars

Just wrapped up a call working on our webinar schedule for the year.  We’ve got a bunch of ideas but we’d like to also get your input as well.  Yes, I know y’all want ZF2 webinars.  We have that down.  I would also like to do an HTML5 and mobile webinar but I need an SME (Subject Matter Expert) for that.  If you know anyone I’d love to hear about it.

I would also love to have webinars on how to use various API’s, even if there is not native PHP support.  So, what kinds of webinars do you want?  Put your suggestions in the comments and let’s see if we can get some good ideas going.

Also, if you have a great topic, or know someone who would give a good one, let me know about that too!

14 Thoughts on “Call for webinars

  1. sprunka on January 17, 2012 at 12:32 pm said:

    I’m trying to answer a question for my bosses. The most common answer is wrong. (I mentioned this on Twitter to @Zend .) The question is “Why PHP? Why not ___?” the most common answer one hears from PHP developers is “Because it’s what I know.” (with the usually unspoken meaning “It would cost too much to learn ___ or hire someone who already knows ____.”) This answer is wrong. I am trying to research what the right answers are. If I find out before you guys can host a webinar on it, I’ll gladly volunteer. But right now, I don’t have the right answer.

    • rahul_pache on January 17, 2012 at 1:22 pm said:

      @sprunka@zend Plz let me know about it when you do. I also want to shut their mouth with an answer.

    • kschroeder on January 17, 2012 at 2:40 pm said:

      @sprunka My first response is that PHP is the first popular language that was built FOR the web. Java is a great language (IMHO) (among other languages) but it was not built for the web. Newer languages may be built for the web but they don’t have near the number of applications or programmers nor will they have been through as many trials as PHP. Few environments are as easy to manage as a PHP-based one. Few languages have a barrier to entry that is so low while also having a level of ability that is so high.

      • sprunka on January 17, 2012 at 2:54 pm said:

        @kschroeder I think the real question my bosses want answered is “Which projects are best done in PHP, and which are best done in Java/Python/Ruby/C++/Whatever else?” It’s more “Why choose PHP for *this* task, are you sure we’re using the best choice?”

        • kschroeder on January 17, 2012 at 2:59 pm said:

          @sprunka I would start by asking if the project is HTTP-based. Because PHP was specifically built for the web, has a strong developer base and tons of existing apps it should automatically be in the top three at that point. At that point, I believe you need to dig deeper into the different options and it becomes a pros and cons discussion… which there isn’t room for in this text box. Sorry to pass the buck :-)

        • sprunka on January 17, 2012 at 3:02 pm said:

          @kschroeder We (I? Zend? PHP Community?) should come up with a good “checklist” of these pros and cons… To make the question simpler to answer… 😉

        • kschroeder on January 17, 2012 at 3:04 pm said:

          @sprunka A good idea, but I’ve been in a number of those discussions before and a checklist approach will probably not buy you much.

        • sprunka on January 17, 2012 at 3:17 pm said:

          @kschroeder Probably true… but it would make the boss stop asking. So it might be worth it. My raise may ride on giving it to him before Sept.

  2. How about some webinars based on Geo-location and the various options and ways of integrating geo located data into applications?

  3. Pingback:

  4. ivaniordanov on January 20, 2012 at 2:31 am said:

    How about S.O.L.I.D. principles, flexible code, Ioc with various examples. In case you don’t have enough information/examples I can talk on this topic(s).

    • rahul_pache on January 21, 2012 at 10:43 am said:

      @ivaniordanov Please explain what is S.O.L.I.D. principal.

      • ivaniordanov on January 26, 2012 at 3:45 am said:

        @rahul_pache@ivaniordanov S.O.L.I.D is acronym of acronyms. It stands for SRP, OCP, LSP, ISP, DIP.SRP stands for Single responsibility principleOCP stands for Open/closed principleLSP stands for Liskov substitution principleISP stands for Interface segregation principle

        DIP stands for Dependency inversion principleBasically the goal of this principles is to write flexible code, that can be easily extended (usually with a single change), and easy to support/implement new features.

Leave a Reply

Your email address will not be published. Required fields are marked *

Post Navigation

Web Analytics