WEBVTT

00:00:00.080 --> 00:00:04.000
2026 will for sure be another interesting
year and I think

00:00:04.059 --> 00:00:07.860
in some regards, like the job market,
it will be better than

00:00:08.000 --> 00:00:11.800
2025 for developers.
So I'll share my perspective

00:00:11.960 --> 00:00:15.880
on AI, obviously, the job market
and why I think

00:00:15.940 --> 00:00:19.500
it will get better, and web dev
and web dev

00:00:19.640 --> 00:00:21.980
trends and technologies in general.

00:00:22.060 --> 00:00:26.020
So let's start with AI because
that obviously will

00:00:26.160 --> 00:00:30.140
still be a very important thing next year,
and here

00:00:30.240 --> 00:00:33.580
I think we have kind of reached a plateau
when it comes to the

00:00:33.640 --> 00:00:36.900
intelligence,
if you want to call it like this,

00:00:36.940 --> 00:00:40.780
does not mean that we won't see more
development

00:00:40.880 --> 00:00:44.640
or better models or tools around these
models

00:00:44.760 --> 00:00:48.640
next year, and let me explain. So
if we had a chart and we would

00:00:48.740 --> 00:00:52.700
start in 2022, obviously where ChatGPT
was released, and

00:00:52.740 --> 00:00:56.360
then we would end at the end of 2025,
I would say the

00:00:56.380 --> 00:00:59.840
"intelligence," and I put
that in quotes because they're not really

00:00:59.860 --> 00:01:03.740
intelligent, they're token generators,
but of course they do that pretty

00:01:03.860 --> 00:01:06.260
well and they can use tools
and I'll get back to that.

00:01:06.280 --> 00:01:09.980
But the intelligence,
the capabilities of these tools,

00:01:10.000 --> 00:01:13.660
I would say developed something like this
maybe, so a

00:01:13.720 --> 00:01:17.510
pretty good development.
Obviously we all saw that, but I

00:01:17.580 --> 00:01:21.340
think that now we're kind of at this
point, so I don't think

00:01:21.380 --> 00:01:25.080
we'll see an exponential improvement or

00:01:25.160 --> 00:01:29.120
anything like that. Instead,
my feeling for the last year whenever

00:01:29.180 --> 00:01:32.780
new models were released was
that there was a lot of hype, there

00:01:32.840 --> 00:01:36.560
were benchmark numbers where the model
was better than most other

00:01:36.620 --> 00:01:40.310
models of course,
but at the same time not that much

00:01:40.320 --> 00:01:44.240
better.
And especially once people started using

00:01:44.280 --> 00:01:47.310
than once that it
was kind of meh in the end.

00:01:47.340 --> 00:01:51.020
I mean,
take for example the LLaMA 4

00:01:51.060 --> 00:01:54.760
last year. When LLaMA 4 was announced,
the model

00:01:55.060 --> 00:01:58.900
family,
we had impressive benchmark numbers.

00:01:59.180 --> 00:02:02.760
We saw that the top LLaMA 4 model,
maverick,

00:02:02.900 --> 00:02:06.820
basically was better than all the other
top models

00:02:06.940 --> 00:02:10.470
or other frontier models we had at
that time

00:02:10.538 --> 00:02:14.390
in benchmarks.
But shortly after the release,

00:02:14.440 --> 00:02:18.140
this where people were kind of,
"It doesn't feel that

00:02:18.200 --> 00:02:21.120
great," and we had
that more than once last year.

00:02:21.160 --> 00:02:24.700
Now don't get me wrong,
models did get better for sure,

00:02:24.760 --> 00:02:28.650
especially of course compared to 2022

00:02:28.920 --> 00:02:32.120
or 2023 or 2024 and so

00:02:32.200 --> 00:02:36.070
on,
but we're at this point where they won't

00:02:36.100 --> 00:02:39.740
get drastically better every year,
and I'm talking about

00:02:39.780 --> 00:02:43.609
large language models here.
If we take a look at video generation

