Definition of myVMNic as fixed variable prevents launching more than one instance

There seem to be a number of templates, which define myVMNic as a fixed variable. A couple of examples are:

101-simple-linux-vm
chef-json-parameters-ubuntu-vm

The trouble is that Azure doesn't permit more than one NIC resource with the same name, therefore it is not possible to launch more than one such instance.

Other similar examples are "myPublicIP", "MyVNET", "subnet-1", "10.0.0.0/24".

Given that it makes them pretty much useless as far as I can tell, I'm not sure there's much value in the simplification. Is there a particular reason for this other than an attempt at simplifying some example templates?

Is there a preferred way of doing it? For example `concat(parameters('vmDnsName'),'-nic')` or some other such means of avoiding requiring the parameters to be defined for it?

Start with the 101-simple-linux-vm and chef-json-parameters-ubuntu-vm templates, then inspect how myVMNic, myPublicIP, MyVNET, subnet-1, and 10.0.0.0/24 are defined. Determine a naming approach that permits multiple instances without requiring unnecessary parameters, and verify that the affected templates can be deployed more than once.

Written by the indexing model from the issue text.