WEBVTT

00:00:00.260 --> 00:00:04.040
How important are tech stack choices by

00:00:04.080 --> 00:00:07.800
developers like you and me now in April

00:00:08.100 --> 00:00:11.640
2026 with all the things
that happened in the AI

00:00:11.760 --> 00:00:15.720
space and with all the advancements in the
AI models, and even

00:00:15.760 --> 00:00:19.580
more importantly, the AI agent harnesses,
the AI

00:00:19.760 --> 00:00:23.080
agent tools like Cloud Code and Codex
and so on?

00:00:23.140 --> 00:00:25.220
And I created videos about these tools.

00:00:25.520 --> 00:00:29.420
I have some courses on these tools,
in case you're interested, Cloud Code

00:00:29.460 --> 00:00:33.220
courses, which are very popular.
But the question today which I

00:00:33.320 --> 00:00:37.089
wanna take a closer look at it
and share my opinion on is, how

00:00:37.160 --> 00:00:40.960
important are tech stack choices by

00:00:41.200 --> 00:00:44.920
developers? Do they still matter,
or should we let the

00:00:44.980 --> 00:00:46.520
AI decide? Or,

00:00:47.400 --> 00:00:50.960
maybe more relevant,
should we make decisions

00:00:51.660 --> 00:00:54.900
based on the fact
that we're about to use AI?

00:00:54.980 --> 00:00:58.700
And I'll let you know what I mean. Now,
obviously, the- the

00:00:58.800 --> 00:01:02.140
most basic form of not caring about the
tech stack...

00:01:02.260 --> 00:01:06.200
And by the way,
I'll primarily focus on tech stack

00:01:06.260 --> 00:01:10.140
choices from the lens of web developers
because that is

00:01:10.180 --> 00:01:13.790
my main thing, web development,
but I guess it will

00:01:13.840 --> 00:01:17.780
apply to all kinds of developers. But the-
the easy

00:01:17.820 --> 00:01:21.740
path you could take is, of course,
that you may be using a

00:01:21.780 --> 00:01:25.660
tool like, let's say, Cloud Code,
doesn't matter, and you don't

00:01:25.700 --> 00:01:28.760
really care about the tech stack that's
being chosen.

00:01:28.840 --> 00:01:32.420
Who cares if you're using TypeScript and

00:01:32.640 --> 00:01:36.380
Next.js with React, or if you're using

00:01:36.500 --> 00:01:39.600
vanilla JavaScript and, let's say,

00:01:40.160 --> 00:01:44.100
TanStack Start,
or maybe you're using Angular instead of

00:01:44.140 --> 00:01:46.640
Who cares, right? Let the AI decide.

00:01:47.400 --> 00:01:51.180
Now, you could do that, of course,
but here, we enter the realm of

00:01:51.400 --> 00:01:55.080
white coding, obviously,
because we as developer

00:01:55.100 --> 00:01:58.800
don't make any choices.
And as soon as you stop

00:01:58.860 --> 00:02:02.080
making choices and decisions,
as soon as you stop

00:02:02.300 --> 00:02:03.990
steering the AI and

00:02:04.980 --> 00:02:08.769
caring about the code, you could say,
"That is my definition of

00:02:08.780 --> 00:02:12.690
white coding." But of course,
there would be one way of saying

00:02:12.740 --> 00:02:15.680
don't really matter anymore,
and I'll get back to that question.

00:02:15.960 --> 00:02:19.580
The- the other maybe more relevant aspect,

00:02:19.740 --> 00:02:20.010
though,

00:02:20.920 --> 00:02:22.060
is that you could argue

00:02:22.960 --> 00:02:26.580
that yes, you as a developer kind of still

00:02:26.780 --> 00:02:30.760
make a choice, but ultimately,
it's influenced

00:02:30.800 --> 00:02:34.700
by the fact that you're about to use AI to
help with the

00:02:34.720 --> 00:02:38.160
development process.
And you will review the code.

00:02:38.260 --> 00:02:40.140
You care about it.
You're not white coding.

00:02:40.210 --> 00:02:44.070
But still,
because you're about to use AI a

00:02:44.200 --> 00:02:48.180
lot, you use a tech stack you know AI
is good at.

