TRANSKRİPT 🔗
WEBVTT
1
00:00:07.519 --> 00:00:12.160
Welcome to the Angular Plus Show.
We're app developers of all kinds share their
2
00:00:12.199 --> 00:00:19.559
insights and experiences. Let's get started. This episode sponsored by betove. Hey,
3
00:00:19.640 --> 00:00:23.079
it's Jennifer Widella, Angular GDE,
co host of The Angular Plus Show
4
00:00:23.079 --> 00:00:26.280
and director of Angular Development at Petobe. I hope you're learning a lot from
5
00:00:26.320 --> 00:00:28.960
the Angular Plus Show, but if
you ever need help dealing with the complex
6
00:00:28.960 --> 00:00:32.119
software engineering problems that arise, my
team at betove would love to help.
7
00:00:32.240 --> 00:00:36.159
From offering staff augmentation to providing senior
engineering leadership, we're here to help your
8
00:00:36.159 --> 00:00:39.079
project succeed. You can check us
out at beetoby dot com. Read some
9
00:00:39.119 --> 00:00:42.479
helpful articles on our blog, join
our discord for real time debugging help,
10
00:00:42.560 --> 00:00:45.920
or email me at Jennifer at potoby
dot com for anything else you may need.
11
00:00:46.119 --> 00:00:53.840
Happy coding. Welcome back, everyone
to another episode of the Angler plus
12
00:00:53.840 --> 00:01:00.759
Show, where we talk about Angular
and Angular adjacent topics. Today. I'm
13
00:01:00.840 --> 00:01:03.319
Jay, one of your hosts.
Today. I have with me Joe Joe
14
00:01:03.359 --> 00:01:07.200
Eames. How's it going, Joe, Oh, I'm doing really well.
15
00:01:07.200 --> 00:01:11.359
Thanks good good. I heard you're
back in the Land of the Free.
16
00:01:11.159 --> 00:01:15.640
Yes, yep. Spent a few
months in Germany just a little bit north
17
00:01:15.719 --> 00:01:22.680
of our guest and then came home
in November. Nice. Nice, that
18
00:01:22.680 --> 00:01:25.159
sounds awesome. I've never actually been
to Germany, but I really want to
19
00:01:25.200 --> 00:01:26.760
go over there. I studied in
Sweden for a while, so I was
20
00:01:26.799 --> 00:01:34.000
like close in terms of not being
in Canada is massive, but never actually
21
00:01:34.000 --> 00:01:38.920
made it over in Germany yet.
Yeah. We'll definitely put it on your
22
00:01:38.920 --> 00:01:42.719
list absolutely. And then we have
our guest with us, Michael Hackey.
23
00:01:42.760 --> 00:01:46.280
How's it going? Michael, Hello, Hello, it's going very well.
24
00:01:47.079 --> 00:01:51.159
Good. Good. So today we're
going to be chatting about you were doing
25
00:01:51.200 --> 00:01:55.719
two different workshops right at Angie comp
this year and NGI komp is happening from
26
00:01:55.840 --> 00:02:00.480
the Joe eighteenth to twenty first correct
eighteen and nineteen workshops and then twenty one
27
00:02:00.480 --> 00:02:05.400
our sessions. You got it?
Yeah? Cool? And then Michael,
28
00:02:05.400 --> 00:02:07.400
I, assuming you're doing one each
day, right, You're not doing two
29
00:02:07.400 --> 00:02:10.039
in one day. That would be
crazy. It's like one of those sitcoms
30
00:02:10.039 --> 00:02:15.520
where you have two dates you run
back and forth between the two. Oh
31
00:02:15.560 --> 00:02:19.879
man, I haven't seen that,
see like that in a wild classic.
32
00:02:21.439 --> 00:02:23.800
So Michael, why don't you tell
us what your two workshops are on you're
33
00:02:23.879 --> 00:02:30.599
known as the performance guy in the
world. One of the things about performance,
34
00:02:32.199 --> 00:02:38.360
Yeah, it should give us a
very good overview of a couple of
35
00:02:38.360 --> 00:02:43.960
different areas in performance and a lot
of practical, practical tips that you can
36
00:02:44.039 --> 00:02:47.680
use basically on any device. That's
one of the two workshops and the second
37
00:02:47.719 --> 00:02:52.639
one, I guess the performance one
is on the second workshop day. On
38
00:02:52.680 --> 00:02:57.919
the first workshop day is the n
X for Scalable Angle Architecture workshop, And
39
00:02:57.960 --> 00:03:01.599
it should help you to how to
say, get the best out of this
40
00:03:01.719 --> 00:03:06.759
wonderful tool. You can do a
lot with it, Like I will not
41
00:03:06.840 --> 00:03:09.960
only focus it on on a mono
repo usage, but we would also learn
42
00:03:10.000 --> 00:03:14.319
a couple of tricks, like how
you can develop libraries. It's a library
43
00:03:14.360 --> 00:03:16.400
developer for Angular. It helps a
lot of tooling and so on and so
44
00:03:16.439 --> 00:03:23.879
forth. Also brought overview plus a
lot of practical tips and tricks like in
45
00:03:23.919 --> 00:03:30.759
the exercises how you can leverage the
tools for the best the X nice.
46
00:03:30.000 --> 00:03:36.039
Yeah, I've been involved in the
NX you know, community and ecosystem since
47
00:03:36.159 --> 00:03:40.879
like version six or I don't know, something like that, right, and
48
00:03:42.919 --> 00:03:47.159
it's gotten so big and so featureful
that I just don't even know everything it
49
00:03:47.199 --> 00:03:52.680
does anymore. It's absolutely crazy.
Like back in the back and back in
50
00:03:52.719 --> 00:03:55.120
my day, it was, you
know, a mono repo tool that had
51
00:03:55.159 --> 00:04:00.000
you know the back then, they
weren't even called general or executors in generator
52
00:04:00.159 --> 00:04:01.599
is. They were whatever the terminology
of angerousy a lot uses, right,
53
00:04:02.280 --> 00:04:09.840
and it's just there's so much there
now. Yeah, they also had a
54
00:04:09.840 --> 00:04:15.680
lot of evolvements I would say,
or innovations mm hmm, and releases.
55
00:04:15.639 --> 00:04:21.439
Yes, the last two they started
to really reflector from a data driven like
56
00:04:21.560 --> 00:04:28.439
you have this n ex chasing file
chasing driven configuration to a more dynamic configuration.
57
00:04:29.519 --> 00:04:33.759
And it's really cool, like you
you basically remove a lot of oiler
58
00:04:33.759 --> 00:04:36.879
plate in a configuration I would call
Load full transcript
it. You can be way more dynamic.
59
00:04:38.839 --> 00:04:45.439
All those refactorings and these dynamic configurations
can hook into all the different graphs
60
00:04:45.439 --> 00:04:48.000
they have, right, they have
a project graph, they have a task
61
00:04:48.120 --> 00:04:53.480
graph. You can really leverage more
and more of those things in a very
62
00:04:53.680 --> 00:05:00.120
dynamic way. That is wonderful,
I believe. Yeah, Project Inference API,
63
00:05:00.199 --> 00:05:04.000
which I think just reached V two
maybe not just I don't know.
64
00:05:04.360 --> 00:05:08.759
It's in V two now and it's
I've been using it recently and it is
65
00:05:08.839 --> 00:05:14.680
fantastic. So hopefully you're going to
talk about the the inference and the you
66
00:05:14.720 --> 00:05:18.480
know, I think they're calling it. Uh, there's a term they used
67
00:05:18.480 --> 00:05:25.160
for removing the configuration. It wasn't
configuration free, it was like negative configuration.
68
00:05:25.399 --> 00:05:27.079
I don't know. It was a
term that they used a long time
69
00:05:27.079 --> 00:05:32.079
ago, but something like this I
can't remember. But let's let's boiler plate
70
00:05:32.279 --> 00:05:39.959
which sounds yes, that's all the
V two changes in the in this schema.
71
00:05:41.040 --> 00:05:46.000
Yeah. And another thing that jumps
in my head when we speak about
72
00:05:46.000 --> 00:05:50.959
the recent scence. They have a
release command now that's pretty pretty new,
73
00:05:51.519 --> 00:05:57.160
not fully stable from from all the
age cases we tasted, but really decent
74
00:05:57.240 --> 00:06:02.720
already. And and a documentation is
missing I believe, I remember. It's
75
00:06:02.759 --> 00:06:06.439
just a documentation that is may could
maybe get a little bit, but it
76
00:06:06.519 --> 00:06:13.560
is wonderful. Michael tell us a
little bit about the release command. So
77
00:06:13.720 --> 00:06:17.199
in general, for example, if
you write the library, you want a
78
00:06:17.279 --> 00:06:23.720
version that library and under a semantic
version ing, and you know you have
79
00:06:23.800 --> 00:06:30.639
this patch major MANA and fixed version, and this is how you drive it
80
00:06:30.680 --> 00:06:33.040
by the number. But when you
want a ship, when you want to
81
00:06:33.040 --> 00:06:40.319
continuously release the software, you don't
want to normally want to do that manually
82
00:06:40.399 --> 00:06:43.399
all the time, right, you
don't want to bump the version here,
83
00:06:43.560 --> 00:06:46.800
go to all other dependency packages,
bump the version there too. That is
84
00:06:46.839 --> 00:06:49.439
a lot of and there is an
error prone process if you do it manually.
85
00:06:50.240 --> 00:06:54.240
I mean, I just try to
make a little bit of historical context
86
00:06:54.279 --> 00:07:00.000
why this release thing is anyway a
topic, so then you can look back.
87
00:07:00.079 --> 00:07:03.199
And there was already this conventional commit
style where you can say I read
88
00:07:03.240 --> 00:07:08.600
my commits in a certain style,
and I can I can flag a commit
89
00:07:08.839 --> 00:07:12.720
that will break the version, and
I can say, this will just bump
90
00:07:12.800 --> 00:07:15.879
the majure sorry, the minor version
or the fixed version. So I could
91
00:07:15.959 --> 00:07:23.360
with with commit messages, determine which
version would be the next version when I
92
00:07:23.439 --> 00:07:28.040
merged the code change, and you
could look at the committee story then and
93
00:07:28.120 --> 00:07:33.519
automatically derive the next version from it
and automatically increase that. And if you're
94
00:07:33.519 --> 00:07:38.839
done with this, you have to
again go through all dependencies or packages and
95
00:07:38.879 --> 00:07:43.399
see if you need to update something. And that is that was done with
96
00:07:43.480 --> 00:07:46.079
a couple of other plugins in the
past. Is still done with this,
97
00:07:46.279 --> 00:07:50.959
but it seems with the with the
release a comment, it will get more
98
00:07:51.000 --> 00:07:55.399
feature reached. In the future,
they want to take over this whole process,
99
00:07:55.600 --> 00:08:00.000
which is it's a lot in its
cluttery and uh, but it gives
100
00:08:00.000 --> 00:08:03.199
a lot of benefits. So therefore
I'm so excited that they started to work
101
00:08:03.240 --> 00:08:09.560
on that. Well, and you
know, back in the day, Learner
102
00:08:09.720 --> 00:08:13.759
had this right and then Annex took
over stewardship of Learner and they've kind of
103
00:08:13.759 --> 00:08:20.240
been integrating the two tools together more. Right, Well, I believe I'm
104
00:08:20.279 --> 00:08:24.680
not a fully expert with Learner,
but they took over the maintenance. Learner
105
00:08:24.800 --> 00:08:31.560
is still Learner. They what they
did with the with the code base is
106
00:08:31.639 --> 00:08:37.120
they basically implemented caching, thestreputer caching, and then a couple of other features
107
00:08:37.159 --> 00:08:41.360
that would be applicable in that area. So pimped it up a little bit
108
00:08:41.879 --> 00:08:46.480
in terms of speed, and that
kept the code based, keptval philosophy of
109
00:08:48.679 --> 00:08:56.080
bigling and bundling. And yeah,
therefore, I'm really really interested what will
110
00:08:56.080 --> 00:09:01.200
happen in the future with all those
comments combination, like with all the different
111
00:09:01.240 --> 00:09:07.559
steps that I said and the releasing
in combination, it will also help us
112
00:09:07.600 --> 00:09:13.480
most probably to get rid or integrate
better with up to date package chasing.
113
00:09:13.639 --> 00:09:16.639
At the moment, it is a
LinkedIn rule. It's good it can fix
114
00:09:16.720 --> 00:09:20.679
already and update the packages. But
maybe if this is also automatically integrated in
115
00:09:20.679 --> 00:09:26.679
the process, it
would it would
be an even better experience. So let's
116
00:09:26.679 --> 00:09:31.759
see. I'm curious what the next
year brings. So I'm kind of curious
117
00:09:33.080 --> 00:09:35.840
to ask a more general question here, Michael, Like, you've always been
118
00:09:35.840 --> 00:09:39.480
known as the performance guy, but
you're teaching a workshop on an AX.
119
00:09:39.600 --> 00:09:48.679
So why an X? Why is
it a really big passion area for you?
120
00:09:48.240 --> 00:09:52.279
Is it something you've done a lot
of work with. Why is it
121
00:09:52.519 --> 00:09:56.279
that you decided to get more in
the NX to start teaching workshops on it.
122
00:09:56.279 --> 00:10:01.399
It's a wonderful question, so I
use it from the beginning. I'm
123
00:10:01.840 --> 00:10:07.159
I'm sold from the beginning. I
just believe that the tooling is wonderful,
124
00:10:07.440 --> 00:10:13.480
and it started with a very small
scope with only one of support the framework
125
00:10:13.480 --> 00:10:16.960
out of the box angular. I
guess the first the first first thing,
126
00:10:18.080 --> 00:10:26.639
right, why they really managed to
get so much better with continuous upgrades with
127
00:10:26.559 --> 00:10:31.639
linding, with these with rules,
and I have an interesting, let's say,
128
00:10:31.679 --> 00:10:37.799
relationship to the tool because I worked
more with libraries than within MONOLAP was
129
00:10:37.879 --> 00:10:41.799
with that tool. When I would
count all the coding time that I had,
130
00:10:41.840 --> 00:10:43.519
it would be way more on the
library set. It is like it's
131
00:10:43.679 --> 00:10:50.799
a funny, interesting thing. So
that's my private interest. But our company,
132
00:10:50.879 --> 00:10:56.120
push based is using it a lot
in pretty much any any project.
133
00:10:56.200 --> 00:11:01.360
We have basically two main focus areas. We have the performance area and we
134
00:11:01.399 --> 00:11:07.200
have the architecture area, and a
lot of the the built architecture, tooling
135
00:11:07.240 --> 00:11:13.759
and also code architecture you can help
with with an AX A lot you can.
136
00:11:15.279 --> 00:11:20.240
You can implement different linking rules,
you can structure the code or the
137
00:11:20.360 --> 00:11:26.360
tooling very well, or the helper
snippets. You know, it's really a
138
00:11:26.399 --> 00:11:33.080
wonderful way to organize a code base
that is only from the architecture perspective.
139
00:11:33.320 --> 00:11:35.559
But what you do is we often
do a mix, right. We say,
140
00:11:35.600 --> 00:11:41.840
like, if we run anyway a
performance audit for your front end and
141
00:11:43.159 --> 00:11:45.759
all that stuff and all the code
that you gave us, why shouldn't we
142
00:11:45.840 --> 00:11:48.440
have a quick look on your on
your back end tour maybe not in a
143
00:11:48.440 --> 00:11:52.639
back sorry, on your tool chain
on your CI. And this is also
144
00:11:52.639 --> 00:11:58.799
where we do optimizations, performance optimizations
in beat speed in how fast you can
145
00:12:00.080 --> 00:12:07.159
liver? We optimize the processing your
team also, and DC is another patient
146
00:12:07.360 --> 00:12:11.679
area I would say, did we
focused on for quite a while. Yeah,
147
00:12:11.720 --> 00:12:16.480
that's awesome. Anecdotally, I couldn't
even imagine developing without NX. You
148
00:12:16.480 --> 00:12:22.919
know, I'm a relatively young,
you know, software engineer, right,
149
00:12:22.960 --> 00:12:26.759
I haven't been in the game for
a very long time. But the horror
150
00:12:26.840 --> 00:12:31.799
stories that I've heard of pre pre
NX, I don't envy all of you
151
00:12:31.960 --> 00:12:35.080
that may have been around for one
or two more years than me. All
152
00:12:35.200 --> 00:12:37.120
Right, Can I be a little
contrarion here for a second. Okay,
153
00:12:37.200 --> 00:12:41.840
let's hear it, Joe. I
actually love the concepts of of NX,
154
00:12:43.919 --> 00:12:48.679
but I had a relatively tough time
when I tried to play around with NX
155
00:12:48.679 --> 00:12:52.399
myself. Interesting, So I have
a little project, little side project that
156
00:12:52.480 --> 00:12:56.480
I work on. It's an angular
front end and a node back end,
157
00:12:56.320 --> 00:13:01.320
and I was working on it,
decided Hey, I'm going to learn NX,
158
00:13:01.360 --> 00:13:03.960
and I threw it ano NX.
And then as I got to started
159
00:13:05.000 --> 00:13:07.200
coding a little bit, I said
to myself, Oh, I want to
160
00:13:07.200 --> 00:13:11.600
throw tailwood into this, right,
So I go to put telwin in,
161
00:13:11.480 --> 00:13:16.840
but Telwan's installation instructions are only set
for if you're just running a regular Angler
162
00:13:16.879 --> 00:13:22.039
project, not an NX angular project. Well, okay, so I look
163
00:13:22.080 --> 00:13:26.080
around and I can't find how to
do it with NX. Man. I
164
00:13:26.159 --> 00:13:33.399
must have spent four hours before I
finally got our tailwind up and running in
165
00:13:33.600 --> 00:13:37.519
NX And it was like and it
was painful work. Right. There's the
166
00:13:37.600 --> 00:13:39.159
joy of programming when you code and
you build stuff, and then there's the
167
00:13:39.159 --> 00:13:43.440
pain part of it programming where you're
trying to just configure a freaking tool to
168
00:13:43.480 --> 00:13:48.000
work correctly. And you know,
telmends was pretty propular. This is just
169
00:13:48.039 --> 00:13:50.960
like a year and a half ago. It was a very popular project.
170
00:13:50.000 --> 00:13:54.279
So it wasn't like it was something
strange and weird. And I've got this
171
00:13:54.360 --> 00:14:01.000
sensation or this sense that hey,
if this isn't something that NX natively has
172
00:14:01.039 --> 00:14:03.759
already come through and said hey,
we now have the support for it,
173
00:14:03.919 --> 00:14:05.840
and you want to bring something into
a project that is one
of those things
174
00:14:05.840 --> 00:14:11.720
that it would be very challenging.
What would you say to that experience,
175
00:14:13.600 --> 00:14:20.759
I would say that sounds not super
terrible cold you manage that that is the
176
00:14:20.799 --> 00:14:26.159
good part of the story. But
yeah, obviously not all things are supported.
177
00:14:28.279 --> 00:14:35.440
But like you can take you let's
say, not natively integrated things all
178
00:14:35.480 --> 00:14:39.639
with a couple of different things,
right, you can in the most primitive
179
00:14:39.639 --> 00:14:43.120
way that I would say that the
tailing integration in angle is maybe not the
180
00:14:43.120 --> 00:14:48.240
most trivial. But let's say,
just moving some MPM scripts that are running
181
00:14:48.240 --> 00:14:50.639
GARP. You don't want to reflect
that the whole code is. You can
182
00:14:50.759 --> 00:14:54.960
just like put this script there,
a custom comment you can write also custom
183
00:14:56.080 --> 00:15:01.480
generators that help you to do that
work. And now this is how you
184
00:15:01.480 --> 00:15:09.799
can, let's say, professionally implement
any type of frame work or library that
185
00:15:09.840 --> 00:15:13.159
you want to work with. Of
course, to quickly get started, it
186
00:15:13.200 --> 00:15:16.679
does not pay off to start with
writing your own executor and that stuff you
187
00:15:16.720 --> 00:15:20.360
want to have quickly a custom comment
that put your MPM script stare that we're
188
00:15:20.399 --> 00:15:28.039
working before already and credible on Jay, Do you have anything else to chip
189
00:15:28.080 --> 00:15:33.840
in from the side of completely valid
issues that you ran into, right,
190
00:15:33.919 --> 00:15:37.440
Like, like we were talking about
earlier, NX is massive at this point,
191
00:15:37.480 --> 00:15:45.159
right, and it supports dozens of
frameworks first party and then like more's
192
00:15:45.600 --> 00:15:50.480
third party. Right, A lot
of the times, if it's a first
193
00:15:50.480 --> 00:15:52.440
party thing, there's a generator of
some sort to do the thing that you
194
00:15:52.440 --> 00:15:56.519
want to do. So there's probably
a set up tailwind generator, right that
195
00:15:56.600 --> 00:16:00.159
sets it up in the A or
sorry nothing the NX way. One thing
196
00:16:00.159 --> 00:16:03.720
I wanted to point out for anybody
and our listeners that are running into the
197
00:16:03.720 --> 00:16:10.080
same issues that Joe is NX has
an AI chatbot now and you can ask
198
00:16:10.159 --> 00:16:14.600
it like how do I set up
tailwind in my NX angular project, and
199
00:16:14.639 --> 00:16:19.600
it'll tell you and then quote sources
and give you links to the documentation for
200
00:16:19.759 --> 00:16:25.960
say the at NX slash Angular set
up tailwind generator for example. Right.
201
00:16:27.279 --> 00:16:32.759
You know, documentation is hard.
We all know that rights as developers and
202
00:16:32.799 --> 00:16:36.639
engineers, and Michael's a library author, right, Like getting docs right is
203
00:16:36.720 --> 00:16:41.559
hard because every person using your product
is different, different skill sets, different
204
00:16:41.559 --> 00:16:45.960
skill levels. Right, So completely
valid concerns Joe, I've done the exact
205
00:16:47.000 --> 00:16:51.039
same thing before. I know they're
working on it, and docs are one
206
00:16:51.080 --> 00:16:53.879
of the things that they like.
The nxtam actually doesn't really care. They
207
00:16:53.919 --> 00:16:59.240
just have such a massive skill right, So if anybody's having issues, I
208
00:16:59.279 --> 00:17:00.519
use the A chap now when I
go to the when I go to the
209
00:17:00.559 --> 00:17:04.880
docks, unless I know, say, exactly what generator I'm looking for or
210
00:17:04.920 --> 00:17:08.279
what executor, I'm just like,
oh, what what prams are available for
211
00:17:08.319 --> 00:17:11.480
this one? But I know where
I'm going. If I don't know that,
212
00:17:11.799 --> 00:17:15.480
I use the AI chatbot and then
go from there because it just searches
213
00:17:15.480 --> 00:17:18.319
the docks for you. And if
it doesn't, if the dogs don't have
214
00:17:18.400 --> 00:17:21.599
the thing, like, if there
is no set up tail wind generator,
215
00:17:22.200 --> 00:17:26.799
then then you'll know right away,
right, So don't blame you at all
216
00:17:27.079 --> 00:17:32.519
for the frustration. And to be
fair, right like, tailwind is one
217
00:17:32.559 --> 00:17:34.599
of the worst tools to try.
It it's a great tool, it's just
218
00:17:34.599 --> 00:17:38.039
worse to try to integrate because it
has to be incorporated into the build process
219
00:17:38.519 --> 00:17:41.519
in a really weird fashion. So
you got you got a muck with the
220
00:17:41.559 --> 00:17:45.519
build process. And that's why you
can't set up tailwind on an Angular project
221
00:17:45.519 --> 00:17:51.440
without a pre built builder in there
or being you know, a super expert
222
00:17:51.480 --> 00:17:53.880
in the Angular build process because it
is complex the way that it runs.
223
00:17:53.920 --> 00:17:57.640
So it's it's actually like one of
the worst kinds of tools to try to
224
00:17:57.720 --> 00:18:02.720
integrate into a project. Most other
things you're going to bring in like I
225
00:18:02.759 --> 00:18:04.519
want this library that does this or
this library that does this, doesn't change
226
00:18:04.519 --> 00:18:10.400
the bill process. Import the thing, require the script or use the script
227
00:18:10.839 --> 00:18:12.839
the CSS whatever it is kind of
thing, right, Joe just happened to
228
00:18:12.880 --> 00:18:17.960
go from zero to one hundred.
Yeah, exactly, something to try to
229
00:18:18.000 --> 00:18:22.279
do. And another thing that's definitely
true about tools like this is the payoff
230
00:18:22.319 --> 00:18:25.440
for them gets bigger the bigger the
project is, the more important
the project
231
00:18:25.559 --> 00:18:29.039
is. Doing something on the side
for fun, just to play around with,
232
00:18:29.240 --> 00:18:33.279
right, Like, you don't have
dedicated engineers who can work through problems
233
00:18:33.279 --> 00:18:37.279
for five Like five hours might have
been my entire budget for the entire month
234
00:18:37.279 --> 00:18:40.000
of how much time we're going to
get to spend on the project, right
235
00:18:40.119 --> 00:18:42.680
when you're doing side projects and stuff
like that. So, yeah, it
236
00:18:44.279 --> 00:18:48.079
is to be fair. Now,
your workshop, Michael, isn't an introduction
237
00:18:48.359 --> 00:18:52.119
to NX, right, So tell
us, like, who the target audience
238
00:18:52.200 --> 00:18:57.400
is for this workshop? Well,
you should. You should have you s
239
00:18:57.400 --> 00:19:00.400
did in the past. You should
know why why you want to use it,
240
00:19:03.279 --> 00:19:06.359
And then I guess you can.
You can benefit on a couple of
241
00:19:06.440 --> 00:19:11.599
layers. You can improve what you
have. You can most probably go home
242
00:19:11.240 --> 00:19:17.759
and reduce your configuration, be quicker
in setting up all the relations in the
243
00:19:17.759 --> 00:19:22.599
packages, understand how to debug these, caching better and so on and so
244
00:19:22.680 --> 00:19:30.160
forth. But I guess with zero
ever touching that topic it would most most
245
00:19:30.160 --> 00:19:34.319
probably be a massive overload for you. So you should be familiar with the
246
00:19:34.359 --> 00:19:40.799
tool, and you should in best
case come with a lot of questions or
247
00:19:40.880 --> 00:19:45.400
prepared problems right in the in the
bricks, and after I always have time
248
00:19:45.440 --> 00:19:52.279
to hang around and debug the projects
and see if we can fix it already
249
00:19:53.319 --> 00:19:57.839
at least the low hanging fruit.
So that's always a good thing that you
250
00:19:57.839 --> 00:20:03.839
can do to prepare for it.
Now, I wouldn't I would like to
251
00:20:04.000 --> 00:20:08.319
also ask you about your performance workshop
here basically kind of the same question here
252
00:20:10.039 --> 00:20:14.599
for the performance workshop, the titles
performance scale right high speed Angular apps on
253
00:20:14.599 --> 00:20:18.480
any device? What's the kind of
overview there? And who's the target audience
254
00:20:18.480 --> 00:20:25.160
for that? I would start with
the target audience, and that is basically
255
00:20:25.920 --> 00:20:32.160
any Angular developer that has to deal
with I call it bigger applications, and
256
00:20:32.200 --> 00:20:40.240
this is not a hundreds maybe also
this case, what can exclude from these
257
00:20:40.319 --> 00:20:45.839
bigger applications? May it be user
facing like a web shop or anything that
258
00:20:45.880 --> 00:20:55.440
you can easily acsiss without being logged
in or even in an internal network or
259
00:20:55.480 --> 00:21:00.720
even closed seems like only accessible within
the company network or other stuff, but
260
00:21:00.799 --> 00:21:10.440
still heavily data driven right from a
lot of articles with images and and that
261
00:21:10.559 --> 00:21:15.920
stuff. Which is I would say
the common type for a user facing data
262
00:21:15.960 --> 00:21:22.960
heavy thing over to massive tables in
like admin interfaces and and a lot of
263
00:21:23.000 --> 00:21:27.400
those at the same time. You
know, this is another type of massive
264
00:21:27.480 --> 00:21:33.160
data load that will make your applications
slow and And this may be the one
265
00:21:33.319 --> 00:21:37.160
or target audience that I want to
point out, because the the other one
266
00:21:37.880 --> 00:21:41.240
is we don't need to talk about
the benefits or why they are interested or
267
00:21:41.240 --> 00:21:47.160
why it could be good for them. They they mostly have already their understanding
268
00:21:47.759 --> 00:21:52.279
why this is good and are interested. What I would point out is a
269
00:21:52.400 --> 00:22:00.759
common I would call it misunderstanding of
applications that run only internally or behind the
270
00:22:00.799 --> 00:22:07.319
log in or just have some data
tables. You know, because most of
271
00:22:07.319 --> 00:22:10.599
the people say they don't need to
be fast, it's not really necessary.
272
00:22:11.400 --> 00:22:15.480
I can tell I can like show
numbers right and charts. If you improve
273
00:22:17.079 --> 00:22:21.039
the time it takes to display a
table to fill out the form to get
274
00:22:21.039 --> 00:22:26.119
your process internally done. In the
company big edmin interfaces, right, they
275
00:22:26.200 --> 00:22:30.039
will use it more often, get
faster, get more productive, and will
276
00:22:30.039 --> 00:22:36.799
be more positive to the software they
like. I hear comments like I did
277
00:22:36.799 --> 00:22:41.720
not know how slow we really are
because you get used to your problem and
278
00:22:41.720 --> 00:22:47.920
then you like really completely forgot how
life could be. Right. Yeah,
279
00:22:48.200 --> 00:22:55.839
So it's like depending on your industry, your type of application, your size
280
00:22:55.839 --> 00:23:00.000
of company, it's not the performance
doesn't matter. It's that there's different types
281
00:23:00.160 --> 00:23:03.480
of performance that matter, right,
Like an e commerce site loading a landing
282
00:23:03.519 --> 00:23:08.640
page may have different performance requirements than
your company's ad in interface, right,
283
00:23:08.680 --> 00:23:14.079
Like you may not be caring about
the same metrics. Yes. For example,
284
00:23:14.559 --> 00:23:19.480
when I when I open up a
web shop, I want to see
285
00:23:19.519 --> 00:23:26.079
as quickly as possible real information.
I want to have the images in a
286
00:23:26.160 --> 00:23:30.000
proper resolution, like there is maybe
a server seat rendering in place. This
287
00:23:30.160 --> 00:23:36.960
is like a one group of fancy
problems that or buswords that you can name
288
00:23:37.200 --> 00:23:41.839
in that area. On the other
hand, a table or like getting just
289
00:23:41.880 --> 00:23:45.200
the user data displayed. When when
you type in the first name, you
290
00:23:45.400 --> 00:23:48.960
see that you can click it and
finally see like what's the person's details are
291
00:23:49.000 --> 00:23:53.240
and what I don't know shippings they
have x Y said, this is the
292
00:23:53.279 --> 00:24:00.519
other type and there is a there
is less if you go for metrics LCP.
293
00:24:00.839 --> 00:24:03.839
Right, you always want to have
a stable site. You don't want
294
00:24:03.880 --> 00:24:11.200
to have boxes that jump around.
But what really is way way more im
295
00:24:11.279 --> 00:24:14.960
important. There is i NP like
the responsiveness of your website. If you
296
00:24:15.079 --> 00:24:19.240
type how long does it take to
remove all the notes, all the table
297
00:24:19.319 --> 00:24:22.839
rods and only display one table road
the one that you want to search for,
298
00:24:23.519 --> 00:24:26.400
and so on and so forth.
And this is a hard problem in
299
00:24:26.920 --> 00:24:32.680
h in these heavy outmoin interfaces,
but very like it's not so feelable in
300
00:24:32.720 --> 00:24:37.559
the in the in a web shop, for example, you don't have a
301
00:24:37.640 --> 00:24:41.839
timely speak right, you have like
five tiles on a Patriots and on a
302
00:24:41.920 --> 00:24:47.319
table. You have a lot so
different different ways how you can tackle those
303
00:24:47.359 --> 00:24:51.640
problems. Yeah, the worst thing
in the world is when you're using some
304
00:24:51.759 --> 00:24:53.720
kind of a SaaS tool or whatever
it is, and you're like, oh,
305
00:24:53.759 --> 00:24:57.839
I need to go search my information
or search for the service, and
306
00:24:57.880 --> 00:25:02.960
the search bar and starts, and
then it's just like waiting, waiting,
307
00:25:02.960 --> 00:25:07.880
and then you like use a developer
know that the the HTP call completed,
308
00:25:07.279 --> 00:25:11.759
but you're like, okay, so
let's go, Like, I know you
309
00:25:11.839 --> 00:25:18.519
have the data, show me the
data. Would you say, waiting like
310
00:25:18.559 --> 00:25:22.480
a I can maybe give a good
input on the whole performance story in general,
311
00:25:23.119 --> 00:25:26.799
A topic that was not so interested
at the beginning. CoA web battles.
312
00:25:26.880 --> 00:25:30.400
I'm like, what I have.
We are the web battles, the
313
00:25:30.480 --> 00:25:33.880
co web battles, whatever, And
it was becoming more and more big of
314
00:25:33.920 --> 00:25:37.960
a single over the years, and
at some point I was like, okay,
315
00:25:40.160 --> 00:25:42.279
let's dig in. And now I
would say it's it's a wonderful thing.
316
00:25:45.519 --> 00:25:52.000
Nowadays with the latest changes and their
latest goals, we should understand,
317
00:25:52.079 --> 00:25:56.079
Like we should first understand what web
battles are and then we can like talk
318
00:25:56.079 --> 00:26:02.039
about bad performance. So the quick
drop on the war web battles are is
319
00:26:02.160 --> 00:26:03.720
like the core, not all of
them, but just the core, the
320
00:26:03.839 --> 00:26:10.119
essential ones. All of them are
user focused, but the real consumer of
321
00:26:10.119 --> 00:26:15.440
the website that feels bad behavior is
frustrated the thread. So user centric,
322
00:26:15.960 --> 00:26:22.640
they are always measurable in proper numbers, and they are actionable. So when
323
00:26:22.839 --> 00:26:26.440
they tell us this and that is
bad, it should also give us a
324
00:26:26.519 --> 00:26:33.400
chance to understand what can we do
now and in many cases, like a
325
00:26:33.519 --> 00:26:37.279
lighthouse trust to do that. The
suggestions like what you can do, what
326
00:26:37.359 --> 00:26:41.680
action can you take as a next
step to improve these stats or that area
327
00:26:41.799 --> 00:26:48.359
web performance. So this is like
the philosophy behind the three numbers. And
328
00:26:48.440 --> 00:26:52.519
the first number is what you said, waiting at a loading speed visually displaying
329
00:26:52.559 --> 00:26:59.400
the information that I want to see. Then there is a CLS cumulative layout
330
00:26:59.400 --> 00:27:03.559
shifts that is just like how easy
it is for me to consume the page?
331
00:27:04.000 --> 00:27:10.160
Is the page visually stable so that
I can read the sentence and it
332
00:27:10.200 --> 00:27:15.319
does not get pushed down by the
next ad banner before that, in the
333
00:27:15.359 --> 00:27:18.039
torment, I have lose the flow
and I have to start reading again,
334
00:27:18.160 --> 00:27:22.119
or even worse, I'm going to
bet on something and I click the button
335
00:27:22.240 --> 00:27:27.400
it pushes down and a kick button
right, Google search stability, Google stecture,
336
00:27:30.160 --> 00:27:34.319
and that is visual stability. And
the last thing to get the cover
337
00:27:34.480 --> 00:27:41.720
battles detour done is the responsiveness.
And that is a wonderful change that is
338
00:27:41.759 --> 00:27:48.119
that happened recently and is still happening. Like it is not fully required as
339
00:27:48.160 --> 00:27:49.759
the new measure, but it is
clear in the next month, is they
340
00:27:49.799 --> 00:27:55.720
will fully switch to it and that
this is i MP. So the responsiveness,
341
00:27:55.799 --> 00:28:02.519
the the quality of interact that you
can do with the zip st may
342
00:28:02.640 --> 00:28:07.880
it be over your keyboard, mouse
or any other interaction should be as smooth
343
00:28:08.279 --> 00:28:15.880
as possible. And this cord this
measures the responsiveness of the weib set makes
344
00:28:15.960 --> 00:28:19.400
nice just to get this done.
It's like interaction to next paint. So
345
00:28:19.799 -->
00:28:26.200
if you click how long does it
take until you see paint the change?
346
00:28:26.359 --> 00:28:33.799
Right? Yeah, even if it's
just a loading screen or something like,
347
00:28:33.960 --> 00:28:38.279
give the user some feedback that their
action did something right. Like then you
348
00:28:38.400 --> 00:28:42.680
sometimes you get those websites where you
like click on the submit button and like
349
00:28:42.680 --> 00:28:45.880
they don't have a lot of in
spare on the smit button, but it's
350
00:28:45.880 --> 00:28:49.920
disabled and you're like, and are
you doing something? Is the page loading?
351
00:28:51.599 --> 00:28:53.599
What's going on right now? And
then like three seconds later you navigate
352
00:28:53.640 --> 00:28:56.680
back or whatever? Right, and
you're like, really would have been nice
353
00:28:56.720 --> 00:29:02.160
if I had some kind of thing
to tell me that you saw what I
354
00:29:02.200 --> 00:29:07.000
did right? Yeah? So are
you going to talk about all these core
355
00:29:07.000 --> 00:29:11.720
web vityls in your workshop or like
what what do you go into in your
356
00:29:11.759 --> 00:29:17.920
workshop? I will definitely talk about
the core web vitals like to theoretically understand
357
00:29:17.960 --> 00:29:22.279
them. We will then of course
get a couple of tools that we can
358
00:29:22.480 --> 00:29:26.440
measure them. Right, we can
straight away open up our example and measure
359
00:29:26.480 --> 00:29:33.920
the current numbers as a starting point, because there's only one ruling performance,
360
00:29:34.319 --> 00:29:41.000
don't guess measure, So we will
learn how to measure first, and then
361
00:29:41.039 --> 00:29:45.720
we will have a couple of jets
exercises, decent debt and we'll be able
362
00:29:45.759 --> 00:29:49.440
after every single step to measure again
and see what we achieved. So this
363
00:29:49.640 --> 00:29:53.759
is the practical part of the web
vittles. How can I measure them?
364
00:29:55.440 --> 00:29:59.440
And we will learn about common tools
like the light to stuff, but also
365
00:30:00.160 --> 00:30:03.440
plugins where you in the console lives
you always at run time, how your
366
00:30:03.480 --> 00:30:08.519
cliques are, like how the imp
is going, and we will learn like
367
00:30:10.319 --> 00:30:12.599
we cannot set it up in a
virtual black, but we can learn about
368
00:30:12.599 --> 00:30:18.640
how we move really big companies and
track their performance progress, how we can
369
00:30:18.680 --> 00:30:23.680
make sure we know where the problems
are and can basically give some kind of
370
00:30:23.720 --> 00:30:29.640
a clue how you track the metrics
and on a large scale, and that
371
00:30:29.799 --> 00:30:38.839
is all connected to corporate battles.
I would say since that time of the
372
00:30:38.920 --> 00:30:44.759
year again. Join us as all
La City, Utah from March eight inteen
373
00:30:44.839 --> 00:30:49.519
nineteen four road shops in March eighteen
for sessions. Angiiconf is not just a
374
00:30:49.599 --> 00:30:56.680
conference, it's a thriving community where
ideas flourish, collaborations ignite in friendships from
375
00:30:56.440 --> 00:31:02.680
angi Comf is absolutely the best place
to learn everything new in Angler and connect
376
00:31:02.720 --> 00:31:07.799
with the Angler community. Go to
EnGIS hypincarms dot org and get your tickets
377
00:31:07.839 --> 00:31:19.079
today to harness the Angler momentum.
See you there, Yeah that makes sense.
378
00:31:19.880 --> 00:31:23.200
Cool, Yeah, I'm that workshop
sounds like it's going to be so
379
00:31:23.359 --> 00:31:29.279
helpful for so many developers. It
always seems like performances, you know,
380
00:31:29.319 --> 00:31:36.519
not purposely an afterthought of developing applications, but it can sometimes be a little
381
00:31:36.559 --> 00:31:41.039
bit of a hard sell to the
decision makers, right where, well,
382
00:31:41.039 --> 00:31:42.880
why don't we just build another feature
that our customers are going to use it
383
00:31:44.000 --> 00:31:47.519
that will help our sales, Right, And it's like, you're not wrong,
384
00:31:48.559 --> 00:31:52.680
but we also have to care about
performance Otherwise that our users are going
385
00:31:52.759 --> 00:31:57.119
to get in there and then churn
and drop off because they have everything takes
386
00:31:57.200 --> 00:32:02.680
twice as long, right, So
I think bring incrational forefunds. I guess
387
00:32:02.680 --> 00:32:09.039
it becomes more interesting when you start
with competitor analysis. How can I go
388
00:32:09.160 --> 00:32:15.279
into that area? So we do
performance outdits that is basically looking at this
389
00:32:15.400 --> 00:32:19.079
one website, this is one featured, is one whatever, and do a
390
00:32:19.160 --> 00:32:23.960
right solutions problem hand over. What
we also do is we have performance consulting
391
00:32:24.000 --> 00:32:30.599
where we really develop with a company
a full strategy on how to move ownership
392
00:32:30.759 --> 00:32:36.079
and interest of a specific topic.
In our case. Now, when we
393
00:32:36.119 --> 00:32:42.400
talk performance from the very beginning of
let's see where we are where the ownership
394
00:32:42.440 --> 00:32:45.559
is most probably in the hands of
the developers to the very right of this
395
00:32:45.920 --> 00:32:51.160
table that we have that shows us
that at the end the ownership is at
396
00:32:51.200 --> 00:32:57.160
the company itself, is baked in
into every single layer. It is understood
397
00:32:57.200 --> 00:33:00.240
by the management. We have our
goals, we have KPIs, have metrixes,
398
00:33:00.519 --> 00:33:06.759
we have knowledge transfer and so on
and so forth. But I guess
399
00:33:06.759 --> 00:33:14.319
I lost what you said before.
Damn yeah, all yeah, yeah,
400
00:33:14.400 --> 00:33:17.200
no, those are all very good
points hard sale, hard sale, okay.
401
00:33:19.640 -->
00:33:28.079
And so one of these performance strategy
where you have all layers, there's
402
00:33:28.160 --> 00:33:31.160
also one layer where you do a
competitor analysis, where you say Okay,
403
00:33:32.119 --> 00:33:39.480
what we have product X. We
have a shop for uh Anglo stickers,
404
00:33:39.599 --> 00:33:45.839
or we have a website for code
tutorials, a live edited edited with a
405
00:33:45.839 --> 00:33:51.240
little bit of text, you know, so online tutorials. And I have
406
00:33:51.359 --> 00:33:54.920
seven competitors, like how do how
do they perform? How do us so
407
00:33:55.079 --> 00:34:00.519
use them? And you can start
simple by just understanding how long it takes
408
00:34:00.640 --> 00:34:05.680
until they are loaded and you can
edit the code editor and finally do your
409
00:34:05.720 --> 00:34:10.239
exercise or until you see the product. But you can also do bay more
410
00:34:10.280 --> 00:34:21.760
interesting things. Nowadays. Another advanced
thing light Toss extended their measurement modes to
411
00:34:22.280 --> 00:34:25.920
two new measurement modes, so you
cannot only do a navigation as before.
412
00:34:25.960 --> 00:34:30.639
Like all these years, the only
thing that they did was initial navigation.
413
00:34:30.559 --> 00:34:35.320
What you can do now is you
can do time spans and snapshots too.
414
00:34:36.000 --> 00:34:40.280
Snapshots is basically just capturing the state
as is, and you can do domin
415
00:34:40.280 --> 00:34:45.559
analysis, accessibility of a pop up
or whatever you know, and the runtime
416
00:34:45.639 --> 00:34:52.679
stuff. And with these new measurement
modes, you can basically track a full
417
00:34:52.800 --> 00:34:58.000
user journey. You can track the
whole thing, my initial navigation to the
418
00:34:58.039 --> 00:35:02.400
page, selecting the product, or
changing the scrolling to the code editor,
419
00:35:02.880 --> 00:35:08.719
putting it there, finishing the whole
process, and have even sections you can
420
00:35:09.079 --> 00:35:15.440
ensure that even after typing in something
in the form, accessibility is still given
421
00:35:15.719 --> 00:35:20.159
and the error message is correctly implemented. You know, stuff that was not
422
00:35:20.400 --> 00:35:25.599
possibly before. And this is a
since one hundred and two, I guess
423
00:35:25.679 --> 00:35:30.599
Chrome possible. We also wrote an
open source tool for that to open source
424
00:35:31.320 --> 00:35:37.800
to automate it more. It's called
user flow. And yeah, very very
425
00:35:37.800 --> 00:35:45.159
interesting changes were done in recent times
on that I did not know. I
426
00:35:45.199 --> 00:35:50.199
thought it was still on the initial
navigation. Yeah, we used all those
427
00:35:50.239 --> 00:35:57.159
tools because back to the hard sell. At some point you have to figure
428
00:35:57.159 --> 00:36:01.559
out why other people are have more
more traffic than you read. And in
429
00:36:01.639 --> 00:36:07.800
many cases it's just like because the
experience is so much more nice. I
430
00:36:07.840 --> 00:36:13.199
remember Notion came out at the tapping
reading, you know what I mean.
431
00:36:13.679 --> 00:36:17.000
Compared to the tools that I had, it was just instant. It had
432
00:36:17.440 --> 00:36:22.760
a quick like it was just like
very fast compared to everything else I had.
433
00:36:23.440 --> 00:36:29.000
So competitor analysis, I would say, is a good driver for selling
434
00:36:29.039 --> 00:36:35.119
a performance improvements. I'm also curious
about, like what skill set a person
435
00:36:35.119 --> 00:36:39.519
needs to have the benefit from the
performance workshop, like what background and capabilities
436
00:36:39.760 --> 00:36:46.519
prerequisites do they need to have?
Very good question. I believe even if
437
00:36:46.559 --> 00:36:51.239
you're an expert, you get you
get stuff out of it. We can
438
00:36:51.320 --> 00:36:54.000
go as deep as deep as the
hole is there is, there's no end.
439
00:36:54.039 --> 00:37:00.440
I believed it from from knowledge that
we would miss there. You should
440
00:37:00.960 --> 00:37:05.119
at least know that there are a
couple of things that you can use.
441
00:37:05.199 --> 00:37:07.920
Right. You should know that there
is a network tub and maybe never used
442
00:37:07.920 --> 00:37:14.639
it, but have an understanding a
little bit of what could be in that
443
00:37:14.760 --> 00:37:19.920
performance and you will go home with
no matter if you used the tools or
444
00:37:19.960 --> 00:37:22.960
not, very good knowledge about the
tools. If you say you use the
445
00:37:23.000 --> 00:37:27.320
network tub every day and you're good
in it, or you use the performance
446
00:37:27.360 --> 00:37:30.320
tub and you're good in it,
I guarantee you twenty things you didn't know
447
00:37:30.480 --> 00:37:37.480
when you go home. So the
tooling side is covered excellent even for first
448
00:37:37.519 --> 00:37:42.199
time as we have this like how
to read flame charts until how to configure
449
00:37:42.239 --> 00:37:46.440
specific things or in very good exercises, we have a lot of bonus material.
450
00:37:47.039 --> 00:37:52.239
If there is a question that goes
too deep, that is too technical
451
00:37:52.400 --> 00:37:57.119
for the time we have available,
I have extra exercises that I hand out
452
00:37:57.480 --> 00:38:01.599
after that extra slide decks that they
are just for after the workshop, reading
453
00:38:01.880 --> 00:38:06.760
reading that at home, look at
it at home. So this is also
454
00:38:06.800 --> 00:38:12.519
possible, and I guess a good
fit for everyone that is interested to learn
455
00:38:12.519 --> 00:38:16.239
in that direction and improve. What
about the tying Back to the NX one,
456
00:38:16.480 --> 00:38:20.599
same question with the NX one.
What kind of skill sets and what
457
00:38:20.679 --> 00:38:24.519
kind of people will benefit from going
to the n
Extra Scalable Angle Architecture Workshop.
458
00:38:25.880 --> 00:38:32.280
They will, like I believe,
a very nice thing that I want
459
00:38:32.360 --> 00:38:38.320
to point out here of the whole
workshop, of course all about an extent,
460
00:38:38.400 --> 00:38:43.239
how to use that tool in particular, but also a couple of tricks
461
00:38:43.280 --> 00:38:52.400
how you can organize a group and
and handle all the accorded special folders.
462
00:38:52.199 --> 00:38:57.039
Let me let me explain what I
mean with it. You have code that
463
00:38:57.159 --> 00:39:00.599
works, then you have some tests
for that. Then you may be for
464
00:39:00.800 --> 00:39:04.199
some pieces you need to know if
the function is fast enough or not,
465
00:39:04.920 --> 00:39:08.920
and then you end up with code
pieces everywhere. These code piece generates you
466
00:39:08.960 --> 00:39:15.280
a schema file okay that lives in
the tooling folder. But everything else you
467
00:39:15.320 --> 00:39:20.440
have test mock files that lay around
wildly. You have the performance nippits to
468
00:39:20.519 --> 00:39:23.280
measure to benchmark between two functions that
you want to use and so on,
469
00:39:24.199 --> 00:39:31.360
and we love to organize that in
as a sibling folder to the source folder.
470
00:39:31.400 --> 00:39:35.079
In pretty much any package. Next
to the source folder, you have
471
00:39:35.159 --> 00:39:38.760
then a dogs folder, tools folder, a perf folder, a mock folder.
472
00:39:39.280 --> 00:39:45.639
And that is a very nice way
that what we demonstrate how to clean
473
00:39:45.719 --> 00:39:50.000
up your code base. It will
It is just a very very small tweak
474
00:39:50.119 --> 00:39:52.239
in your setup. It does not
require a lot of work to move it
475
00:39:52.280 --> 00:39:55.960
there, but after it you will
be way happier because your code base is
476
00:39:57.000 --> 00:40:00.239
so much more slimmer organized and makes
a lot of or sense for newcomers.
477
00:40:00.320 --> 00:40:05.880
Right if they access the code base, they will quickly see the red places,
478
00:40:05.960 --> 00:40:07.960
find the red red we fail in
the red folder and so on.
479
00:40:08.239 --> 00:40:13.519
And this is an integrated pretty well
with an x so this is also i
480
00:40:13.559 --> 00:40:17.960
believe, especially seeing that we that
we will discuss in the victual. What's
481
00:40:19.000 --> 00:40:22.480
your opinion on this, especially folders
like do you or do you know the
482
00:40:22.559 --> 00:40:29.519
clutter even in bigger projects when you
have all these like tiny islands of responsibilities
483
00:40:29.800 --> 00:40:37.760
within a libor app. So we
have somewhere under a thousand libraries in our
484
00:40:37.840 --> 00:40:40.119
mona repo. So you know,
it's a pretty big code base, right
485
00:40:40.159 --> 00:40:46.440
across five different API servers, five
or six Angler apps, a couple of
486
00:40:46.480 --> 00:40:52.559
Lamba functions, and then whole and
the ANTES suites. And I always defer
487
00:40:52.760 --> 00:41:00.039
to just what ANNEX generates. I
don't typically now, to be fair,
488
00:41:00.079 --> 00:41:05.400
we aren't publishing our libraries right like
these are just it's just internal code that
489
00:41:05.440 --> 00:41:08.760
gets included in the build process via
a typescript alias. So this is completely
490
00:41:08.800 --> 00:41:13.440
irrelevant to those people that are actually
publishing libraries to MPM. Let's just be
491
00:41:13.519 --> 00:41:15.800
clear about that, or open source
code for that matter at all, right,
492
00:41:17.840 --> 00:41:24.159
I just I tend to just leave
the defaults because the value, you
493
00:41:24.199 --> 00:41:29.119
know, as the CTO of the
company, I have the way the benefits
494
00:41:29.119 --> 00:41:30.719
of all the different things that we
can do. And while I'm not disagreeing
495
00:41:30.719 --> 00:41:36.159
there's benefits to what you were just
talking about, there's a bigger benefit somewhere
496
00:41:36.159 --> 00:41:40.599
else for us as a startup that's
trying to make money to just survive,
497
00:41:42.320 --> 00:41:45.719
right like we want the company to
survive so that we can grow. And
498
00:41:46.079 --> 00:41:53.280
usually I can't justify spending time changing
the default way that NX generates our code
499
00:41:53.320 --> 00:41:59.400
because there's just more beneficial things for
us to be working on. Now that
500
00:41:59.480 --> 00:42:04.119
being said, I'm a huge component
of this works for us, It is
501
00:42:04.199 --> 00:42:08.039
subjective. It may not work for
you. You might like organizing all of
502
00:42:08.039 --> 00:42:15.159
your stuff. You might write more
documentation in the library code itself than we
503
00:42:15.199 --> 00:42:19.559
do. Right. You might actually
have docs for every single library that you
504
00:42:19.599 --> 00:42:22.159
generate in your mono repo. We
don't not for all of them, right.
505
00:42:22.239 --> 00:42:28.039
A lot of them are just self
exponatory typescript functions that are documented with
506
00:42:28.079 --> 00:42:32.760
doc strinks for example, or jas
docs, right, So we try to
507
00:42:32.800 --> 00:42:37.599
not customize as much as possible and
just let the default be the default.
508
00:42:38.199 --> 00:42:44.320
I trust that whatever the next team
chose made sense at least at some point,
509
00:42:44.679 --> 00:42:46.480
and that's good enough for me,
right, so that I can focus
510
00:42:46.519 --> 00:42:51.519
on my business problems and move my
team forward at a faster pace. So
511
00:42:51.559 --> 00:42:55.519
that's kind of my opinion on the
whole. Like customizing layout classic you know,
512
00:42:55.639 --> 00:43:00.840
senior engineer answer, It depends,
right, for us, it depends
513
00:43:01.519 --> 00:43:07.840
we'd like to do it this way. For somebody else, maybe you want
514
00:43:07.280 --> 00:43:13.519
to have your
code and a folder
called this is our documentation. I don't
515
00:43:13.559 --> 00:43:22.519
know, right, that's completely up
to you, Okay, accepted you like
516
00:43:22.599 --> 00:43:27.280
you'll accept that answer of course?
Of course, what what else can I
517
00:43:27.360 --> 00:43:31.159
do? Like I already heard it? You can try and change change my
518
00:43:31.239 --> 00:43:37.920
mind, change me from the inside. No energy to change a lot of
519
00:43:37.960 --> 00:43:45.039
people. But the information right if
you if you're interested in informing and then
520
00:43:45.000 --> 00:43:51.960
that stuff is sway is better than
changing yes, true, well I mean
521
00:43:52.639 --> 00:44:00.800
uh or interesting things and maybe to
get back overlip of the AX and PERF
522
00:44:00.119 --> 00:44:06.400
is that also the tool chain wants
a good performance, right, Every developer
523
00:44:06.480 --> 00:44:10.440
wants to have a good developer experience
when and when you develop, you on
524
00:44:10.519 --> 00:44:16.480
a fast responsive tool chains in circuits, and this is also part of the
525
00:44:16.559 --> 00:44:21.880
performance story, I would say,
at least in a more realistic point of
526
00:44:21.960 --> 00:44:25.880
view. Absolutely, What has the
NX team been doing recently call it in
527
00:44:25.920 --> 00:44:31.440
the past year to help improve the
performance of the tool chain. Well,
528
00:44:32.320 --> 00:44:39.880
I'm not sure if what the status
is currently, but they announced some months
529
00:44:39.920 --> 00:44:45.559
as ago that they started this,
that they got a big funding and they
530
00:44:45.599 --> 00:44:58.440
start to work on CI system h
and and there were some interesting things.
531
00:44:59.400 --> 00:45:02.519
When you say what do they do
to improve the BEAT toolchain or the speed?
532
00:45:04.280 --> 00:45:07.519
Of course we talk about caching in
different ways like distributed caching, or
533
00:45:07.880 --> 00:45:12.440
we execute the tasks in a little
bit more smarter way, or maybe we
534
00:45:13.039 --> 00:45:16.800
don't parallelize resource heavy tasks. That
would be a little bit more interesting.
535
00:45:16.880 --> 00:45:22.599
It's not so well known but has
heavy impact. Right. Then you go
536
00:45:22.719 --> 00:45:28.440
on and you stumble over some comments
and there is like, yeah, flacky
537
00:45:28.480 --> 00:45:30.280
tests and how do we approach them? So I believe they go in a
538
00:45:30.320 --> 00:45:37.480
direction where they will find more and
more more smarter ways to improve the speed
539
00:45:37.559 --> 00:45:44.559
and quality of the whole toolchain,
right from executing it on a local machine,
540
00:45:44.800 --> 00:45:50.559
having it an sci pipeline and system. And it seems they do well.
541
00:45:50.840 --> 00:46:00.159
The serious whatever this is serious started
and I'm curious, I'm very curious.
542
00:46:01.079 --> 00:46:07.400
Yeah, they their performance story is
really interesting because you know, actually
543
00:46:07.400 --> 00:46:13.119
talk they started as a very we'll
call it simple comparative to today tool right,
544
00:46:13.320 --> 00:46:15.840
and now they're just they're expanding into
whole new markets like the C I
545
00:46:15.960 --> 00:46:20.880
C D market, right, and
then as well as their their damon that
546
00:46:21.000 --> 00:46:24.679
runs the background, which they're they're
just writting and rust because it's just so
547
00:46:24.760 --> 00:46:31.239
much faster to analyze these massive workspaces
using a native language, datively compiled language
548
00:46:31.280 --> 00:46:36.920
like that. Right, It's true. I guess they ordered out half a
549
00:46:37.000 --> 00:46:42.440
year ago. Mm hmmm, something
like that. It's interesting interesting scenes.
550
00:46:42.599 --> 00:46:50.760
Also the Angle team dut a couple
of interesting changes and yeah in the run
551
00:46:50.840 --> 00:47:01.280
time performance, but also are you
up if you know? Sorry, we're
552
00:47:01.280 --> 00:47:07.960
all talking. No, it's your
okay. So what you said actually makes
553
00:47:08.000 --> 00:47:12.880
me think of something. Angel has
undergone a ton of changes recently. How
554
00:47:12.880 --> 00:47:19.280
do those changes affect either performance?
Well, really performance? I assume none
555
00:47:19.280 --> 00:47:22.239
of those changes have any meaningful effect
on an exper So the two workshops you're
556
00:47:22.280 --> 00:47:25.199
doing, like, how does the
last year, year and a half it's
557
00:47:25.239 --> 00:47:31.239
worth changes to angular effect the workshops? You do it in a good and
558
00:47:31.599 --> 00:47:36.920
in an interesting way. The good
way is lots of new things to teach,
559
00:47:37.480 --> 00:47:40.960
lots of new bookings. But the
other thing is like everything that is
560
00:47:42.159 --> 00:47:46.760
new is like, first of all, we try it out when it is
561
00:47:47.480 --> 00:47:52.920
bloody new, you know, so
it takes a little bit more effort to
562
00:47:52.000 --> 00:47:59.039
understand the cutting edge stuff and make
material all of it. Then to explain
563
00:47:59.119 --> 00:48:04.119
to you what the rey featered us, because like everybody is explained everywhere just
564
00:48:04.159 --> 00:48:10.159
go out and you know, so
it brings a lot of research time,
565
00:48:10.599 --> 00:48:16.639
documentation time, experimenting like how you
build up and exercise, what is not
566
00:48:16.679 --> 00:48:22.960
taking too much time but still has
a nice learning learning effect or outcome,
567
00:48:22.159 --> 00:48:27.440
or what are the best takeaways to
like directly use at home. You know,
568
00:48:28.039 --> 00:48:31.960
when you when you're done with a
workshop, you sometimes you ask yourself,
569
00:48:32.239 --> 00:48:36.360
how can what can I do now? Or sometimes your boss ask you,
570
00:48:36.440 --> 00:48:43.440
like what you spend MK for workshops,
hotels and conferences and what can
571
00:48:43.480 --> 00:48:46.280
you do now? Right? So
I really always love to have a decent
572
00:48:46.400 --> 00:48:52.400
part of really good takeaways that most
probably will lend in any project that you
573
00:48:52.599 --> 00:48:54.559
that you have. Right the quick
queens that nobody thinks about, I would
574
00:48:54.559 --> 00:49:00.440
say that is a that is the
thing that I want to point out pop
575
00:49:00.480 --> 00:49:05.639
Pump. I actually did a little
bit of like research. I was just
576
00:49:05.679 --> 00:49:09.760
curious about the performance of signals versus
rx JS, and I did like I
577
00:49:09.800 --> 00:49:15.239
created a test product to test out
the performance differences of the two different mechanisms,
578
00:49:15.239 --> 00:49:17.599
assuming you were using them for like
binding data on the page. It
579
00:49:17.639 --> 00:49:22.880
was it's pretty interesting, thick to
a thing to play around with. But
580
00:49:23.760 --> 00:49:28.679
it's a sad comparison. If you
say that maybe we can have a little
581
00:49:28.679 --> 00:49:37.360
bit into that topic because we signals, you can already change detect on component
582
00:49:37.480 --> 00:49:42.039
level. So normally you go up
the chain and and down again and then
583
00:49:42.119 --> 00:49:45.320
re render everything. And if you're
lucky, you have a couple of on
584
00:49:45.480 --> 00:49:49.199
push components and then you don't render
them, but the dirty path for their
585
00:49:49.280 --> 00:49:52.239
cord is is always re rendered.
You cannot you cannot avoid it even with
586
00:49:52.320 --> 00:49:57.760
one push. So why why do
I say it's it's a sad comparison Because
587
00:49:57.800 --> 00:50:01.320
we have this cool, this cool
comp honent level change detection and hopefully in
588
00:50:01.360 --> 00:50:05.679
the future even more haang fang grant. And on the other hand, the
589
00:50:05.719 --> 00:50:08.800
acing pipe, I mean it works
now, so n less it is also
590
00:50:09.039 --> 00:50:15.440
finally decoupried from that stuff, but
not with a lot of love because it
591
00:50:15.519 --> 00:50:21.239
is still in the bottom up to
top down mechanism, and you could change
592
00:50:21.239 --> 00:50:23.440
a line of code you know,
and would have it also on component level.
593
00:50:24.599 --> 00:50:32.440
So that comparison is said because I
believe that the fact that signals have
594
00:50:32.519 --> 00:50:39.719
an initial value that will get transported
is very visible if you could directly apples
595
00:50:39.760 --> 00:50:45.679
to apples. Compare rxjas and signals, right laziness versus a laziness where you
596
00:50:45.719 --> 00:50:54.360
can also have filter operations versus an
initial value performance perspective. These are like
597
00:50:55.400 --> 00:51:00.920
the researchers that we do now,
like try to get a bigger guy examples
598
00:51:00.000 --> 00:51:07.480
full scale, see how it really
feels to architect with that what is easy
599
00:51:07.519 --> 00:51:13.760
to teach and easy to use.
And for me, the biggest headache is
600
00:51:13.840 --> 00:51:17.880
still the null object pattern. Rather, if I have an initial value,
601
00:51:17.920 --> 00:51:22.960
but the value is not here,
what do I put? And then baboom,
602
00:51:22.039 --> 00:51:28.679
I introduce nule or undefined or empty
string. From the moment I use
603
00:51:28.760 --> 00:51:34.159
that technology up downwards right and of
course in the template I have help us.
604
00:51:34.199 --> 00:51:38.719
But everything in between is not as
nice of a type as I would
605
00:51:38.719 --> 00:51:45.559
want it, but it is very
interesting. You can do nicer templates,
606
00:51:45.599 --> 00:51:49.280
I guess, with with signals less
bloated, if they really go more fangrant,
607
00:51:49.360 --> 00:51:53.639
I guess that is the way to
go for the template part of of
608
00:51:53.679 --> 00:52:01.159
our data data network or data graph. And at least for now, it
609
00:52:01.159 --> 00:52:07.880
seems for me to be the best
to have everything else that is basically event
610
00:52:07.239 --> 00:52:14.440
driven, like all your HDP data
hip rec West web sockets user inputs,
611
00:52:14.760 --> 00:52:16.559
those are all events driven. I
would keep them. If you have it
612
00:52:16.599 --> 00:52:25.559
already in rxchs, it is easier
to deal with like you cannot even have
613
00:52:25.760 --> 00:52:32.119
an event like sing with signals.
And and this reflects in how you can
614
00:52:34.239 --> 00:52:40.119
write your data transformation data PABs and
organize the state. Like if you realize
615
00:52:40.320 --> 00:52:46.280
Angula went into a transition where you
can have more local state people have more
616
00:52:46.320 --> 00:52:52.920
of those not everything is in the
global and your ex patent reluct sorry relux
617
00:52:52.840 --> 00:53:00.199
sing thing like, but really go
more more fangrant, more locally and if
618
00:53:00.239 --> 00:53:05.639
they sit up and just see a
way easier hinting with our x chase,
619
00:53:06.079 --> 00:53:08.599
so they're more power away from the
template that go that the cleaner it is
620
00:53:08.679 --> 00:53:12.880
to work with or x chase,
the closer I go to the template,
621
00:53:13.199 --> 00:53:20.199
the cooler it is to to use
the signal benefits a man moment. Yeah,
622
00:53:20.239 --> 00:53:23.880
I would agree with that for sure. I'm loving working with signals when
623
00:53:24.760 --> 00:53:30.960
I'm using them within a component,
But otherwise, like for state not necessarily
624
00:53:30.000 --> 00:53:37.519
state management, but for data fetching
and stuff like that, I'm still well.
625
00:53:37.559 --> 00:53:39.000
I mean, like the libraries are
using only support our x chs,
626
00:53:39.079 --> 00:53:43.760
and I don't have any desire to
build an interrop layer between them, so
627
00:53:44.119 --> 00:53:46.800
you know, like graph ql,
we're using Apollo Angular. I'm not gonna
628
00:53:46.800 --> 00:53:51.679
go build a signal interrop layer just
just because right, I'm just gonna use
629
00:53:51.719 --> 00:53:54.920
observables and then convert them into a
signal when I get to the component level,
630
00:53:55.199 --> 00:53:59.920
and then that's what actually gets displayed
in the template. And that's honestly
631
00:54:00.159 --> 00:54:06.159
joy to work with compared to using
rchs in the template. And the performance
632
00:54:06.199 --> 00:54:09.039
is you know, more or less
built in there because you can get that
633
00:54:09.119 --> 00:54:15.159
more fine grained change detection with the
signals because that's what's bound to the template
634
00:54:15.199 --> 00:54:21.320
and not the actual archs pipe.
You ever tread all the template package of
635
00:54:21.320 --> 00:54:25.599
our ex single, I think I
played with it one time forever ago,
636
00:54:27.119 --> 00:54:31.239
but I have it anytime recently.
Now there's the the RXCHAS integration way better
637
00:54:31.280 --> 00:54:37.159
done. But what I think it's
said is all the new performance features that
638
00:54:37.199 --> 00:54:44.880
they shipped with the new control flow, we cannot just extend them. Is
639
00:54:44.920 --> 00:54:49.360
before it could just extend or the
directives structure directives noise is baked into the
640
00:54:49.400 --> 00:54:53.760
compiler. Then there was a I
guess the only drawback that I saw with
641
00:54:53.840 --> 00:54:59.599
the new control flow. Yeah,
they aren't letting us extend it, at
642
00:54:59.679 --> 00:55:01.480
least for time being. We don't
know if they're going to let us to
643
00:55:01.559 --> 00:55:07.639
it in the future or not.
But yeah, right now, we're not
644
00:55:07.639 --> 00:55:10.679
allowed to extend it, so we're
kind of we're stuck with what we have,
645
00:55:10.800 --> 00:55:15.480
which is amazing. The new control
flow is unreal and it's so much
646
00:55:15.519 --> 00:55:20.480
more enjoyable to work with for sure, so much cleaner. But for someone
647
00:55:20.559 --> 00:55:24.000
like you that is a library author
that likes to you know, pack and
648
00:55:24.039 --> 00:55:28.880
customize and extend, I could definitely
understand why you would like it to be
649
00:55:29.440 --> 00:55:38.119
extensible. Cool well in you know
wrapping up here, Uh, the for
650
00:55:38.159 --> 00:55:45.000
everyone listening, remember the workshops are
March eighteenth and March nineteenth at eng COMF
651
00:55:45.159 --> 00:55:49.679
twenty twenty four, and then we
have sessions. They're available. They're available
652
00:55:49.719 --> 00:55:52.679
online as well as in person,
so if you can't make it to comp
653
00:55:52.760 --> 00:55:57.199
you can get them online. Right
there are virtual yeah yeah, there's even
654
00:55:57.559 --> 00:56:01.760
a block post there about their own
then attendancy of an inchicon workshop if you
655
00:56:01.840 --> 00:56:06.599
googled it. It was an attendee
of me of my last year's workshop of
656
00:56:06.639 --> 00:56:10.119
the performance workshop, and he was
not sure if it really pays off to
657
00:56:10.159 --> 00:56:15.039
attend the remote workshop, like with
not sitting there and ordered stuff, and
658
00:56:15.119 --> 00:56:20.239
it turned out to be really really
catisfying for him. You most probably find
659
00:56:20.840 --> 00:56:24.400
the scene online. That's Awes and
Joe. Correct me if I'm wrong,
660
00:56:24.400 --> 00:56:28.079
But the virtual ones are a couple
of days before, right, and then
661
00:56:28.079 --> 00:56:31.559
the person they're live all at the
same time. Life. Oh okay,
662
00:56:31.760 --> 00:56:37.039
there is one virtual only workshop being
held a few days before, on like
663
00:56:37.079 --> 00:56:40.760
Wednesday, Thursday or Friday the week
before. But like virtual online, there
664
00:56:40.760 --> 00:56:45.960
will be online attendees and in person
attendees for Michael's workshops. So now the
665
00:56:45.000 --> 00:56:50.039
online attendees will try to feel as
close as possible, like they're just virtually
666
00:56:50.079 --> 00:56:55.000
sitting in the room Tello presence robots
right before we're hologramming everybody in right.
667
00:56:55.480 --> 00:57:00.199
Yeah, yeah, cool. So
that's that's March eighteenth and nineteen, and
668
00:57:00.239 --> 00:57:02.559
then join us. All three of
us will be there at anti comp this
669
00:57:02.639 --> 00:57:08.159
year, and so will and Keita, Laura and Brian, the other host
670
00:57:08.199 --> 00:57:13.679
of the Angler Plus show, So
we'll be there for at least the sessions
671
00:57:13.960 --> 00:57:17.960
on the twentieth and the twenty first. We have an unbelievable lineup of speakers
672
00:57:17.960 --> 00:57:22.360
this year. I'm really excited,
and we're doing a live Anger Plus Show
673
00:57:23.159 --> 00:57:27.119
recording like we did last year.
I don't know if it'll be as funny
674
00:57:27.119 --> 00:57:30.800
as last year, because last year's
was was just gold. But yeah,
675
00:57:31.000 --> 00:57:34.320
it should be a really good time. I mean, Edgie Comp is always
676
00:57:34.320 --> 00:57:37.239
a good time. But we should
we hope to see you there. That
677
00:57:37.320 --> 00:57:42.639
link that Michael was talking about will
be in the show notes about attending the
678
00:57:42.719 --> 00:57:45.760
virtual workshop, so if you want
to read that, see below, and
679
00:57:46.440 --> 00:57:50.559
yeah, sign up for the virtual
one if you can't make it to Salt
680
00:57:50.639 --> 00:57:57.639
Lake otherwise we'll we'll see you in
person. Obviously in person is always the
681
00:57:57.679 --> 00:58:04.440
best, right, Yes, yes, a clear yess from everyone going to
682
00:58:04.480 --> 00:58:07.679
Edgie Comp is like the highlight of
my ear for sure. Yes, lent
683
00:58:07.800 --> 00:58:13.880
to such a wonderful conference. Yeah, absolutely, So thank you Michael for
684
00:58:13.960 --> 00:58:16.760
joining us today on the ingod plus
show. Talk about your two different workshops.
685
00:58:17.000 --> 00:58:21.719
Again, those are called for everybody
wanting to sign up performance at Scale
686
00:58:22.000 --> 00:58:25.599
high Speed Angler applications on any device. And then the second one is NX
687
00:58:25.599 --> 00:58:30.360
for scalable Angular architectures. So go
sign up virtual in person. I don't
688
00:58:30.400 --> 00:58:34.480
care, but you should do it
in person so that we all see there.
689
00:58:35.639 --> 00:58:39.639
Thank you Joe for co hosting with
me today of course, pleasure appreciate
690
00:58:39.679 --> 00:58:44.760
it, and I hope you guys
have a good day. Yeah. Thanks,
691
00:58:45.920 --> 00:58:49.079
Hi Bie, Hey, this is
Presston Min. I'm one of the
692
00:58:49.159 --> 00:58:52.960
n g Champions riders in our daily
battle to crush out code, we run
693
00:58:52.000 --> 00:58:58.239
into problems and sometimes those problems aren't
easily solved. Nji comp broadcasts articles and
694
00:58:58.280 --> 00:59:01.679
tutorials from NDIE champions like myself that
helped make other developers' lives just a little
695
00:59:01.719 --> 00:59:07.000
bit easier. To access these articles, visit medium dot com, Forward Slash
696
00:59:07.199 --> 00:59:12.440
NGCOMF. Thank you for listening to
the Angular Plus Show, a ngcoff podcast.
697
00:59:12.840 --> 00:59:15.559
We would like to thank our sponsors, the NGCOMF organizers Joe Eames and
698
00:59:15.599 --> 00:59:21.639
Aaron Frost, our producer Gene Bourne, and our podcast editor and engineer Patrick
699
00:59:21.719 --> 00:59:30.840
Kays. You can find him at
spoonful ofmedia dot com.