Keep Your Skills Sharp the Hard Way
Home
About
Contact
Dark Mode
Table of contents
Keep Your Skills Sharp the Hard Way<br>The endless stream of 'better prompts' and 'agentic loops' content is mostly a campaign by the people who bill you for the dependence. The thing it tells you to skip is the only thing that keeps the agent from shipping damage under your name.
By Ruslan Tolkachev
TL;DR Staying sharp in the LLM era isn’t nostalgia and it isn’t prompt-craft. The “agentic loop / context engineering” genre is largely a marketing story told by the parties who profit from your subscription and your dependence. The move that holds up is to keep sweating hard problems by hand, because skill you didn’t earn through friction doesn’t stick, and without it you can’t push the model to its ceiling and can’t catch it when it ships damage instead of productivity.
Take it to the extreme to see the shape of it. Two people build the same production database with the same model and the same tools. One is a database SME with twenty years on the job. The other is the world’s best LLM prompter who genuinely could not tell you what SELECT does. On day one the prompter’s toy demo might even look fine.<br>The difference shows up before either of them writes a line, in the questions only one of them knows to ask. The SME reads the workload first. Read-heavy or write-heavy, the capacity it has to carry and the growth curve it has to absorb, and the SLO that decides what “fast enough” even means before any tuning is worth doing. She pins down how primary keys get generated, because on a write-heavy table a random UUID v4 scattered across the clustered index pays a page-split and write-amplification cost that a monotonic key never does, and that choice is brutal to walk back once the table is large. She knows the shard key Elasticsearch rides on decides whether tonight’s extract is a seek or a full scan, so the CDC path and the load it lands on the source get designed up front instead of discovered when the extract starts timing out. And she carries the domain itself: which application-side issues are already known, which failure modes she’s personally cleaned off the floor, the landmines you can only steer the model around if you already know they’re there. The prompter can aim the model at none of this, because they don’t know it exists, and they can’t catch the model quietly dropping it. The prompt was never the skill. The skill is what lets the prompt produce a thing that survives contact with production.<br>Both databases boot. Both serve the feature set. On day one nobody in the room can point at the difference. Hand the two of them to whoever will carry the pager, though, with no idea which model wrote either one or how good the prompter was, and they take the SME’s without opening the schema. They’ve met the other kind at 3am.<br>The uncomfortable part is personal. You become the prompter by giving away, a little at a time, the work that would have made you the SME the on-call just picked.<br>The block-an-afternoon fix doesn’t reach the erosion<br>The obvious move is to put learning back on the calendar. Block Friday afternoons for a course, grind some algorithm problems, carve out time to “stay current.” Reasonable on its face, and it mostly fails for two reasons.<br>The first is that after-hours willpower loses to the sprint every time. The judgment above didn’t erode on a quiet Friday; it eroded inside the delivery flow, one pasted prompt at a time, under deadline, where the agent was the fast path and the fast path was rewarded. A learning block on the calendar is the first thing the sprint eats. The erosion happens in production flow, so a fix that lives outside production flow is aimed at the wrong place.<br>The second is that decontextualized practice rebuilds the wrong thing. Grinding LeetCode is useful for the reps it gives you (more on that below), but it doesn’t rebuild system-specific judgment, because the judgment that catches a bad migration is judgment about your schema, your access patterns, the specific table that takes a metadata lock the moment you add a column with a default on the version of MySQL you happen to run. None of that is in a course. It’s in the work. Decontextualized practice keeps the general muscle warm; it does not deposit the local knowledge that turns the agent from a liability into a multiplier on your codebase specifically.<br>Note This is an argument for selective retention, not Luddite refusal. This doesn’t mean write everything by hand. The point is narrower: there’s a specific category of work, the work that builds the judgment you need to supervise the agent, that you give up at your own cost when you outsource it by reflex. Most of the rest, hand it off and move on.
Why the skill you didn’t sweat for doesn’t stick<br>The mechanism...