00:02:48.540 --> 00:02:52.480
You use TypeScript,
you use Next.js with React, for example,

00:02:52.580 --> 00:02:56.120
because you know there's been a lot of
training data on that, and

00:02:56.560 --> 00:03:00.480
AI will do good at that. So, these
are the two

00:03:01.020 --> 00:03:04.200
main points here. We have the first

00:03:04.900 --> 00:03:08.840
way of not caring, which is let AI choose,
the white coding approach,

00:03:09.160 --> 00:03:12.860
and we have the second, uh, aspect,
which is that we let

00:03:12.920 --> 00:03:14.640
AI influence the choice.

00:03:16.520 --> 00:03:20.040
I would argue both approaches are

00:03:20.140 --> 00:03:23.380
kind of wrong and a bit shortsighted.

00:03:24.480 --> 00:03:26.420
I would argue, as a developer,

00:03:27.560 --> 00:03:31.500
it's more important than ever, maybe,
to have an

00:03:31.540 --> 00:03:35.460
opinion on the tech stack you're going to
work on, to make

00:03:35.560 --> 00:03:39.380
smart decisions and choices, because,
of course, the

00:03:39.500 --> 00:03:43.000
way we developers work is shifting, is

00:03:43.080 --> 00:03:46.240
changing. We are writing less code.

00:03:46.380 --> 00:03:50.280
I definitely write less code.
May be different for you.

00:03:50.300 --> 00:03:52.180
Maybe it will forever be different for
you.

00:03:52.200 --> 00:03:56.060
But as a industry as a whole,
it's clear to see

00:03:56.120 --> 00:03:59.960
that there is a big shift going on to
developers writing less

00:04:00.020 --> 00:04:03.780
code and instead orchestrating
and using these

00:04:03.860 --> 00:04:07.360
AI agents and tools. And that, of course,

00:04:08.220 --> 00:04:12.000
implies that it becomes even more
important which

00:04:12.020 --> 00:04:15.840
choices and decisions we make.
If you go down the

00:04:15.940 --> 00:04:17.079
white coding tunnel,

00:04:18.060 --> 00:04:21.320
if you let AI make the- the choices, th-

00:04:21.540 --> 00:04:22.240
decisions,

00:04:23.940 --> 00:04:27.690
that may not be a great future as a
developer, for obvious reasons,

00:04:27.780 --> 00:04:31.340
because who needs you if all you do is

00:04:31.360 --> 00:04:34.890
ask the AI without any opinions, without

00:04:35.000 --> 00:04:38.020
any influence on the code it will produce?

00:04:38.160 --> 00:04:40.040
Nobody needs a developer for that, right?

00:04:40.100 --> 00:04:43.500
So, that will not lead anywhere. Now,
that may be

00:04:44.320 --> 00:04:48.300
a- a decent,
a good approach for quickly building some

00:04:48.400 --> 00:04:52.280
building some internal application
that just needs to do

00:04:52.380 --> 00:04:56.080
one thing well and you don't care about
edge cases, niche cases, problem

00:04:56.140 --> 00:04:56.660
security.

00:04:57.560 --> 00:05:01.200
There are definitely use cases where this
may

00:05:01.360 --> 00:05:05.160
be a- a valid approach,
where you may just white code

00:05:05.260 --> 00:05:08.520
something. This also, of course,
may be very useful.

00:05:08.640 --> 00:05:12.560
White coding may be very useful for people
that don't know how to

00:05:12.620 --> 00:05:16.520
code but that can build some of the
software they need for

00:05:16.580 --> 00:05:20.540
themselves with ease.
With all the disadvantages white coding

00:05:20.620 --> 00:05:21.680
it has its-

00:05:22.560 --> 00:05:26.440
its- its purpose, I would say. There
are use cases where it may

00:05:26.520 --> 00:05:30.360
be a decent decision. But of course,
obviously,

00:05:30.400 --> 00:05:34.260
case, and the people
that do white code may not even know which

00:05:34.340 --> 00:05:38.060
options exist out there. Now,
when it comes to letting AI

00:05:38.140 --> 00:05:42.060
influence the choice, I would argue,
this may

