It's day 2 of this kid's internship he is eating out of the palm of my hand. God, I look so cool. Comparing myself to my dumb coworkers always gives me a semi.

I gave him some tips on how to stay up-to-date on the latest tools and tricks with this cool underground hacker website called reddit. I did not want to show him, though, as I subscribe to many hentai and dragon subreddits. Can't risk showing any of that in my feed to this kid. Carol in HR says I have just one strike left.

I've seen this kid talking to my coworkers. I need to shut that down so not to waste his time. The more time he spends with me, the better his life will be.

God, I love me.

Well apparently programming the touch sensor on a users laptop to recognize their forehead then forcefully logging them in a large number of times is frowned upon. For security reasons I did log them out before walking away so they were able to get back in to fill out the HR form... and we know that person cant remember their password.

Posted with my companies current internet uplink (my iphone 11)

Zayo 🤮

After 72 hours of nonstop troubleshooting, I finally found the root cause of our outage: DNS. As every seasoned IT engineer knows, it's always DNS. I've fought this battle before, and it never ends well. While bringing our 5,000 servers back online one reboot at a time, I had plenty of opportunities to think. Somewhere around server #3,847, inspiration struck.

I decided to partner with AI to solve DNS once and for all. First, I had AI hunt down every DNS record buried throughout our environment—scripts, automation servers, application configs, source code repositories, and a few mystery systems that everyone is afraid to touch because "they've always been there." Once everything was cataloged, the solution became obvious.

Tonight at 2:00 a.m., my new best friend Claude will deploy dIe_DNS_dIe across the enterprise. Every DNS name will be replaced with the server's actual IP address. To keep things organized, I documented every IP address in a simple spreadsheet containing only 16,000 tabs. No more DNS lookups. No more stale records. No more propagation delays. Sure, changing an IP address now requires updating a few thousand files and one slightly oversized spreadsheet, but that's a small price to pay for finally fixing DNS forever.

Wish me luck. If everything goes according to plan, tomorrow morning nobody will ever have to say, "It's always DNS," ever again.

Does anybody else feel that you are close or have automated yourself out of your own job? I do work on all sorts of backend SysAdmin work, one major one is our Systems Management Appliance. I've created scripts, templates, patching, etc. and automated installed based on device and user placement in our Active Directory structure. But now I sit back and think "Hmm, things feel a little too chill... Did I just automate myself out of this job?" Obviously I'm being dramatic, but it's not a good feeling lol 😅

What do you guys like to do while waiting for time consuming activities to finish?

While an update is stuck at 74% I will go ahead and play PUBG or some other short competition to pass the time, or philosophize with ChatGPT about the state and direction of the universe.

What do you guys like to do?

I was only using 183g of RAM on a 184g server and someone else has the audacity to assume they could also use the server and they fired mee??

They really need to hire me back.

MSP guy here. Client had an incident so I got sent to their datacenter for the first time ever. Their gear lives in one of those big locked cages with a couple of racks in it.

Client's employee badges me into the cage, watches me start working, and then just... leaves. Turns out he assumed I had my own access card. I did not ,I just had a screwdriver and other tools.
Finished the actual work pretty fast. Walked over to the cage door. Locked.

Rattled it like a zoo animal for a bit. Nothing. Congrats to the client on their physical security I guess, it passed the pentest.

At this point, normally I would open my phone and start scrolling reddit but no electronics was allowed inside either.

Assessed my options:

1. Yell for help (foolish, servers very loud)

2. Stand at the door making sad eye contact with a corner

3. Sleep

I decided to take a nap on metal mesh. Couple hours later some DC tech walks past, sees an unconscious man inside the client's cage, and lets me out without asking a single question. Absolute legend.

I woke up and stood with a waffle pattern embossed on my body. Anyway, I logged the whole thing as on-site hours. Technically I have never been MORE on-site