00:02:43.640 --> 00:02:47.620
Veo or Sora 2, obviously we saw a

00:02:47.660 --> 00:02:51.600
drastic improvement there compared to the
years before, and the same is true for

00:02:51.800 --> 00:02:55.260
image generation models.
We had the release of Nano

00:02:55.340 --> 00:02:58.720
Banana, not the pro version
but the normal version, in

00:02:59.020 --> 00:03:02.900
August of this year I think, and that
was really groundbreaking.

00:03:02.920 --> 00:03:06.700
And then of course we also had Nano Banana
Pro which

00:03:06.880 --> 00:03:10.660
raised the bar even more,
and we had other models like the

00:03:10.700 --> 00:03:14.320
Flux models by Black Forest Labs,
Flux 2 recently

00:03:14.380 --> 00:03:18.320
released,
and all these models definitely got much

00:03:18.380 --> 00:03:22.170
year before.
But if we take a look at large language

00:03:22.180 --> 00:03:24.200
think we're reaching that plateau.

00:03:24.320 --> 00:03:28.310
Now I will say there's a lot of
development on

00:03:28.340 --> 00:03:31.900
those models to make them better at
specific tasks.

00:03:31.960 --> 00:03:35.360
I think that's the clear trend we can
already see that will continue in

00:03:35.620 --> 00:03:39.460
2026 because of course we now have those
thinking

00:03:39.470 --> 00:03:43.150
models.
That is pretty much the standard now for

00:03:43.180 --> 00:03:46.609
models. We also have models that
are better at following

00:03:46.640 --> 00:03:49.600
instructions and at

00:03:50.300 --> 00:03:53.320
tool calling, and that is a big one.

00:03:53.380 --> 00:03:56.840
This here really is a big one because
that is

00:03:56.900 --> 00:04:00.600
important. It's that improved tool calling

00:04:00.660 --> 00:04:04.080
capability of new models
that makes them way more

00:04:04.140 --> 00:04:07.580
useful in the applications
that use these models,

00:04:07.600 --> 00:04:11.340
and that is important.
With this chart here,

00:04:11.460 --> 00:04:15.140
I'm referring to how models or their raw

00:04:15.200 --> 00:04:19.079
intelligence kind of improves. Now
if I were to

00:04:19.160 --> 00:04:23.060
copy this chart and judge the capabilities
of

00:04:23.140 --> 00:04:27.120
applications that
are built on top of these models, it would

00:04:27.240 --> 00:04:30.560
probably look more something like this,
more linear, not

00:04:30.580 --> 00:04:34.300
exponential still but linear. Because
when we look at applications that

00:04:34.520 --> 00:04:37.780
use AI like ChatGPT or Gemini themselves

00:04:37.900 --> 00:04:41.840
obviously, then they got better. Oh,
also of

00:04:41.940 --> 00:04:45.720
course because all these models have great

00:04:46.160 --> 00:04:50.040
multimodal capabilities. They're good at,
uh, taking a look

00:04:50.120 --> 00:04:53.450
at images, understanding images,
generating images by

00:04:53.860 --> 00:04:57.240
integrating other models,
and that's basically what these

00:04:57.300 --> 00:05:00.320
applications are doing then
which takes me back to this chart

00:05:00.360 --> 00:05:04.040
here. It's important to understand
that of course we

00:05:04.140 --> 00:05:08.020
are exclusively almost interacting with
applications

00:05:08.040 --> 00:05:12.000
that use AI,
unless you use the raw models via the API

00:05:12.020 --> 00:05:13.650
to build your own applications of course.

00:05:13.660 --> 00:05:17.580
But as end users,
we interact with applications like

00:05:17.660 --> 00:05:21.290
ChatGPT or Gemini of course,

00:05:21.760 --> 00:05:25.020
so that would be example applications we
have, but

00:05:25.140 --> 00:05:28.380
also something like Cursor or

00:05:28.660 --> 00:05:32.500
Claude Code. These
are applications built on top

00:05:32.680 --> 00:05:36.480
of AI models and those of course got much
better over the

