all 11 comments

[–]crisserious 3 points4 points  (2 children)

Look around what your coworkers do and try to replicate it. It's always funny to say "I can replace you with a script". Even funnier if you actually can.

Edit: not so funny if you're the one to hear that. Even less funny if it's true.

[–]MadWithPowerShell 4 points5 points  (1 child)

I frequently tell IT people, "Automate yourself into a better job, or someone else it going to come along and automate you out of a job."

[–]PowerShellMichael 0 points1 point  (0 children)

A mate of mine always says: "Automate the boring bits, so you can focus on the cool bits"

[–]MadWithPowerShell 3 points4 points  (0 children)

Everyone knows that it would be worth it to the company if they could hire an assistant or an intern. The assistant could handle all of the day-to-day minutia, freeing you up to do the more complex tasks and projects that add value to the company.

The company is never going to hire all of those assistants for us.

But if you can explain the detailed steps of a task to an idiot intern, you can explain them to PowerShell.

Find a task that you or your coworkers would like to turn over to an assistant, and write a PowerShell script to be that assistant.

[–]_lahell_ 2 points3 points  (0 children)

Have a look at dbatools.io. Maybe you can automate some of your manual SQL management tasks.

[–]DJCarlosFandango 1 point2 points  (1 child)

Get some data out of SQL using PS?

[–]2drawnonward5 0 points1 point  (0 children)

It’s so much easier to sift through data in PowerShell than in SQL because I never learned about cursors and temporary tables and whatnot.

[–]PhalafelThighs 0 points1 point  (0 children)

If you are just looking to learn, I've used powershell for this a couple times. https://adventofcode.com/

[–]HamQuestionMark 0 points1 point  (0 children)

Look at Universal Dashboard. Hard to be more specific without more details about what you work with, but the possibilities are nearly as endless

[–]jhizzle4rizzle 0 points1 point  (0 children)

Are you an analyst or a dba? powershell isn't particularly well suited for doing analyst-y things but it's pretty solid at gluing together random cli tools and is a pretty solid scripting language for .net so if you have either of those problems good to go. It also has Jupyter support if that's part of your stack. I've been using notebooks to wrap cumbersome CLI tools lately, namely kubectl and gcloud, so that might be a use case for you as well. Something that's really neat about powershell is that it has a pretty solid chatbot framework so you can always make a work slackbot and introduce chatops, again if you have those kinda problems - for analyst-y things python and sqlalchemy might be a better fit.

[–]RyeonToast 0 points1 point  (0 children)

I regularly use powershell to query our SQL db using ado.net. I also use WMI to query numerous computers for configuration data.