| The next initially seems on quick.ai and is reposted right here with the writer’s permission. |
I’ve spent many years instructing individuals to code, constructing instruments that assist builders work extra successfully, and championing the concept that programming ought to be accessible to everybody. By quick.ai, I’ve helped hundreds of thousands study not simply to make use of AI however to know it deeply sufficient to construct issues that matter.
However these days, I’ve been deeply involved. The AI agent revolution guarantees to make everybody extra productive, but what I’m seeing is one thing totally different: builders abandoning the very practices that result in understanding, mastery, and software program that lasts. When CEOs brag about their groups producing 10,000 strains of AI-written code per day, when junior engineers inform me they’re “vibe-coding” their approach by way of issues with out understanding the options, are we racing towards a future the place nobody understands how something works, and competence craters?
I wanted to speak to somebody who embodies the alternative strategy: somebody whose code continues to run the world many years after he created it. That’s why I referred to as Chris Lattner, cofounder and CEO of Modular AI and creator of LLVM, the Clang compiler, the Swift programming language, and the MLIR compiler infrastructure.
Chris and I chatted on Oct 5, 2025, and he kindly let me document the dialog. I’m glad I did, as a result of it turned out to be considerate and provoking. Try the video for the total interview, or learn on for my abstract of what I realized.
Speaking with Chris Lattner
Chris Lattner builds infrastructure that turns into invisible by way of ubiquity.
Twenty-five years in the past, as a PhD pupil, he created LLVM: probably the most basic system for translating human-written code into directions computer systems can execute. In 2025, LLVM sits on the basis of most main programming languages: the Rust that powers Firefox, the Swift operating in your iPhone, and even Clang, a C++ compiler created by Chris that Google and Apple now use to create their most crucial software program. He describes the Swift programming language he created as “Syntax sugar for LLVM”. Right now it powers your entire iPhone/iPad ecosystem.
While you want one thing to final not simply years however many years, to be versatile sufficient that individuals you’ll by no means meet can construct stuff you by no means imagined on prime of it, you construct it the best way Chris constructed LLVM, Clang, and Swift.
I first met Chris when he arrived at Google in 2017 to assist them with TensorFlow. As a substitute of simply tweaking it, he did what he all the time does: he rebuilt from first ideas. He created MLIR (consider it as LLVM for contemporary {hardware} and AI), after which left Google to create Mojo: a programming language designed to lastly give AI builders the type of basis that would final.
Chris architects programs that develop into the bedrock others construct on for many years, by being a real craftsman. He cares deeply concerning the craft of software program growth.
I instructed Chris about my issues, and the pressures I used to be feeling as each a coder and a CEO:
“All people else world wide is doing this, ‘AGI is across the nook. In case you’re not doing every part with AI, you’re an fool.’ And truthfully, Chris, it does get to me. I query myself… I’m feeling this strain to say, ‘Screw craftsmanship, screw caring.’ We hear VCs say, ‘My founders are telling me they’re getting out 10,000 strains of code a day.’ Are we loopy, Chris? Are we previous males yelling on the clouds, being like, ‘Again in my day, we cared about craftsmanship’? Or what’s occurring?”
Chris instructed me he shares my issues:
“Lots of people are saying, ‘My gosh, tomorrow all programmers are going to get replaced by AGI, and due to this fact we’d as effectively quit and go dwelling. Why are we doing any of this anymore? In case you’re studying the right way to code or taking pleasure in what you’re constructing, then you definately’re not doing it proper.’ That is one thing I’m fairly involved about…
However the query of the day is: how do you construct a system that may truly final greater than six months?”
He confirmed me that the reply to that query is timeless, and really has little or no to do with AI.
Design from First Ideas
Chris’s strategy has all the time been to ask basic questions. “For me, my journey has all the time been about making an attempt to know the basics of what makes one thing work,” he instructed me. “And if you try this, you begin to understand that plenty of the present programs are literally not that nice.”
When Chris began LLVM over Christmas break in 2000, he was asking: what does a compiler infrastructure should be, basically, to help languages that don’t exist but? When he got here into the AI world he was wanting to study the issues I noticed with TensorFlow and different programs. He then zoomed into what AI infrastructure ought to appear to be from the bottom up. Chris defined:
“The rationale that these programs had been basic, scalable, profitable, and didn’t crumble underneath their very own weight is as a result of the structure of these programs truly labored effectively. They had been well-designed, they had been scalable. The those that labored on them had an engineering tradition that they rallied behind as a result of they wished to make them technically glorious.
Within the case of LLVM, for instance, it was by no means designed to help the Rust programming language or Julia and even Swift. However as a result of it was designed and architected for that, you possibly can construct programming languages, Snowflake may go construct a database optimizer—which is actually cool—and a complete bunch of different functions of the know-how got here out of that structure.”
Chris identified that he and I’ve a sure curiosity in frequent: “We prefer to construct issues, and we prefer to construct issues from the basics. We like to know them. We prefer to ask questions.” He has discovered (as have I!) that that is crucial if you’d like your work to matter, and to final.
In fact, constructing issues from the basics doesn’t all the time work. However as Chris mentioned, “if we’re going to make a mistake, let’s make a brand new mistake.” Doing the identical factor as everybody else in the identical approach as everybody else isn’t more likely to do work that issues.
Craftsmanship and Structure
Chris identified that software program engineering isn’t nearly a person churning out code: “Quite a lot of evolving a product isn’t just about getting the outcomes; it’s concerning the workforce understanding the structure of the code.” And in reality it’s not even nearly understanding, however that he’s in search of one thing way more than that. “For individuals to truly give a rattling. For individuals to care about what they’re doing, to be pleased with their work.”
I’ve seen that it’s attainable for groups that care and construct thoughtfully to attain one thing particular. I identified to him that “software program engineering has all the time been about making an attempt to get a product that will get higher and higher, and your potential to work on that product will get higher and higher. Issues get simpler and quicker since you’re constructing higher and higher abstractions and higher and higher understandings in your head.”
Chris agreed. He once more confused the significance of considering long term:
“Basically, with most sorts of software program initiatives, the software program lives for greater than six months or a yr. The sorts of issues I work on, and the sorts of programs you prefer to construct, are issues that you simply proceed to evolve. Have a look at the Linux kernel. The Linux kernel has existed for many years with tons of various individuals engaged on it. That’s made attainable by an architect, Linus, who’s driving consistency, abstractions, and enchancment in a number of totally different instructions. That longevity is made attainable by that architectural focus.”
This sort of deep work doesn’t simply profit the group, however advantages each particular person too. Chris mentioned:
“I believe the query is actually about progress. It’s about you as an engineer. What are you studying? How are you getting higher? How a lot mastery do you develop? Why is it that you simply’re in a position to remedy issues that different individuals can’t?… The those that I see doing rather well of their careers, their lives, and their growth are the individuals which are pushing. They’re not complacent. They’re not simply doing what everyone tells them to do. They’re truly asking arduous questions, and so they need to get higher. So investing in your self, investing in your instruments and methods, and actually pushing arduous to be able to perceive issues at a deeper stage—I believe that’s actually what allows individuals to develop and obtain issues that they possibly didn’t assume had been attainable a number of years earlier than.”
That is what I inform my workforce too. The factor I care most about is whether or not they’re all the time bettering at their potential to unravel these issues.
Dogfooding
However caring deeply and considering architecturally isn’t sufficient for those who’re constructing in a vacuum.
I’m unsure it’s actually attainable to create nice software program for those who’re not utilizing it your self, or working proper subsequent to your customers. When Chris and his workforce had been constructing the Swift language, they needed to construct it in a vacuum of Apple secrecy. He shares:
“The utilizing your personal product piece is actually vital. One of many large issues that brought about the IDE options and plenty of different issues to be an issue with Swift is that we didn’t actually have a person. We had been constructing it, however earlier than we launched, we had one check app that was type of ‘dogfooded’ in air quotes, however probably not. We weren’t truly utilizing it in manufacturing in any respect. And by the point it launched, you possibly can inform. The instruments didn’t work, it was sluggish to compile, crashed on a regular basis, a number of lacking options.”
His new Mojo undertaking is taking a really totally different path:
“With Mojo, we take into account ourselves to be the primary buyer. We now have lots of of 1000’s of strains of Mojo code, and it’s all open supply… That strategy could be very totally different. It’s a product of expertise, but it surely’s additionally a product of constructing Mojo to unravel our personal issues. We’re studying from the previous, taking greatest ideas in.”
The result’s evident. Already at this early stage fashions constructed on Mojo are getting state-of-the-art outcomes. Most of Mojo is written in Mojo. So if one thing isn’t working effectively, they’re the primary ones to note.
We had an analogous aim at quick.ai with our Solveit platform: we wished to succeed in a degree the place most of our employees selected to do most of their work in Solveit, as a result of they most well-liked it. (Certainly, I’m writing this text in Solveit proper now!) Earlier than we reached that time, I usually needed to power myself to make use of Solveit in an effort to expertise first hand the shortcomings of these early variations, in order that I may deeply perceive the problems. Having achieved so, I now recognize how easy every part works much more!
However this sort of deep, experiential understanding is strictly what we threat shedding after we delegate an excessive amount of to AI.
AI, Craftsmanship, and Studying
Chris makes use of AI: “I believe it’s a vital software. I really feel like I get a ten to twenty% enchancment—some actually fancy code completion and autocomplete.” However with Chris’ deal with the significance of expertise and continuous studying and enchancment, I puzzled if heavy AI (and significantly agent) use (“vibe coding”) may negatively affect organizations and people.
Chris: While you’re vibe-coding issues, all of the sudden… one other factor I’ve seen is that individuals say, ‘Okay, effectively possibly it’ll work.’ It’s nearly like a check. You go off and say, ‘Possibly the agentic factor will go crank out some code,’ and also you spend all this time ready on it and training it. Then, it doesn’t work.
Jeremy: It’s like a playing machine, proper? Pull the lever once more, strive once more, simply strive once more.
Chris: Precisely. And once more, I’m not saying the instruments are ineffective or unhealthy, however if you take a step again and also you take a look at the place it’s including worth and the way, I believe there’s slightly bit an excessive amount of enthusiasm of, ‘Properly, when AGI occurs, it’s going to unravel the issue. I’m simply ready and seeing… Right here’s one other facet of it: the nervousness piece. I see plenty of junior engineers popping out of college, and so they’re very apprehensive about whether or not they’ll be capable of get a job. Quite a lot of issues are altering, and I don’t actually know what’s going to occur. However to your level earlier, plenty of them say, ’Okay, effectively, I’m simply going to vibe-code every part,’ as a result of that is ‘productiveness’ in air quotes. I believe that’s additionally a major drawback.
Jeremy: Looks like a profession killer to me.
Chris: …In case you get sucked into, ‘Okay, effectively I want to determine the right way to make this factor make me a 10x programmer,’ it could be a path that doesn’t deliver you to growing in any respect. It might truly imply that you simply’re throwing away your personal time, as a result of we solely have a lot time to reside on this earth. It will possibly find yourself retarding your growth and stopping you from rising and really getting stuff achieved.
At its coronary heart, Chris’s concern is that AI-heavy coding and craftsmanship simply don’t seem like appropriate:
“Software program craftsmanship is the factor that AI code threatens. Not as a result of it’s unimaginable to make use of correctly—once more, I exploit it, and I really feel like I’m doing it effectively as a result of I care so much concerning the high quality of the code. However as a result of it encourages of us to not take the craftsmanship, design, and structure significantly. As a substitute, you simply devolve to getting your bug queue to be shallower and making the signs go away. I believe that’s the factor that I discover regarding.”
“What you need to get to, significantly as your profession evolves, is mastery. That’s the way you type of escape the factor that everyone can do and get extra differentiation… The priority I’ve is that this tradition of, ‘Properly, I’m not even going to attempt to perceive what’s occurring. I’m simply going to spend some tokens, and possibly it’ll be nice.’”
I requested if he had some particular examples the place he’s seen issues go awry.
“I’ve seen a senior engineer, when a bug will get reported, let the agentic loop rip, go spend some tokens, and possibly it’ll give you a bug repair and create a PR. This PR, nonetheless, was fully fallacious. It made the symptom go away, so it ‘fastened’ the bug in air quotes, but it surely was so fallacious that if it had been merged, it might have simply made the product approach worse. You’re changing one bug with a complete bunch of different bugs which are tougher to know, and a ton of code that’s simply within the fallacious place doing the fallacious factor. That’s deeply regarding. The precise concern will not be this explicit engineer as a result of, thankfully, they’re a senior engineer and good sufficient to not simply say, ‘Okay, cross this check, merge.’ We additionally do code overview, which is a vital factor. However the concern I’ve is that this tradition of, ‘Properly, I’m not even going to attempt to perceive what’s occurring. I’m simply going to spend some tokens, and possibly it’ll be nice. Now I don’t have to consider it.’ This can be a enormous concern as a result of plenty of evolving a product isn’t just about getting the outcomes; it’s concerning the workforce understanding the structure of the code. In case you’re delegating data to an AI, and also you’re simply reviewing the code with out fascinated with what you need to obtain, I believe that’s very, very regarding.”
Some of us have instructed me they assume that unit checks are a very good place to have a look at utilizing AI extra closely. Chris urges warning, nonetheless:
“AI is actually nice at writing unit checks. This is among the issues that no person likes to do. It feels tremendous productive to say, ‘Simply crank out a complete bunch of checks,’ and look, I’ve received all this code, superb. However there’s an issue, as a result of unit checks are their very own potential tech debt. The check might not be testing the fitting factor, or they may be testing a element of the factor moderately than the true concept of the factor… And for those who’re utilizing mocking, now you get all these tremendous tightly sure implementation particulars in your checks, which make it very troublesome to vary the structure of your product as issues evolve. Checks are similar to the code in your major software—it’s best to take into consideration them. Additionally, a number of checks take a very long time to run, and they also affect your future growth velocity.”
A part of the issue, Chris famous, is that many individuals are utilizing excessive strains of code written as a statistic to help the concept that AI is making a constructive affect.
“To me, the query will not be how do you get probably the most code. I’m not a CEO bragging concerning the variety of strains of code written by AI; I believe that’s a totally ineffective metric. I don’t measure progress primarily based on the variety of strains of code written. In truth, I see verbose, redundant, not well-factored code as an enormous legal responsibility… The query is: how productive are individuals at getting stuff achieved and making the product higher? That is what I care about.”
Underlying all of those issues is the assumption that AGI is imminent, and due to this fact conventional approaches to software program growth are out of date. Chris has seen this film earlier than. “In 2017, I used to be at Tesla engaged on self-driving automobiles, main the Autopilot software program workforce. I used to be satisfied that in 2020, autonomous automobiles could be in all places and could be solved. It was this determined race to go remedy autonomy… However on the time, no person even knew how arduous that was. However what was within the air was: trillions of {dollars} are at stake, job substitute, reworking transportation… I believe at this time, precisely the identical factor is going on. It’s not about self-driving, though that’s making progress, just a bit bit much less gloriously and instantly than individuals thought. However now it’s about programming.”
Chris thinks that, like all earlier applied sciences, AI progress isn’t truly exponential. “I imagine that progress seems to be like S-curves. Pre-training was a giant deal. It appeared exponential, but it surely truly S-curved out and received flat as issues went on. I believe that we’ve quite a lot of piled-up S-curves which are all driving ahead superb progress, however I at the least haven’t seen that spark.”
The hazard isn’t simply that individuals may be fallacious about AGI’s timeline—it’s what occurs to their careers and codebases whereas they’re ready. “Know-how waves trigger huge hype cycles, overdrama, and overselling,” Chris famous. “Whether or not or not it’s object-oriented programming within the ’80s the place every part’s an object, or the web wave within the 2000s the place every part needs to be on-line in any other case you may’t purchase a shirt or pet food. There’s reality to the know-how, however what finally ends up taking place is issues settle out, and it’s much less dramatic than initially promised. The query is, when issues settle out, the place do you as a programmer stand? Have you ever misplaced years of your personal growth since you’ve been spending it the fallacious approach?”
Chris is cautious to make clear that he’s not anti-AI—removed from it. “I’m a maximalist. I would like AI in all of our lives,” he instructed me. “Nevertheless, the factor I don’t like is the individuals which are making selections as if AGI or ASI had been right here tomorrow… Being paranoid, being anxious, being afraid of residing your life and of constructing a greater world looks like a really foolish and never very pragmatic factor to do.”
Software program Craftsmanship with AI
Chris sees the important thing as understanding the distinction between utilizing AI as a crutch versus utilizing it as a software that enhances your craftsmanship. He finds AI significantly beneficial for exploration and studying:
“It’s superb for studying a codebase you’re not aware of, so it’s nice for discovery. The automation options of AI are tremendous vital. Getting us out of writing boilerplate, getting us out of memorizing APIs, getting us out of trying up that factor from Stack Overflow; I believe that is actually profound. This can be a good use. The factor that I get involved about is for those who go as far as to not care about what you’re trying up on Stack Overflow and why it really works that approach and never studying from it.”
One precept Chris and I share is the crucial significance of tight iteration loops. For Chris, engaged on programs programming, this implies “edit the code, compile, run it, get a check that fails, after which debug it and iterate on that loop… Operating checks ought to take lower than a minute, ideally lower than 30 seconds.” He instructed me that when engaged on Mojo, one of many first priorities was “constructing VS Code help early as a result of with out instruments that allow you to create fast iterations, your whole work goes to be slower, extra annoying, and extra fallacious.”
My background is totally different—I’m a fan of the Smalltalk, Lisp, and APL custom the place you’ve a reside workspace and each line of code manipulates objects in that surroundings. When Chris and I first labored collectively on Swift for TensorFlow, the very first thing I instructed him was “I’m going to wish a pocket book.” Inside per week, he had constructed me full Swift help for Jupyter. I may sort one thing, see the end result instantly, and watch my knowledge remodel step-by-step by way of the method. That is the Brett Victor “Inventing on Precept” fashion of being near what you’re crafting.
If you wish to keep craftsmanship whereas utilizing AI, you want tight iteration loops so you may see what’s taking place. You want a reside workspace the place you (and the AI) are manipulating precise state, not simply writing textual content information.
At quick.ai, we’ve been working to place this philosophy into observe with our Solveit platform. We found a key precept: the AI ought to be capable of see precisely what the human sees, and the human ought to be capable of see precisely what the AI sees always. No separate instruction information, no context home windows that don’t match your precise workspace—the AI is true there with you, supporting you as you’re employed.
This creates what I consider as “a 3rd participant on this dialogue”—beforehand I had a dialog with my pc by way of a REPL, typing instructions and seeing outcomes. Now the AI is in that dialog too, in a position to see my code, my knowledge, my outputs, and my thought course of as I work by way of issues. After I ask “does this align with what we mentioned earlier” or “have we dealt with this edge case,” the AI doesn’t want me to copy-paste context—it’s already there.
One in every of our workforce members, Nate, constructed one thing referred to as ShellSage that demonstrates this superbly. He realized that tmux already reveals every part that’s occurred in your shell session, so he simply added a command that talks to an LLM. That’s it—about 100 strains of code. The LLM can see all of your earlier instructions, questions, and output. By the following day, all of us had been utilizing it continually. One other workforce member, Eric, constructed our Discord Buddy bot utilizing this identical strategy—he didn’t write code in an editor and deploy it. He typed instructions one after the other in a reside image desk, manipulating state instantly. When it labored, he wrapped these steps into capabilities. No deployment, no construct course of—simply iterative refinement of a operating system.
Eric Ries has been writing his new e-book in Solveit and the AI can see precisely what he writes. He asks questions like “does this paragraph align with the mission we said earlier?” or “have we mentioned this case research earlier than?” or “are you able to examine my editor’s notes for feedback on this?” The AI doesn’t want particular directions or context administration—it’s within the trenches with him, watching the work unfold. (I’m writing this text in Solveit proper now, for a similar causes.)
I requested Chris about how he thinks concerning the strategy we’re taking with Solveit: “as an alternative of bringing in a junior engineer that may simply crank out code, you’re bringing in a senior skilled, a senior engineer, an advisor—any person that may truly aid you make higher code and train you issues.”
How Do We Do One thing Significant?
Chris and I each see a bifurcation coming. “It looks like we’re going to have a bifurcation of expertise,” I instructed him, “as a result of individuals who use AI the fallacious approach are going to worsen and worse. And the individuals who use it to study extra and study quicker are going to outpace the pace of progress of AI capabilities as a result of they’re human with the good thing about that… There’s going to be this group of those that have realized helplessness and this possibly smaller group of individuals that everyone’s like, ‘How does this particular person know every part? They’re so good.’”
The ideas that allowed LLVM to final 25 years—structure; understanding; craftsmanship—haven’t modified. “The query is, when issues settle out, the place do you as a programmer stand?” Chris requested. “Have you ever misplaced years of your personal growth since you’ve been spending it the fallacious approach? And now all of the sudden everyone else is far additional forward of you when it comes to having the ability to create productive worth for the world.”
His recommendation is obvious, particularly for these simply beginning out: “If I had been popping out of college, my recommendation could be don’t pursue that path. Notably if everyone is zigging, it’s time to zag. What you need to get to, significantly as your profession evolves, is mastery. So that you might be the senior engineer. So you may truly perceive issues to a depth that different individuals don’t. That’s the way you escape the factor that everyone can do and get extra differentiation.”
The hype will settle. The instruments will enhance. However the query Chris poses stays: “How will we truly add worth to the world? How will we do one thing significant? How will we transfer the world ahead?” For each of us, the reply entails caring deeply about our craft, understanding what we’re constructing, and utilizing AI not as a substitute for considering however as a software to assume extra successfully. If the aim is to construct issues that final, you’re not going to have the ability to outsource that to AI. You’ll want to speculate deeply in your self.