ReadingResearchRadarInvestment framework
Sign in / Sign up
← Back to reading
News5 min read·2026-10-21DisconfirmAI Editorial

Vicki Boykis: LLMs Are the Compressed Average of Public Code — Without Fundamentals, You Let the Agent Drive

Machine learning engineer Vicki Boykis argues in an interview that LLM output is the statistical average of public code, and people who skip fundamentals cannot recognize this average or maintain control in agent-assisted workflows. She supports this with Git muscle memory, an Anthropic code-comprehension study, and her 'who's driving' metaphor, while acknowledging that not reading code makes sense in some low-context situations.

ImportanceMaterialEvidenceE3 inspectableWrite-upQuick

Original publication time 2026-10-17 08:00 GMT+8

Machine learning engineer Vicki Boykis made a specific judgment in an interview in October 2026: in a world where agents can generate code, explain papers, and complete most intermediate steps, the reason to learn machine learning fundamentals has changed — not because you will do everything by hand in the future, but because you need to judge whether the agent is doing things correctly and when to stop it.

Her core mechanism is this: LLM training data is primarily public code, and public code accounts for roughly only twenty percent of the world's software output. The internal code that large companies run for distributed workloads, the architecture decisions refined over years — she believes these are most likely not in the training set, though she acknowledges there may be exceptions. So model output is 'the compressed average of what we think good software should be.' If you lack fundamentals, you cannot recognize this average, and therefore cannot judge when you need to deviate from it.

Vicki used a recurring metaphor: are you driving, or is the agent driving? She described her actual workflow — at Malachyte, a New York startup doing real-time search and personalization for e-commerce, she insists on sketching out complicated features on a whiteboard or paper first, then hand-writing entry-point code, and only then letting the agent fill in details. She requires the agent to show its plan without pushing code, reviews piece by piece, and commits herself. She says doing this is 'very hard,' but it is friction she deliberately creates for herself.

Sign in / Sign up
ReadingResearchRadarInvestment framework

She gave a concrete example of why fundamentals still matter: Git commands. She admits she is not a Git expert, not in the top five to ten percent of users, but says that without muscle memory for git fetch, git rebase, git commit, git push, and git pull, she would not know what the agent did or whether it was correct when it performed these operations for her. With that baseline, the agent makes her five times faster; without it, she can only trust an output she does not understand.

She also cited a study by Anthropic in collaboration with another institute: when reviewing a new codebase, one group only used agents to generate code, while another group generated code and then quizzed the agent to verify understanding — the latter retained more information. Vicki thinks this shows that current agent products are over-designed toward generation, and that people should proactively use them for questioning and synthesis rather than letting them do everything for you.

On the claim that 'taste is the moat,' Vicki's attitude is cautious. She says mastering something does teach you what is good, what to throw away, what to keep, especially in complex systems where software and ML interact — you need to think about trade-offs between speed, transparency, and accuracy, and making those trade-offs requires having built many such systems. But she immediately says 'I don't know,' because she saw posts arguing taste is no longer the moat, then she herself muses: 'I guess taste is like a statistical distributed probability over all the possible outcomes. So we're gonna automate taste soon.' She does not rebut this idea, only admits uncertainty.

Vicki also stated the boundaries of her position. She says some people's work genuinely does not require reading code, 'in some cases maybe it does even make sense.' Her own situation is that recommendation systems and real-time search involve multi-service interactions with high context load, so she must check what the agent did. She also acknowledges that when exploring a completely unfamiliar codebase, she lets the agent explore freely, because 'I don't know anything, go explore' — at that point she accepts being led.

Her advice for newcomers is concrete: do small projects, small enough to finish. Stand up an agent, figure out how to sandbox it correctly, have it give you a daily calendar readout; or use a local small model to generate commit messages. She says good projects teach you something even if they fail, and they move you from 'everyone says this API is good' to 'I used this API, I think it's good or bad.' With opinions, you can choose your next step.

Her final recommendation is not 'learn everything' but 'follow your interests.' She says now more than ever it is worth following your curiosity deeply, because the boring intermediate steps and clerical work can be smoothed over by agents, but if you do a PhD in a subject you literally cannot care about just to avoid being left behind, you will get far less than if you go deep in a direction you genuinely find fascinating. She observes the gap between passionate and non-passionate people is 'night and day' — the former build benchmarks, fine-tune, develop new methods; the latter are just catching up.

It should be noted that this is one practitioner's personal experience and judgment, not a conclusion verified by controlled experiments. Her 'compressed average' argument rests on the estimate that public code accounts for roughly twenty percent of global software output, a figure she qualifies with 'I guess' and 'probably not.' She only described the conclusion of the Anthropic study she cited, without sample size or specific experimental design. These boundaries do not diminish the practical value of her core advice, but readers should treat it as an experienced practitioner's workflow judgment rather than a proven universal law.

Sources

  • Source materialvickiboykis.com↗
Continue researching →