In case you haven't heard, the 2014 Winter Scripting Games are just now getting started. Regardless of your skill level with PowerShell, it couldn't be a better time to participate since this is the first time in the history of the scripting games that you'll be able to work as part of a team and receive proactive feedback (before your code is judged) from a team of expert coaches who use PowerShell in the real world on a daily basis. Ultimately, the scripting games make learning PowerShell more interesting and challenging while giving you the opportunity to network with other enthusiasts in the industry.
Now it's time to talk about a PowerShell tip that I wanted to share.
Tip #1 - Read the Help!
While this may not be the most popular tip, believe it or not, it's one of the most important and it's something that's so simple it's often times overlooked. In my opinion, you'll never truly be effective with PowerShell and be able to figure things out for yourself until you learn to read the help.
Click here to be redirected to the original post of this article on the author’s blog site where you can read the remainder of the article.
µ
[…] In my tip #1 blog you learned that you need to “Read the Help!”. This tip builds on the first one because it allows others to “Read the Help!” for the PowerShell code that you write. […]
[…] my tip #1 blog you learned that you need to “Read the Help!”. This tip builds on the first one […]
[…] Why was this command written this way? Where did it come from? I copied it off of someones else’s blog who apparently didn’t bother to “Read the Help”. The original command also used cryptic aliases so it’s not an exact copy. Tip #1 was “Read the Help”. […]