Quotesby GlyphCoding quotes
53 quotes from 24 people
- AI has removed the typing from software engineering & left the system design.
+2more from this blog
- What this means is that model performance isn’t the only thing that matters: the integration between model and harness is where true agent differentiation is found.
- Engineering specializations are disappearing, judgment and agency are more important, and it only takes one or two engineers for previously “impossible” rewrites and migrations to succeed.
+1more from this blog
- When you’re skilled at AI Engineering, your best work won’t be merely implementing a product that someone else spec’ed out.
- AI is fantastic at automating tasks that have verifiable outcomes, which is why we’re seeing amazing strides from coding, mathematical proofs, and workplace productivity is an extension to that.
- Since the end of 2025, it has seemed that the era of devs writing code by hand is over at startups and in Big Tech. AI agents work faster and generate more pull requests (PRs) than devs ever did, and the size of those pull requests is also increasing.
+1more from this blog
- Now, we focus much less on code and instead focus on deciding what to build, designing the architecture, writing the spec, and verifying outputs.
- Both startups are experimenting with how far they can push AI agents to automatically fix bugs and remove tech debt. It’s working better than anyone might’ve expected in the recent past, but not producing code that can be merged without review.
- A novice who vibe codes without understanding software fundamentals can create simple applications, but this often leads to the coding agent making bad tradeoffs in latency, availability, consistency, reliability, maintainability, simplicity, and/or cost.
+1more from this letter
- I can churn out code a hundred times faster. I don’t have the cognitive capacity to stay on top of 100 times the amount of code. So you still need a team of engineers, so you can load balance that cognitive capacity across the team.
+3more from this blog
- I can do way more work as a single engineer than I could without agents.
- It used to be that the discipline was enforced on you by the amount of time it took.
- That’s exactly the problem with coding agents and software: it’s very easy to keep adding new rooms, because the cost of adding those rooms is so much cheaper.
- Every quote from Simon Willison
- And even if you have AIs writing all your code for you, you're still in the position of an engineering manager, and good engineering managers should be able to do the work of those working for them.
- If by 2028 we’ve automated software engineering and the price of compute is 15x higher than it is right now, then it’s going to be much more difficult for you, with no revenue, to compete for compute against the frontier labs.
- Software development is changing, and what is happening in coding is going to be happening in many fields. There are now important areas of work where AI outperforms humans, and yet, AI is far from perfect.
- This significant increase in the automation of coding has been equivalent to dropping many, many more employees into Anthropic, speeding up our overall pace of development.
- This paper points to a future where we get rid of all the software underpinning computers in a traditional sense and just replace it with a gigantic neural network.
- AI will first automate away the things that are easier to form a closed loop learning system on. This is why code and AI research may be accelerated and then displaced quickly - you can have testable closed loop systems so machines can learn and iterate quickly.
+1more from this blog
- In terms of living now and having a visceral feel for it, I think the closest, I would say, is if you’re coding, and you give it a complex task, and you never open the ID, and you’re in some agent manager world, and you see it do it, and how powerful it is.
- AI has crossed the threshold where it can do most of the intelligence work autonomously and leave the judgement to humans.
- With coding, except for that irreducible uncertainty, I think we’ll be there in one or two years.
- Claude Code and friends have conclusively demonstrated that developers will embrace LLMs on the command line, given powerful enough models and the right harness.
+3more from this blog
- I think that’s a waste of a great term, especially since it’s becoming clear likely that most programming will involve some level of AI-assistance in the near future.
- The most impactful event of 2025 happened in February, with the quiet release of Claude Code.
- This turns out to be the big unlock: the latest coding agents against the ~November 2025 frontier models are remarkably effective if you can give them an existing test suite to work against.
- Every quote from Simon Willison
- And I've vibe coded entire ephemeral apps just to find a single bug because why not - code is suddenly free, ephemeral, malleable, discardable after single use. Vibe coding will terraform software and alter job descriptions.
+1more from this blog
- But if history has taught us anything, this is not the end of the developer, it’s the dawn of something new, the renaissance developer.
+1more from this blog
- There’s a reason the fastest-growing AI companies are hiring software engineers as fast as they can.
- As model intelligence accelerates with Gemini 3, we have the opportunity to reimagine the entire developer experience.
+1more from this blog
- Software 1.0 easily automates what you can specify. Software 2.0 easily automates what you can verify.
- Sometimes I describe it as the cable TV of all these AI agents because I’ll have, essentially packaged into one subscription, Codex, Claude, Cognition stuff, anyone’s agents, Grok, all of them will be there.
- 2025 has seen the arrival of agents that can do real cognitive work; writing computer code will never be the same. 2026 will likely see the arrival of systems that can figure out novel insights.
- I think there’s no engineer who, tomorrow, if you magically became 2x more productive, it’s just going to create more things.
+1more from this podcast
- AI is almost certainly going to unlock a massive revolution in knowledge work and code.
+2more from this podcast
- I would guess that sometime in the next 12 to 18 months, we'll reach the point where most of the code that's going toward these efforts is written by AI.
- I'm talking more like: you give it a goal, it can run tests, it can improve things, it can find issues, it writes higher quality code than the average very good person on the team already.
- Every quote from Mark Zuckerberg
- Code will be more of a disposable commodity, with less reuse, and instead generated on the fly for personalized use.
+1more from this blog
- And these models react pretty violently to the addition of a period in a prompt. And so I think there needs to be this idea that you need good old fashioned software engineering, and you need to measure the performance of these things.
- We’ve transitioned from instruction-driven computer coding, which very few people can do, to intention-driven computing, which is connecting with somebody through intention...
- I think software engineering will spawn a new subdiscipline, specializing in applications of AI and wielding the emerging stack effectively, just as “ site reliability engineer ”, “ devops engineer ”, “ data engineer ” and “ analytics engineer ” emerged.
+1more from this essay
- We are observing a once in a generation “shift right” of applied AI, fueled by the emergent capabilities and open source/API availability of Foundation Models. A wide range of AI tasks that used to take 5 years and a research team to accomplish in 2013, now just require API docs and a spare afternoon in 2023.
- Every quote from Shawn Wang (swyx)
