WEBVTT

00:08.400 --> 00:08.880
I've been in

00:08.880 --> 00:09.480
the road for the

00:09.480 --> 00:10.240
last few months

00:10.240 --> 00:11.360
doing all these

00:11.360 --> 00:12.320
AI roadshows

00:12.320 --> 00:13.160
and we go region

00:13.160 --> 00:14.040
by region, country

00:14.040 --> 00:14.640
by country,

00:14.640 --> 00:15.080
meeting all

00:15.080 --> 00:15.800
the companies.

00:15.800 --> 00:17.520
And I think it's

00:17.520 --> 00:18.080
very important

00:18.080 --> 00:18.480
to do this

00:18.480 --> 00:19.200
because we

00:19.200 --> 00:20.160
really notice

00:20.160 --> 00:20.960
how companies

00:20.960 --> 00:21.640
valued it.

00:21.640 --> 00:22.440
They get together,

00:22.440 --> 00:22.880
they meet

00:22.880 --> 00:23.840
their peers, they...

00:23.840 --> 00:24.440
We develop

00:24.440 --> 00:24.800
the sense

00:24.800 --> 00:25.560
of community.

00:25.560 --> 00:26.240
It's just great

00:26.240 --> 00:26.720
to see

00:26.720 --> 00:27.440
how everybody

00:27.440 --> 00:28.600
is evolving with AI

00:28.600 --> 00:29.080
and how

00:29.080 --> 00:29.560
everybody

00:29.560 --> 00:30.080
is sharing

00:30.080 --> 00:30.680
their secrets

00:30.680 --> 00:31.280
and their tricks,

00:31.280 --> 00:32.040
and their methods.

00:32.040 --> 00:32.320
Today

00:32.320 --> 00:33.040
in particular, I'm

00:33.040 --> 00:33.560
very excited

00:33.560 --> 00:34.400
about this event

00:34.400 --> 00:35.120
because the companies

00:35.120 --> 00:36.040
is in the Baltics

00:36.040 --> 00:36.880
and in Poland.

00:36.880 --> 00:37.880
They are by far

00:37.880 --> 00:38.280
some of the

00:38.280 --> 00:39.120
most advanced

00:39.120 --> 00:39.840
AI companies

00:39.840 --> 00:40.320
that we have

00:40.320 --> 00:41.000
in Everfield.

00:41.000 --> 00:42.000
So there's been

00:42.000 --> 00:42.200
a lot

00:42.200 --> 00:42.960
of preparation

00:42.960 --> 00:43.680
for this event,

00:43.680 --> 00:45.200
and I see everybody

00:45.200 --> 00:46.000
so eager.

00:46.000 --> 00:46.720
So this is

00:46.720 --> 00:47.280
not going to be

00:47.280 --> 00:47.720
a session

00:47.720 --> 00:48.520
where we talk about

00:48.520 --> 00:49.240
basic stuff.

00:49.240 --> 00:50.160
This is going to be

00:50.160 --> 00:51.120
a full day,

00:51.120 --> 00:52.480
very advanced

00:52.480 --> 00:53.280
AI at the

00:53.280 --> 00:54.240
highest level

00:54.240 --> 00:54.960
when it comes to

00:54.960 --> 00:55.360
software

00:55.360 --> 00:56.240
engineering.

00:58.160 --> 00:58.760
Sprints

00:58.760 --> 00:59.880
already gone in

00:59.880 --> 01:00.600
our company.

01:00.600 --> 01:02.800
So then AI arrived.

01:02.800 --> 01:03.560
We thought

01:03.560 --> 01:04.800
that we don't

01:04.800 --> 01:05.720
need to plan

01:05.720 --> 01:06.280
in sprints

01:06.280 --> 01:07.760
because you can do

01:07.760 --> 01:08.840
so much in one day,

01:08.840 --> 01:09.520
for example,

01:09.520 --> 01:10.320
that before

01:10.320 --> 01:11.040
you were doing

01:11.040 --> 01:11.600
all week.

01:11.600 --> 01:13.200
So that planning

01:13.200 --> 01:13.840
process,

01:13.840 --> 01:14.320
It's not

01:14.320 --> 01:15.320
necessarily now

01:15.320 --> 01:15.840
for the week.

01:15.840 --> 01:17.040
So we just go

01:17.040 --> 01:18.000
task by task

