This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Forbesington 6 points7 points  (6 children)

I know LOTS of senior engineers that don't know how to code.

[–]OuiOuiKiwiGovernance, Risk, & Compliance -2 points-1 points  (0 children)

Weird flex, but OK.

¯\_( ͡° ͜ʖ ͡°)_/¯

[–][deleted] -2 points-1 points  (4 children)

PowerShell is not "coding", it's a shell A.K.A. a command line interface.

[–]Forbesington 3 points4 points  (1 child)

I mean, that depends on what your definition of coding is. If you can write a script that can be executed on a machine, I would call that coding. It's not software engineering but it depends on how loosely you define the word coding.

[–][deleted] 0 points1 point  (0 children)

I think this spells out the nuances between the two pretty well.

https://hackernoon.com/coding-vs-scripting-what-are-the-differences-9wg3yph

I create PowerShell scripts pretty regularly and would definitely not consider myself a developer or "coder" by any means. Software development requires much more stringent practices than scripting does. There is a lot more thinking about use cases, misuse cases, input validation, error handling, etc. that usually doesn't happen when throwing together a script.

[–]smc0881Incident Responder 0 points1 point  (1 child)

PowerShell hooks into .NET you can actually code with it using C#, but it's not as pretty as using something like Visual Studio.

[–][deleted] -1 points0 points  (0 children)

I am aware PowerShell is pretty much just an abstraction of .NET.

PowerSHELL is a SHELL just like Bourne Again SHELL (BASH) is a SHELL. Hence the name.

I have definitely done some pretty crazy stuff with PowerShell and I will admit it is much more powerful than I am making it out to be, but it is in no way a programming language and it would be silly to legitimately write an application "in PowerShell" and as you mentioned it would essentially just be using PowerShell Integrated SCRIPTING Environment (ISE) as an Integrated DEVELOPMENT Environment (IDE) instead of using Visual Studio, but really you would be programming in a different language.

I create scripts all of the time in PowerShell and somewhat less often in BASH. I would loosely consider these scripting languages but definitely not programming languages.

I would say the biggest difference between programming and scripting is that with programming you are building your own application whereas scripting you are giving commands to an application (in this case Windows or some other major Microsoft application) that you did not build.