From Where Should I Begin With?

PowerShell Help
1

Hello there,

This is my first post after just joining this discussion, so please forgive me and provide kind assistance if I have posted to the wrong subsection.

I am new here but a real enthusiast and loving this community so far. I have a background in teaching coding and in education and feel I could help with documentation, at least for starters.

As a new member in this forum and wish to share and gain some knowledge. I am looking forward to create my own discussion to resolve my query and gain some knowledge though I have taken part in various discussion which is definitely helped me a lot.

Also in what category should be taken depends on what factors?

Thankyou in advance.

2

If you’re asking for help with Powershell then the category would be “Powershell Help”

3

Welcome!

We’re glad to have you and are excited for the insight you can bring!

General PowerShell inquiries should be under the category PowerShell Help. I’d say most things if you are not sure, that’s probably the place for it. There are a few additional categories for specific PS technologies, such as Pester, Plaster, and DSC. While ‘uncategorized’ exists, I find it’s mostly not needed.

Open discussions is rarely used but sometimes its a good place to share training resources or talk about ‘best practices’ and are generally not for questions that are 'I have X problem how to solve? type questions.

One thing I do usually let people know is that we are here to help other people with PowerShell but we aren’t here to write full scripts for others. Some definitely may share a good code snippet, but it should not be expected. If a topic/thread comes off as an individual attempting to have others write code for them, there’s a good chance a moderator will reach out to them in some way to let them know that’s not what the forums are for.

When you do post your inquiry, some guidance:

  1. Provide a specific question to be answered.
  2. Don’t just share code or a situation without providing details. Often it’s helpful to ‘take a step back’ from the current problem you are having, as sometimes, we all find ourselves ‘too deep’, and taking that step back can really help provide some context.
  3. Provide any necessary background information, including requirements, business need, situation, etc. and if necessary, who the code is for and how it’s triggered (scheduled task, double clicking etc.).
  4. Format all code as code.
  5. The expected behavior/output.
  6. The actual behavior/output.
  7. Do your best not to make assumptions about what potential respondents may or may not know.
  8. If you run into an error with your current shared code, share the error message.

hopefully this helps!

4

Thankyou mate for sparing a time first of all. It would definitely helped me out a lot. Looking forward for more such discussions and contribute to the community.