00:05:36.540 --> 00:05:40.000
year and I think they will continue to get
better. Why?

00:05:40.010 --> 00:05:43.969
Because the developers of these
applications get better at

00:05:44.040 --> 00:05:47.940
integrating those AI models,
there's a lot of wiring of different

00:05:47.980 --> 00:05:51.560
models behind the scenes, there
is of course prompt and context

00:05:51.640 --> 00:05:54.900
engineering, and there are tools that
are exposed to those

00:05:55.020 --> 00:05:58.920
models. If we take a look at ChatGPT

00:05:59.000 --> 00:06:02.820
here, the ChatGPT of today
is of course nothing related to the

00:06:02.860 --> 00:06:06.400
ChatGPT we had in 2022. It has, for

00:06:06.460 --> 00:06:09.920
example, web search. It can,

00:06:09.969 --> 00:06:13.921
uh...... write and execute code. It can

00:06:14.112 --> 00:06:17.932
generate images and that, of course,
is technically done through a

00:06:17.972 --> 00:06:21.612
different model,
not through the GPT large language

00:06:21.672 --> 00:06:25.532
model,
but through an image generation model,

00:06:25.632 --> 00:06:29.462
ChatGPT application
that wires these different models

00:06:29.472 --> 00:06:33.332
together.
And other applications like Claude Code

00:06:33.392 --> 00:06:37.122
are also potentially wiring different
models together, doing

00:06:37.152 --> 00:06:40.982
prompt engineering,
and they expose tools to these models

00:06:40.982 --> 00:06:44.852
like web search, which
is exposed by ChatGPT and also

00:06:44.892 --> 00:06:46.992
by Cursor. It can also search the web.

00:06:47.012 --> 00:06:50.682
And that is one part where those models,
of

00:06:50.772 --> 00:06:54.382
course, did get better because they
are optimized and

00:06:54.532 --> 00:06:58.032
fine-tuned for being good at tool calling.

00:06:58.072 --> 00:07:01.992
Now,
just to make sure we're all on the same

00:07:02.032 --> 00:07:05.632
a tool really just means
that the developers of an

00:07:05.692 --> 00:07:09.511
application describe the available tools
to the

00:07:09.552 --> 00:07:12.632
model and then the model emits

00:07:12.642 --> 00:07:16.332
tokens that describe an intended tool use

00:07:16.912 --> 00:07:19.602
if it feels like calling that tool.

00:07:19.612 --> 00:07:23.372
Now, of course,
whether it feels like calling a tool

00:07:23.382 --> 00:07:27.132
simply on the prompt engineering,
the system prompt and how the model

00:07:27.252 --> 00:07:31.052
has been trained and fine-tuned.
So for example, if a tool

00:07:31.192 --> 00:07:35.152
has a get weather tool available
and the user asks it

00:07:35.272 --> 00:07:38.192
what will be the weather tomorrow,
there is a very high

00:07:38.452 --> 00:07:42.362
likelihood for the model to suggest
that it wants to call the get

00:07:42.532 --> 00:07:46.322
weather tool. Now as a next step,
it will emit those tokens

00:07:46.352 --> 00:07:49.632
that describe that tool call
and then it's again the

00:07:49.692 --> 00:07:53.652
application like ChatGPT that will make

00:07:53.712 --> 00:07:57.392
the actual tool call. So
that it will execute the actual code

00:07:57.432 --> 00:08:00.972
behind the tool and
that will then pass the results of

00:08:01.392 --> 00:08:05.352
back into the chat history, so to say,

00:08:05.392 --> 00:08:09.272
to have the large language model then
generate the final

00:08:09.292 --> 00:08:11.392
output that should be shown to the user.

00:08:11.412 --> 00:08:15.022
So all that tool calling
and these intermediate results are not

00:08:15.052 --> 00:08:18.932
necessarily shown to the user,
but the final result, which

00:08:18.971 --> 00:08:22.842
call, is. And that, of course,
is where those models did get

00:08:22.872 --> 00:08:26.862
much better,
or the applications I should say,