00:05:42.240 --> 00:05:46.000
have been a valid argument maybe, like,
a year

00:05:46.080 --> 00:05:46.500
ago,

00:05:47.420 --> 00:05:51.340
may- maybe not even back then,
but definitely not anymore today,

00:05:51.420 --> 00:05:51.740
you why.

00:05:53.000 --> 00:05:56.180
Obviously, AI has a favorite stack.

00:05:56.280 --> 00:05:58.300
I've said that before in other videos.

00:05:58.360 --> 00:06:02.140
If you let AI run,
if you go down the white coding

00:06:02.220 --> 00:06:06.080
path, chances are pretty high,
if we're talking about web development,

00:06:06.460 --> 00:06:10.220
that you will get a TypeScript, React,
Next.js,

00:06:10.680 --> 00:06:12.932
Tailwind, uh, uh...... project, right?

00:06:13.602 --> 00:06:17.252
That's the favorite stack of AI,
and there are

00:06:17.352 --> 00:06:21.252
reasons for that. Obviously,
there have been a lot of React,

00:06:21.412 --> 00:06:24.512
Next.js,
Tailwind projects in the training data,

00:06:25.452 --> 00:06:29.172
depending on how we look at the training
data, if we include code

00:06:29.252 --> 00:06:32.732
from the 2010s, the early 2010 years,

00:06:33.212 --> 00:06:35.852
obviously there will not be any Tailwind
in there.

00:06:35.912 --> 00:06:39.602
There will be far fewer TypeScript
projects or no TypeScript

00:06:39.612 --> 00:06:43.112
projects in there, um,
no Next.js projects.

00:06:43.192 --> 00:06:46.832
So, obviously,
there would have been a lot of vanilla

00:06:47.032 --> 00:06:50.662
jQuery projects in that training data too,
and there definitely

00:06:50.772 --> 00:06:54.412
were. But the reason for
that not being the

00:06:54.492 --> 00:06:58.432
favorite tech stack of AI, of course,
is not just the amount

00:06:58.472 --> 00:07:01.372
of training data it saw, which matters,
but it's not the only thing.

00:07:01.732 --> 00:07:05.642
But it's also that these AI models,
as we use them, no

00:07:05.812 --> 00:07:09.532
matter by which provider,
they go through different stages.

00:07:09.592 --> 00:07:11.772
There is the pre-training str- stage.

00:07:11.792 --> 00:07:14.212
There is the fine-tuning,
the reinforcement learning stages.

00:07:14.252 --> 00:07:17.972
There are all these stages where the model
provider kind of

00:07:18.072 --> 00:07:20.392
shapes these models and their behavior.

00:07:20.732 --> 00:07:22.472
And then there are system prompts.

00:07:22.512 --> 00:07:26.132
If you're using a tool like Claude Code,
there is an

00:07:26.212 --> 00:07:29.312
invisible system prompt, more
or less invisible, that

00:07:29.392 --> 00:07:33.072
instructs the AI model to act in

00:07:33.192 --> 00:07:36.972
certain ways. And we already know,
we saw that, um,

00:07:37.372 --> 00:07:40.912
that these models have definitely been

00:07:41.032 --> 00:07:44.952
influenced to prefer certain technologies
like TypeScript and

00:07:45.032 --> 00:07:48.992
React. And why is that? That is because,
especially TypeScript,

00:07:49.032 --> 00:07:52.712
for example, is a language
that works pretty well for AI,

00:07:52.832 --> 00:07:56.512
because it is able to validate the

00:07:56.572 --> 00:07:59.792
code it produced by checking for type
errors.

00:08:00.052 --> 00:08:02.592
Obviously,
that's not the only way of validating.

00:08:02.672 --> 00:08:06.412
A type-error-free code base
is not necessarily a good code

00:08:06.452 --> 00:08:09.872
base and (laughs) not necessarily a code
base that works the way you want it to

00:08:09.892 --> 00:08:11.972
work, but it's a indicator.

00:08:12.902 --> 00:08:16.872
It tends to be better than vanilla
JavaScript as far

00:08:16.932 --> 00:08:20.712
as I know. So, these
are reasons why AI has the

