It's not. Simple reality is your going to end up in help desk (you might end up in a SNOC or related but ultimately I'd advise help desk just so you learn some real world ops). Security, like it's engineering counterparts is not something you can do with zero experience in the industry. The two hardest job interviews you will ever have in the general it industry are getting into help desk, and getting out of help desk.

How can you not link the rpgnet review of such a...system. https://www.rpg.net/reviews/archive/14/14567.phtml

I'm in a similar boat. Flew across the country because after "missing" 2017s I immediately felt regret. Now I'm debating Europe in 2026.

But the colors. Can someone who understands this stuff please explain to me why a simple reduction in light in the lead up to (and following) totality makes all the colors seem "wrong"?

Along a similar vain to making a git friend, buy your sysadmins/ops people a box of doughnuts once in a while. They (generally) all code and will have some knowledge of what you are working on.

It's not uncommon for the password manager to not be on the same system as where the password is being entered - hence a human needs to type. For example: consumer electronics with their own dinky little screens. Smart TVs/game systems and servers where remote access is not possible (or copy/paste does not work by design).

Not the person you asked, but another forever dm who likes it.

I fell into it because I wanted to play and the best way to control scheduling was to run the game.

If you like to write stories that's wonderful - take a look at some of the pre generated adventures in any system to understand how the different components work in pen and paper games. Just remember that no plot can survive contact with the players unscathed (after all it's group story telling)- and some level of improve skill will help the overall experience. After that just have fun.

Hey now! Gitlab ci is totally fine so long as your simply running your build.sh file out of it. Anything more and your risking madness.

Just use npm to install all the dependencies. What's the worst that can happen.

Just to pile on. I've seen devs throw out the entire git history when moving between repos for ongoing projects.

I'm sorry but you don't want to use permanent IP bans. Most residential circuits are DHCP meaning banning via IP only has a short term positive effect.

That said automatic scanning of known hashes, and automatically reporting to relevant authorities with relevant details should be doable (provided there is a database somewhere - I honestly have never looked).

Interesting footnote about p and q. You see them turn up on formal logic proofs (for philosophy)

Fyi. If your IT department is remotely on top of things - they know. They just might have larger fish to fry.

We can see all kinds of things about any devices that log on to check email, connect to the VPN, etc.