01:18.000 --> 01:18.520
a project

01:18.520 --> 01:19.160
by project.

01:19.160 --> 01:19.880
Now I would say

01:19.880 --> 01:22.040
we can trust 100%,

01:22.040 --> 01:22.760
but we should be

01:22.760 --> 01:23.320
in the loop.

01:23.320 --> 01:24.040
The quality of

01:24.040 --> 01:25.040
the code is really,

01:25.040 --> 01:25.840
really amazing.

01:25.840 --> 01:26.800
But the problem

01:26.800 --> 01:27.960
in most cases

01:27.960 --> 01:29.240
that you still have

01:29.240 --> 01:30.080
that knowledge,

01:30.080 --> 01:31.200
which AI don't have

01:31.200 --> 01:32.120
about the project,

01:32.120 --> 01:33.240
about how

01:33.240 --> 01:34.040
your customer

01:34.040 --> 01:34.520
is using

01:34.520 --> 01:35.240
your products.

01:35.240 --> 01:36.040
So you still have

01:36.040 --> 01:36.840
to double check

01:36.840 --> 01:37.480
if it will

01:37.480 --> 01:38.160
really fit.

01:38.160 --> 01:39.160
Like implementation

01:39.160 --> 01:39.760
is okay,

01:39.760 --> 01:41.000
but how it works

01:41.000 --> 01:41.400
in the

01:41.400 --> 01:42.280
whole product

01:42.280 --> 01:43.720
is the questionable

01:43.720 --> 01:44.120
thing.

01:44.120 --> 01:45.400
I’ll just,

01:45.400 --> 01:46.160
I don't know,

01:46.160 --> 01:47.240
I would just leave

01:47.240 --> 01:47.960
my job.

01:47.960 --> 01:48.240
I'm

01:48.240 --> 01:48.960
the developer

01:48.960 --> 01:49.920
for 20

01:49.920 --> 01:50.680
years already.

01:50.680 --> 01:51.240
Now I'm

01:51.240 --> 01:52.600
enjoying it again

01:52.600 --> 01:53.200
after all

01:53.200 --> 01:54.040
those years.

01:54.040 --> 01:54.760
I enjoy it

01:54.760 --> 01:55.400
because I can

01:55.400 --> 01:56.200
deliver things.

01:56.200 --> 01:57.840
I can be a creator,

01:57.840 --> 01:58.320
not the

01:58.320 --> 01:59.320
developer only,

01:59.320 --> 02:00.280
but the creator.

02:00.280 --> 02:01.440
I can do things

02:01.440 --> 02:02.400
whatever I want.

02:02.400 --> 02:03.200
So yeah,

02:03.200 --> 02:04.120
that's amazing.

02:04.120 --> 02:05.040
Before I was using

02:05.040 --> 02:06.760
ChatGPT as

02:06.760 --> 02:07.560
my daily runner,

02:07.560 --> 02:08.000
I was just

02:08.000 --> 02:08.600
prompting

02:08.600 --> 02:09.720
questions,

02:09.720 --> 02:10.360
copy pasting

02:10.360 --> 02:10.880
the codes

02:10.880 --> 02:11.840
in the system.

02:11.840 --> 02:12.440
I remember

02:12.440 --> 02:13.080
when we got the

02:13.080 --> 02:13.880
first day interview

02:13.880 --> 02:14.680
from Everfield,

02:14.680 --> 02:15.320
like about

02:15.320 --> 02:16.280
the AI adoption.

02:16.280 --> 02:17.000
I think

02:17.000 --> 02:18.600
I lied on it

02:18.600 --> 02:19.520
because

02:19.520 --> 02:20.440
I was afraid

02:20.440 --> 02:21.160
that the fact

02:21.160 --> 02:21.800
that I'm copy

02:21.800 --> 02:22.760
pasting code

02:22.760 --> 02:23.480
from the

02:23.480 --> 02:25.000
AI will be judged

02:25.000 --> 02:25.760
against me.

02:25.760 --> 02:26.120
Like I will

02:26.120 --> 02:26.600
put AGroup

02:26.600 --> 02:27.440
in a bad position.

02:27.440 --> 02:28.200
I think

02:28.200 --> 02:28.760
generally

02:28.760 --> 02:29.560
I replied with

02:29.560 --> 02:30.440
a bit of honesty

02:30.440 --> 02:30.720
there

