My full breakdown of some key themes from the event (www.ai.engineer/code) 👇
#ai #genai #trends #aiecode2025

The biggest structural shift? The Builder’s role (Eng & PM)

Old: Writer of Syntax (Human-in-the-loop).
New: Orchestrator of Outcomes (Human-on-the-loop).

When code generation is trivial, value shifts from typing to verifying. The engineer now builds the "harness" and context that the AI runs in.

The Killer App for 2025? "Brownfield" Modernization. 🏭

Forget new apps. The highest ROI is using agents to uplift massive legacy codebases at a scale humans simply can't match.

The new enemy is “Code Slop."
If you only measure velocity, you will drown in low-quality, unmaintainable code.
Smart orgs are shifting metrics from Speed → Rework Rates & Maintainability.

There’s a growing tension: "Vibe Coding" (optimistic speed) vs. Engineering Rigor (reliability) ⚡️
The debate isn't 'can AI code'. It's 'can we trust it?'
Some leaders signaled a critical point of view: You cannot "vibe code" critical systems. You must “earn understanding of the architecture” first.

Above (sky) and below (smartphone in hand) 😛

True - I wasn’t thinking of identities, just patterns. Though I guess once we see the patterns, we’ll get curious about identity, and then run into the issues you mentioned.

.. or what a graph of the public bitcoin ledger would show (though perhaps that exists already?)