|Think about Loose Coupling|
Druby Dru (Hermit)
|on Jan 08, 2003 at 15:09 UTC||Need Help??|
Perl is the first programming language that I learned. I started out from scratch with no programming experience whatsoever, but I knew Perl would make my job much easier and more efficient if I learned it (how right I was). To anyone who helps me, thank you very much, I would have given up learning Perl if it wasn't for this site (I actually did a few times before finding this site). I hope some day I'm at the point where I can help the newer monks with their questions, but I feel I can't hold a candle to many of the real programmers on this site. Because of Perl, I decided to major in Computer Science.
I do not code in Perl full time, I'm not even a programmer by profession. I may go 2 weeks without doing anything in Perl, but this is rare and I'm usually doing something everyday with Perl. I'm a Senior Network Security Analyst and I work with firewalls, routers, switches, IDS's, vulnerability scanning products, which all produce lots and lots of log files that get devoured, sliced, then diced by Perl.
Perl and Security are my two favorite subjects with Linux and OpenSource software being a close second.
Tips on Posting:
I've been at the monastary since 2000 and written many bad posts. As a result, here are some of the things I learned on how to post and get the most out of your question (for both you and future readers).
1. First, please try to use Super Search to find the answer to your question. It's very unlikely your question is unique that has not been answered in the past. If you still can't find what you need via Super Search, then The Monks appreciated it if you include something along the lines of: "I've tried the following terms in Super Search, without any luck" in your post.
2. Start with a greeting. I like "Hi Monks" "Hey there Monks" "How's it hanging today Monks" "What's Sappening Monks".
3. Always use strict and warnings with your code. This will catch the majority of your mistakes.
4. Always post code no matter how far out in left field you might think you are. The monks seem to appreciate that you at least gave an effort.
5. Explain what the problem is and include any error messages.
6. If it is homework, just say so and the monks will respect your more, but don't ever post homework without code.
7. End with a simple gesture. I like "Thanks"
8. When I am done writing my post, I then like to assign it a title. Use something so that when someone is having a similar problem, they will know what it is when they perform a search. Make the title specific rather then broad. Good - "How to Create An Anonymous Hash using Split" Bad - "Hash Question"
9. Use a spellchecker. I like spellcheck.net or Firefox's built in spellchecker
10. Preview your post a minimum of 3 times.
11. Use a "readmore" tag in your post after the first paragraph (or first few sentences) in case it gets front paged, it won't take up the whole page.
12. If there is anything within your "code" tags that extend to the next line (appears with a "+" sign at the beginning), reformat it so it does not have this plus sign. Basically format anything within your "code" tags so it's easy to read and the monks do not have to copy and paste it to an external program to read it properly. The less time someone has to work on formatting your post so they can read it (which usually means none), the more likely you are to get an answer.
Some things I do when not coding in Perl:
1. Woodworking - great way to utilize the other side of your brain.
2. Reading Slashdot, Perlsphere, and Security Bloggers Network
3. Turf Grass Management.
4. Restoring our 1936 home.
5. Dealing with NADD
6. Martial arts - I currently train in Kajukenbo.
1. What shortcuts can I use for linking to other information?
2. Chatterbox FAQ
3. How (Not) To Ask A Question
4. Perl Docs
5. Debugging Perl, Debugging Perl2, Debugging Perl3
6. Perl One Liners
7. File test operators
8. Merlyn's LM articles
9. Perlvar - predefined perl variables
10. Stats Page
11. Regular Expression Resources
Nodes that I want to read when I have a chance:
2. Where and how to start learning Perl
4. Money vs. Perl
6. Perl and Net::Pcap
8. Recommended Reading
My Favorite Nodes:
1. 1st Monasterians
Monks for hire