Daniel Dines
๐ค SpeakerAppearances Over Time
Podcast Appearances
I would say that you need to think end-to-end process versus thinking piecemeal task by task. We are a company thinking, let's go bottom-up. Let's identify a few tasks that are rule-based. Let's put them in production, get quick return on investment, and then move on. But many customers feel you have to have the end-to-end picture of the process.
And I think for Argentic, it will be truly important because I don't believe in... so much in isolated agents that, you know, business user will chat with rather than this enterprise workflows that will connect agents.
And I think for Argentic, it will be truly important because I don't believe in... so much in isolated agents that, you know, business user will chat with rather than this enterprise workflows that will connect agents.
And I think for Argentic, it will be truly important because I don't believe in... so much in isolated agents that, you know, business user will chat with rather than this enterprise workflows that will connect agents.
People will become more productive. Roles will be changed more from doing things to more overseeing technology, doing things, validating what technology is creating for you.
People will become more productive. Roles will be changed more from doing things to more overseeing technology, doing things, validating what technology is creating for you.
People will become more productive. Roles will be changed more from doing things to more overseeing technology, doing things, validating what technology is creating for you.
No, I don't think so. These validations will be actually mostly on the difficult cases in the longer term. So you asked me when agents will become like fully autonomous. I think there will be a progression to become comfortable with the output of an agent.
No, I don't think so. These validations will be actually mostly on the difficult cases in the longer term. So you asked me when agents will become like fully autonomous. I think there will be a progression to become comfortable with the output of an agent.
No, I don't think so. These validations will be actually mostly on the difficult cases in the longer term. So you asked me when agents will become like fully autonomous. I think there will be a progression to become comfortable with the output of an agent.
I'm not sure about it. The catch here is that building agents require some interesting skills. Today, we are at the point where we know technology works, but in order to make it working, you require very high skilled people in some particular areas. Building an agent requires creating a prompt. Building a good prompt, it's actually more difficult than building a script.
I'm not sure about it. The catch here is that building agents require some interesting skills. Today, we are at the point where we know technology works, but in order to make it working, you require very high skilled people in some particular areas. Building an agent requires creating a prompt. Building a good prompt, it's actually more difficult than building a script.
I'm not sure about it. The catch here is that building agents require some interesting skills. Today, we are at the point where we know technology works, but in order to make it working, you require very high skilled people in some particular areas. Building an agent requires creating a prompt. Building a good prompt, it's actually more difficult than building a script.
A script is more predictable. You have the requirements. You just follow the requirements using logic, algorithm logic. With the prompt, things are not like this. Because slight changes in the prompt can make it working like you want or not. We put a lot of work right now into helping our automation developers building better prompts, suggesting them prompts, helping them build evaluation sets.
A script is more predictable. You have the requirements. You just follow the requirements using logic, algorithm logic. With the prompt, things are not like this. Because slight changes in the prompt can make it working like you want or not. We put a lot of work right now into helping our automation developers building better prompts, suggesting them prompts, helping them build evaluation sets.
A script is more predictable. You have the requirements. You just follow the requirements using logic, algorithm logic. With the prompt, things are not like this. Because slight changes in the prompt can make it working like you want or not. We put a lot of work right now into helping our automation developers building better prompts, suggesting them prompts, helping them build evaluation sets.
It's much easier to test a script that works as intended than a prompt, because the input data can make such a huge difference, and it's very hard to test it.
It's much easier to test a script that works as intended than a prompt, because the input data can make such a huge difference, and it's very hard to test it.
It's much easier to test a script that works as intended than a prompt, because the input data can make such a huge difference, and it's very hard to test it.
Jobs are changing over time. We are seeing in agriculture, if you think about 100 years ago, 50% of UK or US population worked in agriculture. Nowadays, it's only 2%. They are mostly people that supervise machines doing their work. Yes, many of the jobs today will change, but they will be new jobs. Society evolves. You don't want to be stuck in the existing society.