A number of years into the AI shift, the hole between engineers will not be expertise. It’s coordination: shared norms and a shared language for the way AI suits 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 typically easy: The price of orientation has exploded. The panorama is saturated with instruments and recommendation, and it’s onerous to know what issues, the place to start out, and what “good” appears like when you care about manufacturing realities.
The lacking map
What’s lacking is a shared reference mannequin. Not one other software. A map. Which engineering actions can AI responsibly help? What does high quality imply for these outputs? What adjustments when a part of the workflow turns into probabilistic? And what guardrails maintain integration secure, observable, and accountable? With out that map, it’s straightforward to drown in novelty, and straightforward to confuse widespread experimentation with dependable integration. Groups with the least time, funds, and native help pay the 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 displaying up in follow. It’s straightforward to ship spectacular demos. It’s a lot more durable to make AI-assisted work dependable beneath real-world constraints: measurable high quality, controllable failure modes, clear knowledge boundaries, operational possession, and predictable price 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 software churn. To try this at scale, we want shared scaffolding: a public mannequin and shared language for what “good” appears like in AI-native engineering.
Now we have seen why this sort of shared scaffolding issues earlier than. Within the early web period, promise and noise moved quicker 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 form 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 buddies 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 function, expertise, and every day follow. There was no scarcity of trainings, guides, blogs, or instruments, however the extra sources appeared, the more durable it turned to evaluate 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 out of the blue every 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 attempting to make sense of the shift too, and for some time I feel I used to be ready for a clearer construction to emerge from elsewhere. It was solely when buddies began reaching out to me for assist and steerage 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 means via these adjustments similar to many different engineers. However over time, I had change into identified for my work in IT workforce growth, talent and functionality frameworks, and engineering excellence and enablement. I understand how to assist individuals navigate complexity in a sensible and sustainable means, 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 challenge in early October 2025, constructing on frameworks and strategies I already had expertise with.
After I started sharing it with buddies in IT to assemble suggestions, I noticed how a lot it resonated. It helped them make sense of the complexity round AI, assume extra clearly about their very own upskilling, and start shaping AI adoption methods of their very own. That’s after 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 means it had helped my buddies.
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 arrange 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 excellent. It’s meant to be helpful, freely out there, 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 individuals 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 received’t get there in isolation. We’d like the business, globally, to converge on shared requirements for reliable follow.
Concerning the AI Flower
The AI Flower maps the core actions that make up engineering work throughout the primary 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 individuals discover how AI can help these actions in follow, offering steerage on how one can start utilizing AI in that work, sharing hyperlinks to helpful studying sources, and outlining the primary dangers, trade-offs, and mitigations.
However the AI panorama is altering shortly. This activity-based strategy helps engineers perceive how AI can help core engineering duties, the place dangers might come up, and how one can 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 change into extra abstracted, extra automated, or absorbed into the infrastructure layer. Meaning engineers might want to do greater than learn to use AI inside as we speak’s actions. They may also 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 Talent Fossilization Mannequin captures that development. It reveals how each engineering expertise and AI-related expertise evolve over time, and the way a few of them change into much less seen as work strikes to a better degree of abstraction. Collectively, the AI Flower and the Talent Fossilization Mannequin are supposed to assist engineers keep adaptable as the sphere continues to shift.
The primary function of the AI Flower is to assist engineers discover their means via these speedy adjustments and develop with them. Whereas I present content material for every part and exercise, the true worth lies within the framework and construction itself. To change into actually helpful, it should want the perception, care, and contribution of engineers throughout disciplines, views, and areas.
I genuinely consider the AI Flower, as an open and freely out there 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 neighborhood exams it, challenges it, and improves it over time.
And if any business can flip open critique and contribution into shared requirements at a world scale, it’s ours, isn’t it?
Be a part of me at AI Codecon to study 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.)
For those who’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 reasonably than particular strategies. I’ll go deeper on that stability precept, together with the Talent Fossilization mannequin, at AI Codecon as effectively.