00:08:26.892 --> 00:08:30.552
they will continue to get better because
we, as developers, can leverage

00:08:30.742 --> 00:08:34.712
those large language models
that have been optimized for being good at

00:08:34.751 --> 00:08:38.702
tool calling and so on to build more
capable applications on top of

00:08:38.732 --> 00:08:41.962
them.
So that is the trend I see continuing

00:08:42.452 --> 00:08:46.312
I see Cursor or Claude Code
and all those other

00:08:46.352 --> 00:08:49.952
applications and all those applications
that are not related to coding at all

00:08:49.992 --> 00:08:53.541
become even better in the next year,
not exponentially,

00:08:53.572 --> 00:08:57.261
but linearly I would say.
Now what does that mean for

00:08:57.352 --> 00:09:01.012
us developers? Well,
it means two main things I would say.

00:09:01.032 --> 00:09:04.112
For one, it gives us opportunities.

00:09:04.152 --> 00:09:07.892
There are opportunities for building
interesting stuff

00:09:08.012 --> 00:09:11.832
on top of AI,
on top of large language models,

00:09:11.892 --> 00:09:15.052
models,
and potentially combined capabilities.

00:09:15.092 --> 00:09:18.852
Like the Build My Graphic app I built,
I built it for me because I

00:09:18.892 --> 00:09:22.612
need infographics for videos like this
and it's not just about infographics.

00:09:22.632 --> 00:09:25.362
You can generate all kinds of graphics
there.

00:09:25.392 --> 00:09:29.351
And I built this on top of Nano Banana
Pro, but also

00:09:29.392 --> 00:09:33.152
by using many other models to process the
user input,

00:09:33.172 --> 00:09:36.932
do research, whatever,
and then generate graphics based on

00:09:37.032 --> 00:09:40.452
style templates provided by me.
So I built an application on top of

00:09:40.472 --> 00:09:44.212
think there will be many opportunities for
small and bigger useful

00:09:44.392 --> 00:09:48.372
applications that you can build on top of
AI because the

00:09:48.432 --> 00:09:52.292
AI models have all these capabilities now
which they didn't have two

00:09:52.352 --> 00:09:56.002
or three years ago.
So I think the first important implication

00:09:56.032 --> 00:09:59.652
takeaway is that this gives us
opportunities.

00:09:59.662 --> 00:10:03.202
The second important implication for us
developers, I

00:10:03.332 --> 00:10:06.992
think, is that we must be able to

00:10:07.032 --> 00:10:10.032
work with AI assistants

00:10:10.912 --> 00:10:14.612
for coding.
And I know that's not everybody's cup

00:10:14.752 --> 00:10:18.672
of tea, coffee, whatever. You, of course,
don't have to

00:10:19.052 --> 00:10:22.852
if you have the luxury of not needing to,
but if you

00:10:22.932 --> 00:10:26.581
are in a job and want to keep that job
or want to

00:10:26.632 --> 00:10:30.412
find a job,
you really need to build the skills to

00:10:30.451 --> 00:10:33.932
effectively work with AI assistants for
coding.

00:10:33.952 --> 00:10:36.112
And you might wonder, what does that mean?

00:10:36.172 --> 00:10:39.752
I mean, I can write a prompt.
It's about writing the right

00:10:39.832 --> 00:10:43.752
prompts, asking for the right things,
providing the right context, not

00:10:43.852 --> 00:10:47.412
overwhelming the model
and asking for too much,

00:10:47.492 --> 00:10:51.271
small, incremental demands or requests.

00:10:51.352 --> 00:10:55.242
And I will create separate resources on
that to share more about how I

00:10:55.312 --> 00:10:59.112
work with AI and how I think you can
effectively work with AI

00:10:59.172 --> 00:11:01.271
because I definitely want to help there.

00:11:01.292 --> 00:11:05.012
But I think you need to build that

00:11:05.132 --> 00:11:08.912
skill unless you're really in a position
where you're your own boss and you can do

