A number of years into the AI shift, the hole between engineers is just not expertise. It’s coordination: shared norms and a shared language for the way AI matches into on a regular basis engineering work. Some groups are already getting actual worth. They’ve moved past one-off experiments and began constructing repeatable methods of working with AI. Others haven’t, even when the motivation is there. The reason being usually easy: The price of orientation has exploded. The panorama is saturated with instruments and recommendation, and it’s laborious to know what issues, the place to start out, and what “good” seems to be like when you care about manufacturing realities.
The lacking map
What’s lacking is a shared reference mannequin. Not one other instrument. A map. Which engineering actions can AI responsibly assist? What does high quality imply for these outputs? What modifications when a part of the workflow turns into probabilistic? And what guardrails preserve integration protected, observable, and accountable? With out that map, it’s simple to drown in novelty, and simple to confuse widespread experimentation with dependable integration. Groups with the least time, funds, and native assist pay the very best value, and the hole compounds.
That hole is now seen on the organizational degree. Extra organizations try to show AI into enterprise worth, and the distinction between hype and integration is exhibiting up in follow. It’s simple to ship spectacular demos. It’s a lot tougher to make AI-assisted work dependable below real-world constraints: measurable high quality, controllable failure modes, clear knowledge boundaries, operational possession, and predictable value and latency. That is the place engineering self-discipline issues most. AI doesn’t take away the necessity for it; it amplifies the price of lacking it. The query is how we transfer from scattered experimentation to built-in follow with out burning cycles on instrument churn. To try this at scale, we want shared scaffolding: a public mannequin and shared language for what “good” seems to be like in AI-native engineering.
Now we have seen why this type of shared scaffolding issues earlier than. Within the early web period, promise and noise moved sooner than requirements and shared follow. What made the web sturdy was not a single vendor or methodology however a cultural infrastructure: open information sharing, world collaboration, and shared language that made practices comparable and teachable. AI-native engineering wants the identical type of cultural infrastructure, as a result of integration solely scales when the business can coordinate on what “good” means. AI doesn’t take away the necessity for cautious engineering. Quite the opposite, it punishes the absence of it.
A public scaffold for AI-native engineering
Within the second half of 2025, I started to note rising unease amongst engineers I labored with and mates in IT. There was a transparent sense that AI would change our work in profound methods, however far much less readability on what that truly meant for an individual’s position, abilities, and every day follow. There was no scarcity of trainings, guides, blogs, or instruments, however the extra sources appeared, the tougher it grew to become to guage what was related, what was helpful, and the place to start. It felt overwhelming. How have you learnt which matters actually matter to you when abruptly every little thing is labeled AI? How do you progress from hype to helpful integration?
I used to be feeling a lot of that very same uncertainty myself. I used to be making an attempt to make sense of the shift too, and for some time I believe I used to be ready for a clearer construction to emerge from elsewhere. It was solely when mates began reaching out to me for assist and steering that I noticed I might need one thing significant to contribute. I don’t take into account myself an AI skilled. I’m discovering my approach by means of these modifications similar to many different engineers. However through the years, I had develop into recognized for my work in IT workforce growth, talent and functionality frameworks, and engineering excellence and enablement. I understand how to assist folks navigate complexity in a sensible and sustainable approach, and I take pleasure in bringing readability to chaos.
That’s what led me to start out engaged on the AI Flower as a passion mission in early October 2025, constructing on frameworks and strategies I already had expertise with.
After I started sharing it with mates in IT to assemble suggestions, I noticed how a lot it resonated. It helped them make sense of the complexity round AI, suppose extra clearly about their very own upskilling, and start shaping AI adoption methods of their very own. That’s once I realized this informal experiment held actual worth, and determined I wished to publish it so it may assist empower different engineers and IT organizations in the identical approach it had helped my mates.
With the AI Flower, I’m providing a public scaffold for AI-native engineering work: a shared reference mannequin that helps engineers, groups, and organizations undertake and combine AI sustainably and reliably. It’s meant to steer and manage the dialog round AI-assisted engineering, and to ask focused suggestions on what breaks, what’s lacking, and what “good” ought to imply in actual manufacturing contexts. It’s not meant to be good. It’s meant to be helpful, freely obtainable, open to contribution, and formed by the strongest useful resource our business has: collective intelligence.
Open information sharing and collaboration can’t be optionally available. If AI is changing into a part of how we design, construct, function, safe, and govern programs, we want greater than instruments and enthusiasm. Many people work on programs folks depend on on daily basis. When these programs fail, the affect is actual. That’s why we owe it to the individuals who rely on these programs to do that with care, and why we gained’t get there in isolation. We’d like the business, globally, to converge on shared requirements for reliable follow.
In regards to the AI Flower
The AI Flower maps the core actions that make up engineering work throughout the principle engineering disciplines. For every exercise, it defines what beauty like, based mostly on practices that ought to already really feel acquainted to engineers. It then helps folks discover how AI can assist these actions in follow, offering steering on find out how to start utilizing AI in that work, sharing hyperlinks to helpful studying sources, and outlining the principle dangers, trade-offs, and mitigations.
However the AI panorama is altering shortly. This activity-based strategy helps engineers perceive how AI can assist core engineering duties, the place dangers could come up, and find out how to begin constructing sensible expertise. However by itself, it isn’t sufficient as a long-term mannequin for AI adoption.
As AI capabilities evolve, many engineering actions will develop into extra abstracted, extra automated, or absorbed into the infrastructure layer. Which means engineers might want to do greater than learn to use AI inside at this time’s actions. They may even have to work with rising approaches comparable to context engineering and agentic workflows, that are already reshaping what we take into account core engineering work. An idea I name the Ability Fossilization Mannequin captures that development. It exhibits how each engineering abilities and AI-related abilities evolve over time, and the way a few of them develop into much less seen as work strikes to a better degree of abstraction. Collectively, the AI Flower and the Ability Fossilization Mannequin are supposed to assist engineers keep adaptable as the sphere continues to shift.
The principle function of the AI Flower is to assist engineers discover their approach by means of these speedy modifications and develop with them. Whereas I present content material for every part and exercise, the actual worth lies within the framework and construction itself. To develop into actually invaluable, it should want the perception, care, and contribution of engineers throughout disciplines, views, and areas.
I genuinely imagine the AI Flower, as an open and freely obtainable framework, can function a scaffold for that work. That is my contribution to a altering business. However it should solely be helpful—it should solely “bloom”—if the group checks it, challenges it, and improves it over time.
And if any business can flip open critique and contribution into shared requirements at a worldwide scale, it’s ours, isn’t it?
Be part of me at AI Codecon to be taught extra
If the AI Flower resonates and also you need the total walkthrough, I’ll be presenting it at O’Reilly’s upcoming AI Codecon. (Registration is free and open to all.)
When you’re involved about how shortly AI engineering patterns are evolving, that concern is legitimate. We’ve already seen the middle of gravity shift from advert hoc immediate work, to context engineering, to more and more agentic workflows, and there may be extra coming. A core design aim of the AI Flower is to remain steady throughout these shifts by specializing in underlying capabilities fairly than particular methods. I’ll go deeper on that stability precept, together with the Ability Fossilization mannequin, at AI Codecon as properly.