Sometimes people really don't know why they want to learn Perl. This may not be the case with your group, but I've found that in any teaching, making the subject relate to the student is always a good first step. This guy is an operator right? I'd suggest trying to figure out what sort of work he's been doing, and show him how perl can make his life easier. Lay out examples of what you want to teach that are relevant to what he's been doing for the last 20 yrs. of his life and it will be much easier for him to grasp the fundamentals. Want to teach him about data conversion? Figure out an instance where he's done manual data conversion in the past and then show him how to do it in perl. That'll gaurantee an "ah-ha" moment.

Folks with little or no programming background can learn and use perl, but it's far more difficult if they don't have some way to apply the theory to concrete examples of it's use.
I didn't learn Perl to learn Perl. I learned it to make my life easier. Now I'm using it to make other peoples lives easier too.

~monk d4vis
#!/usr/bin/fnord

ps. If that doesn't work, try beating them harder.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.