00:11:08.932 --> 00:11:12.642
whatever you want,
and then of course it's totally fine

00:11:12.672 --> 00:11:15.262
AI at all. Let me be very clear here.

00:11:15.292 --> 00:11:19.142
I'm also not saying,
and I want to be clear about that too,

00:11:19.212 --> 00:11:23.142
that thing that will generate all perfect
code and that we should

00:11:23.172 --> 00:11:26.142
go into live coding. Quite the opposite.

00:11:26.252 --> 00:11:29.452
I'm talking about AI assistants here,
not live

00:11:29.532 --> 00:11:32.642
coding. You as a developer can and should

00:11:33.072 --> 00:11:36.842
steer and control the model.
You should tell it what

00:11:36.872 --> 00:11:40.832
to do and you should get good at being
precise there about

00:11:40.852 --> 00:11:44.812
providing the right context,
about being able to evaluate the results

00:11:44.832 --> 00:11:48.532
you get back,
about building a plan before you even

00:11:48.632 --> 00:11:50.872
prompting. And again,
I'll share more about that.

00:11:50.892 --> 00:11:54.442
But that is the,
the second important imple- implication, I

00:11:54.512 --> 00:11:58.332
think. That is my take on AI

00:11:58.432 --> 00:12:02.012
in this, uh, new year, uh,
from a developer's perspective.

00:12:02.072 --> 00:12:05.812
Now of course, AI is one thing,

00:12:05.892 --> 00:12:09.712
arguably the most important one,
but let's talk about the

00:12:09.872 --> 00:12:13.852
job market because that clearly
is also important to many people.

00:12:13.892 --> 00:12:17.832
And here,
we probably all know this chart here, this

00:12:17.892 --> 00:12:21.452
horrible chart where we had this peak here
during the

00:12:21.492 --> 00:12:24.292
pandemic and, and now we're down here.

00:12:24.332 --> 00:12:28.192
Now the good thing, I guess,
about this chart is that it looks like we,

00:12:28.232 --> 00:12:32.052
bottom, right? Maybe there even
is a slight improvement coming for us

00:12:32.112 --> 00:12:35.112
or already happening,
and I definitely think there will be an

00:12:35.132 --> 00:12:39.082
improvement n- next year.
Now we also have to differentiate

00:12:39.112 --> 00:12:42.712
of course.
We have to differentiate between jobs for

00:12:42.812 --> 00:12:46.312
senior developers,
and I'm only talking about the developer

00:12:46.352 --> 00:12:49.652
here, and junior developers. I think for

00:12:49.771 --> 00:12:53.472
senior developers it was already okay
or good

00:12:53.952 --> 00:12:57.742
and it definitely will be good in the next
year because all those

00:12:57.771 --> 00:13:01.412
companies are scrambling to get senior

00:13:01.432 --> 00:13:05.162
developers, especially the ones that
are capable of working with

00:13:05.212 --> 00:13:08.902
AI, of steering the AI, and of judging

00:13:08.932 --> 00:13:12.512
the output by AI. So senior developers

00:13:13.312 --> 00:13:17.252
h-
have a relatively good position I'd say,

00:13:17.312 --> 00:13:20.202
get much better in the coming year.

00:13:20.936 --> 00:13:24.796
The problem, of course, is
that not everybody's a senior

00:13:24.856 --> 00:13:28.516
become a senior by being a junior first
and

00:13:28.616 --> 00:13:32.496
here, we definitely had a-
a bad (laughs) state

00:13:32.536 --> 00:13:36.306
of that job market in 2025.
But the good thing is,

00:13:36.306 --> 00:13:39.846
I expect that to get better in-- not

00:13:39.876 --> 00:13:43.156
badder,
(laughs) but better in the next year.

00:13:43.236 --> 00:13:46.236
In 2026, I expect that to

00:13:46.316 --> 00:13:49.656
improve. Now, why do I expect
that to improve?

00:13:49.696 --> 00:13:51.956
Of course,
we have all these reports about layoffs.

