A PAGE TALKS ABOUT (Ai-ERA: Demystified In A Nutshell)
Tags: webdev, automation, ai, testing
Published: 2024-05-06 05:30:43

**_MY ANALYSIS: WRITING A STORY_**

![My Analysis: Wirting A Story](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/9y1ylxydzlzqpt3pul6g.png)

![Channel Objectives](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/6monpe3dyforran59bmw.png)

![Demystified In A Nutshell](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/z2xsrrxc96bh8cm3r1zn.png)

APAGE TALKS ABOUT column from the @reWireByAutomation channel, the story comes under the category of “Trends” of Channel objectives. This short story, I wanted to present is inspired by my reading, understanding, and analysis of the AI era, which is currently getting ready to become an integral part of life, like other technological eras we have adopted and experienced throughout history.

In simple terms, it’s a human-created machine intelligence that replicates **_five key aspects of human abilities: Writing, Speaking, Vision, Reasoning, and Decision Making._** The theory, concepts, story, and technology are centered around these five components to enhance systems’ intelligence and coherence, thereby improving tasks in a new dimension, whatever you may call it. _**This encapsulates the essence of the AI ERA as I believe it, pursue it, and envision it.**_

Now, the question arises: what is our role in it? Based on what I’ve learned and visualized, it’s a straightforward concept. **_There should be only two roles: Creator and Executor._** While we’ve long understood the significance of the Creator role since the beginning of the Technology Era, the Executor role become even more crucial, placing it on par with the Creator in the AI Era. This is something I strongly believe in, and which drives business at scale.

In this context, the **_Creator_** optimizes available abilities to craft an intelligent system **_(AI Agents / AI Assistants)_** tailored to specific needs. While this presents a challenge, the evolutionary process has already commenced, with tangible results evident. However, there is still a need for further evolution, the implementation of best practices, enhancements, increased intelligence, adherence to AI ethics, and the standardization of AI policies.

The role of the Executor, as I mentioned above regarding its significance, will lead to greater prominence when the element of **_“CREATIVITY”_** is incorporated into the journey. Executors must embrace a new dimension, building upon traditional/legacy methods, and harness **_AI Assistants / AI Agents in a manner that enhances productivity and delivers tangible business growth outcomes._**

In addition, I perceive that Executor enablers are more creative in leveraging AI agents / AI assistants, thereby enhancing the journey at scale like never before.

So, in the standard process, I would see the Executor Journey comprised of **Three phases: Discover, Implement, and Progress**

**Discover:** Conduct a business purpose analysis and develop a creative approach to address the need, select the appropriate AI Assistant / AI Agent, and determine the most effective ways to utilize them.

**Implement**: Train, integrate, and utilize AI Assistants in the right manner.

**Progress:** Continuously monitor the outcomes, align with objectives, identify gaps, and enhance approaches to yield better business results.

As a whole, this transformation extends across all industries, including Technology, Consumer, Healthcare, Manufacturing, and Banking & Finance.

In summary, I perceive that this technical change will open new avenues in how we conduct activities across various industries. A thorough understanding of AI agents and their implementation can transform the journey into a new dimension, leading to increased efficiency.

As part of our pipeline stories, @reWireByAutomation will feature several AI assistant implementations that have been recently incorporated into products **_(Development IDEs and Tools)_** by various technology vendors.

**_With this, @reWireByAutomation is signing off!_**