02:30.720 --> 02:31.480
that I use it.

02:31.480 --> 02:31.760
I think

02:31.760 --> 02:32.480
I didn't say daily,

02:32.480 --> 02:33.400
but occasionally.

02:33.400 --> 02:34.160
But after I

02:34.160 --> 02:34.880
switched to Claude,

02:34.880 --> 02:35.680
it was.

02:35.680 --> 02:36.160
It was just

02:36.160 --> 02:36.840
night and day.

02:36.840 --> 02:37.400
Honestly,

02:37.400 --> 02:38.000
it can just

02:38.000 --> 02:38.520
do stuff.

02:38.520 --> 02:39.080
You tell it

02:39.080 --> 02:40.040
the end result

02:40.040 --> 02:40.800
and it

02:40.800 --> 02:41.320
connects all

02:41.320 --> 02:41.680
the dots

02:41.680 --> 02:42.280
in between.

02:42.280 --> 02:42.920
Sometimes I think

02:42.920 --> 02:43.480
of an idea

02:43.480 --> 02:44.400
and you immediately

02:44.400 --> 02:45.280
decline it with

02:45.280 --> 02:45.640
a thought

02:45.640 --> 02:46.400
that it's too

02:46.400 --> 02:47.240
heavy, is too hard,

02:47.240 --> 02:47.800
but then you see

02:47.800 --> 02:48.720
people actually

02:48.720 --> 02:49.120
do it.

02:49.120 --> 02:49.720
You meet them,

02:49.720 --> 02:50.560
you talk about it,

02:50.560 --> 02:50.880
and then

02:50.880 --> 02:51.400
you understand

02:51.400 --> 02:51.960
that this is

02:51.960 --> 02:52.640
just the only

02:52.640 --> 02:53.560
fear in your mind

02:53.560 --> 02:54.520
was stopping you

02:54.520 --> 02:55.120
or blocking you

02:55.120 --> 02:56.960
from doing stuff

02:56.960 --> 02:57.920
that you wanted

02:57.920 --> 02:58.240
to do

02:58.240 --> 02:58.960
this whole time.

02:58.960 --> 02:59.920
I was writing

02:59.920 --> 03:01.000
wonderful ideas,

03:01.000 --> 03:01.560
and especially

03:01.560 --> 03:02.360
I'm interested

03:02.360 --> 03:03.360
in chatbot

03:03.360 --> 03:04.240
because we tried it

03:04.240 --> 03:04.920
last year

03:04.920 --> 03:06.360
and failed heavily

03:06.360 --> 03:08.080
and we failed due to...

03:08.080 --> 03:08.760
It was unable

03:08.760 --> 03:09.520
able to read

03:09.520 --> 03:10.520
the context

03:10.520 --> 03:10.960
or what

03:10.960 --> 03:11.880
we tried to fit

03:11.880 --> 03:12.560
instead of

03:12.560 --> 03:13.400
like answering,

03:13.400 --> 03:14.040
I couldn't

03:14.040 --> 03:14.800
find answer

03:14.800 --> 03:15.480
or something.

03:15.480 --> 03:16.280
It started to

03:16.280 --> 03:17.240
hallucinate.

03:17.240 --> 03:17.720
So that's

03:17.720 --> 03:18.600
why I had

03:18.600 --> 03:19.160
this question

03:19.160 --> 03:20.240
to the colleague, like

03:20.240 --> 03:21.000
did you face it

03:21.000 --> 03:21.440
how you deal

03:21.440 --> 03:21.720
with it?

03:21.720 --> 03:22.920
Because it was

03:22.920 --> 03:23.560
what we faced.

03:23.560 --> 03:24.120
However,

03:24.120 --> 03:25.360
despite this

03:25.360 --> 03:26.960
not so good ending,

03:26.960 --> 03:28.240
when we did

03:28.240 --> 03:29.200
measurements

03:29.200 --> 03:30.240
about efficiency,

03:30.240 --> 03:30.720
it showed

03:30.720 --> 03:31.080
that

03:31.080 --> 03:33.440
approximately 53%

03:33.440 --> 03:34.160
efficiency

03:34.160 --> 03:34.760
increased

03:34.760 --> 03:35.440
when you use

03:35.440 --> 03:36.400
even such

03:36.400 --> 03:37.920
a bit hallucinating