00:13:51.996 --> 00:13:55.796
We have all these reports about layoffs
because of

00:13:55.876 --> 00:13:59.776
AI that happened in, uh, 2025 but we

00:13:59.876 --> 00:14:03.016
have to be careful here. It's pretty easy

00:14:03.076 --> 00:14:06.846
to mention AI as a reason for a

00:14:06.896 --> 00:14:09.046
layoff. That's a nice reason to have.

00:14:09.076 --> 00:14:12.966
It's especially a reason
that might please investors because,

00:14:12.996 --> 00:14:16.415
they wanna hear that you're an AI first
company and that you're

00:14:16.456 --> 00:14:20.316
embracing AI. And I'm not saying
that AI is not

00:14:20.356 --> 00:14:24.046
having any impact on the job market,
it clearly has, and even if it's

00:14:24.176 --> 00:14:28.036
just that many executives expect AI to be
able to

00:14:28.076 --> 00:14:31.756
do your job in the future,
so they rather don't hire anybody new for

00:14:31.816 --> 00:14:35.756
now. I'm pretty sure though, that more
and more companies will

00:14:35.816 --> 00:14:39.736
realize that going all in on AI

00:14:39.836 --> 00:14:43.556
or relying heavily on AI instead of humans
that made and

00:14:43.616 --> 00:14:46.136
work with AI, is not a good strategy.

00:14:46.236 --> 00:14:49.856
I'm sure we'll see in 2026
that more companies

00:14:50.436 --> 00:14:54.356
want to have a workforce that's capable of
using AI as a

00:14:54.396 --> 00:14:58.196
tool because it is a great tool,
at least in certain industries.

00:14:58.236 --> 00:15:02.036
Encoding, I would say,
it can be a very useful tool but it's

00:15:02.046 --> 00:15:05.896
that, a tool, not a replacement,
and I think more

00:15:05.956 --> 00:15:09.726
companies will realize that in 2026
and they will

00:15:09.816 --> 00:15:12.986
also realize that yes, of course,
it would be nice to have

00:15:13.096 --> 00:15:16.786
more seniors that are capable with

00:15:16.836 --> 00:15:20.796
AI,
that's why this will be such a good job

00:15:20.836 --> 00:15:24.816
think,
but that there aren't enough seniors

00:15:25.096 --> 00:15:28.736
squeeze and that's why I think more
companies will be open to hiring

00:15:28.836 --> 00:15:32.296
juniors again. But the role of

00:15:32.336 --> 00:15:35.415
developers will change,
not just next year, but in

00:15:35.476 --> 00:15:39.096
general. As I mentioned, it will be more

00:15:39.256 --> 00:15:43.096
about working with AI,
about controlling AI,

00:15:43.136 --> 00:15:47.056
and junior developers
that feel confident working with AI

00:15:47.116 --> 00:15:51.096
will be more interested next year than
junior developers or developers

00:15:51.116 --> 00:15:54.866
in general that don't. And therefore,
that is one

00:15:54.896 --> 00:15:58.425
important takeaway for next year,
the first important

00:15:58.436 --> 00:16:02.336
takeaway. As a developer
that wants to get a

00:16:02.436 --> 00:16:05.956
job, you must be able to

00:16:06.036 --> 00:16:09.476
use AI. And again,
sounds like a simple thing but

00:16:10.016 --> 00:16:13.175
you must feel confident using it.
You must be able to show potential

00:16:13.216 --> 00:16:17.036
employers that you can get a real value
out of

00:16:17.096 --> 00:16:21.006
AI assistance. That's one thing,
but I also

00:16:21.036 --> 00:16:24.696
think there is a second thing,
unfortunately, that will be important

00:16:25.296 --> 00:16:28.976
as a junior developer, especially
if you wanna get a job next

00:16:29.056 --> 00:16:32.316
year, and that second thing is
that you will need connections

00:16:32.956 --> 00:16:36.756
and/or a strong social media presence or

00:16:36.876 --> 00:16:40.616
anything like that in addition to having a
good portfolio, a good

