Naming convention can be tricky. Although a fixed naming convention may provide aesthetics or simplified use, this is not required. In general, the naming convention I advocate for is the one already in use in Powershell. Since functions are created on the basis of a noun verb, each word begins with a capital letter or, if it is an abbreviation, all capital, or if it is property, then, as well, respectively.
For example, I created some functions for myself:
Get-ServerDiag Mount-TrueCryptVolumes Start-RDP Generate-RandomPassword Nuke-Environment
You can imagine what these functions do, it's pretty clear, straightforward, and compatible with Powershell's built-in functions. However, I have exceptions to the โimportโ of several Unix commands into Powershell (for example, killall , pidof , etc.). You can always use Set-Alias if you want to write something else.
This issue, no matter how important it may be, can be discussed, since there seems to be no โone, better wayโ. All this, in the end, depends on personal preferences.
Koliat
source share