Technical newsletter by Vinoth Govindarajan taking AI agents apart: control loops, memory, orchestration, evaluation and what breaks in production. Recent series walks through the OpenCode architecture end to end.
Why I recommend it: Free to subscribe, over 2,000 readers; written for people who build software, not for beginners. Substack publications can add paid-only posts at any time, so check the top of a post before counting on it.
Technical writing on legacy modernisation, monoliths and microservices, technical debt, cloud migration and where AI coding tools break down on large old codebases.
From the site: Check out all latest posts from vFunction including modernization strategies, cloud migration best practices, and company updates.
Why I recommend it: technical rather than promotional, though vFunction sells modernization software. The pieces on AI assistants meeting million-line codebases are the honest ones.
Yann LeCun's position paper arguing that today's language models are the wrong architecture, and sketching what he thinks should replace them. Free to read.
Why I recommend it: The serious technical case against scaling language models further. Dense, but it is the argument itself rather than a summary of it.
A technical design paper by Alice Poteat (Anthropic, August 2026) setting out how function hooks let plugins extend Claude Code — the event model, composition order, rendering and enterprise controls.
Why I recommend it: Advanced and unapologetically technical. Read it as an example of a clear design document as much as for the AI tooling itself.
Slide deck of advice from working technology architects and engineers: how to open strong, when to ask clarifying questions, what depth is expected at junior vs. senior level, and how to talk through architecture, scaling, and performance.
In plain terms: This slide deck shares advice from working tech professionals on handling technical interviews. Use it to learn how to explain your coding process, tackle tough questions, and tailor your answers for junior or senior roles.
Why I recommend it: Lead with your strongest projects — interviewers dig into whatever you highlight.