00:08:20.772 --> 00:08:24.672
favorite tech stack
and why you may come to the conclusion

00:08:24.732 --> 00:08:28.612
a good idea to go with
that favorite tech stack

00:08:28.652 --> 00:08:30.472
or something closely related.

00:08:31.592 --> 00:08:35.432
For example, you may decide
that using vanilla JavaScript is not

00:08:35.472 --> 00:08:39.072
something you wanna do because you heard,
by me for example, that

00:08:39.152 --> 00:08:43.112
AI benefits from using type-safe languages
like

00:08:43.152 --> 00:08:43.712
TypeScript.

00:08:44.672 --> 00:08:47.752
And there may be some truth to that.
But in...

00:08:48.372 --> 00:08:51.252
At this point in time, in April 2026,

00:08:52.092 --> 00:08:56.032
it has been proven over and over again,
and it has been my experience too,

00:08:56.112 --> 00:08:59.872
that AI and these AI agents like Claude
Code are

00:08:59.932 --> 00:09:03.432
really good at picking up whichever tech
stack you

00:09:03.492 --> 00:09:07.452
throw at them. It used to be the case
that it is kind of annoying

00:09:07.492 --> 00:09:11.452
to, for example, work with libraries
or frameworks that are pretty

00:09:11.552 --> 00:09:15.452
new and where there hasn't been a lot of
data

00:09:15.512 --> 00:09:19.312
in the training data
or maybe no data at all,

00:09:19.432 --> 00:09:23.392
anymore. As a developer using AI,
you can obviously go

00:09:23.472 --> 00:09:26.032
to the docs of any library you wanna use.

00:09:26.192 --> 00:09:29.852
Let's say you wanna use the latest version
of Nuxt.js

00:09:29.952 --> 00:09:33.682
or you wanna use Svelte 5
or whatever it is,

00:09:34.332 --> 00:09:37.892
uh, TanStack Start, for example, which
is relatively new.

00:09:38.972 --> 00:09:42.192
You can go to the docs of these projects,
and you can

00:09:42.612 --> 00:09:46.212
pick the relevant articles
and just throw them into the

00:09:46.272 --> 00:09:50.172
context of your current chat session so
that the AI is aware of

00:09:50.252 --> 00:09:54.192
this documentation.
And it will be able to pick up on the code

00:09:54.232 --> 00:09:58.052
examples and the explanation it sees there
and apply that to

00:09:58.112 --> 00:10:01.112
your code base. So you can absolutely

00:10:01.352 --> 00:10:05.272
use very new libraries
that may not have been

00:10:05.332 --> 00:10:09.192
in the,
in the training data in your project

00:10:09.252 --> 00:10:11.652
typically don't even have to go to the
docs and

00:10:12.532 --> 00:10:16.492
choose them manually. Instead,
if you just have a specific enough

00:10:16.512 --> 00:10:18.652
prompt where you tell it
that you wanna use

00:10:19.572 --> 00:10:23.312
a library, let's say TanStack Start,
and you tell the AI that it should go

00:10:23.432 --> 00:10:27.152
lo- look at the docs,
and you maybe gave it a c- uh, an

00:10:27.252 --> 00:10:31.092
MCP like the Context-7 MCP or the

00:10:31.272 --> 00:10:34.692
AI agents like Claude Code and so on,
they also have web search, you

00:10:34.762 --> 00:10:38.672
trust that it does a web search
and finds the relevant

00:10:38.732 --> 00:10:42.712
documentation. And you can, of course,
influence that by using skills,

00:10:43.572 --> 00:10:47.352
Uh, for example, I have a,
a code research skill where I

00:10:47.412 --> 00:10:51.372
tell the AI that for certain prompts I may
be

00:10:51.492 --> 00:10:55.332
using, it should take a look at
that skill, and in that skill,

00:10:55.372 --> 00:10:58.652
how it should look up docs.
So you may have stuff like that.

00:10:58.852 --> 00:11:02.052
And if you do have that,
you typically don't have to include

00:11:02.072 --> 00:11:05.872
documentation yourself. Uh, instead,
the AI can look

00:11:05.972 --> 00:11:09.752
for it on its own and include it
and pull in the relevant documentation as

