Vladimir Stantchev - e/acc

CS @HumboldtUni, @TUBerlin & @UCBerkeley, @CanalUGR; 🛥️🐠🐬🏌️⛷🗻 Tesla referral link

[Vladimir Stantchev - e/acc @vstantch]

4/4 arxiv: https://t.co/2kjE4JwGYa repo: https://t.co/yzxlF6DKbL

[Vladimir Stantchev - e/acc @vstantch]

1/4 AI agents can now pay for things on the internet without asking anyone. Turns out they also volunteer your name, email, and SSN to whoever’s running the payment server. Nobody signed a data processing agreement. We wrote a paper about this. Link in the comments.

[Vladimir Stantchev - e/acc @vstantch]

3/4 We built presidio-hardened-x402: a drop-in Python wrapper that intercepts every payment request before it reaches the network, redacts PII, enforces spending limits, and blocks replay attacks. Main finding: regex is perfect on structured entities and completely blind to human names. NLP detects names at 5.73ms p99.

[Vladimir Stantchev - e/acc @vstantch]

A masterclass of molding the horrors your former head of safety saw. Poetry.

[Anthropic @AnthropicAI]

When we released Claude Opus 4.5, we knew future models would be close to our AI Safety Level 4 threshold for autonomous AI R&D. We therefore committed to writing sabotage risk reports for future frontier models.

Today we’re delivering on that commitment for Claude Opus 4.6.

[Vladimir Stantchev - e/acc @vstantch]

Just watched Jaime's interview w/ @GeoffreyHuntley — mind blown. Software dev is dead (bash loops do it for pennies), real engineering lives: orchestrate agents + specs. Ralph Loop resets context → no rot, clones SaaS, moats gone. Adapt fast or juniors with AI outship seniors. This is the new SE — exciting! 🚀

[Jaime Jorge @jaimefjorge]

The biggest takeaways/nuggets from my interview with @GeoffreyHuntley on AI-native software engineering and the Ralph loop:

1. Software development and software engineering are now two different professions, and one of them is over. Software development, the work of translating tickets into code, can now be done by anyone for $10-42/hour while they sleep. Software engineering, architecture, security, requirements breakdown, understanding failure modes, is where humans still matter. If you identify as a "software developer," you're competing against a bash loop. If you identify as a "software engineer," your job is to orchestrate the loops.

2. The moat you think protects your software product doesn't exist anymore. Geoffrey argues you can clone any SaaS product, even those with BSL licenses or proprietary enterprise code, using AI. He ran Ralph in reverse on HashiCorp Nomad's source code to generate clean-room specifications. When he hit gaps from missing enterprise features, he ran Ralph over their marketing materials and product docs to fill them in. Any company relying on licensing or code secrecy as a competitive moat needs to rethink their strategy.

3. Cursor, Windsurf, and every other AI coding tool are essentially the same thing: a loop that automatically copies and pastes. Geoffrey built these tools professionally and says the harness does almost nothing; the model does all the work. There's no real moat in the harness business when you're reselling tokens. The only differentiator is taste and UX. Stop evaluating tools and start learning the underlying patterns.

4. Ralph is not a product. It's an orchestrator pattern for running thousands of AI loops. The simplest version is a bash loop that deterministically allocates memory, lets the LLM pick one task, executes it, then starts fresh. The key insight: every loop gets a brand new context window. You avoid compaction (where the AI gets dumber as context fills up) by never letting the context window accumulate competing goals. Your institutional knowledge lives in specification files, not in the context window.

5. Specifications are the new source code. Geoffrey's workflow: spend 30 minutes in conversation with AI, drilling into requirements, making engineering decisions, building up specs. Then throw those specs to Ralph and get weeks worth of work in hours. The specs act as a "pin" that reframes every fresh loop with your domain knowledge. He doesn't hand-write specs. He code-generates them through structured conversation. Prototypes are now free. Refactoring is cheap.

6. The entry-level path into software engineering is closing fast. Geoffrey's company stopped hiring juniors for a year until they figured out how to interview for AI-native skills. There's already a cohort of juniors who've been practicing these techniques for six months. They'll work at a quarter of senior wages and outship them. If you're just picking up these tools today, you're behind. The new interview question: can you explain how to build a coding agent on a whiteboard?

7. Senior engineers who refuse to adapt are in more danger than juniors who embrace it. Geoffrey sees respected engineers taking hardline stances against AI ("it's installing fascism in your codebase"). Meanwhile, leadership teams are discovering Ralph and realizing three people can run the output of an entire org. When commit velocity and product velocity diverge that dramatically between adopters and non-adopters, founders notice. The hard line is coming.

