Richard Siddaway's Blog

A recent post on powershell.org – https://powershell.org/2017/06/22/taking-powershell-to-the-next-level/ – gave this path for learning PowerShell and becoming more proficient

Books:
Learn Powershell In A Month of Lunches
Learn Powershell Toolmaking in a month of Lunches
Windows Powershell In Action 3rd Edition

Online:
Advanced Tools And Scripting with Powershell 3.0 Jump Start
Writing Powershell Powershell DSC Resources And Configuration
Demo Code

To that list I’d add

Books:  PowerShell in Depth 2nd edition – read it before PowerShell in Action

In parallel with the books and online courses find an area that you can work in – Active directory, Exchange, Windows admin, Hyper-V, SharePoint, SQL Server or whatever and start solving practical problems. You’ll learn more fro doing that than all the books you’ll ever read

The first in a regular(ish) series of articles has been published on the TechNet UK Blog.

http://blogs.technet.com/b/uktechnet/archive/2015/11/20/why-you-need-to-learn-powershell.aspx

Covering all things PowerShell related the articles will be appearing every 3-4 weeks.

I’ve been thinking about how people learn PowerShell through watching some people at work who are learning it and watching the questions on the forums – many of which start off “I’m new to PowerShell and…”

There seems to be two broad approaches:

Option 1 is to get some training. This could be a formal course, video training or the excellent Learn PowerShell in a Month of Lunches book. Then find problems to solve.

Option 2 takes the opposite approach and finds the problems to solve then starts figuring out how to use PowerShell to solve them.

Which route you take depends on a number of things:

how you like to learn

the environment you work in – can you actually find time to start using PowerShell, and approval,

the technologies you work with

The options above both assume that scripting is your end goal. I’d suggest one other approach that may help. Use the cmdlets you have directly from the command line.  You can accomplish a lot by piping a few cmdlets together. This gets you used to working with cmdlets and the PowerShell language.

Keep it Simple and start small. You’ll soon start progressing.