Search
115 results
People
Said and published
-
AI will increasingly produce mathematical proofs, just as it already writes most code.
Difficult proofs will now be built with AI, just as most code will be written with AI.
-
WebAssembly will play a huge role in the future of the web as more code goes native.
As more code goes native, I expect WebAssembly to play a huge role in the future of the web.
-
This is so useful. pushing to add this to codex as well.
-
Echoes of OpenAI renaming the Codex desktop app to "ChatGPT" here - everyone's racing to establish themselves as a general agent now
-
“A local, agent-first store that links the written intent behind a code change to its VCS commit and to stakeholder systems such as Jira, Confluence and Linear.” ❤️
-
guys, @anydesk is awesome. running my macmini m1 as codex remote.
-
Merging should deploy: you should have to stop the train to keep merged code out of production, not push it to get there.
As soon as you merge, it should be going out. You like you should have to stop the train to make your code not go into production as soon as you've merged.
-
he vibe coded the recording tool as i sat next to him at the vienna office. sometimes it's alright to have the ceo vibe slop his way to success.
-
Safari 27 supports JSPI, a magic WebAssembly capability for sync native code to suspend on an async 𝙿𝚛𝚘𝚖𝚒𝚜𝚎. On https://t.co/OL0LzGtvAw, libfx uses the built-in browser 𝚏𝚎𝚝𝚌𝚑 stack to make API calls. As more…
-
Projects have changed not only how I interact with Claude but how I code. I stopped managing sessions. I just send thoughts as they come, Claude splits them into threads, and the project remembers how I work. It's where…
-
It will take a generation for new software to replace old software, and people will still be employed writing code in 10 years.
It’ll take a generation for the “new software” to replace the “old software”. Just like there are people happily employed as ASP developers today, there will be people employed to write code in 10 years.
-
Code quality still matters even as LLMs make writing code much faster.
But for everything else, code quality still matters tremendously.
-
Codex — OpenAI
I have to admit that I still primarily alternate between Codex and Claude Code as my daily drivers, for now
-
Claude Code — Anthropic
I have to admit that I still primarily alternate between Codex and Claude Code as my daily drivers, for now
-
Using Local Coding Agents
-
Nobody has found keeping specs and code in sync worth the upkeep; the code stays the source of truth.
I don't think anyone found it useful enough to like maintain a system to keep the specs and the code in sync versus just using the code as the source of truth always.
-
I've been scratching my head trying to think how to package assets for my #lispGameJam project, I really REALLY wanted to be able to inline assets as raw hex code, like I normally do for uxn projects, not have to read…
-
Clean Code — Robert C. Martin
Clean Code is another standard recommendation, but that one wasn't for me. There are useful design principles in there worth studying, but the book as a whole is too narrow and a bit too dogmatic for my taste. Your…
-
Bad code is kudzu
-
Codex-maxxing
-
Paradigms of Artificial Intelligence Programming — Peter Norvig
…described in this book probably won't land you a job today. But reading the code examples will transform how you think about source code. The book shines when it comes to code comments, a topic that I've never seen…
-
RE: https://social.tupo.space/@joshua/117174153454890194 My current AI-code policy is that I will always use the best model I can access, as long as it's practically able to do the job. Right now, as far as I know,…
-
AI should be used as a failure machine that tests many ideas cheaply, not as a way to build one idea faster.
the way we should be using AI is as a testing machine, a failure machine, and a way to vibe code, cloud code, but but build build the, you know, the the lowest possible cycled version of your product that you can get…
-
Code review as a review mechanism depends on reviewers being able to infer effort from reading code, and AI-agent-generated code erases that signal.
the reviewer is the principal, the contributor is the agent, and code review only worked because the reviewer could cheaply infer effort from reading the code. Agents collapse that signal.
-
The specific rules taught as clean code are simply bad programming practices, and they get worse when you apply them together.
If you look at those things, they're kind of just bad programming practices. I I don't really know how else to say them. They don't mesh well when you put them together.
-
AI programming : are you angry yet?
-
nobody should patronize those who newly have opinions about third party evaluators. non-experts forming opinions fast is part of the american tradition. the constitution itself was, in a very important sense, vibe coded…
-
A plan that spells out every line of code to change gives you no leverage: it costs as long to read as the pull request, so you end up skimming it and reading the code twice.
And the plan doc, what was bad about it is it didn't give you leverage. The plan was every single line of code that was going to change like in diff blocks and like all the new stuff to write. And so like people would…
-
AI-written prose is an inferior read because a model emits a statistical average -- code's audience is a machine, writing's audience is people.
The reason for this hardline stance is that we believe in the value of human thought and experience, as told by people with first-hand knowledge. It’s also about the audience: The “audience” for AI-written code is…
-
you can do the same thing with open models as well. plan cheaply with claude code, and then execute CHEAPly with open models. it runs.
-
Consistent with what I found with Qwen3.6 a while back: Claude Code uses 2-3x as many tokens than (many) other harnesses at similar success rate. - Unoptimized? - Buggy? - Deliberate (coz that helps it in more…
-
As AI makes coding easy for everyone, the ability to code stops being a meaningful edge for entrepreneurs.
Indie entrepreneurs need to stack every advantage they have, and increasingly "coding" won't be the advantage it once was.
-
I made this floating-scrollbar #CSS demo as the result of a discussion we had in today’s Front-End Study Hall: https://codepen.io/editor/meyerweb/pen/01a0b0bd-0100-750d-8c24-745f6318896d I don’t know if it’s actually a…
-
As AI writes more of the code, an engineer's job shifts away from expressing logic in a language and towards articulating high-level trade-offs.
Maybe as AI writes more and more code of our code, it's less about like the details of how you express logic in a particular programming language and much more about those kinds of high-level trade-offs.
-
"As Code"
-
Structure and Interpretation of Computer Programs — Harold Abelson
…about the power of wishful thinking when coding. SICP uses wishful thinking as a design tool: write code as if the abstraction already existed. Pretend. Then, once the ideal abstraction has taken shape, you go ahead…
-
Chatting Alone — Alex Martsinovich
Martsinovich argues, via code snippets, that there is no such thing as a "conversation" with a chatbot. The AI is born anew every time it speaks, and it simply reads the dialogue so far and then tries to write the next…
-
The real shift Kubernetes made was from infrastructure as code to infrastructure as data: you declare the object and control loops reconcile it, instead of running a program.
we went from infrastructure is code to infrastructure is data and infrastructure is code is like if this do that um bring in this module for loops all this stuff and Kubernetes is like no no no you have to specify…
-
Cheating tools have pushed Google back to in-person interviews, where somebody watches you code and you cannot cheat your way through it.
I think Google has pretty much gone to on-sites at this point, back to the traditional whiteboard format. And they'll let you code on a laptop if you want to, as well, but it's going to be in person. Somebody's going to…
-
Programmers who refuse to use LLMs to code will fall behind those who do.
Writing every line by hand is no longer the norm. Those who refuse to use an LLM will fall behind because they won't be able to produce as much
-
The latest Threat Intelligence report is an absolutely terrifying and important read. As models become more intelligent, without the right safeguards and monitoring they also become more dangerous. Many capabilities are…
-
VS Code — Microsoft
I use VS Code as my main code editor for both; my daily work and recording courses and videos.
-
Agentic code search has recall that falls as a codebase grows, so the agent does not find the code it needs -- and which search tool you give it barely matters.
You can give it a Bash tool so it can ripgrep its way through the codebase. You can give it some queryable codebase index, an LSP server, a vector database. In the end it doesn't matter much. The bigger the codebase,…
-
in which more paths are charted towards code independence
-
Visual Studio Code — Microsoft
I use VS Code as my primary editor mainly because it’s more modern, highly configurable, and lightweight in comparison to other Electron-based editors such as Atom.
-
…* between languages, but also between mediums. sketch <> figma design <> code <> image also, they do an inverted form of lossy compression: input + priors = input inflated with understanding of the world we're so…
-
Developers who defined the job as being the only person who could write code have just watched the only thing they were good at get commoditised.
All you had to do was write code and you were safe. And you probably made more money than everybody and you were fine with that. Now you got caught. The only thing you were good at is now been commoditized.
-
Write testable code by writing generic code
-
Hand-optimizing hot spots barely matters any more, because the libraries are already fast and CPUs are extremely good at running bad code quickly; what is left is architecture.
One of the reasons that you don't see hotspot optimization as a thing that really matters that much anymore and one of the reasons I advise that architecture and and not making bad decisions is much more important is…
-
The joy of a programmer is to type the code himself; promoting yourself out of that makes you a project manager of a murder of AI crows.
I have been hyper accelerated as a programmer. It's a different kind of programmer, but it still has the same affinity to aesthetics, at least when I'm producing Ruby code.
-
A language can keep changing without a Python-2-to-3 break, as long as code written under the old and the new rules can be mixed freely in one program.
Really the big idea is to say we want the old code to continue working but we still want to change the language. And so the the difference from other kinds of versions of languages I mean Python 2 version Python 3 comes…
-
Introduction to Demo Time – Use Visual Studio Code as your presentation tool
-
Redefining the engineer's job as building guardrails is not novel — it is the same problem as making a junior engineer effective, which we never solved either.
The thing that I find interesting is that's not novel. This has been the thing we've always been trying to do forever. How do we get a junior engineer to ship code safely without breaking stuff? Right? How do we make…
-
…the common pattern: • A sandboxed target within Docker containers • Inputs: code only (0-day), with patch (1-day scenario) • Tools such as bash, static analyzers, etc. • A grader to eval exploits or captured…
-
A migration must be finished once it is started, because a half-migrated codebase confuses models as much as it confuses people.
always make sure that when you start a migration, you finish the migration.
-
Today in "iPhone apps are already iPad apps", here's Quick Reads for iOS running on iOS 27 as the screen gets wider with zero code changes so far. I really think this will be Apple's differentiator in folding phones.…
-
…Desktop Mainboard AI Max+ 395 - 5090 eGPU running Qwen 3.8 27B for fast tok/s LLM use - sometimes 150+ tok/s - 2x DGX Spark: running Deepseek v4 Flash 0731 - better but slower model - pi 5 for monitoring - Mac…
-
What trips up newcomers to Rust is not the code but the shape of their data.
I think the most tricky thing people run into is how should you put together your data structures? I mean for your code you can mostly do the same things as you can in other languages. I mean that's not entirely true…
-
Let the agents democratize open source
-
We're starting to leave the territory where you'd test an LLM by e.g. "create an svg of pelican on a bicycle". As one idea to generalize it, I was interested what Opus 5 would do if I gave it the first paragraph of the…
-
Dank Mono — Phil Plückthun
I use Dank Mono as a font for VS Code. I also use this font on this website in the blog for code snippets.
-
Per-engineer productivity inevitably declines somewhat as an organization and its codebase grow
It is almost inevitable that per-engineer productivity drops to some extent as an organization and codebase grows, even though it's also nearly-impossible to quantify that effect.
-
My Current AI Dev Workflow
-
Astral Codex Ten — Scott Alexander
That still leaves this as my top Substack or personal blog.
-
Grok @Bot is the hottest new AI product in the world right now. I'm absolutely hooked. It all started a few months ago as a tiny team holed up in a separate part of the office, building from scratch. Four weeks after…
-
Examples in documentation should be compiled and run as tests, so that changing the code breaks the docs instead of quietly outdating them.
…makes all examples into tests. This means that if you change the underlying code now your test fails. And so this means that you can't even you can't forget to update your examples in your…
-
…of this moment for cyber - but using human parallels for what I believe is code is dangerous territory. B) IMO it gets the impact of open source models wrong and is unreasonably dismissive for reasons that are not…
-
Notion — Notion Labs
my current favorite notes app. Can grow and get as complex as you need it to be, but for simple notes, the markdown and code highlight support is fantastic.
-
As AI makes code cheaper to produce, understanding and architectural design become more valuable.
Thus, code is cheaper than ever, but I suspect that insight and good architectural design and understanding, at least for now, will become more valuable than ever.
-
Without good intuition for models, treat 100k tokens on smaller models and 200k on the frontier ones as the line past which the quality of your results is probably already degrading.
But if you don't have good LLM intuition, like 100K for smaller models, 200K for these like really beefy like Codeex and Opus 4.8 models is usually a good like training wheel guideline of like if you pass there, your…
-
Rust's defining experience is that once the code compiles it works — not literally true, but true often enough that people keep saying it.
I think part of what I liked about Rust is this feeling that as you write the code when it compiles it works. I mean this has to be in quotes right because obviously it's possible that there are bugs but this is…
-
Breaking up a monolith takes years rather than months not because the work is hard but because the business keeps adding to it faster than you can pull pieces out.
had we freeze time, that piece of code could be decomposed in a matter of 3 to 6 months. But it took us 2 years to do that because as we peel out a piece of code, the business keep on going forward, right?
-
Consider Knitting
-
TextMate
I use TextMate to code; I don't even really care that it hasn't been updated in a while - it suits my purposes as is.
-
emacs
For writing code, I use emacs and Google's internal distributed build system (a version of which was open sourced as Bazel) and our version control system
-
Compiler mechanisms that force a required optimization to occur, rather than relying on incidental compiler behavior, are a more robust way to write performance-sensitive code.
I'm hopeful this framework will turn out to be a much more robust style for writing performance-sensitive code, especially over time and as compilers evolve.
-
Two people with agents can reach enterprise-grade codebase complexity in weeks -- what took organisations years, and they at least adapted to it as it grew.
And organizations have super high pain tolerance. But human-made enterprise codebases take years to get there. The organization slowly evolves along with the complexity in a demented kind of synergy and learns how to…
-
Prompts are code, .json/.md files are state
-
Advent of Code in C++ Template Metaprogramming
-
The Pragmatic Programmer: From Journeyman to Master — Andrew Hunt and David Thomas
This is about the craft of software development, and thinking about how to produce good code. As the name suggests, it's a very pragmatic and hands-on book. It really helped me on my journey as a software engineer, to…
-
A manager whose own code finishes every project is adding their value rather than multiplying the team’s.
If it’s your code that gets you over the finish line for every project, you aren’t providing multiplicative value for the team, you’re providing the additive value of your work as an engineer.
-
Using Zig to Provide Stack Traces on Kernel Panic for a Bare Bones Operating System
-
The Nature of Code — Daniel Shiffman
…through the math. All done in the Processing language, which is fun and easy to pick up. The reason I like this book so much is probably due to timing. In 2013, I was on the verge of abandoning software development.…
-
Peak programmer has passed: the economic value of writing code by hand has peaked, and Jevons' paradox will not bail every programmer out.
So, I do think it is correct for the average programmer to think maybe we've seen the best of the golden days.
-
Some Silly Z3 Scripts I Wrote
-
Test coverage is a tool for finding untested code and says nothing about how good the tests are.
Test coverage is of little use as a numeric statement of how good your tests are.
-
The programming practices taught as best practice are ruinous for performance and should not be followed.
The ideas underlying the “clean” code methodology are almost all horrible for performance, and you shouldn’t do them.
-
The Venn diagram of developer experience and agent experience is a circle: well-modularised code and good tests help the agents exactly as they help the humans.
…a lot of feedback saying, "Yeah, actually, if you have well-modularized code, that actually makes it easy for the agents to work…
-
This is a super exciting release - Claude Fable 5 is the same underlying model as Mythos but with added safeguards. The benchmarks are great and it's SOTA on everything by a margin but I'll add that *qualitatively*…
-
AI agents can now do real cognitive work, and writing software is permanently changed as a result.
2025 has seen the arrival of agents that can do real cognitive work; writing computer code will never be the same.
-
Claude 3.7 Sonnet — Anthropic
As a Python and JavaScript programmer my favorite models right now are Claude 3.7 Sonnet with thinking turned on, OpenAI’s o3-mini-high and GPT-4o with Code Interpreter (for Python).
-
Async: What is blocking?
-
AI is welcome as a better search engine and a pair programmer that does not drive, but writing the code itself is not something to hand over to it.
I love chiseling my code and the way I use AI is in a separate window. I don't let it drive my code. I've tried that. I've tried the cursors and the wind surfaces and I don't enjoy that way of writing. And one of the…
-
Letting non-programmers build their own unmaintainable software is still a large step forward, because the alternative was a thousand-page requirements document and an eight-year wait.
You look under the underneath though at the code and it was just a horrible unmaintainable mess. But the fact that people could program the programs that they wanted was a a significant step forward as opposed to I'm…
-
Notepad++
I also spend a lot of time in Notepad++, which I use both as a code editor and my note-taking application; my file of ideas is literally just a text file that remains permanently open in a background tab.
-
Structural Lessons in Engineering Management
-
Async/await makes asynchronous code easier to write without healing the split it created, and the divide reappears as soon as you write a higher-order function.
It is better. I will take async-await over bare callbacks or futures any day of the week. But we're lying to ourselves if we think all of our troubles are gone.
-
Publishing the source is not the same as developing in the open, and only the second changes how the work actually goes.
You know, there's open source and there's open development. And and and we were technically open source in the beginning, but it was not open development. We would sort of lob the source code out in this repository and…
-
The idea that AI will decide to kill humanity is a category error: it is math and code, built and controlled by people, not a living thing shaped by evolution.
…kill humanity is a profound category error. AI is not a living being that has been primed by billions of years of evolution to participate in the battle for the survival of the fittest, as animals are, and as we are.…
-
Test suites as classifiers
-
Great list of what the best devs do, such as: • Read the source, docs, error msgs • Simplify problems, write simple code • Get their hands dirty • Write to share & write well • Have beginner's mind & keep learning • Not…
-
NVIDIA's Nsight Graphics GPU flame graphs are shallow and cumbersome to use compared to full-stack profiling tools
They do have flame graphs in Nsight Graphics for GPU workloads, although their flame graphs are currently shallow as it is GPU code only, and onerous to use as I believe it requires an interposer; on the plus side they…
-
Garbage collection is a problem for backends too, not only for embedded code: a collection that lands on an incoming request is a latency spike.
…spike where you it takes much longer to to reply. So that's one of the reasons it can be helpful in in back end as…
-
Facts and Fallacies of Software Engineering — Robert L. Glass
Facts and Fallacies of Software Engineering by Robert L. Glass. In essence, this is a book about an industry that refuses to learn. That was true 25 years ago when this book was published, and it's probably twice as…
-
VS Code and Copilot are loss leaders in an embrace-extend-extinguish play, raising the switching cost until nobody can leave.
Whereas something like Microsoft, they made VS Code as a loss leader. Copilot's probably operating on a loss leader. These things are all getting you so tied into, GitHub, remote workspaces, CI, Copilot, you become this…
-
Coding with LLMs in the summer of 2025 (an update)
-
Writing to files safely is too hard to do with raw syscalls; application code should go through a library or a database.
as an application developer, writing to files safely is hard enough that it should be done via some kind of library and/or database, not by directly making syscalls
-
Writing Solid Code — Steve Maguire
This book had a big impact on me as young software developer. It was the first time I saw in print the principle "bugs that go away by themselves come back by themselves". It's something that I've often repeated to…
-
Dismissing a subject as a waste of time because you never used its details on the job is the wrong way to think, and it is the same mistake people make about learning to code now that AI writes the loops.
I think a lot of the things that people might say that like oh, it was a waste of time to learn this subject cuz I didn't actually use like those details on the job. I think that's a very wrong way to think about it.…
-
Most of the code the world runs on is maintained by hobbyists with an hour or two a month, so any proposal that needs more than that will simply be ignored.
It means that anything you offer must fit in 1h per month. That is it. And if it does not, if it needs more involvement than that, we, as maintainers, will not do it. At all.
-
LLM Knowledge Bases Something I'm finding very useful recently: using LLMs to build personal knowledge bases for various topics of research interest. In this way, a large fraction of my recent token throughput is going…
-
AI will do to software what the cloud did: expand the market massively rather than crush the margins of the incumbent.
So this AI thing will be that right. So if you take coding um what we built with GitHub and VS code in over whatever decades uh suddenly the coding assistant is that big in one year and so that I think is what's going…
-
The metric that matters is engineering velocity, not the share of code AI writes, and at Google AI has raised it by about ten percent.
But the most important metric, and we carefully measure it is, like, how much has our engineering velocity increased as a company due to AI, right? It's tough measure, and we rigorously try to measure it, and our…
-
I am slowly trying to figure out Nix/NixOS. I just realized something I'm very confused by: Is it really the case “pinning’ in NixOS prototypically means “pinning a single version of the entire package repository, and…