I've started a new job working for a firm that uses a full windows stack. I feel like I've gone backwards in terms of productivity, not because Windows is less powerful, but because I'm just really unfamiliar with the environment. I find myself constantly banging my head against Powershell, throwing up my hands, and banging out whatever it was I was trying to do in Cygwin. I feel like this is a dirty solution, and would prefer to get comfortable in the proper Windows environment.
With that said, how should a beginner like myself be searching through get-command's output for general cmdlets I'd like to perform? I understand I should be thinking in an object space, so is there an elegant way to search through the properties presented so I can do things like, say, find out if there is an alias for a particular cmdlet, or to search if a cmdlet is even available? (was looking for a symlink cmdlet, and would prefer to stay in the cmdline over googling if possible).
The lack of grep/piping is driving me crazy. I must be missing something, any advice given my predicament?
diroutput to only list.exefiles over 1MB") will produce a specific answer that ALSO teaches PowerShell syntax. – Jay Bazuzi Nov 4 '12 at 22:57