Home
Join

8 Replies

  • A few additional suggestions!

    • Use the code tag! It's awesome. Serif fonts for code are not awesome
    • If you use the code tag, mark the correct language! I saw people marking VBScript as apache configs :\
    • Let us know what platform you're on. Windows? Linux? OS X? This is important info to have!
    • Help me help you! Help me help you! Try to give as much info as possible, otherwise we can't do much.
    • If you have a script > 50 lines, use a paste site like pastebin.com or gist.github.com and give us the link.

    Thanks for compiling this list! This is my favorite forum, but I've seen some posts lately that have strayed from these previously unwritten guidelines...

    I'm glad to see this in writing!

     

    By the way, this is the code button. Use it for pasting code into your posts!

    It's the coolest button in the whole community:

    attach_file Attachment Screen_Shot_2013-....53_AM.png 13.6 KB
    Spice (3) flagReport
    Was this post helpful? thumb_up thumb_down
  •  

    Martin9700 wrote:

    • Don’t apologize for being a “noob” or “newbie” or “n00b.” There’s just no need – nobody will think you’re stupid, and the forums are all about asking questions. Just ask. Mentioning that you're new to scripting can be helpful though.

    What's the difference in saying "I'm a noob" and "I'm new to scripting?" Maybe noob got a negative connotation because gamer's use it to make fun of people? I personally don't think people are stupid when they call themselves noobs.

    Was this post helpful? thumb_up thumb_down
  • Agreed, and the n00b is just an example.  What we're trying to say is don't apologize for it!  We get it, we all started somewhere and we're here to help.  

    Was this post helpful? thumb_up thumb_down
  • May I also suggest for near the top of the etiquette list:

    If you solve the issue yourself please explain how, no matter how obvious the solution looked in hindsight.

    There are few things more frustrating than spending hours troubleshooting and searching about an issue to finally find the one post from someone who seems to have the exact same issue, read down all of the troubleshooting points you have already pursued and then get to the OPs comment "Nevermind, fixed it myself".

     

    Spice (10) flagReport
    Was this post helpful? thumb_up thumb_down
  •  

    Martin9700 wrote:

    Agreed, and the n00b is just an example.  What we're trying to say is don't apologize for it!  We get it, we all started somewhere and we're here to help.  

    Ahhh, I got ya. I think I didn't completely understand the point on that one. I'm with you now though, and I agree.

    Was this post helpful? thumb_up thumb_down
  • A big thanks to Martin, for his help. He has been a great help :0)

    Was this post helpful? thumb_up thumb_down
  • Bodestone wrote:

    May I also suggest for near the top of the etiquette list:

    If you solve the issue yourself please explain how, no matter how obvious the solution looked in hindsight.

    There are few things more frustrating than spending hours troubleshooting and searching about an issue to finally find the one post from someone who seems to have the exact same issue, read down all of the troubleshooting points you have already pursued and then get to the OPs comment "Nevermind, fixed it myself".

    Yep that's a n00b move :)

     

    Was this post helpful? thumb_up thumb_down
  • Thanks for this list Martin, and thanks for re-titling it.


    Was this post helpful? thumb_up thumb_down

Read these next...