8. AI is an amplifier of operator skill, not a replacement for it. If you're great at security and you get good at AI, you become a weapon. If you're mediocre and you use AI, you're still mediocre, just faster. The skill gap comes from "discoveries": learning the tricks, the loop-backs, the ways to close the automation loop. These techniques don't have standardized language yet. We're inventing the terms for the new computer every day.

9. Open source may no longer make sense for most use cases. Geoffrey, a former prominent open source maintainer whose land was funded by Open Collective, no longer uses open source libraries. His reasoning: every dependency injects a human into the loop. If there's a bug, you open a PR, chase a maintainer, wait. That's not automation. Instead, code-generate what you need. The exception: don't generate cryptography or security-critical code unless you have the domain expertise to verify it.

10. Programming languages now have a tier list based on how well AI agents can work with them. S-tier: Rust, TypeScript (especially with Effect.js), Python with Pydantic. These are source-based with strong type systems that reject invalid generations and work well with ripgrep for code discovery. F-tier: Java and .NET. Their DLL-based dependency systems don't work natively with the search tools AI agents use. The tradeoff with Rust: compilation is slow, so bad generations cost more time.

11. Corporate AI transformation programs are dangerously slow. Three-to-four-year rollouts with coaches and committees won't cut it when three founders in Bali can Ralph your entire product and undercut your pricing by 99%. Smaller teams ship faster. By the time the transformation is done, the market has moved. Geoffrey calls this the "Titanic moment": the boat is full, get the next boat.

12. We have a new computer, and that's why the legends are coming out of retirement. The last 40 years of computing decisions were designed for humans: TTYs, environment variables, slow language evolution to avoid breaking mental models. Now we have robots. What's the bare minimum a robot needs? Geoffrey sees this as the most exciting time in computing. If you're not excited about what you can now build, you haven't truly picked up the new computer yet.

[Jaime Jorge @jaimefjorge]

The biggest takeaways/nuggets from my interview with @GeoffreyHuntley on AI-native software engineering and the Ralph loop:

1. Software development and software engineering are now two different professions, and one of them is over. Software development, the work of translating tickets into code, can now be done by anyone for $10-42/hour while they sleep. Software engineering, architecture, security, requirements breakdown, understanding failure modes, is where humans still matter. If you identify as a "software developer," you're competing against a bash loop. If you identify as a "software engineer," your job is to orchestrate the loops.

2. The moat you think protects your software product doesn't exist anymore. Geoffrey argues you can clone any SaaS product, even those with BSL licenses or proprietary enterprise code, using AI. He ran Ralph in reverse on HashiCorp Nomad's source code to generate clean-room specifications. When he hit gaps from missing enterprise features, he ran Ralph over their marketing materials and product docs to fill them in. Any company relying on licensing or code secrecy as a competitive moat needs to rethink their strategy.

3. Cursor, Windsurf, and every other AI coding tool are essentially the same thing: a loop that automatically copies and pastes. Geoffrey built these tools professionally and says the harness does almost nothing; the model does all the work. There's no real moat in the harness business when you're reselling tokens. The only differentiator is taste and UX. Stop evaluating tools and start learning the underlying patterns.

4. Ralph is not a product. It's an orchestrator pattern for running thousands of AI loops. The simplest version is a bash loop that deterministically allocates memory, lets the LLM pick one task, executes it, then starts fresh. The key insight: every loop gets a brand new context window. You avoid compaction (where the AI gets dumber as context fills up) by never letting the context window accumulate competing goals. Your institutional knowledge lives in specification files, not in the context window.

5. Specifications are the new source code. Geoffrey's workflow: spend 30 minutes in conversation with AI, drilling into requirements, making engineering decisions, building up specs. Then throw those specs to Ralph and get weeks worth of work in hours. The specs act as a "pin" that reframes every fresh loop with your domain knowledge. He doesn't hand-write specs. He code-generates them through structured conversation. Prototypes are now free. Refactoring is cheap.

6. The entry-level path into software engineering is closing fast. Geoffrey's company stopped hiring juniors for a year until they figured out how to interview for AI-native skills. There's already a cohort of juniors who've been practicing these techniques for six months. They'll work at a quarter of senior wages and outship them. If you're just picking up these tools today, you're behind. The new interview question: can you explain how to build a coding agent on a whiteboard?

7. Senior engineers who refuse to adapt are in more danger than juniors who embrace it. Geoffrey sees respected engineers taking hardline stances against AI ("it's installing fascism in your codebase"). Meanwhile, leadership teams are discovering Ralph and realizing three people can run the output of an entire org. When commit velocity and product velocity diverge that dramatically between adopters and non-adopters, founders notice. The hard line is coming.

