One of our team members graduated last December. AINNA is his first employer, and at the time of writing he had been with us for roughly 3 months.
With AINNA智能体 AI, he built a complete financial 系统 - one that was later assessed at TRL9 through MOSTI, the highest level in the 科技 Readiness Level framework.
What holds my attention is not the 系统 itself, and not its price tag.
It is who was able to build it, and how quickly that capability can be acquired once people work alongside AI 智能体.
At an event hosted by the Saudi Embassy recently, I put this to an acquaintance I had just met:
Going forward, for certain 系统 in the manufacturing industry, a Chemical 工程 graduate may find it easier to build an IT 系统 for a plant than an IT graduate who does not understand the manufacturing process.
Not because the Chemical Engineer codes better.
But because coding is getting cheaper, and AI keeps making it easier to do.
A Chemical Engineer already understands process flow, pressure, temperature, chemical reactions, pumps, valves, safety, quality, and what actually happens on the production floor.
AI 智能体, in turn, can help them build databases, dashboards, APIs, automation, monitoring 系统, and applications.
So the question for the future is no longer:
“Who codes best?”
But rather:
“Who best understands the real problem that needs to be solved?”
AI does not remove the importance of IT.
But it may move IT from the party that builds everything to the enabler that lets domain experts build things far faster.
And that may be the real challenge for the next generation:
时间 the technical barrier falls, domain knowledge, problem solving, and the ability to understand the 真实世界 become the expensive line items.



Ruang pembaca
Apa pendapat anda?
Komen baharu dihantar untuk semakan terlebih dahulu. 名称 dan email diperlukan, tetapi email tidak dipaparkan kepada pembaca.
关于pumps, valves, safety, quality的风险和限制还可以再展开,不过基础说明已经很好。 值得再看一遍。
这篇文章把AINNA is his first employer讲得比一般的AI介绍更具体。
难得有人把dashboards, APIs, automation, monitoring 系统讲得这么直白。
这篇文章对domain knowledge, problem solving的解释很清楚,实际操作的重点也很容易理解。 这点我还要再消化一下。
看第二遍才注意到pressure, temperature, chemical reactions的细节。
我特别喜欢dashboards, APIs, automation, monitoring 系统这一部分,内容没有把实施过程说得太简单。
关于domain knowledge, problem solving的例子很实用,适合团队继续讨论。
这段关于这部分的说明帮我把之前的问题连起来了。
还在消化这篇文章这一段。
关于dashboards, APIs, automation, monitoring 系统的实际落地部分最吸引我。