New answers tagged

2

I think it's more intuitive to name areas by function first. For example /areas/feature1 /areas/feature1/models /areas/feature1/data-access /areas/workspace /areas/workspace/data-access There are two main reasons, one it doesn't require the observer to know that the workspace feature is implemented on a filesystem. Two, it tends to remain this way longer, ...


3

PowerShell is a script language. It is designed to rig-up function blocks created using programming languages. The pitfall to application programmers when they start using PowerShell is that they approach it as a 3rd generation programming language. They take their experience from C/Java/Pascal and try to map that to the PowerShell environment. This soon ...


3

Each line of code you write needs to be tested and maintained. If you get intermittent build failures due to defects in the scripts, then the PowerShell scripts are getting difficult to test. If extending the PowerShell script is becoming difficult, then maintainability is becoming an issue. When deciding to go from a "simple" scripting language to something ...


Top 50 recent answers are included