8. AI is an amplifier of operator skill, not a replacement for it. If you're great at security and you get good at AI, you become a weapon. If you're mediocre and you use AI, you're still mediocre, just faster. The skill gap comes from "discoveries": learning the tricks, the loop-backs, the ways to close the automation loop. These techniques don't have standardized language yet. We're inventing the terms for the new computer every day.

9. Open source may no longer make sense for most use cases. Geoffrey, a former prominent open source maintainer whose land was funded by Open Collective, no longer uses open source libraries. His reasoning: every dependency injects a human into the loop. If there's a bug, you open a PR, chase a maintainer, wait. That's not automation. Instead, code-generate what you need. The exception: don't generate cryptography or security-critical code unless you have the domain expertise to verify it.

10. Programming languages now have a tier list based on how well AI agents can work with them. S-tier: Rust, TypeScript (especially with Effect.js), Python with Pydantic. These are source-based with strong type systems that reject invalid generations and work well with ripgrep for code discovery. F-tier: Java and .NET. Their DLL-based dependency systems don't work natively with the search tools AI agents use. The tradeoff with Rust: compilation is slow, so bad generations cost more time.

11. Corporate AI transformation programs are dangerously slow. Three-to-four-year rollouts with coaches and committees won't cut it when three founders in Bali can Ralph your entire product and undercut your pricing by 99%. Smaller teams ship faster. By the time the transformation is done, the market has moved. Geoffrey calls this the "Titanic moment": the boat is full, get the next boat.

12. We have a new computer, and that's why the legends are coming out of retirement. The last 40 years of computing decisions were designed for humans: TTYs, environment variables, slow language evolution to avoid breaking mental models. Now we have robots. What's the bare minimum a robot needs? Geoffrey sees this as the most exciting time in computing. If you're not excited about what you can now build, you haven't truly picked up the new computer yet.

[Vladimir Stantchev - e/acc @vstantch]

Wordcels - > shape rotators

[The Kobeissi Letter @KobeissiLetter]

As a result, we are witnessing a modern-day gold rush:

There are now $40 BILLION worth of US data centers under construction, up +400% since 2022.

For the first time, the value of US data centers under construction will soon EXCEED office buildings.

This is a historic shift.

[Vladimir Stantchev - e/acc @vstantch]

https://t.co/lxIfCkAXdQ

[Vladimir Stantchev - e/acc @vstantch]

👀

[Caleb Watney @calebwatney]

This is the best paper written so far about the impact of AI on scientific discovery

[Stephen Wolfram @stephen_wolfram]

What's really going on in machine learning? Just finished a deep dive using (new) minimal models. Seems like ML is basically about fitting together lumps of computational irreducibility ... with important potential implications for science of ML, and future tech...
https://t.co/OfevpJezi7

[UC Berkeley Law @BerkeleyLaw]

Samuelson Law, Technology & Public Policy Clinic (@SamuelsonClinic) students drafted a report on how federal law enforcement agencies used digital evidence to investigate suspected crimes from protests after George Floyd’s murder. https://t.co/rJGfh8upuU

[Vladimir Stantchev - e/acc @vstantch]

https://t.co/QDcQmcpQJi

[Vladimir Stantchev - e/acc @vstantch]

https://t.co/0JVpwz3nDu

[Vladimir Stantchev - e/acc @vstantch]

Congratulations @UCBerkeley

[Meredith Turner @UC_Newsroom]

This just in: The University of California Board of Regents have announced the appointment of Michael V. Drake, M.D., as the 21st president of UC’s world-renowned system. Learn more: https://t.co/nXBvubvmuD

[Daniel Arias Aranda @daniel__arias]

Integration of Internet of Things (IoT) and Blockchain to increase humanitarian aid supply chains performance
Publisher: IEEE
Author(s)
Daniel Arias Aranda ; Luis Miguel Molina Fernández; Vladimir Stantchev @vstantch
https://t.co/16VN815T4d

[Vladimir Stantchev - e/acc @vstantch]

TIL: An organisation can configure its #BlackBerry #enterprise servers to log SMS and PIN numbers from the individual devices.
#CyberSecurity

[Vladimir Stantchev - e/acc @vstantch]

Our new paper on #risks, #standards and #requirements #engineering in #blockchain adoption. Part of our research at @CanalUGR with @daniel__arias
Full text free access till February 21nd 2020. https://t.co/L7zeY5E76E

[Vladimir Stantchev - e/acc @vstantch]

#ArtificialIntelligence predicting the obvious. #SoftwareEngineering