James Ruskin

@ja.mesrusk.in

A PowerShell enthusiast with too many hobbies that he doesn't really manage to do any more.

Duskers is getting a sequel! 10 years later 😅 The Steam post has more info, including the new teaser trailer - featuring the voice of Deonte (our producer). You can even wishlist it on Steam if you're into that sorta thing 😉 steamcommunity.com/games/254320...

Steam :: Duskers :: Duskers Is Getting A Sequel!

Incredibly excited to say that, after 10 years, we're finally returning to the desolation of space to revisit the universe of Duskers! For starters check out it's shiny new Steam Page (wishlist it!), ...

steamcommunity.com

One thing I really appreciate learning #PowerShell is how it demystified so much for me. Actually being able to poke and query things gave me the closure my brain needed to really understand the tech I was using What accelerated that learning? Asking questions 1/2

Hey #PowerShell peeps! The new auto complete thing in VSCode is messing up our terminals. It doesn't auto complete actual functions. Give this an upvote to get a fix in to the backlog and (hopefully) improve it! github.com/microsoft/vs... (And share onwards for visibly. Can't have a bad terminal)

Terminal suggest doesn't get content from the actual terminal session. · Issue #285640 · microsoft/vscode

Does this issue occur when all extensions are disabled?: Yes/No Yes Terminal auto suggest entries are not based on actual terminal functions, and suggestions are therefore not correct. If I create ...

github.com

So, managed [71-and-a-bit books](blog.justpowerdown.com/what-i-read-...) this year (with a fair few re-reads) - I'm pretty happy with that! Binged Dresden, Dungeon Crawler Carl, and Sandman Slim (amongst other series), and found some new authors and books that I'm itching to explore! Here's to 2026!

What I read in 2025

I saw someone talking about what they'd read so far in 2025, and though I've re-read a lot of my comfort series this year (as I seem to keep doing) it was interesting to revisit what I had read throug...

blog.justpowerdown.com

A plea to junior and senior developers alike - when someone does a build from main, please ensure that git doesn't report 46 changed files. Generally speaking, any files created or updated during a build should be considered "artifacts" and artifacts should be .gitignored.

Screenshot of VSCode showing 46 changes in a repo. Except I didn't make any changes. All I did was a build. Cloning main and performing a build should never result in 46 changes to the repo. If it does, it means you are either not using .gitignore properly and/or your build artifacts aren't targetting a proper "output" directory.

When you perform a build, any files created or modified during that build should be considered "artifacts" and those artifacts should never be committed to the repo IMO. There are always exceptions such as when a build also generates or updates documentation that you commit and maintain as a part of the repo rather than an artifact. There are mixed opinions on that practice.

I had the absolute joy and indescribable terror of emailing 1200 of my closest coworkers to announce we would be making the GitHub repo for our PowerShell module public tomorrow. I set my alarm for 11pm to flip the switch at 8am CET. It is done! Link to GitHub in the docs: www.milestonepstools.com

Screenshot from the MilestonePSTools home page with the text:

Manage XProtect at ANY scale
Configure. Automate. Report. You decide what is possible on the Open Platform.
Compatible with all supported versions of XProtect.

Automate user onboarding like a pro → Write a PowerShell script that: creates users, assigns groups, sets passwords → Add automatic email notifications → Log every action to a CSV This is the kind of thing managers notice. You’re not just repeating steps you’re building trust in your reliability.