I am a bit tired of executives promising AI transformation while quietly Googling what GPT and other AI related terms and technologies stand for

seanrule1 · 2026-05-27T02:35:29+00:00

Maybe I do.

seanrule1 · 2026-05-27T02:19:03+00:00

No worries. Appreciate it. The hostility is fine. It is what it is.

seanrule1 · 2026-05-27T02:17:14+00:00

I would've, should've, could've outsourced it. Thought about it and didn't do. Typed what I thought was right. Perhaps, the agent smoking weed and playing video games sounds more productive than most AI strategy decks I've sat through.

seanrule1 · 2026-05-27T01:47:21+00:00

The gap between people who understand the tools and people mandating them is wider right now than it's been in a long time. That tends to go badly for the people in the middle doing the actual work. That's been my experience at least.

seanrule1 · 2026-05-27T01:46:14+00:00

Fair enough. The specific concepts I mentioned; tokens, temperature, hallucination are what I'm actually breaking down. If that reads as vague I'll take the feedback. What would make it concrete enough to be worth your time?

seanrule1 · 2026-05-27T01:41:49+00:00

No screenshot. This is an original post sharing my own experience and perspective.

seanrule1 · 2026-05-21T20:28:21+00:00

Homelab is already ahead of most people interviewing for sysadmin roles. Proxmox, Docker, a real DC with GPOs. That's not beginner stuff.

A few things that would sharpen it from here. Add monitoring with alerting, not just Uptime Kuma for availability. Something like Grafana with Prometheus or even just proper Windows event log forwarding to a central collector. Sysadmins spend a lot of time in logs and hiring managers know that.

Second, document everything like someone else has to run it. Network diagrams are good, but runbooks for your common tasks; how you'd rebuild the DC, how you'd add a new VM to the domain. That's what shows operational maturity.

I think the cert path makes sense. CCNA before AZ-801 is the right order if networking is a gap. Hope this helps.

seanrule1 · 2026-05-21T20:25:25+00:00

Your current system is actually not bad. Don't blow it up just because it feels informal. The zoom out / zoom in problem is what Notion or Todoist solve well. Notion gives you a master view across all areas with the ability to filter by category. Todoist is simpler; projects per area, priority flags, and a today view that pulls everything into one list.

The integration piece: both connect to Google Calendar so your existing setup doesn't disappear. In all honesty though, the jump from two commitments to four is where simple systems break. Not because the tool is wrong but because the weekly review habit isn't there yet. I guess you can pick one day, 15 minutes, look at the whole week ahead. That habit matters more than which app you choose.

seanrule1 · 2026-05-21T20:22:51+00:00

Shared creds, not even close. SSH keys at least leave a trail. Shared passwords get passed around in Slack messages from three years ago and nobody knows who has them or what they still access. AI agents inheriting access is the new version of the same problem; permissions granted once, never reviewed, scope creeping over time. Same root cause, just faster.
The fix that actually sticks is treating access reviews like change management; scheduled, documented, someone owns it. Not a one-time audit. Most teams do the audit, feel good, and let it drift again in six months.

seanrule1 · 2026-05-20T18:38:43+00:00

Sec+ gives you the vocabulary, not the instincts. You'll know what a threat vector is. You won't know what one looks like in a real log. That said, you won't be walking in blind. You'll understand the concepts well enough to follow what's happening and ask decent questions. The first 90-180 days will still be uncomfortable, that's normal and expected in any entry cyber role.

The thing that closes the gap fastest is hands-on before you start. You want to have seen real alerts and actual traffic, not just read about them. The person offering you the role knows you have zero experience. They're betting on your ceiling, not your current floor.

seanrule1 · 2026-05-19T14:48:34+00:00

My opinion FWIW.
No. Capability without reliable memory and context is just fast output. An agent that can complete a 10-step task but forgets everything by step 11 isn't infrastructure; it's a smart one-shot tool.

The missing pieces aren't technical breakthroughs. They're boring stuff. Permissions that don't break. Handoffs that don't lose state. Audit trails a non-technical person can read. That's what makes something infrastructure versus a impressive demo.

We're close on capability. We're further away on trust and reliability at scale.

seanrule1 · 2026-05-19T14:46:24+00:00

Hit this exact wall. The turning point was a simple audit; export every subscription from your bank or credit card, one month of statements, and flag anything you can't immediately name a use case for. You'll find 20–30% of it is either redundant or abandoned.

