The Skill List Died. Data Access Is the Job.

We ran a senior hiring loop last spring. Round two scored Postgres internals: isolation levels, MVCC, deadlock graphs. Candidate A recited them without blinking. Candidate B asked if we had a replica she could log into.

We gave both a read-only replica and Claude Code. B pulled last week’s lock logs, asked the model what waited on what, then opened the wait graph herself. Twelve minutes. A asked for a whiteboard and drew the textbook deadlock. Clean picture of the wrong week.

I used to treat A’s recitation as the craft. I collected the same lists on weekends. I could talk through a lock graph on a whiteboard and still wait three days for a replica ticket. Then I pointed a model at a machine I could actually reach, and the lists started looking like a museum tour of a building I had never entered.

What Senior Looks Like Now

The bar moved. Senior now means you can reach the system of record, point a model at the real artifact, and say the claim is wrong because you opened the same file. The new bar is harder than the old one. Reciting isolation levels in a conference room is a speech you can rehearse. Getting unfettered read access to production-adjacent data is political, slow, and often blocked. A blocked ticket does not cancel the ask. Name the owner and work the next file you can reach. The people who still win incidents are the ones who can open the door.

The same pattern shows up outside engineering. I sat with a controller who could walk a close deck from memory and still could not export the raw ledger. We got a CSV on a Thursday. A model found two mapping errors before lunch. She already knew the accounts. She had never been allowed to see the rows. I have watched a CI lead argue about a YAML file the runner never used, then go quiet when we pulled the artifacts. I have watched a plant supervisor recite last year’s alarm codes while the bottleneck sat in a dump nobody had permission to open. His recitation was fluent. The dump stayed locked, so the line stayed slow.

The AI gap piece is a cousin. That essay assumes everyone already has the model. This one asks a prior question: can you even show the model the machine?

The operating system piece is another cousin. That one is about where agents live. This one is about whether you are allowed to look.

Unfettered does not mean you need write access to production. It means you can reach the same rows the incident is about without asking someone to paste a screenshot. A screenshot or sanitized sample is a copy. The job is the row, the log, the export you can open again tomorrow. Write the path down so the junior is not hunting a file that only lives on your laptop. I have paid for Copilot seats on repos nobody could clone. I have watched teams buy a model and then argue about a PDF of a query plan. The spend looked serious while the file was still missing.

Why People Still Collect Trivia

The old list feels like safety. If you can name the internals, you belong in the room. Hiring still scores the recitation. Performance reviews still have a depth line that means you can lecture the junior. Studying is cheaper than asking security for a replica. A flashcard never files a ticket.

None of that makes the old knowledge worthless. Knowing how locks work still helps you smell a lie. I still want the person who can look at a model’s answer and say the isolation story does not match the log. That check is judgment you can only do with the file open. Recitation without the log is a comfort object you can carry into any meeting.

People stay on the list because the list is under their control. Access is not. Access requires a human in security, a ticket, a justification, sometimes a fight with a vendor who sold you a system and then locked the export. Collecting trivia lets you keep feeling senior while the actual constraint sits in someone else’s queue.

I did this. I kept a private study list long after I had stopped opening the machines those items described. It felt like maintenance. I was studying so I did not have to ask for access.

The list dies fast once the door opens. Point Claude at a reachable Postgres box and most of the interview script becomes a lookup. Point it at a clean ledger export and the I-know-every-mapping identity lasts about an hour. Point it at the CI artifacts and the person who memorized the pipeline file finds out the runner used a different one. Permission to see was always the scarce thing. The encyclopedia made us feel prepared while we waited.

Open the Door This Week

Write the list of systems you cannot see: production database, warehouse, billing export, CI artifacts, the vendor portal that only one person can log into. If the list is empty, you are lying or you are unusually lucky.

Pick one. Ask for read access this week. Not admin. Not a rewrite of the permission model. Read. You own the ask and the check. You do not own security’s queue or the vendor lock. If they say no, write down the blocker in one sentence: policy, vendor, fear, or nobody owns the request. Name the blocker so you have a job, because a vague we-cannot is how the week dies. Studying while you wait is still the dodge.

I wasted a month once refreshing a study list while a replica ticket sat in security with no owner. I told myself I was staying sharp while I stayed busy so I did not have to ping the same person again. The day the replica landed, I used the model for twenty minutes and threw out half the list. The other half still mattered because I could finally check it against a live wait.

If the model is banned or the machine is air-gapped, theory still earns its keep. You still open the file and check the claim yourself. A list you never apply does not count. The function stays the same: reach the real artifact and verify. The model is a shortcut when the room allows it.

When you get the door open, point the model at the real artifact: a dump, a log directory, a CSV of the ledger. Not a screenshot of a dashboard and a prompt that says what is wrong. Dashboards are already someone else’s summary.

Then verify one claim yourself. Open the same row. Follow one wait. Add the numbers by hand once. If you skip that step, you replaced a flashcard with a confident paragraph you cannot defend.

Drop one museum item from your study list. If you have not touched that system in a year, stop pretending the recitation is your job. Keep enough theory to catch a lie. Stop treating the encyclopedia as the work.

How you evaluate a new tool is a different essay. That one is about a trusted wow, a short clock, and a dumpster. This one is about what you feed the model after you keep it. Code got cheap is about deciding what should exist. This is about whether you can see what already exists. Just because AI can is about what to automate. Access sits earlier than all three. If the file is locked, the rest of the argument does not start.

You Will Know When the Recitation Stops Saving You

The next incident is the test. Do you open the replica, or do you open the notes app? Reaching for the study guide first means you are still doing the old job. Finding a problem you have never seen because you could see the data means the new job showed up.

Watch what happens to the junior. If the access lives in your head and your laptop, you rebuilt the old bottleneck. The scarce resource should be the path to the logs, written down, not your memory of last quarter’s outage.

When someone recites internals in a meeting, ask where the file is. That question used to sound rude. It is now the only useful one. I have ended more than one status update by asking for the dump instead of another explanation of how locking works. The explanation was fine. We still could not see Tuesday.

Final Thoughts

The skill list became cheap. Models pointed at a reachable machine will outrun most of the encyclopedia you were proud of. The work that remains is getting to the data and checking the claim.

If your identity is I know the internals, mourn it and then go file the access ticket. The incident still needs the person who can open the machine.

If you want a community that will not confuse a study list with the work, MasteryLab is where people practice judgment on real machines.

FAQ

Did memorizing internals become useless?

No. Knowing how locks, ledgers, and pipelines work still helps you smell a lie. What died is treating the recitation as the senior job. A model pointed at a reachable machine will outrun most of the encyclopedia. The scarce work is getting to the real file and checking the claim.

What does data access mean in this argument?

Unfettered read access to the system of record: a replica, a ledger export, pipeline artifacts, alarm history, the vendor dump one person still owns. Dashboards do not count. Someone already summarized those. If you cannot open the file the model is talking about, you do not have access.

How is this different from the AI judgment-gap essay?

The July 19 piece assumes equal model access and asks who has the judgment to use it. This piece is earlier in the stack. A lot of teams never get to that question because they cannot show the model the machine. Access is the prior constraint. Judgment still matters after the door opens.

What should I do this week if I do not have production access?

Write the systems you cannot see. Pick one. Ask for read access, not admin. If they say no, write the blocker in one sentence: policy, vendor, fear, or nobody owns the request. A named blocker is a job. Then point a model at whatever real artifact you can get, and verify one claim yourself.