3 ms·

I go back and forth between windows/unix for my day job and I also would be curious on any actual bullet points. I find that even in a situation where PS could

I go back and forth between windows/unix for my day job and I also would be curious on any actual bullet points. I find that even in a situation where PS could potentially prove more useful or has an extra feature, what you end up with is a new set of chrome tabs open just to try and figure out how to do the thing. I suppose this might(?) be mitigated if you're embedded in the .NET world, but I just can't seem to get the memory down for the silly cmdlet naming and since they also have the admittedly interesting object-piping thing going on, you're always battling two pain points at a time instead of just one (e.g. syntax/naming in bash)

WorldMaker 10y ago
One of the best bits of PS1 advice I've seen was to get used to the Verb-Noun naming pattern [1] and in particular, the discoverability of the very standardized set of verbs [2]. Once you can guess the verb you want, then it can often be a simple matter of finding the right noun, and often nouns will be useful in sets similar to verbs. Get-Verb, Get-Command, and Get-Help are all quite useful for looking for a command. For dealing with the object pipeline I tend to find ConvertTo-Json very handy because as a developer I'm already quite used to reading objects in JSON already. (ConvertFrom-Json can similarly be used to bootstrap a PS1 pipeline with test data or remote data.) [1] https://blogs.technet.microsoft.com/heyscriptingguy/2012/05/14/discover-the-easy-way-to-begin-learning-windows-powershell/ https://blogs.technet.microsoft.com/heyscriptingguy/2012/05/... [2] https://msdn.microsoft.com/en-us/library/ms714428(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/ms714428(v=vs.85).a...