Phips Peter retweeted
A brief history of AI Coding since Nov 2025:
Nov 2025: Opus 4.5 releases, OpenClaw gets built
Dec 2025: community agrees that models get good enough to handle 95% of coding tasks
Jan 2026: Ralph loops get popular, early efforts on loops/orchestration
Feb: Everyone feels knackered, too much strategic decision-making, fears around cognitive debt begin
Mar: Skills explosion as community converges around easy-to-share processes (superpowers already ahead of the game here)
Apr: most SOTA devs haven't written a line of code in months
May: "The unreasonable effectiveness of HTML" - more interest in richer review surfaces
Jun: "Loop Engineering" wins vaguepost of the year, signals more hype around process
Jul: Every talk in every conference becomes "here is my software factory"
Aug: Opus 5 speaks incomprehensibly, interest in ASD-STE100 peaks
Sep: Grok Bot gets popular, more interest in long-running "manager" threads which retain context and delegate work
Oct: The promised speed gains haven't materialised, "dark factory" feels a long way off still
Nov: No-slop manifesto releases, reading the code still appears essential
TL;DR: no-one is writing code anymore, and we are still figuring out what that means
Phips Peter retweeted
Smith and Montesquieu thought that markets and commerce made us better: that they create an incentive to pursue self-improvement and to create things of value for others. In the positive AI visions, where the labor of humans is made redundant, I find myself wondering how we fare in the presumptive absence of these incentive gradients. Perhaps we are released to a life of freedom, where we can study Mozart and read Dickens, but that still seems complicated: both Mozart and Dickens were themselves deeply commercially-motivated in the production of their work, as were most of the great artists through human history. If the premise is that nobody will need to work or produce, how confident are we that we actually get the next Mozart and Dickens? The relevant question is not the partial equilibrium of whether one individual can pursue a life of enlightened leisure, but the general equilibrium of what form a society as a whole will take on.
One could maybe invoke Periclean Athens or the aristocratic gentleman scientists of Victorian England as a counterpoint. While these individuals were perhaps not motivated by commercial considerations, they were embedded in wider societies shaped by commerce, attendant betterment, and trade: Byron was himself upper class, but he was also surrounded by and writing for an educated bourgeois audience. So we’re back to the equilibrium question. Furthermore, even these individuals were surely motivated by a sense of high-stakes and consequential agency: if they did not apply themselves to their labors, they presumably believed that the work would not otherwise exist. Thucydides was addressing pressing military matters.
So I would like to read more optimistic cases from AI proponents about what a society (vs individual life) looks like if everything goes well: what people do, why they do it, whether humans achieve excellence (and in which domains), and which historical groups we should look to as relevant precedent.
One can perhaps imagine that humans will turn out to have a strong preference for work created by other humans. This may work in certain domains (ceramics?), but for how many will it actually apply? (I’m told that much of what is sold on indie crafts websites is now in fact manufactured in China.) It’s hard to see how this human preference, even if strong, would, for example, save scholarship.
Another idea would be to accept that nobody will become Einstein or Mozart or Byron, and that human excellence as such diminishes, but that there are compensatory benefits (planet brains and Dyson swarms?).
I believe that we can satisfy individual desires, but to what extent will we cultivate behavior worthy of admiration? Will a post-scarcity society mold capable and ambitious people? Which institutions will sustain them and which responsibilities will they have? I’d like to hear more of the equilibrium for the maximalist case spelled out.
Phips Peter retweeted
Introducing Motherload — import data files from TypeScript with full type information
Powered by TypeScript 7.1's content mappers (now in beta)
.md
.toml
.yaml
.csv / .tsv
.jsonc / .json5
.txt
.env
Phips Peter retweeted
Content mappers in TS 7.1 are an absolute game changer
It’s plugins for TypeScript: a way to dynamically compute a static type signature for external file types (.vue, .md, etc) and integrate them directly into tsc compilation
TypeScript 7.1 Beta is now available! Now with a preview API, content mapper support, new features, and some great optimizations. Give it a try and give us some feedback! devblogs.microsoft.com/types…
Phips Peter retweeted
At @asana our products reflect how AI is a part of how entire teams execute, not just individual productivity.
Excited to dig into this at our upcoming Work Innovation Summit, alongside customers like @Aetna, @FedEx, and @databricks who are using AI across cross-functional teams to move work forward.
Plus, there will be live demos and hands-on workshops with Asana experts - including many of the talented R&D folks that helped build these products. See you there!
Is there a way in the @ChatGPT Codex desktop app to browse files in the project and comment on them to start the task? Basically I want the review UX all the time.
1
62
Phips Peter retweeted
Today, Agentic Work Management is live. It also happens to land almost exactly one year after I joined @Asana, which feels fitting because so much of what we’ve been building toward is now in customers’ hands. Over the past year, we’ve accelerated our product roadmap, welcomed @StackAI to Asana, and are now bringing a new multi-product platform to market.
Agentic Work Management gives people and AI one operating system, built around a simple product belief: AI Teammates become more useful when they work with the whole team. Multiple people can guide the same Teammate, the Work Graph gives it the context of the organization and the history of how work gets done, and shared memory carries decisions forward. Governance keeps that work bounded and auditable.
Take the Executive Reporter, one of more than 30 new prebuilt AI Teammates. Instead of handing you a report and stopping, it pulls live portfolio data so the story stays current, assembles QBRs and board-ready briefs, tracks progress against goals, and flags risks before they become surprises.
Starting today, AI Teammates and Asana Dash are included for every paid Asana customer.
I couldn’t be prouder of the team that brought this to life and grateful to the customers who helped us shape it. I’m excited to see how you put these products to work, what you teach us, and what we build next.
We’ll be demonstrating Agentic Work Management and sharing practical customer blueprints at Work Innovation Summit New York on October 14. Hope to see you there.
Phips Peter retweeted
Request to harnesses:
I love that you now send "Accept: text/markdown`. Next thing is: Put the programming language you prefer into the Accept-Language header.
Accept-Language: "en-us, python"
So, I don't have to feed you the TS examples when you're looking for python.
Phips Peter retweeted
Wrote this a few months ago, and folks seem to be rediscovering it and reposting it again
Still stand by it - nothing has changed about this framing, and my fear for juniors
Tactical vs Strategic Programming, and why I'm nervous for juniors:
Good programming involves a mix of tactical and strategic decision-making:
- Tactical: on the ground, short-term. The soldier doing the fighting.
- Strategic: high-view, long-term. The general planning the war.
You need to be a tactician to write good code. To choose the right syntax. To figure out the file structure. To figure out how best to test your changes.
But you need to be a strategist to build code that lasts. To design the architecture. To automate away problems. To think beyond today.
Agents have eaten the tactical part of programming. When you can pay below minimum wage for code, there's no point going into the trenches yourself.
But AI cannot code strategically. Agents need someone at the top of the pyramid to tell them what to do. They need oversight.
So, a developer's day-to-day job has become 100% strategy. Long-term thinking, all the time. (maybe this is why I'm so tired all the time now)
If you identify as a tactical programmer - a code monkey - then you are out of luck. The job has changed.
Personally, I like it. I always preferred thinking strategically about code. If you asked me what my job was about, I'd say 'building apps', not 'writing code'.
But what makes me nervous is that we've pulled down the only bridge that brought juniors into the industry.
We used to train juniors like this:
1. Give them only tactical tasks
2. Let them build up their strategic experience slowly
Eventually, they are a good enough strategist that they are no longer a junior.
But what happens when all tactical code is written by AI? What is the point of a junior?
We obviously need juniors. We need new lifeblood coming into the industry. We need to leave paths open for extraordinary hires to enrich our companies.
But how do we train them? How do you train strategic thinking?
These are the questions I'm thinking about. I'd love to know your thoughts.
Phips Peter retweeted
Tactical vs Strategic Programming, and why I'm nervous for juniors:
Good programming involves a mix of tactical and strategic decision-making:
- Tactical: on the ground, short-term. The soldier doing the fighting.
- Strategic: high-view, long-term. The general planning the war.
You need to be a tactician to write good code. To choose the right syntax. To figure out the file structure. To figure out how best to test your changes.
But you need to be a strategist to build code that lasts. To design the architecture. To automate away problems. To think beyond today.
Agents have eaten the tactical part of programming. When you can pay below minimum wage for code, there's no point going into the trenches yourself.
But AI cannot code strategically. Agents need someone at the top of the pyramid to tell them what to do. They need oversight.
So, a developer's day-to-day job has become 100% strategy. Long-term thinking, all the time. (maybe this is why I'm so tired all the time now)
If you identify as a tactical programmer - a code monkey - then you are out of luck. The job has changed.
Personally, I like it. I always preferred thinking strategically about code. If you asked me what my job was about, I'd say 'building apps', not 'writing code'.
But what makes me nervous is that we've pulled down the only bridge that brought juniors into the industry.
We used to train juniors like this:
1. Give them only tactical tasks
2. Let them build up their strategic experience slowly
Eventually, they are a good enough strategist that they are no longer a junior.
But what happens when all tactical code is written by AI? What is the point of a junior?
We obviously need juniors. We need new lifeblood coming into the industry. We need to leave paths open for extraordinary hires to enrich our companies.
But how do we train them? How do you train strategic thinking?
These are the questions I'm thinking about. I'd love to know your thoughts.
Phips Peter retweeted
Good post on what the applied AI strategy looks like at scale. It’s clear that there’s a wide gap between the AI models and the underlying workflows of an enterprise, which leaves a ton of opportunity for applied AI companies.
“The world doesn’t just want raw models and agents; it wants problems resolved and outcomes achieved. The premium will sit with the companies that can diffuse this intelligence through every aspect of civilization, converting raw tokens into real world outcomes, transforming industries, and creating economies in the process.”
This requires understanding the context, driving the change management, having a harness that can route to various models, connecting to the critical business systems in that vertical, solving the UX challenges of connecting users to agents in the right way in a workflow, understanding the evals in the space, and so on.
That’s a ton of value that goes beyond just the model intelligence itself. And there’s a window of opportunity right now to build the defining companies that can bring intelligence to the critical domains in an enterprise.
Phips Peter retweeted
Friction is what builds taste and mastery. The tools that remove it also remove what made us good enough to use them well.
Worth reading if you're leading teams or are an early-career engineer: larsfaye.com/articles/ai-cod…
Phips Peter retweeted
I'M SUPER EXCITED TO BE REUNITED WITH CLARE AND GALEN!
Our new podcast, "Still Counting", is launching soon.
🎧BIG NEWS! We're having a sequel. 🎧
Still Counting with me, @NateSilver538 and @galendruke is coming to you weekly starting Sept 9th in partnership w/@CrookedMedia
Subscribe wherever you get your podcasts! youtube.com/@StillCountingPo…
Phips Peter retweeted
🎧BIG NEWS! We're having a sequel. 🎧
Still Counting with me, @NateSilver538 and @galendruke is coming to you weekly starting Sept 9th in partnership w/@CrookedMedia
Subscribe wherever you get your podcasts! youtube.com/@StillCountingPo…
Phips Peter retweeted
Biggest problem in Agentic Eng now are classic boring, important and excrutiating problems: auth, integrations, and getting in the real human workflow to meet users where they are.
Model intelligence nowhere even close to being on that list.
Phips Peter retweeted
Technical debt used to be something you just had to live with in a sufficiently large codebase. No longer.
Phips Peter retweeted
Replying to @VicVijayakumar
It’s what I thought at first.
But they’ve been doing this migration (mostly by hand) since 2024. Migrated the top 25% of tests (frequent / important ones.) The rest were very low ROI, went to bottom of migrations pile
They would have prob finished in 5 years, yes
























