The Rhythm of Competence and the Illusion of the Degree

Capability is not proven by conversation or decorative certificates. Spoken dialogue is one superficial interface. Real capability is governed by timing, structure and execution.

Nothing about systems was learned in a lecture hall. It came from a drum kit in Nottinghamshire, and an autistic kid whose speech came in spits and spats, usually when someone asked me a direct question. Unscripted conversation was a chaotic wall of static.

Christmas Day 2007: my first kit, basic, red and junior, bought to see if it would stick. It took a hammering all holiday until the skins split and it broke. Then a Wii-connected electronic kit became the main setup. The moment my hands gripped the sticks, the static went completely silent.

An electronic kit does not care about posh accents, eye contact or social charm. It runs on cold telemetry and unforgiving timing. If your strike drifts four milliseconds, it registers a miss. You cannot sweet-talk an input sensor. You are locked in the pocket or you are out of time. Session drummer Kenny Aronoff says the same from the other side: when programmed drums arrived, he had to get as tight as the machine, because that is what the producers were listening to (watch the interview).

A poem to my parents came before neat sentences did. The spelling was all over the shop, but the message hit dead centre. My mum understood it at once, because real communication is the weight of the truth, not the packaging.

That is the baseline for everything: the rhythm never lies. A system is not judged by its brochure. Raw input and raw output, nothing else.

Reading a specification

A job description, a supplier requirement, a safety standard and a process document are all specifications. The kit taught me to check a specification against the work it describes.

Where does the strictest requirement sit, and does it sit on the riskiest task? Is there an equivalent route for someone who can prove the skill another way? Does the stated reason explain the rule, or only repeat it? Has anyone put the document next to the real work?

That is how the mistakes everyone walks past show up: the gate with no reason behind it, the requirement that blocks capable people from the task it was meant to protect, and the rule that looks sound until it meets a case it was not written for.

When a system filters on decoration instead of deliverables, it filters out the people who can actually do the work.