Re: mod_perl training (was Re: Certification)
On Sun, Dec 10, 2000 at 06:13:13PM +0800, Gunther Birznieks wrote: It sounds to me like you have hit the nail on the head. Perhaps what is needed in terms of recouping costs for a mod_perl hands-on development course and/or online course is the open source/collaborative approach. This seems to be a good solution to this problem. Instead of one person sucking up the costs of developing these courses, we could get a group together to do this. Sounds good to me. I would be willing to donate my time to write and initially test the exercises to the slides that are taught for the days. If a couple people were to donate their time to writing the slides based on an outline produced by Stas and Randal. So would I. I'm more than willing to proof read, test, and be a guinea pig. We could host it on sourceforge as the modperltraining project. Sourceforge could also host the mailing list. Then regardless of if Randal would then be willing to take the course material and beta test it as a class he offers (eg maybe giving the course itself would not be profitable for him), we ourselves could be giving this course all over the world in beta-test Perl Monger groups. Yet another good idea. We all love open-source, and collaborative efforts, so let's create a good set of training materials, and then let people teach this material in their own neighborhoods. I know there are still issues such as getting people of the same level of expertise in the same room and mod_perl not being a "core" technology, but I think mod_perl can be taught assuming similar requirements as the PROM class you offer as an initial thought? mod_perl doesn't require all of PROM, but probably about a day of it would be integrated to bring people up to speed on the basics? You lost me here. I'm not sure what "core" technology means. I always thought it would be relatively easy for an experienced teacher to develop a coherent, reliable course for mod_perl, as long as some requirements are met (able to program perl and able to configure and administer an apache server). Once those guidelines are met, discussing the Apache API, going into detail on each of the response phases, and going through examples and exercises, would flow somewhat unfettered. 1. the Apache server life cycle 2. the request loop 3. Discussion of the API for each phase of the loop with examples 4. Exercises This would take about 3 (maybe 4) days with someone who meets the pre-reqs. 1 for the intro and terminology 1 long day to discuss the APIs for each phase (maybe two), and 1 day to go over exercises and have some "lab" work. This is just a rough estimate, and if someone thinks I've lost my coconuts let me know. Getting someone up to speed on mod_perl (not Apache::* modules, but the perl API to Apache), shouldn't take too long. I'd say about 1-1.5 hours for each stop in the request loop. 4-5 hours to teach someone the guts of Apache, including terminology and the real base knowledge stuff, and 8-10 hours to go over exercises, and develop skeleton handlers. We are looking at about 30 hours of hard, hard work. They don't call some training sessions "boot camps" for nothing. Again, feedback is good. Just make it constructive. Calling me a "moronic putz" isn't helpful, but saying "Hey, Moronic Putz, you underestimate " is good. helping with this project, please email me privately. If I get enough people willing to contribute (at least 5), I'll set up the sourceforge project to start the ball rolling Oh yeah, did I say I didn't mind donating my admin time as well to this experiment. :) Count me in. I'll be willing to guinea pig stuff and give feedback, as well as do research and help out more experienced teachers. Later, Gunther JJ -- J. J. Horner [EMAIL PROTECTED] Apache, Perl, mod_perl, Web security, Linux
Re: mod_perl training (was Re: Certification)
At 10:45 AM 12/8/2000 -0500, Richard Dice wrote: "Randal L. Schwartz" wrote: But here's the reality of trainings. You need to get 10 to 20 people in a room at the same time that are all starting roughly at the same skill level and also want to end up in the same place. And then you need to do that about 8 to 20 times with the same slide set before you break even, because the cost of producing the materials is pretty high: figure one to three DAYS of research for every HOUR of face time in the classroom. I've been lucky enough to "inherit" (as a subcontractor) sets of Perl training materials put together by a really decent guy named James. I shudder to think of the time investment he made in creating that stuff. He and I have talked from time to time about revising/updating the existing materials, and maybe even creating some new courses, but how to find the time... Mod_perl is a topic I'd really like to work on -- both in terms of teaching and also in putting together the training materials to begin with. I've yet to figure out the "magic formula" to make this work, though. I can't figure out where the "start" and "finish" are with mod_perl that would make sense for 80 to 400 people. It's not core techology, like the llama. We target the llama as how you would want ANY perl hacker to spend their first 30 hours. But what 20-30 hours are *common* for any mod_perl hacker? And what do you do for pre-reqs? These are all really good points. One other slightly-more-minor consideration when it comes to teaching a Perl course is system set-up. If you control the training environment, (ie. you have your own classroom and students come out to it) then this isn't a problem. But if you teach at the client's location, then it can be an issue trying to get their machines configured to the point where you can actually have workshops on what you teach. Mod_perl is a biggie in terms of the kind of setup you have to do: you need a lot of Perl modules installed on the machine, a recent version of Perl, source-code level acceses to building Apache, and not just the time needed to do this to a classroom full of computers, but also _permission_. That all said, I'm sure there will be mod_perl courses available somehow, someday. 5000(0(0?)?) mod_perl hackers can't be wrong. :-) Cheers, Richard At first I read Randal's message I didn't know what to say. It's absolutely true, but it's also very demoralizing to me (to say that it's not profitable to teach mod_perl in the best possible way -- hands on). It sounds to me like you have hit the nail on the head. Perhaps what is needed in terms of recouping costs for a mod_perl hands-on development course and/or online course is the open source/collaborative approach. I would be willing to donate my time to write and initially test the exercises to the slides that are taught for the days. If a couple people were to donate their time to writing the slides based on an outline produced by Stas and Randal. I believe this layered approach would produce some reasonable training material versus someone working on 1 day of training and another person working on another day of training. If we did it that way, the days would not have cohesion. But instead, you get 2 people doing the outline collaboratively. You then get 2 people fleshing out the outline with some comments from the first and then you get 1 person writing the exercises because you want the exercises to build off of each other. The the slides could be slowly improved in a larger open source community after that. I believe Randal's years of Perl training expertise would make him well qualified to at least contribute an outline of what he believes a course in mod_perl should entail and in what general order (kind of like a leader in this aspect if he were willing to take it on). Stas would also be ideal in both contributing a day of training and the outline. Although he hasn't done hands-on training (I presume) and I have never done so (although I've given 1-2 day lectures plenty of times), which is a different matter. Once the rough drafts are produced, it's a matter of having an open source tree where the notes/exercises and slides can be adjusted as time goes on. I would suggest HTML as the format for slides because it would be the easiest to manage as a group project in CVS. We could host it on sourceforge as the modperltraining project. Sourceforge could also host the mailing list. Then regardless of if Randal would then be willing to take the course material and beta test it as a class he offers (eg maybe giving the course itself would not be profitable for him), we ourselves could be giving this course all over the world in beta-test Perl Monger groups. I am pretty sure that if we target 6 months for this project to reach beta, that by then I could give a mod_perl course using an eLinux training room in Singapore for the local Asia crowd. How
Re: mod_perl training (was Re: Certification)
"Randal L. Schwartz" wrote: But here's the reality of trainings. You need to get 10 to 20 people in a room at the same time that are all starting roughly at the same skill level and also want to end up in the same place. And then you need to do that about 8 to 20 times with the same slide set before you break even, because the cost of producing the materials is pretty high: figure one to three DAYS of research for every HOUR of face time in the classroom. I've been lucky enough to "inherit" (as a subcontractor) sets of Perl training materials put together by a really decent guy named James. I shudder to think of the time investment he made in creating that stuff. He and I have talked from time to time about revising/updating the existing materials, and maybe even creating some new courses, but how to find the time... Mod_perl is a topic I'd really like to work on -- both in terms of teaching and also in putting together the training materials to begin with. I've yet to figure out the "magic formula" to make this work, though. I can't figure out where the "start" and "finish" are with mod_perl that would make sense for 80 to 400 people. It's not core techology, like the llama. We target the llama as how you would want ANY perl hacker to spend their first 30 hours. But what 20-30 hours are *common* for any mod_perl hacker? And what do you do for pre-reqs? These are all really good points. One other slightly-more-minor consideration when it comes to teaching a Perl course is system set-up. If you control the training environment, (ie. you have your own classroom and students come out to it) then this isn't a problem. But if you teach at the client's location, then it can be an issue trying to get their machines configured to the point where you can actually have workshops on what you teach. Mod_perl is a biggie in terms of the kind of setup you have to do: you need a lot of Perl modules installed on the machine, a recent version of Perl, source-code level acceses to building Apache, and not just the time needed to do this to a classroom full of computers, but also _permission_. That all said, I'm sure there will be mod_perl courses available somehow, someday. 5000(0(0?)?) mod_perl hackers can't be wrong. :-) Cheers, Richard -- Richard Dice * Personal 519 635 9568 * Fax 519 635 9569 ShadNet Creator * http://shadnet.shad.ca/ * [EMAIL PROTECTED] Occasional Writer, HotWired * http://www.hotwired.com/webmonkey/ "squeeze the world 'til it's small enough to join us heel to toe" - jesus jones - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod_perl training (was Re: Certification)
In a message dated 12/8/00 10:48:13 AM Eastern Standard Time, [EMAIL PROTECTED] writes: I can't figure out where the "start" and "finish" are with mod_perl that would make sense for 80 to 400 people. It's not core techology, like the llama. We target the llama as how you would want ANY perl hacker to spend their first 30 hours. But what 20-30 hours are *common* for any mod_perl hacker? And what do you do for pre-reqs? Make the course for someone who knows whatever intermediate perl, knowing basic C will help the student. Combine it with and advanced perl course. Cover.. 1. Using Perl to Configure Apache 2. .xs programming, and When to use It 3. Callback functions and what that means for signals 4. the mod_perl API 5. briefly, using apxs 5. "Fall back to" secure settings. CERT's safe CGI, Exec/CGI, suexec, tcpd-wrappers, mod_ssl, anyone who runs anything under Apache::Registry has X privs 6. A sample mod_perl module (trans, Acc/Auth/Authz, fixup) 7. BlockRobot Timer et cetera as time allows