00:11:09.952 --> 00:11:13.932
it needs to. And, shocking, of course,
as a developer you can also still

00:11:13.992 --> 00:11:17.652
write code. And it, it turns out that
if you

00:11:18.152 --> 00:11:19.002
have a project,

00:11:20.172 --> 00:11:23.212
AI tends to kind of

00:11:23.472 --> 00:11:27.192
replicate what's already in there
regarding code

00:11:27.272 --> 00:11:31.072
style, for example. So
if you have a project,

00:11:31.112 --> 00:11:35.002
maybe you already created some functions
in there, some routes

00:11:35.192 --> 00:11:38.812
already, anything like
that where you may be using

00:11:38.852 --> 00:11:42.842
Nuxt.js or TanStack Start
or whatever it is, the AI will

00:11:42.872 --> 00:11:46.192
pick up on that.
And it will not suddenly start using

00:11:46.252 --> 00:11:49.812
Next.js syntax and features in that

00:11:49.852 --> 00:11:51.872
TanStack Start project typically.

00:11:51.912 --> 00:11:54.992
So all these things combined,
existing code,

00:11:55.342 --> 00:11:57.500
uh..Pulling in the right context,

00:11:58.340 --> 00:12:02.100
nudging the AI at, uh, to-
towards looking up

00:12:02.140 --> 00:12:05.380
documentation and including that,
all these things together make it

00:12:05.720 --> 00:12:09.670
really easy these days, um,
to work with libraries

00:12:09.740 --> 00:12:13.310
or a tech stack in general that
is not the default

00:12:13.400 --> 00:12:17.380
and that may include certain technologies
that are not well-known by

00:12:17.440 --> 00:12:21.090
AI. That has been my experience.
I read a lot on X by other

00:12:21.180 --> 00:12:24.720
people where the experience has been kind
of similar, so that

00:12:24.860 --> 00:12:28.620
definitely works today. Maybe that
was different a year ago, but

00:12:28.680 --> 00:12:32.560
it's absolutely viable today. And
that kind of brings me back to

00:12:32.640 --> 00:12:36.440
my original question:
Does the tech stack choice

00:12:36.500 --> 00:12:40.320
still matter? Because, of course,
it's great that you can make a choice,

00:12:40.420 --> 00:12:44.360
that you are not forced to take one of
these two routes, right?

00:12:44.760 --> 00:12:48.720
That is great. But does it matter?
And I would argue, yes, it matters a

00:12:48.820 --> 00:12:52.490
lot. As I said initially, that
is one of the things that

00:12:52.580 --> 00:12:55.530
sets a developer apart from
non-developers.

00:12:55.640 --> 00:12:57.440
Not the only thing, but a thing.

00:12:58.400 --> 00:13:02.080
Different projects benefit from different
tech stack

00:13:02.140 --> 00:13:05.990
choices. And yes, theoretically,
you can build anything

00:13:06.020 --> 00:13:09.760
with any tech stack
or with most tech stacks, and often it may

00:13:09.820 --> 00:13:13.810
not matter, but it can matter. If you
are working on

00:13:13.820 --> 00:13:17.740
some project where performance is key,
and I don't mean the performance

00:13:17.780 --> 00:13:21.540
for your 10 users, I mean for, uh,
bigger projects where performance

00:13:21.680 --> 00:13:25.560
really will matter,
you may prefer to go for a

00:13:25.680 --> 00:13:29.620
backend language like Go, for example,
because you

00:13:29.680 --> 00:13:33.500
want better performance,
a better memory footprint than you maybe

00:13:33.560 --> 00:13:37.520
with, let's say, TypeScript.
That being said, just to

00:13:37.540 --> 00:13:38.480
also have that in there,

00:13:39.660 --> 00:13:43.540
there is no reason to over-optimize
if you're just building something and you

00:13:43.620 --> 00:13:45.560
don't even know how many users you'll
have.

00:13:45.640 --> 00:13:49.580
If you ever reach the point where your
application chokes under

00:13:49.620 --> 00:13:51.860
the load, you can always rewrite it.

00:13:52.200 --> 00:13:55.320
That also is easier than ever now with AI.

