The same E3, E5, and E7 question, this time mapped onto the Microsoft Zero Trust architecture, component by component.
A one-screen visual of the security coverage Microsoft 365 E3, E5, and E7 each add, mapped to the Cyber Defense Matrix.
A three-level rubric for taking more control of the technology I own, with Reolink as a stepping stone and AI helping with the work.
A year ago I wrote a nine-layer identity maturity framework. The part that still holds up is the ordering, and the four gates that tell you whether you have earned the next layer.
I cut my GitHub account from 32 repositories to 9. Here is the rule I used, and what four of the deletions say about where AI actually helps.
Most enterprise AI projects I see are a new front door onto software the company already owns. My philosophy for AI transformation is three moves in order: make today faster, get the rest of what you bought, then buy more precisely.
How I use GitHub Copilot, saved instructions, and browser checks to turn an article into a visual presentation.
I spent six years building technical depth on top of sales leadership. Here is how I rebuilt my resume to show the whole plan.
A review of VS Code's newer agent features changed how I think about instructions, portable skills, Agent Host sessions, subagents, hooks, and approval boundaries.
A draft thought on two Charlotte transportation fixes I keep coming back to: parking incentives that use lots and decks first, and a faster path from transit idea to groundbreaking.
Staying present on social media usually dies as a separate chore. If the drafting capability lives inside the same agent session that ships the work, and the risky parts are deterministic guardrails, the post becomes a byproduct instead of a second job.
A copyable markdown workflow for building presentation-ready articles with Copilot agents, optional present mode, and screenshots that prove the layout works.
Missed the session? This is the walkthrough version: add your name to a real project, let a coding agent handle the Git mechanics in the open, and practice the part that matters most: understanding the change before you approve it.
A real session taught me the difference between using Copilot as a coding helper and using it as an operator inside GitHub. The lesson wasn't more automation. It was better judgment around issues, proof, and ownership.
I set out to build a social-promotion helper in VS Code and learned a more useful lesson about agentic tooling: where a capability lives decides whether it travels. The first version worked and went nowhere. The second one snaps into any session.
The loudest AI predictions keep getting the second move wrong. Radiologists were supposed to be gone by now; instead they are busier and better paid than ever. That same pattern shows up in two places nobody is watching closely enough: what happens to the value of data once a model is trained, and why the rush to put agents in charge of other agents is quietly admitting the limits of what we built.
Your environment is already a platform. The agentic shift does not ask you to build a second one. It asks you to run agents across the same identity, data protection, investigation, and governance machinery your people already depend on.
A public-safe version of my mid-year performance narrative -- structured around the actual Connect prompts, with customer details scrubbed and the answers written the way I'd want to read them as a hiring leader.
I gave up on January resolutions and replaced them with three personal new years -- relationship, professional, personal -- each one anchored to a single word.
My walking deck, rebuilt as a seven-part interactive introduction I can pull up anywhere.
A running list of Charlotte arts organizations and spots I want to keep handy for nights out, weekend plans, and general reminders that I should leave the house more often.
I decided to make my career development plan public. This is the first edition of a series I will publish every six months -- because the kind of accountability that drives real growth does not happen in a file share.
The current enterprise AI conversation is full of category mistakes. This post starts a series on how to tell the difference between an AI-enhanced app, an assistive agent, an autonomous runtime, and the security controls that should change as authority increases.
How I transformed my basic Jekyll blog into a modern, professional platform using AI assistance - including the exact prompts and techniques that made it successful.
A hands-on tutorial for using GitHub Copilot to build and manage an Azure lab, taking the vibe coding approach into infrastructure work instead of application code.
Real questions from people trying to choose a cybersecurity path, pulled from Reddit, with the direct answers I would give each of them.
People ask what salary a certification should get them. Certifications buy you confidence and interview anecdotes, and I would not price a career on them.
Between Microsoft, teaching at night, and SANS certifications, time blocking is the only scheduling method that held. Here is my actual weekly schedule.
The ten daily habits that moved the needle for me, from cold showers and Duolingo to Python practice, and why the routine matters more than any single item on the list.
We plan careers in years and decades. Counting the same life in hours changes which trade-offs look reasonable.
The ten links I keep handing to people who want to supplement their cybersecurity learning with something interactive instead of another video course.
Infrastructure as Code is going to matter more over time, so I used some downtime to learn it properly. This is the walkthrough from definition to a working deployment.
A build log for pulling my tweets through Azure Logic Apps into Power BI, so I could see whether I was spending my time well or just spending it.
Do you need to code before getting into cybersecurity? The question breaks down once you separate scripting from software development, so here is where I would start and when.
A full walkthrough for connecting an Azure vNet to an AWS VPC from scratch, jumping between both consoles, with every resource and doc link at the bottom.
Telling people to go ask someone in the field stopped feeling like a real answer. Feedback loops give a better way to choose a cybersecurity path and correct as you go.
Learning to use a hammer and learning to make one are different careers. Scoping which side of that line you are on is the fastest way to stop drowning in cybersecurity.
I have spent my whole career in training rooms, and the advice for standing out in a cohort changed once those rooms moved online. Here is the version that works now.
Two questions come up in almost every conversation I have with career changers: how do I break in, and how do I stand out. Here is what I actually tell them.
Self-paced online learning broke my study habits until I admitted I had no process. These are the two techniques that got learning working again after my career change.
Missing out on a promotion or a project is a signal, not a verdict. Isolate the problem, ask directly, and start contributing before anyone hands you permission.
You check your tire alignment once a year for a smoother ride and better mileage. This is what happens when you run the same inspection on your goals.
There is no such thing as a bad goal, but there are unclear ones. Here is how I move a goal from something I keep changing to something I actually do.
Moving from sales to tech meant relearning how I learned. These are the soft skills I had to rebuild first: reading comprehension, research method, and critical thinking.
Everyone says to apply anyway and ignore the experience requirement. That advice is lazy on its own. Here is how to go build the experience instead of pretending you have it.
Luck is timing meeting preparation. After a career change I had to build the preparation half on purpose, and this is the system I used to keep momentum going.
You are the average of the five people you spend the most time with, which makes mentorship a math problem. Here is how I went about raising my average.
Sales teams rehearse rebuttals and forget to rehearse the yes. Here is how planning for a successful call, not a defensive one, changes what you ask and what you close.
Meeting people got harder when the world went virtual, so here is the prep work, the search method, and the follow-up cadence I used to keep building a network without a room to walk into.
Try a broader search term or clear the query to widen the record.