Just a few 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 typically 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 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 straightforward to drown in novelty, and simple to confuse widespread experimentation with dependable integration. Groups with the least time, funds, and native assist 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 exhibiting up in apply. It’s straightforward to ship spectacular demos. It’s a lot more durable to make AI-assisted work dependable underneath real-world constraints: measurable high quality, controllable failure modes, clear information 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 apply 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 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 apply. What made the web sturdy was not a single vendor or methodology however a cultural infrastructure: open data 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 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, expertise, and each day apply. 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 instantly all the pieces 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 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 spotted I might need one thing significant to contribute. I don’t take into account myself an AI skilled. I’m discovering my method by means of these modifications similar to many different engineers. However through the years, I had develop 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 method, and I take pleasure in bringing readability to chaos.
That’s what led me to start out engaged on the AI Flower as a pastime undertaking 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, assume 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 needed to publish it so it may assist empower different engineers and IT organizations in the identical method 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 set up 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 data sharing and collaboration can’t be elective. If AI is changing into a part of how we design, construct, function, safe, and govern methods, we want greater than instruments and enthusiasm. Many people work on methods individuals depend on daily. When these methods fail, the influence is actual. That’s why we owe it to the individuals who rely on these methods to do that with care, and why we gained’t get there in isolation. We want the business, globally, to converge on shared requirements for reliable apply.
Concerning 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 attractiveness like, primarily based on practices that ought to already really feel acquainted to engineers. It then helps individuals discover how AI can assist these actions in apply, offering steering on how one can 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 method helps engineers perceive how AI can assist 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 develop into extra abstracted, extra automated, or absorbed into the infrastructure layer. Which means engineers might want to do greater than discover ways to use AI inside at present’s actions. They may also must work with rising approaches corresponding 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 exhibits how each engineering expertise and AI-related expertise evolve over time, and the way a few of them develop into much less seen as work strikes to the next degree of abstraction. Collectively, the AI Flower and the Talent Fossilization Mannequin are supposed to assist engineers keep adaptable as the sector continues to shift.
The primary goal of the AI Flower is to assist engineers discover their method by means of these speedy modifications 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 develop into actually precious, it is going to want the perception, care, and contribution of engineers throughout disciplines, views, and areas.
I genuinely imagine 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 is going to solely be helpful—it is going to solely “bloom”—if the neighborhood assessments 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 a 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.)
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’s extra coming. A core design objective of the AI Flower is to remain secure throughout these shifts by specializing in underlying capabilities relatively than particular methods. I’ll go deeper on that stability precept, together with the Talent Fossilization mannequin, at AI Codecon as properly.