00:13:55.460 --> 00:13:58.700
But yeah,
those choices obviously still matter.

00:13:59.620 --> 00:14:01.800
It also matters what you, as a developer,
know.

00:14:02.240 --> 00:14:06.220
If you are really good in Angular,
let's say, there's no

00:14:06.400 --> 00:14:09.160
reason to build a React application.

00:14:09.180 --> 00:14:13.040
Because, as a developer,
you still wanna understand and

00:14:13.080 --> 00:14:16.520
review the code and get in there
and write some code hi- here and there

00:14:16.580 --> 00:14:19.560
to, again, get AI to move into the right

00:14:19.680 --> 00:14:22.920
direction.
We don't wanna become white coders.

00:14:22.960 --> 00:14:26.470
Instead,
we wanna leverage our knowledge

00:14:26.520 --> 00:14:30.080
enhance it or leverage it, yeah, with AI.

00:14:30.160 --> 00:14:34.040
So obviously,
if you know something really well, that

00:14:34.060 --> 00:14:37.920
reason to go with
that technological choice, with

00:14:38.000 --> 00:14:40.610
library, programming language, whatever it

00:14:40.640 --> 00:14:44.080
is. And therefore, yes, tech stack

00:14:44.120 --> 00:14:47.910
choices do matter,
and different languages, different

00:14:48.020 --> 00:14:51.580
frameworks, libraries, they have pur-
purposes.

00:14:51.600 --> 00:14:55.140
They have a reason to exist. Now,
you could definitely make the

00:14:55.220 --> 00:14:56.820
argument that

00:14:58.180 --> 00:15:01.940
there are some changes going on there
because maybe, like,

00:15:01.960 --> 00:15:05.460
five or six years ago, a new JavaScript

00:15:05.520 --> 00:15:09.460
library may have appeared. You know,
back then, we had new

00:15:09.520 --> 00:15:12.920
JavaScript libraries almost every week,
it felt like.

00:15:13.000 --> 00:15:15.860
Uh, a new library may have come up because

00:15:16.720 --> 00:15:19.640
it provided better developer ergonomics.

00:15:20.140 --> 00:15:23.320
That may not be as relevant today anymore.

00:15:23.360 --> 00:15:26.600
Today, you could argue, uh,
a new library could come up

00:15:26.880 --> 00:15:30.760
because it's easier to use by agents,
because

00:15:30.880 --> 00:15:34.460
it does something
that makes it particularly

00:15:34.640 --> 00:15:38.310
easy to be used by agents
while still being readable and

00:15:38.360 --> 00:15:40.500
understandable by humans too, of course.

00:15:40.840 --> 00:15:44.200
But yeah, I definitely could see a sh-
a shift like this happening.

00:15:44.730 --> 00:15:48.320
And some reasons for why you might have
chosen a certain

00:15:48.380 --> 00:15:52.260
library or framework
or programming language in the past may

00:15:52.320 --> 00:15:55.780
not matter anymore because you
are writing less code.

00:15:56.420 --> 00:16:00.220
Still, for me personally, at least,
and I have the luxury of

00:16:00.260 --> 00:16:04.120
being able to make a lot of tech stack
choices for my own projects, obviously,

00:16:04.180 --> 00:16:07.680
so for me, aesthetics still matter, for

00:16:07.700 --> 00:16:11.540
example.
I still wanna work with a tech stack,

00:16:12.140 --> 00:16:16.020
I enjoy looking at the code because I'm,
I'm looking at a lot of code.

00:16:16.080 --> 00:16:19.700
I'm reviewing a lot of code,
so I want to look at

00:16:19.760 --> 00:16:22.880
something I- I- I like seeing, right?

00:16:23.260 --> 00:16:27.180
So yeah, tech stack choices,
in my opinion, still

00:16:27.280 --> 00:16:30.940
matter.
The reasons may have changed a bit and,

00:16:31.040 --> 00:16:34.370
the,
the impact of choosing certain

00:16:34.980 --> 00:16:37.840
uh, but it's an important choice,
in my opinion.

00:16:38.080 --> 00:16:41.990
And of course, as always,
I am also interested in hearing your

00:16:42.020 --> 00:16:42.210
that.