🤠 Sunday Night Prep: Five Things To Check Before Monday

In partnership with

This is an IT Support Group

Sunday Night Prep 🤠

A short one. Five things to check before Monday so Monday doesn't check you.

GM IT pros,

Happy Sunday! Third email from me this weekend, so I'll keep this one short — I know you've got a real life. This is just a pre-Monday checklist so you walk into the office (or the home office, or wherever your laptop lives) already two steps ahead of whatever the week is planning to throw at you.

If you skipped Friday's roundup and Saturday's editorial, the TL;DR is: Oracle did a 6 AM layoff email, GitHub Copilot starts training on your prompts April 24 unless you opt out, and Fortinet is on fire. Again.

Now the checklist.

-Stetson

The Sunday Night 5

Five things. Fifteen minutes. Monday-proof your week.

✅ 1. Confirm the Fortinet Box Is Actually Patched

CVE-2026-35616 (FortiClient EMS, 9.1 CVSS, pre-auth bypass) has been actively exploited since March 31 and CISA's KEV deadline was Thursday. "We patched it" is not the same as "I verified it's patched." Log into the box, check the build string against Fortinet's advisory, confirm. Takes two minutes. If it's not on the fixed build, you're patching Monday morning before coffee — and explaining to the CIO why you didn't Sunday night.

✅ 2. Flip The Copilot Training Toggle Before April 24

GitHub's new default: your Copilot Free/Pro/Pro+ prompts train Microsoft's models starting April 24 unless you opt out. Go to github.com/settings/copilot/features, scroll to Privacy, turn off "Allow GitHub to use my data for AI model training." Takes ten seconds. Then tell your devs — especially the ones with personal Pro accounts, which is all of them. Copilot Business and Enterprise are exempt; the side hustle isn't.

✅ 3. Pre-Stage Patch Tuesday (It's Tuesday This Week)

Microsoft Patch Tuesday lands April 14 — this Tuesday. Analysts are calling 80-100+ CVEs. This is the first Patch Tuesday after March's parade of broken updates (KB5079391 yanked in 24 hours, KB5079473 breaking Microsoft account sign-in, emergency patches fixing the emergency patches). Do yourself a favor and set up the test ring tonight so Tuesday's releases go there first. Monday-you will thank Sunday-you. Tuesday-you will thank both of you.

✅ 4. Kill Any Flowise Instance You Stood Up "Just To Try It"

CVE-2025-59528 in Flowise is a flawless 10.0 CVSS code injection bug and it's being actively exploited right now. If you spun up a Flowise container six months ago to experiment with agent workflows and then forgot about it, go log in and turn it off. These "just to try it" POCs are exactly what attackers are scanning for. The rule for this kind of orphaned AI tooling: if you can't remember why it exists, it shouldn't.

✅ 5. Write Down Three Wins From Last Week

Non-technical one. Yesterday's editorial hit on this but it's worth repeating in checklist form: sit down for five minutes tonight and write down three specific things you did last week that were judgment calls, not runbook executions. The weird root cause you found. The policy exception you talked management out of. The automation you chose not to build because it would've been fragile. Keep the list in a file on your own machine, not the corporate wiki. Every IT person I know wishes they had this list when they needed it, and nobody has it when they need it.

🎯 Bonus Round (If You Have Extra Time)

Three more things, for the overachievers and the anxious and the people who just really don't want to watch another cooking show tonight:

• Reboot your workstation. Not a lock-screen. An actual reboot. It's been up for how long now? Exactly.

• Check your personal password manager for anything flagged as reused or weak. Fix one. Just one. Baby steps.

• Run df -h on whatever server you think about the least. I guarantee one of them is at 94%.

🥷 Shell Samurai: Sunday-Night Worthy

If any of the above reminded you that your shell skills could use a tune-up — and let's be honest, whose couldn't — Shell Samurai is the hands-on Linux trainer I built for exactly this. Real commands, safe sandbox, no signup wall. Spend 20 minutes tonight, walk into Monday sharper. shellsamurai.com for the pitch, app.shellsamurai.com to jump straight into a lesson. Built by yours truly. Shameless plug, zero regrets.

One more thing before you log off: I vet every sponsor before they ship. The one below made the cut — give it ten seconds of your scroll, and if it's for you, click it. If it's not, at least you know I didn't waste your inbox.

AI Agents Are Reading Your Docs. Are You Ready?

Last month, 48% of visitors to documentation sites across Mintlify were AI agents—not humans.

Claude Code, Cursor, and other coding agents are becoming the actual customers reading your docs. And they read everything.

This changes what good documentation means. Humans skim and forgive gaps. Agents methodically check every endpoint, read every guide, and compare you against alternatives with zero fatigue.

Your docs aren't just helping users anymore—they're your product's first interview with the machines deciding whether to recommend you.

That means:
→ Clear schema markup so agents can parse your content
→ Real benchmarks, not marketing fluff
→ Open endpoints agents can actually test
→ Honest comparisons that emphasize strengths without hype

In the agentic world, documentation becomes 10x more important. Companies that make their products machine-understandable will win distribution through AI.

Make Your Docs Agent-Ready

That's it. Go eat dinner. Go watch something dumb. Go to bed at a reasonable hour for once. The queue will be there Monday and it will be fine because you already handled the Fortinet box and the Copilot toggle and the test ring and you know exactly what to say if someone asks what you did this quarter.

Back to the regular snark-filled roundup next Friday.

Stay paranoid. Stay patched. See you next Friday 🤠

-Stetson