03:37.920 --> 03:38.760
AI tools.

03:38.760 --> 03:40.160
For me, this

03:40.160 --> 03:40.840
bringing back

03:40.840 --> 03:41.440
this idea,

03:41.440 --> 03:42.640
especially to

03:42.640 --> 03:43.040
win it

03:43.040 --> 03:43.720
over after

03:43.720 --> 03:44.600
a failure,

03:44.600 --> 03:45.440
I think it will

03:45.440 --> 03:46.000
be the thing

03:46.000 --> 03:47.040
that will be

03:47.040 --> 03:48.320
top priority.

03:48.640 --> 03:49.760
What a day that was.

03:49.760 --> 03:50.680
So we had a

03:50.680 --> 03:52.280
very full session.

03:52.280 --> 03:53.000
Everybody

03:53.000 --> 03:53.920
was talking,

03:53.920 --> 03:54.400
doing their

03:54.400 --> 03:55.320
presentations,

03:55.320 --> 03:56.520
showing their code,

03:56.520 --> 03:57.440
showing how

03:57.440 --> 03:58.200
they interact

03:58.200 --> 03:58.920
with AI.

03:58.920 --> 03:59.920
And it's amazing

03:59.920 --> 04:01.320
to see because it's...

04:01.320 --> 04:01.880
When you work

04:01.880 --> 04:02.920
from your home

04:02.920 --> 04:03.920
or from the office,

04:03.920 --> 04:04.320
you don't

04:04.320 --> 04:05.200
really understand

04:05.200 --> 04:06.080
the extent of

04:06.080 --> 04:06.960
like all

04:06.960 --> 04:07.600
these people

04:07.600 --> 04:08.440
getting together

04:08.440 --> 04:09.200
and working

04:09.200 --> 04:09.960
on, on

04:09.960 --> 04:10.560
solving these

04:10.560 --> 04:11.600
very difficult

04:11.600 --> 04:12.240
problems.

04:12.240 --> 04:13.280
And now I see it.

04:13.280 --> 04:13.680
Software

04:13.680 --> 04:14.560
engineering used

04:14.560 --> 04:15.320
to be

04:16.320 --> 04:16.800
something

04:16.800 --> 04:18.320
complicated, like

04:18.320 --> 04:19.440
difficult brain

04:19.440 --> 04:20.360
cracking problems

04:20.360 --> 04:21.200
that will

04:21.200 --> 04:22.160
keep developers

04:22.160 --> 04:22.680
working through

04:22.680 --> 04:23.200
the night,

04:23.200 --> 04:24.360
trying to find

04:24.360 --> 04:25.120
the bug,

04:25.120 --> 04:25.440
trying

04:25.440 --> 04:26.320
to find the issue

04:26.320 --> 04:27.000
with the big

04:27.000 --> 04:27.640
code base.

04:27.640 --> 04:28.560
And now

04:28.560 --> 04:29.480
we see

04:29.480 --> 04:30.120
today on

04:30.120 --> 04:30.680
the session

04:30.680 --> 04:31.600
like how people

04:31.600 --> 04:32.320
have been able

04:32.320 --> 04:32.920
to make

04:32.920 --> 04:33.920
their lives easier,

04:33.920 --> 04:35.040
to delegate

04:35.040 --> 04:35.760
the boring

04:35.760 --> 04:36.680
part of software

04:36.680 --> 04:37.600
engineering to

04:37.600 --> 04:38.640
AI agents,

04:38.640 --> 04:40.120
and how we are now

04:40.120 --> 04:40.600
being able

04:40.600 --> 04:41.120
to focus

04:41.120 --> 04:41.960
on our customers,

04:41.960 --> 04:42.520
being able

04:42.520 --> 04:43.080
to deliver

04:43.080 --> 04:44.080
more value to them.

04:44.080 --> 04:45.200
And everybody

04:45.200 --> 04:46.040
got their creative

04:46.040 --> 04:46.800
juices flowing

04:46.800 --> 04:48.280
because we are

04:48.280 --> 04:48.800
no longer

04:48.800 --> 04:49.640
bounded by

04:49.640 --> 04:50.680
the boring part

04:50.680 --> 04:51.640
of software

04:51.640 --> 04:52.560
engineering.

04:52.560 --> 04:53.400
Everybody is

04:53.400 --> 04:54.120
an inventor.

