> My biggest issue with powershell is how undiscoverable it is This surprises me as I feel exactly the opposite. I may not know how to manage X via PowerShell

> My biggest issue with powershell is how undiscoverable it is This surprises me as I feel exactly the opposite. I may not know how to manage X via PowerShell, but I know those pre-approved verbs like Get/Set/New/Test/Convert etc. Then I know commands from same module usually start with some abbreviation like Get-Net.... Then I can tab throguth commands. Or just Get-Module (to see loaded/available modules) and then Get-Command -ModuleName x or just help tcp. And if "help Get-NetTCPSetting -Full" won't help, yeah, fallback to google. Example. Now how would I set an IP address for an interface not having an idea? (where you see italicized, actually there are star-wildcard around the word) 1. help ip (ohh, too much results) 2. help set-ip - alright, Set-NetIPAddress 3. help Set-NetIPAddress -Examples (seems I need to specify some interface. It is probably at Get-NetIPInter<TAB> - ahh, gives me Get-NetIPInterface, here you are.) 4. Get-NetIPInterface 5. Set-NetIPInterface -<TAB><TAB><TAB> (autocompletes arguments and I choose which I would like to set or not)