00:16:40.656 --> 00:16:44.536
resume, and so on because there
is this huge crowd of junior

00:16:44.616 --> 00:16:48.336
developers. I mean, look at this chart,
right? We're coming from here.

00:16:48.476 --> 00:16:51.396
Lots of people worked in the development
industry, lots of people

00:16:51.536 --> 00:16:55.136
started getting into it because there
was all this

00:16:55.156 --> 00:16:58.935
demand here and therefore,
all these people are

00:16:59.096 --> 00:17:02.175
still here today but there are less jobs.

00:17:02.185 --> 00:17:05.935
So in order to stand out from that crowd

00:17:06.036 --> 00:17:10.026
here, you will need something
that makes you stand out

00:17:10.215 --> 00:17:13.806
and for sure, that is proving
that you can work with AI,

00:17:13.836 --> 00:17:17.256
employers will want that,
but it will also be

00:17:17.435 --> 00:17:21.296
about, well, having connections,
having a strong social

00:17:21.316 --> 00:17:23.715
media presence, anything
that makes you stand out.

00:17:23.726 --> 00:17:27.616
And I know that these
are not great news because you wanna work

00:17:27.695 --> 00:17:30.416
not as an influencer. I totally get that.

00:17:30.536 --> 00:17:33.956
I just think that will be something
that will be needed to

00:17:33.996 --> 00:17:37.764
vastly improve your chances of getting

00:17:37.796 --> 00:17:41.264
that job. And again, you still need that

00:17:41.296 --> 00:17:45.136
portfolio and all that fun stuff, but
that will be important

00:17:45.196 --> 00:17:49.136
too. So that is the job market next

00:17:49.235 --> 00:17:52.936
year.
The last thing I wanna take a look at

00:17:53.016 --> 00:17:56.735
dev in general, so the fun part now.
Which trends do I see there?

00:17:56.755 --> 00:17:59.996
Which technologies, uh,
should you learn and use?

00:18:00.016 --> 00:18:03.076
And here, I would say we have one

00:18:03.136 --> 00:18:06.636
clear default stack, the standard

00:18:06.796 --> 00:18:10.766
stack you will use in most projects next
year and that

00:18:10.856 --> 00:18:13.596
is TypeScript, React,

00:18:14.016 --> 00:18:17.676
Next.js, Tailwind. That is

00:18:17.755 --> 00:18:21.636
AI's favorite right here. That
is what you get in

00:18:21.716 --> 00:18:25.636
most, uh, applications
if you just ask AI to generate something

00:18:25.716 --> 00:18:29.396
for you, some web app. Uh,
that will be important next year too.

00:18:29.436 --> 00:18:33.356
Now, by the way,
I of course have the JavaScript angle

00:18:33.396 --> 00:18:37.036
PHP world. Let me be very clear, PHP,
Laravel, all

00:18:37.156 --> 00:18:40.036
amazing technologies
which can land you jobs.

00:18:40.156 --> 00:18:43.456
I just have that JavaScript lens, which
is why I'm talking about that.

00:18:43.476 --> 00:18:46.456
But if we take a look at the

00:18:46.516 --> 00:18:50.136
ReactJS download numbers, for example,

00:18:50.216 --> 00:18:54.096
it's pretty clear to see that AI has a

00:18:54.156 --> 00:18:57.856
favorite here in web development in
general and especially the

00:18:57.916 --> 00:18:59.976
JavaScript web development world,
of course.

00:19:00.016 --> 00:19:03.786
So that is that default stack we'll have
next year.

00:19:03.796 --> 00:19:07.505
That is the stack
which you should learn

00:19:07.576 --> 00:19:11.366
are that most companies
or many companies will be using

00:19:11.396 --> 00:19:15.179
that. Now-If you have the luxury

00:19:15.260 --> 00:19:18.730
of deviating from
that because you're not looking for a job

00:19:18.760 --> 00:19:22.639
your own,
or because you wanna kind of expand your

00:19:22.679 --> 00:19:26.159
wanna have more than just one stack
that you bring to the table,