04:54.120 --> 04:55.440
Everybody is

04:55.440 --> 04:56.280
pushing the limits

04:56.280 --> 04:57.240
of what's possible.

04:57.240 --> 04:57.960
When people

04:57.960 --> 04:59.400
come to me with,

04:59.400 --> 05:00.240
we just don't have

05:00.240 --> 05:01.240
time for this.

05:01.240 --> 05:02.800
Like we are busy.

05:02.800 --> 05:04.200
We have,

05:04.200 --> 05:04.480
you know,

05:04.480 --> 05:05.760
migrations to do.

05:05.760 --> 05:07.320
We have customers

05:07.320 --> 05:08.040
asking for

05:08.040 --> 05:08.600
features.

05:08.600 --> 05:10.240
We are trying to

05:10.240 --> 05:11.960
meet regulation

05:11.960 --> 05:12.560
changes

05:12.560 --> 05:13.560
and compliance

05:13.560 --> 05:13.920
checks

05:13.920 --> 05:15.160
and certifications

05:15.160 --> 05:15.840
is just so

05:15.840 --> 05:16.520
much going on

05:16.520 --> 05:17.200
that we don't have

05:17.200 --> 05:18.240
time for AI.

05:18.240 --> 05:18.720
We kind of

05:18.720 --> 05:19.360
look into that

05:19.360 --> 05:20.760
later in the year.

05:20.760 --> 05:21.160
And I'm

05:21.160 --> 05:21.640
telling that no,

05:21.640 --> 05:22.600
no, no, no, no,

05:22.600 --> 05:23.000
you should

05:23.000 --> 05:23.560
place the right

05:23.560 --> 05:24.560
focus on it

05:24.560 --> 05:25.560
right now.

05:25.560 --> 05:26.360
Because whatever

05:26.360 --> 05:26.720
you do

05:26.720 --> 05:27.360
in enabling

05:27.360 --> 05:29.080
your team to use AI

05:29.480 --> 05:30.280
right now,

05:30.280 --> 05:30.800
it's going to

05:30.800 --> 05:31.040
help

05:31.040 --> 05:32.320
your future self

05:32.320 --> 05:33.360
to become

05:33.360 --> 05:33.920
not only

05:33.920 --> 05:34.640
more productive,

05:34.640 --> 05:35.640
but to have teams

05:35.640 --> 05:37.080
that are happier,

05:37.080 --> 05:37.680
that like to

05:37.680 --> 05:38.360
work with it,

05:38.360 --> 05:39.240
that are able to

05:39.240 --> 05:39.600
go through

05:39.600 --> 05:40.040
all the

05:40.040 --> 05:41.320
backlogs and,

05:41.320 --> 05:41.880
you know, do

05:41.880 --> 05:42.520
all those things

05:42.520 --> 05:43.880
that there was

05:43.880 --> 05:44.800
never time for.

05:44.800 --> 05:45.520
So what

05:45.520 --> 05:45.840
So what

05:45.840 --> 05:46.200
I see

05:46.200 --> 05:46.800
in the session

05:46.800 --> 05:47.160
today

05:47.160 --> 05:47.600
is that

05:47.600 --> 05:48.440
those companies

05:48.440 --> 05:49.440
that have been

05:49.440 --> 05:49.880
struggling

05:49.880 --> 05:50.680
with adoption

05:50.680 --> 05:51.440
or being a bit

05:51.440 --> 05:52.440
defensive at first,

05:52.440 --> 05:53.040
now they come

05:53.040 --> 05:53.720
back and say,

05:53.720 --> 05:54.480
oh, it's so good

05:54.480 --> 05:54.880
that we

05:54.880 --> 05:55.680
actually did this.

05:55.680 --> 05:56.880
We are so happy

05:56.880 --> 05:57.400
that we

05:57.400 --> 05:58.320
were able to

05:58.320 --> 05:59.160
to pull this off.

05:59.160 --> 05:59.680
And actually

05:59.680 --> 06:00.920
it's helping us

06:00.920 --> 06:01.960
on our day to day

06:01.960 --> 06:02.680
in running

06:02.680 --> 06:03.760
our businesses.

06:03.760 --> 06:04.800
So that's something

06:04.800 --> 06:05.760
that is

06:05.760 --> 06:07.240
absolutely amazing

06:07.240 --> 06:07.560
to see.