About

The IT Guy publishes short, step-by-step fixes for the everyday tech headaches that make regular people give up and call a relative.

We watch vendor changelogs, security advisories, billing announcements, and user complaint threads. When a problem starts to spike — Windows broke printers again, an iOS update killed AirPods auto-switching, a banking app login loop — we publish a guide while the issue is still hot.

How the guides are written

Each base is produced by an automated pipeline, then reviewed, fixed and tested by hand:

1. RSS feeds (vendor blogs, news aggregators, Reddit) are fetched on a schedule.
2. A small language model summarizes each item and classifies how badly it'll hurt regular users.
3. A larger model picks the items most likely to send people to Google in the next two weeks and writes a draft.
4. We use a RAG (Retrieval Augmented Generation) setup to rank issues based on how much damage a bug can cause.
5. We manually review the article, search for fixes or try to come up with one then test it using VMs/Emulators.
6. We re-write the steps into a comprehensible guide and publish it.

We weight signals from the vendors themselves and from large user complaint threads over speculation. Then the RAG setup gives us the insights into which bugs are the most urgent. The rest of the process is just good old debugging, fixing, writing.

When a guide doesn't help

If the steps don't work, please contact your IT guy. Or wait a day or 2, the community always comes through.