00:19:26.700 --> 00:19:30.639
I think for next year,
one interesting thing to dive into would

00:19:30.679 --> 00:19:34.000
an alternative to Next.js like React
Router or TanStack

00:19:34.159 --> 00:19:37.700
Start, which is amazing
and TanStack Start,

00:19:37.740 --> 00:19:41.610
especially something I wanna cover more
next year.

00:19:41.939 --> 00:19:45.700
I think it also might be interesting to
look at modern browser APIs

00:19:46.500 --> 00:19:50.269
like the, uh, Popover API, for example,
which I recently

00:19:50.300 --> 00:19:53.919
covered on my other, uh, channel
and I'll do more about

00:19:54.020 --> 00:19:58.000
and about CSS because a lot

00:19:58.080 --> 00:20:01.179
has improved here. Uh, raw

00:20:01.340 --> 00:20:05.240
CSS and also what the browser can do for
you has gotten

00:20:05.439 --> 00:20:08.220
so much better in the last two years.

00:20:08.260 --> 00:20:12.220
It's just that nobody noticed because of,
well, AI.

00:20:12.300 --> 00:20:16.120
It's the big thing
which takes all the attention but there

00:20:16.179 --> 00:20:20.000
has been such amazing development here
that you can get a

00:20:20.220 --> 00:20:24.100
lot done by just using what's built into
the browser which is available

00:20:24.379 --> 00:20:28.159
across all major browsers.
So it's production ready and/or

00:20:28.360 --> 00:20:32.320
by using modern CSS features like native,
uh,

00:20:32.360 --> 00:20:36.179
CSS nesting where you can write CSS code

00:20:36.220 --> 00:20:40.040
like this and it just works,
no compilation step needed, by

00:20:40.139 --> 00:20:43.860
using CSS layers to control precedence

00:20:43.870 --> 00:20:47.530
and much, much more. There's a lot of

00:20:47.580 --> 00:20:50.129
amazing stuff available in the browser
right now.

00:20:50.159 --> 00:20:53.639
It's also something I wanna teach more in
the next year

00:20:53.659 --> 00:20:56.899
to, well,
bring some more awareness to that

00:20:57.399 --> 00:21:01.340
because you might not need all those extra
libraries you're

00:21:01.379 --> 00:21:05.280
pulling into your project or all
that code that's being written

00:21:05.340 --> 00:21:08.879
to be wr-
you don't need to manage your own modals

00:21:08.980 --> 00:21:12.919
code and your own divs which
are then maybe not accessible

00:21:13.000 --> 00:21:16.800
or not always on top.
You can let the browser do a lot of that

00:21:16.860 --> 00:21:18.980
work and the result will be better.

00:21:19.000 --> 00:21:22.989
And then, of course,
I mentioned it before, you can build stuff

00:21:23.100 --> 00:21:26.820
with and on top of AI, on top of large

00:21:26.840 --> 00:21:30.600
language models,
image generation models and so on,

00:21:30.639 --> 00:21:34.460
There are all these opportunities, uh,
which you as a

00:21:34.480 --> 00:21:38.159
developer can try to take advantage of

00:21:38.280 --> 00:21:40.179
because you know how to write code.

00:21:40.220 --> 00:21:43.790
You can use AI to accelerate the
development

00:21:43.790 --> 00:21:47.440
process and, therefore,
you have these opportunities

00:21:47.540 --> 00:21:51.460
stuff on top of AI by using AI,
that can really also

00:21:51.480 --> 00:21:55.340
be an interesting area next year,
and I got exciting stuff to share next

00:21:55.379 --> 00:21:59.000
exciting content I'm working on and, um,
yeah, I'm,

00:21:59.020 --> 00:22:01.840
therefore,
really looking forward to the next year.

00:22:01.899 --> 00:22:05.659
I think it will be a better year there for
developers than 2025

00:22:05.720 --> 00:22:09.610
was to some extent.
Definitely still challenging,

00:22:09.659 --> 00:22:12.340
definitely also exciting, I think.