in reply to Newbie madness, experienced ambiguity.
I too have been around about a month.
I agree that when you do post a ambigous node, all you receive is look at this node or this was brought up previosly here or merlyn's typical i did an article on this for (substitute any one of the magazines merlyn writes for here.)
Perlmonks is an online community, they are here to HELP us newbies to write/learn perl.
If you have ever been a member of the old usenets threads, you get rtfm if you are lucky (comments about your heritage/lifestyle/family if you aren't) if you ask that sort of a question there.
At least here, you get the chapter and verse so you know where to start.
As a newbie, we are faced with a lot of challenges, learning syntax versus semantics.
Perlmonks reminds me of a teacher (Thanks prof harley)i had for a class in o/s principles.
The first day of class the teacher stated that her goal was for us to walk out of her class knowing one thing in regard to unix.
That one thing was to learn how to use the documentation that already existed to solve our problems.
Computer Science/programming/system administration is all about one thing- being so lazy that you figure out how to use tools that you have to solve problems.
I am a jr. sysadmin professionally, i am learning perl because I am so lazy that i hate having to go in each day and logg into all of the boxes i am responsible for and searching for anomolies.
I heard that perl was a great sysadmin tool if i could harness its power.
So i went out and bought the llama.
Great book, taught me the basics.
Read a column in Linux-mag.
Merlyn mentioned this website in one of his columns.
Checked the site- hey it seemed pretty cool.
Looked in the chatterbox- see people's names, checked their bios really quick- hmmm all the people that were higher levels, noticed what they were saying, at least once a day someone that is at bishop level or above mentions going back in and reading the camel book.
Ahhhhhhhhhhhhh-ha (note to self get and READ camel book- note to self did get, am READING camel)
Learning to write code effectively is a matter of learning to use all of your tools effectively.
Solving your own problems.
Use perlmonks as a tool, not as a crutch.
Use them to glean ideas rather than expecting them to write your code.
Learn to use the super search. I spent a whole day writing a stupid sniplet of code the copy bookmarks code that I posted here and couldn't get it to work from any directories above the one i was in.
A few days later, i used super search and found exactly the IDENTICAL problem with an answer from vroom.
The post was date december 2000.
Why should people answer the same broad question twice- especially if it already exists?
Show the member's here respect, that you value THEIR time.
Do research into the problem, mention yes i looked at this problem, however:
1. My situation is different b/c why what you saw does'nt work due to yadda yadda yadda or
2. (or My personal favorite) I am an idiot and can't figure this out
Programmers like to be challenged, ask any one of the people that write code for a living why they work where they do and one of the top three answers will probably be for the challenge they face there.
If you want their help, challenge them to HELP you do what you want done quicker, better, or more securely.
The people here are here for one reason, to propagate the language of perl, extend it past it's limits, and most importantly, to teach us, how to teach ourselves.