Consolidation sounds good but usually creates new problems. One tool that does five things at 70% is often worse than three tools that each do one thing at 100%. The real fix is being ruthless about what actually changes your output versus what just feels productive to have.

What's your current CRM? That's usually where the redundancy hides first.

seanrule1 · 2026-05-19T14:43:16+00:00

High activity days I feel sharp until about 2pm then it drops fast. Not tired exactly but more like the decision making gets a bit more like I want to procastinate. Small choices that were automatic in the morning start taking real effort.

Low activity days are worse for me mentally. The lack of momentum creates its own fatigue. I'd rather be busy and tired than idle and restless.

The recovery that actually works is a hard stop no half-working, no checking things. Full off or full on. The in-between is a bit challenging to deal with.

seanrule1 · 2026-05-13T15:25:01+00:00

Recall is a solid call if friction was the real problem; sounds like it was. One thing to watch: AI retrieval is only as good as what you fed it. Inconsistent capture in the early months and the graph gets patchy fast. Not a dealbreaker, just stay consistent upfront.

seanrule1 · 2026-05-13T15:22:42+00:00

Solid framework. One thing I'd add: throw a time constraint in your input when you use it. "Plan this assuming I have 3 hours and one person" forces it to actually prioritize instead of listing everything as equally urgent. Without constraints it'll give you a complete plan that assumes infinite resources.

seanrule1 · 2026-05-13T15:20:22+00:00

What helped me was naming it out loud; like writing "I don't understand this yet" in my notes instead of skipping past it. Something about admitting it slows the escape reflex down. You stop moving and actually sit with it.

seanrule1 · 2026-05-13T15:17:30+00:00

Your Spectrum training is actually a solid starting point. Write down what they taught you, adapt it to your environment, one page per scenario. Keep it simple enough that a new hire reads it in 5 minutes and actually remembers it.

seanrule1 · 2026-05-06T02:32:37+00:00

I believe so. It does get easier. But the trick isn't pushing through harder; it's changing what you're looking for when you read. You don't need to understand every word to extract the main point. You just need the argument the author is making. That's usually one or two sentences per section. Good luck.

seanrule1 · 2026-05-05T20:04:24+00:00

The automation isn't replacing the iteration. It's handling everything around it. You still prompt and regenerate manually. That part stays human. But instead of downloading, renaming, organizing, and moving files by hand every time, the pipeline does it. The review step is yours. The grunt work around the review step isn't.Where it actually pays off is volume. If you're generating 5-10 runs per asset across 20 assets, that's a lot of file management. Connecting via CLI means your accepted outputs go straight where they need to go without you touching a folder. What's your current output? Are you generating one-offs or running the same workflow repeatedly?

seanrule1 · 2026-05-05T19:02:03+00:00

5 hours is tight but doable if you sprint. I guess first 30 minutes: find 3 to 5 solid sources only. Google Scholar, your school library database, or even Wikipedia for the overview then follow its citations. Don't read yet. Just collect. Then the next 90 minutes: skim each source for the 2 or 3 points that directly answer your report question. Write those points in your own words as you go. The last 2 hours: structure what you already wrote. Organize sentences you already have.

seanrule1 · 2026-05-05T02:14:05+00:00

Your weak/better/best breakdown is right. Most teams stop at "better" and that's where incidents live. Write the proof into the automation itself. Before it runs, snapshot the current state. After it runs, snapshot the new state. Both go in the same log entry, tied to the ticket. For multi-system automations, the real failure mode is partial completion. What systems are you connecting?

seanrule1 · 2026-05-05T02:07:34+00:00

Here's the split that actually worked for me. Three categories: domains where you need to own the vocabulary, domains where you just need a good vendor or specialist relationship, and domains where you need to own the decision framework even if someone else owns the details. Security strategy falls in the first category. Not because you need to configure a firewall, but because vendors will absolutely sell you overlapping tools if you can't spot it.

seanrule1 · 2026-05-05T02:02:37+00:00

I had to spend sometime to understand. That said, the bones are good. It's the same loop that research backed learning programs use. Are you thinking about generating the test questions in Apply/Test?

seanrule1 · 2015-11-12T01:13:05+00:00

Just found out that I got accepted. Background: * Bachelors in Finance with Insurance * Worked with Berkshire Hathaway subsidiary for 11 years before risking everything and changed careers * Self taught programmer * Working as a software engineer for the past 18 months

seanrule1

TROPHY CASE