Everything, logged
The trail log
Every post, sorted newest first. Filter by topic, or by how far along the trail you are.
Every post, sorted newest first. Filter by topic, or by how far along the trail you are.
No posts match that search yet — try a broader term, or clear the filter.
It's not a brain. It's a very fast, very obedient clerk — and that distinction changes how you think about slow computers.
The desk-and-filing-cabinet model that ends the 'I have 512GB of RAM' confusion forever.
One has a spinning disk and a moving arm; the other has no moving parts at all. That single difference explains almost everything.
CPU, RAM, storage, and graphics are the famous residents. The motherboard is the roads, plumbing, and postal service connecting them.
One professor doing calculus versus a thousand students doing arithmetic — and why that second model ended up running AI.
Nobody brags about their PSU. But when one goes marginal, it produces the most confusing symptoms in all of hardware.
You don't need encyclopaedic knowledge to troubleshoot hardware. You need a repeatable method and the discipline to change one thing at a time.
Something has to wake the hardware up and find the operating system. Meet the code that runs before anything you'd recognise as a computer.
Same operating system, same apps — completely different failure modes. Batteries, hinges, heat, and the economics of soldered everything.
The shape of the plug no longer tells you what the port can do — and that one fact explains half of all docking-station tickets.
Every device needs an address before anyone can send it anything. Here's how the numbering actually works — and why we're running two systems at once.
Humans remember names; networks route numbers. DNS is the translation layer between them — which is why when it fails, it looks like everything failed.
You've connected hundreds of devices to networks and never once typed an IP address. Something did it for you — here's the four-step conversation.
One connects devices into a network; the other connects networks to each other. The corridor-and-border analogy that keeps them straight.
Dozens of devices, one public IP. The receptionist trick that quietly saved the internet from running out of addresses.
Two ways to send data: one guarantees everything arrives in order, one just throws and keeps moving. Both are the right choice — for different jobs.
A firewall doesn't understand 'good' or 'bad' traffic. It checks packets against a list of rules, top to bottom, and does what the first match says.
Wi-Fi is radio, and radio obeys physics. Frequencies, walls, and interference — the three ideas behind almost every 'Wi-Fi is bad' complaint.
The /24 notation, the network-vs-host split, and why subnetting is really just deciding how to slice a street into postcodes.
One technology, two very different jobs: getting you inside the office network from home, and hiding your traffic from the coffee shop.
Confidentiality, integrity, availability — not a checklist to memorise, but the three ways anything can go wrong with information.
Phishing doesn't exploit stupidity — it exploits urgency, authority, and busy Tuesday afternoons. Understanding the mechanics beats mocking the victims.
Something you know, something you have, something you are — and why one stolen password shouldn't be enough to become you.
Virus, worm, trojan, ransomware, spyware — the words get used interchangeably in headlines, but each names a genuinely different behaviour.
Symmetric and asymmetric encryption in one analogy each — and the elegant trick where anyone can lock a box that only you can open.
Not about distrust — about limiting how much any single mistake, phish, or breach can cost. The principle behind half of IT's 'annoying' rules.
A patch is a published confession that a lock was broken. From that moment, attackers and defenders are in a race — and the race is the whole story.
Why break encryption when you can just ask? Pretexts, tailgating, and the uncomfortable truth that politeness is a vulnerability.
Security has a precise vocabulary that news headlines blend into mush. Four words, one burglary metaphor, permanent clarity.
Every login, connection, and error leaves a record. Security work is largely learning to read — and centralise — the footage.
'Never trust, always verify' is the slogan. The castle that stopped working is the actual story.
Every padlock icon hides a rapid negotiation: prove who you are, agree on maths, build a shared secret in plain sight of eavesdroppers.
The protocol behind every corporate Windows login, explained as a festival wristband system — including why attackers love golden tickets.
The internet has no map and no manager. It has 70,000 networks gossiping routes to each other — on the honour system.
The internet's phone book was designed with no security at all. Here's how attackers abuse that — and how defenders fought back.
One identity on-premises, one in the cloud, and the synchronisation machinery that lets 'one username, everywhere' actually work.
Zero trust sounds abstract until you see the policy engine that enforces it: signals in, decision out, on every single sign-in.
VLANs guard the borders between network zones. But most attack traffic moves sideways, inside zones — and that needed a new answer.
The encryption is the last five percent. Walking the whole chain — access, foothold, escalation, exfiltration — is how defenders learn where it breaks.
Someone has to write the rules that turn a billion log lines into the one alert that matters — and not the thousand that don't.
Tickets, SLAs, change requests, 'raising a P1' — if you've heard any of these, you've met ITIL without being introduced.
Users don't want servers, networks, or apps. They want to get paid, send email, and print the thing. That reframing is the whole foundation.
Every service stands on four legs — people, technology, partners, and process. ITIL's first big model is a checklist for not sawing one off.
Forget the process diagrams for a moment — these seven habits of judgement are the most practically useful page in all of ITIL.
One diagram claims to show how an organisation turns demand into value. Here's what each layer actually means — and why the order matters.
Not a pipeline — a road network. ITIL's engine room is six activities that every piece of work visits in its own order.
The fire, the faulty wiring, and the rewiring work — one analogy that permanently separates ITIL's three most confused terms.
Logging, categorising, prioritising by impact and urgency, escalating, resolving — the anatomy of the process every IT career starts inside.
Firefighters restore service; detectives stop the fires recurring. Root cause analysis, known errors, and why this practice is chronically underfunded.
Most outages are self-inflicted — caused by changes. The practice that manages that risk, and how ITIL 4 rescued it from its own paperwork.
Not 'the helpdesk with extra steps' — the single point of contact, the request catalogue, and why this role is IT's best career school.
A service level agreement is a promise with a measurement attached. Here's how promising works — and the watermelon trap that catches everyone.
Half of IT's hardest questions — 'what does this outage affect?', 'is it safe to change this?' — are map questions. Here's the map, and why it's so hard to keep true.
Seven questions, one register, and the difference between organisations that evolve and ones that fossilise with excellent documentation.
Foundation to Master, honestly appraised — what the exam actually tests, who benefits most, and how to study without a bootcamp budget.
Forget the movie robots. Modern AI is pattern-matching at colossal scale — and knowing that one fact deflates most of the hype and most of the fear.
No database of answers, no search engine underneath — just next-word prediction, scaled until it started looking like thinking.
Hallucination isn't a bug that better engineering will simply delete — it's the price of how these systems work. Here's the mental model, and the working rules.
The difference between a useless answer and a brilliant one is usually the question. Context, constraints, and examples — the mechanic's guide to prompting.
Defenders use AI to find the needle in a billion log lines. Attackers use it to write the phishing email that finally gets past you. Both are already true.
Why the seven-layer diagram is taught backwards, and the one mental model that makes troubleshooting click.
The apartment-building analogy that finally makes broadcast domains make sense — plus how to try it at home.
IaaS, PaaS, and SaaS explained through renting, not buying — and where to get a free server to practise on.
You are not expected to know everything on day one. Here's the short list of things that are actually worth your energy.