Mostly harmless, conspicuously useful
The Hitchhiker's Guide to Becoming an IT Support Specialist
An IT support specialist keeps the organization's endpoints, accounts, applications, and connections in working order, which is a perfectly reasonable ambition until you recall that a printer is a network device when it works and a hardware device when it does not, that the user is always certain they changed nothing, and that the ticket's priority has been generously set to "urgent" by the same user who is also certain they changed nothing. You learn to translate "my computer is slow" into endpoints, accounts, DNS, wireless, and a service desk that records each request as evidence rather than as a cry for help. The grand objective is resolution on the first contact, an accurate ticket, and a durable fix; the daily evidence is usually a restart that works and proves nothing, a knowledge article that resolves the next ticket before it is written, and a user who is grateful and still certain they changed nothing. This guide travels from greeting the user to governing the support practice, with practical stops at troubleshooting, identity, endpoint management, and the recurring discovery that the cable is the network's first and last confession.
Level 1 · Novice
Restart it, then admit the restart proved nothing
You observe tickets, endpoints, peripherals, and user conversations without changing anything, learning how a device that booted this morning can deny all knowledge of itself by lunchtime.
You begin with read-only evidence: a ticketing system full of requests, a workstation inventory, peripheral lists, operating-system versions, and a knowledge base expressing recent opinions about what works. A desktop operating system is the software that boots the machine, manages files, runs applications, and presents the interface a user blames first; computer hardware is the workstation, monitor, keyboard, mouse, printer, and the cables that connect them, most of which are innocent. You sit with experienced specialists, read tickets, shadow calls, and inspect devices so you can distinguish a hardware failure from a software failure before prescribing either.
Suppose a user reports a printer that "won't print." Before ordering a replacement, you check the cable, the network light, the print queue, the user's selected printer, and the small label that reveals the document was sent to a printer two floors away that the user has never visited. The queue clears, the user is reunited with their document, and the printer, being a network device when it works and a hardware device when it does not, is spared an unnecessary funeral.
Words from the spaceship manual, translated
- Desktop operating system
- The system software that boots a workstation, manages files and applications, and presents the interface users blame first. Windows, macOS, and a handful of Linux desktops live here, each with its own opinions about updates and restarts.
- Peripheral
- A device attached to a workstation — printer, scanner, monitor, keyboard — that extends its function and its grievances. A peripheral is at its most confident immediately before it stops being recognised.
- Hardware failure
- A fault in a physical component — disk, memory, power supply, cable — that no amount of software, restarts, or goodwill will resolve. It is distinguished from a software failure by the cost of the replacement and the silence of the warranty.
- Print queue
- The ordered list of documents awaiting a printer, and the place where a single stuck job holds an entire department hostage with exemplary patience.