Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I did a small offering to my co-workers on regular expressions. The approach I decided to take:

Emphasize the gentle learning curve of regular expressions. (Whut.) In other words, if you know them a little, you can use them a little. Let the anchors be their anchor: ^ and $, then build from there. The next logical steps are: .+ and .* homegrown character classes built-in character classes (\w and the like)

I moved quickly to using backreferences to replace strings, since we often have to generate scripts from lists that the users send us.

Try to find things they are actually doing and show how regexps can replace "elaborate string manipulation using only built-in string functions." Remind them that less code means fewer bugs. Enlist the help of someone who works on another team and see what they do that can be made easier with regular expressions. (If that team is a large team, so much the better.) If your audience sees that you've taken the trouble to tailor your presentation to their everyday needs, they will respond.

I'd also keep it short. The goal won't be to teach them the ins and outs of regexps, just to let them see how they can be of value


In reply to re: regexp class by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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 or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others contemplating the Monastery: (3)
As of 2022-08-14 06:19 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found

    Notices?