TRANSCRIPT 🔗
00:00:00.150 --> 00:00:01.200
Sam Brace: Hey everybody.
00:00:01.410 --> 00:00:05.400
My name is Sam Brace, and I am the
Senior Director of Customer Education
00:00:05.400 --> 00:00:10.080
and Cloud community here at Cloudinary,
and you are about to watch and listen
00:00:10.080 --> 00:00:12.540
to the latest episode of Dev Jams.
00:00:22.440 --> 00:00:26.580
I gotta tell you, I'm really excited
for this episode because in terms
00:00:26.585 --> 00:00:30.720
of JavaScript development, we have
one of the, my opinion, the foremost
00:00:30.725 --> 00:00:32.580
experts in JavaScript development.
00:00:32.580 --> 00:00:37.290
Joining us as the guest for this
episode, Kent Dodds, and if you've ever
00:00:37.290 --> 00:00:43.230
gone to Epic react.dev, if you've ever
just seen overall talks in the space,
00:00:43.230 --> 00:00:47.580
if you're even touched some platforms
like Remix, you've been experiencing
00:00:47.580 --> 00:00:50.220
things that Kent Dodds has done and.
00:00:50.790 --> 00:00:56.235
What's very exciting is that Kent has
an amazing blog and associated community
00:00:56.235 --> 00:00:58.395
that's tied to his overall brand.
00:00:58.785 --> 00:01:03.135
But what's great about this is that
he has gone through and developed
00:01:03.465 --> 00:01:07.935
some really great ways to handle
what we call cumulative layout shift.
00:01:08.085 --> 00:01:11.925
And that's done through low quality
image placeholders, making sure that
00:01:12.105 --> 00:01:16.275
people have content that's loading
quickly and efficiently, but also
00:01:16.605 --> 00:01:20.715
doing it in a way where they can
make sure that they know content's
00:01:20.720 --> 00:01:22.275
even gonna be appearing on the page.
00:01:22.335 --> 00:01:25.035
So those are all topics we're
gonna be talking about here today
00:01:25.215 --> 00:01:27.165
in this overall Dev Jams episode.
00:01:27.675 --> 00:01:32.565
Now, of course, with every Dev Jams
episode, my co-host Becky Peltz, who
00:01:32.565 --> 00:01:37.035
handles overall curriculum management
and program development for our
00:01:37.035 --> 00:01:38.625
developers that use Cloudinary.
00:01:38.685 --> 00:01:43.065
She's joining me for this episode, just
as we said on every single one of these.
00:01:43.475 --> 00:01:46.155
Becky, it is wonderful to have
you here for this conversation.
00:01:46.665 --> 00:01:48.205
Becky Peltz: Hey, I'm happy to be here.
00:01:48.685 --> 00:01:51.345
I we'll be learning a lot here.
00:01:51.405 --> 00:01:55.605
There's a blog that we've all
read that is, just wonderful at
00:01:55.605 --> 00:01:58.985
blending inspiration to solution.
00:01:59.525 --> 00:02:04.575
You read through it and it just flows out
this great idea and then how to solve it.
00:02:05.115 --> 00:02:09.785
And then we get to see how he
uses Cloudinary to to as a big
00:02:09.785 --> 00:02:11.475
tool in getting that solution.
00:02:12.795 --> 00:02:16.395
Sam Brace: One thing that I love about
it, and you articulated it
Load full transcript
well, is that
00:02:16.755 --> 00:02:20.295
the one thing that's nice about having
a guest like Kent on here, because as
00:02:20.300 --> 00:02:24.495
we said, he's an expert in this overall
space, is that he also is very good at
00:02:24.495 --> 00:02:28.515
being able to show the step by steps,
the understanding, sometimes historical
00:02:28.515 --> 00:02:32.385
background information you may need
to know, which I know we appreciate as
00:02:32.825 --> 00:02:36.045
educators, but it really does help to have
a holistic view of why you might wanna
00:02:36.045 --> 00:02:39.610
be doing something or what this person
experienced with the overall project.
00:02:39.780 --> 00:02:40.060
Becky Peltz: Yeah.
00:02:40.060 --> 00:02:44.894
I know he's an educator and I think
that, programmers, we're good at
00:02:44.894 --> 00:02:48.176
breaking down steps for machines, but I
think when you get into educators, you
00:02:48.180 --> 00:02:52.245
get people that can break it down for
people and it's so much appreciated.
00:02:53.385 --> 00:02:55.125
Sam Brace: Completely agree.
00:02:55.665 --> 00:02:58.965
So before we bring Kent on to be able
to talk about all the great work that
00:02:58.965 --> 00:03:03.095
he's doing with his blog presence, and
of course because me and Becky work
00:03:03.095 --> 00:03:05.454
for Cloudinary, there's gonna be some
Cloudinary things that we're gonna
00:03:05.459 --> 00:03:06.945
talk about in this overall space.
00:03:07.275 --> 00:03:11.295
But we do wanna make sure that you
guys know that if you are the first
00:03:11.295 --> 00:03:15.405
time listener, first time watcher of
this overall content, you can always go
00:03:15.410 --> 00:03:18.255
to Cloudinary dot com slash podcasts.
00:03:18.435 --> 00:03:22.755
And that's where all of our
podcasts for the two programs
00:03:22.755 --> 00:03:23.695
that are managed by the company.
00:03:24.165 --> 00:03:25.065
Are going to be.
00:03:25.365 --> 00:03:29.145
So if you ever have questions about
what past episodes, what topics have
00:03:29.145 --> 00:03:32.775
we gone and covered, they're all
going to be in that overall space.
00:03:33.015 --> 00:03:38.265
And of course you may decide to listen
to or watch some of the programs on
00:03:38.265 --> 00:03:44.305
certain services like YouTube or Apple
Podcasts or Google Podcasts or Spotify.
00:03:44.455 --> 00:03:46.185
We happen to be in all
those different places.
00:03:46.185 --> 00:03:49.875
So if this is your first time
here, welcome and of course we
00:03:49.875 --> 00:03:51.315
are very happy to have you here.
00:03:51.345 --> 00:03:54.525
And we wanna make sure that you know
where you can be catching all of these
00:03:54.525 --> 00:03:58.965
episodes down the road because this
won't be the last conversation we have.
00:03:58.965 --> 00:04:02.025
But it may be definitely one of
the best, cuz as I said, we are so
00:04:02.025 --> 00:04:03.645
excited to have Kent here today.
00:04:05.205 --> 00:04:09.335
Let's bring Kent
on and let's get
into the start of our conversation.
00:04:09.455 --> 00:04:11.585
So Kent, welcome to the program.
00:04:12.095 --> 00:04:13.255
Kent Dodds: Thank you so much.
00:04:13.255 --> 00:04:14.495
And you're right.
00:04:14.495 --> 00:04:18.425
Those were very nice words
like you said at the start.
00:04:18.430 --> 00:04:18.965
Thank you.
00:04:18.965 --> 00:04:19.565
I appreciate it.
00:04:19.565 --> 00:04:21.204
Sam Brace: And also very true, very true.
00:04:22.595 --> 00:04:26.165
People that are not completely
familiar with all the great things
00:04:26.165 --> 00:04:30.215
that you've done, all of the work
that you did to get to the spot, give
00:04:30.215 --> 00:04:31.565
us a little bit of historical data.
00:04:31.595 --> 00:04:32.795
Who's Kent and why
00:04:32.800 --> 00:04:33.315
Kent Dodds: are you here?
00:04:35.015 --> 00:04:39.320
Yeah, so I live in Utah with
my wife and four kids, and it's
00:04:39.320 --> 00:04:41.255
a very snowy day out today.
00:04:41.285 --> 00:04:44.015
It's been a very fun winter
if you enjoy snowboarding.
00:04:45.044 --> 00:04:46.145
And yeah.
00:04:46.664 --> 00:04:51.005
So I have been an educator since,
like even before I graduated.
00:04:51.010 --> 00:04:55.745
I've been teaching people the
stuff that I know, whatever it is.
00:04:55.745 --> 00:05:03.095
And I worked as a full-time engineer
for a number of companies, probably the
00:05:03.095 --> 00:05:05.145
one most people recognize is PayPal.
00:05:05.305 --> 00:05:12.775
And then I decided to go full-time
teacher because I was I just enjoyed
00:05:12.775 --> 00:05:14.475
that more and I can't do it all.
00:05:14.995 --> 00:05:16.765
Went full-time teacher.
00:05:16.765 --> 00:05:19.785
That's right around the time
I built testing JavaScript
00:05:19.785 --> 00:05:21.445
and then I built Epic React.
00:05:22.645 --> 00:05:27.315
And then I actually built my website
and lots of the stuff that we're
00:05:27.315 --> 00:05:28.195
gonna be talking about today.
00:05:28.755 --> 00:05:34.275
And then I, now I'm working on
Epic web.dev which is everything
00:05:34.280 --> 00:05:35.345
that I know about the web.
00:05:35.345 --> 00:05:39.195
And this topic will certainly
be included in that.
00:05:39.755 --> 00:05:46.415
And yeah I also did spend about 10
months working on remix, the sign
00:05:46.415 --> 00:05:51.255
behind me and the framework that
I use to build my website as well.
00:05:52.885 --> 00:05:58.305
Yeah I do plenty of stuff in the
open source space and I blog a lot.
00:05:58.385 --> 00:05:59.625
So that's me.
00:06:00.480 --> 00:06:01.350
Sam Brace: Kent, is that it?
00:06:01.350 --> 00:06:02.560
I mean that
00:06:02.560 --> 00:06:05.320
Becky Peltz: Is that all?
00:06:05.560 --> 00:06:10.300
Sam Brace: That amazingly historical
data that you have there, and it shows
00:06:10.300 --> 00:06:11.860
the overall space that you're in.
00:06:12.200 --> 00:06:16.050
It's where being an educator, but also
understanding a lot about how the web
00:06:16.050 --> 00:06:19.140
works, a lot of things that we're talking
about, of course, you're tied to the
00:06:19.140 --> 00:06:21.000
React community, the JavaScript community.
00:06:21.270 --> 00:06:25.470
So it's where you're touching a lot of
different places, but it's where to say
00:06:25.470 --> 00:06:28.530
that you've, you have some experience
working in this other area, so what
00:06:28.530 --> 00:06:32.580
you're telling people to do or not
to do there's some credence to that.
00:06:33.420 --> 00:06:35.520
Kent Dodds: Yeah I would say so.
00:06:35.790 --> 00:06:38.400
People follow my advice and
then they thank me later.
00:06:38.740 --> 00:06:42.870
And then I don't know if people follow
my advice and it doesn't work out.
00:06:42.930 --> 00:06:44.570
They just haven't mentioned anything.
00:06:44.570 --> 00:06:50.470
But I do have experience in this space
shipping apps to millions of users.
00:06:51.070 --> 00:06:56.340
And I've been developing for
the web for almost a decade now.
00:06:56.750 --> 00:06:59.610
So it's yeah I've got some stuff to say.
00:07:01.260 --> 00:07:04.380
Sam Brace: When I'm seeing comments
popping up from, people are saying like,
00:07:04.409 --> 00:07:09.330
he's also the author of React Testing
and off and a thousand NPM packages.
00:07:10.200 --> 00:07:12.460
Becky Peltz: You're being
modest, in other words.
00:07:13.880 --> 00:07:17.159
Sam Brace: Regardless of how people feel
or not feel about this, it is to say that
00:07:17.280 --> 00:07:18.900
I'm very happy that you're here today.
00:07:18.960 --> 00:07:22.320
And what I'd love to be able to
understand, so now that we can see
00:07:22.325 --> 00:07:27.790
this, you have your blog, you have
your website, so that's kentcdodds.com.
00:07:28.290 --> 00:07:32.070
What took you to the space that
you started to say yourself.
00:07:32.070 --> 00:07:34.530
I wanna start working on some of
the things that we're gonna be
00:07:34.530 --> 00:07:38.520
talking about today as I mentioned
earlier, cumulative layout shift,
00:07:38.520 --> 00:07:40.530
low quality image placeholders.
00:07:40.909 --> 00:07:44.099
Why did you start to see the need
for some of these things that
00:07:44.099 --> 00:07:45.000
we're gonna be talking about?
00:07:45.815 --> 00:07:46.530
Kent Dodds: Yeah, that's a great question.
00:07:47.159 --> 00:07:52.480
My original website at kentcdodds.com,
if you go to the web archive and look
00:07:52.480 --> 00:07:58.200
back in like 2015, the website was
basically a white screen with text that
00:07:58.200 --> 00:08:00.870
says, I'm too busy to build my website.
00:08:00.900 --> 00:08:03.419
Here's some links to my
Twitter and whatever.
00:08:03.449 --> 00:08:08.919
And then at some point I decided, I would
like to have a better online presence.
00:08:08.919 --> 00:08:13.590
And so I wrote my site in Gatsby
and statically generated it.
00:08:13.594 --> 00:08:16.979
And that's when I started writing
being really active on my blog.
00:08:17.400 --> 00:08:20.969
And one of the cool things that I
got out of Gatsby was it's built
00:08:20.969 --> 00:08:23.440
in support for image processing.
00:08:23.719 --> 00:08:29.510
So it was able to take my
image, turned it into an SVG.
00:08:29.510 --> 00:08:32.520
And so when you landed on the
page, you would see an SVG as a
00:08:32.520 --> 00:08:35.770
placeholder, and then the image
would load in and it looked awesome.
00:08:36.819 --> 00:08:41.505
There were a number of problems
with that not at least being that
00:08:41.505 --> 00:08:42.795
processing took a lot of time.
00:08:42.795 --> 00:08:47.215
And so deploying my site, even like
fixing a typo, would take 20 minutes.
00:08:47.445 --> 00:08:48.225
It was the worst.
00:08:48.230 --> 00:08:48.825
I hated that.
00:08:49.235 --> 00:08:53.955
And so you could add a bunch of caching
and stuff, but yeah, that was not fun.
00:08:53.955 --> 00:09:01.835
And so when I for that and various other
reasons, I decided to rebuild my website.
00:09:01.935 --> 00:09:04.515
And it was this really
big effort that I did.
00:09:04.615 --> 00:09:06.735
Was that last year or
maybe the year before?
00:09:07.265 --> 00:09:14.375
And yeah, in the process, I didn't want to
lose that really nice loading experience
00:09:14.375 --> 00:09:19.095
cuz my website has images everywhere.
00:09:19.095 --> 00:09:21.330
But like the biggest,
of course, is my blog.
00:09:22.050 --> 00:09:26.025
Every blog post has a header image,
and I wanted that loading experience
00:09:26.025 --> 00:09:32.535
to be as good as possible just because
when I decided I wanted to make a
00:09:32.535 --> 00:09:36.795
professional website, part of the reason
was because I wanted to illustrate that
00:09:36.795 --> 00:09:38.485
I really knew what I was talking about.
00:09:38.485 --> 00:09:42.465
Especially when I am saying,
"Hey, come learn how to build
00:09:42.525 --> 00:09:43.845
awesome websites with me".
00:09:43.850 --> 00:09:47.835
If my personal website's no good, then
okay, you're gonna teach me how to make
00:09:47.840 --> 00:09:49.875
like a website like yours, that's garbage.
00:09:49.875 --> 00:09:50.565
I don't want that.
00:09:50.565 --> 00:09:53.235
So my personal website
needs to be very good.
00:09:54.465 --> 00:09:59.975
And so avoiding poor user experiences
I've had cumulative layout shift.
00:10:00.045 --> 00:10:04.890
And that basically that, if you go to a
website and you think see things popping
00:10:04.890 --> 00:10:07.275
in that's bad cumulative layout shift.
00:10:07.275 --> 00:10:12.275
You basically want it to poof, there
it is, and nothing moves, other
00:10:12.275 --> 00:10:13.635
than things that may be animated.
00:10:14.105 --> 00:10:15.335
Nothing moves.
00:10:15.855 --> 00:10:16.155
Yeah.
00:10:16.175 --> 00:10:19.865
That's like in animations are a fun
subject that we could talk about later.
00:10:19.865 --> 00:10:22.145
But the idea is you don't
want things popping in place.
00:10:22.594 --> 00:10:27.844
And images are one of the biggest
culprits of bad cumulative layout
00:10:27.844 --> 00:10:33.785
shift as well as banners that
pop up that those are the worst.
00:10:35.245 --> 00:10:37.444
And yeah, so that, that sort of thing.
00:10:37.444 --> 00:10:40.895
Or ads, of course, like I, I don't do
any ads, but pretty much anything that
00:10:40.895 --> 00:10:46.885
you do that happens only on the client
can cause cumulative layout shift.
00:10:46.885 --> 00:10:49.775
And the fact is that we're
not server rendering images.
00:10:49.775 --> 00:10:53.584
We're server rendering an image tag that
tells the browser how to load the image.
00:10:53.584 --> 00:10:57.635
So you can technically server
render an image if you use Base
00:10:57.635 --> 00:10:59.014
64, and we can talk about that.
00:10:59.754 --> 00:11:01.145
I actually do that.
00:11:01.965 --> 00:11:06.305
But for performance reasons,
you typically don't want to
00:11:06.305 --> 00:11:09.155
server-render your image like that.
00:11:09.825 --> 00:11:13.274
There are special considerations
that you need to take into
00:11:13.295 --> 00:11:16.474
account when you're talking about
an image heavy site like mine.
00:11:19.564 --> 00:11:19.744
Becky Peltz: Yeah.
00:11:20.144 --> 00:11:25.324
You definitely don't wanna see
big chunks of things moving around
00:11:25.655 --> 00:11:30.155
and at the same time, there's a
lot of options for those chunks.
00:11:30.160 --> 00:11:33.244
And I think, you have to
pick a really good option.
00:11:34.574 --> 00:11:37.185
For, we'll see how you figured it out.
00:11:37.545 --> 00:11:40.965
But just popping up a bunch of
little tiny thumbnails isn't
00:11:40.965 --> 00:11:45.094
really gonna be a solution because
that's gonna be just distracting.
00:11:45.785 --> 00:11:48.825
Yeah, the user is looking
for a continuous experience.
00:11:48.915 --> 00:11:53.895
It's okay if it's, if it changes,
but it has to kind of transition.
00:11:53.895 --> 00:11:56.695
It can't be like "boom" kind of effect.
00:11:57.445 --> 00:12:02.745
And I think as people who write frontend
code are really dependent on the device
00:12:02.745 --> 00:12:06.105
or the browser that they're working with,
they really have to like, understand
00:12:06.105 --> 00:12:08.595
it and work with what it can do.
00:12:08.595 --> 00:12:13.275
And I think probably why Google is the one
that is telling us about cumulative layout
00:12:13.275 --> 00:12:18.625
shift and how you're gonna maybe lose your
SEO ranking if you don't, get it working.
00:12:21.599 --> 00:12:24.364
Sam Brace: Now we've talked about
cumulative layout shift, but I also
00:12:24.364 --> 00:12:28.980
know that's an area that Google has
started to look at when they came up
00:12:28.980 --> 00:12:30.870
with the concept of Core Web Vitals.
00:12:30.900 --> 00:12:35.040
That's something that I started at
least hearing about a lot back in 2021,
00:12:35.040 --> 00:12:38.880
I feel was the first time when someone
said Core Web
Vitals or Web Core Vitals
00:12:38.880 --> 00:12:40.635
or whatever they wanna, mix, match.
00:12:41.500 --> 00:12:43.620
But something called me about this.
00:12:43.860 --> 00:12:46.020
Was that also part of
the reasoning for it?
00:12:46.020 --> 00:12:49.709
It was tied to Core Web Vitals and the
scores that are associated with that?
00:12:51.230 --> 00:12:56.800
Kent Dodds: So I actually do have
metrics for my Core Web Vitals,
00:12:56.819 --> 00:12:58.160
and they're actually even public.
00:12:58.160 --> 00:13:01.140
You can find it on, if you scroll
down to the bottom of my website,
00:13:01.140 --> 00:13:03.115
there's a transparency link.
00:13:03.225 --> 00:13:05.709
I think it's, do I call it transparency?
00:13:05.790 --> 00:13:08.840
I, it might be mission or something.
00:13:09.500 --> 00:13:13.365
Yeah, "My Mission", if you go to
that that's my transparency page.
00:13:13.365 --> 00:13:20.525
And on there's a link to both my analytics
as well as my metrics for my site.
00:13:20.825 --> 00:13:23.745
So anybody who wants to
explore that a little bit.
00:13:23.925 --> 00:13:28.875
So I do keep track of the Core Web
Vitals, but I never look at it.
00:13:28.875 --> 00:13:32.925
For me, especially since I'm
not actually selling anything on
00:13:32.925 --> 00:13:35.235
my website, I'm selling myself.
00:13:35.865 --> 00:13:38.475
And the investment that you're
offering me is your time.
00:13:38.505 --> 00:13:39.724
That's really it.
00:13:39.740 --> 00:13:41.035
And also I suppose your email address.
00:13:41.445 --> 00:13:48.135
Of course I link to to courses and
stuff like that, and I do sell those,
00:13:48.135 --> 00:13:50.345
but not on my personal website.
00:13:50.345 --> 00:13:54.885
So the reason why my personal website
needs to be a good experience is
00:13:55.275 --> 00:13:58.695
just like I said to illustrate that
I do know what I'm talking about.
00:13:58.695 --> 00:14:03.215
I know how to make really awesome
experiences for the web and also because
00:14:03.215 --> 00:14:05.655
it's it's like a game of code golf.
00:14:05.685 --> 00:14:08.505
Like you just, it's fun.
00:14:08.595 --> 00:14:10.395
How good can I make this experience?
00:14:11.405 --> 00:14:20.005
And for businesses where you are selling
something on the site, it can make a
00:14:20.095 --> 00:14:25.655
drastic impact on your bottom line based
on how quickly your application loads
00:14:25.655 --> 00:14:31.704
and how confident users are that your
application is doing what it should be.
00:14:31.735 --> 00:14:36.875
That it's capable of doing
whatever it is that you're selling.
00:14:37.135 --> 00:14:40.645
So if users land on your site and
things are bouncing around a lot, it
00:14:40.645 --> 00:14:44.875
really reduces their confidence in
your ability to provide whatever it
00:14:44.875 --> 00:14:46.315
is that you're intending to provide.
00:14:47.005 --> 00:14:49.875
Becky Peltz: Yeah, a website is
a reflection of your product.
00:14:50.815 --> 00:14:55.025
If you're doing a lot of crazy weird stuff
on your website, maybe the product is a
00:14:55.025 --> 00:14:58.075
little funky too, just leave it alone.
00:14:58.525 --> 00:14:58.765
Kent Dodds: Yeah.
00:14:58.765 --> 00:15:02.065
I sometimes will pick restaurants
based on how good their website is.
00:15:03.015 --> 00:15:03.505
Sam Brace: Yeah.
00:15:04.855 --> 00:15:08.575
I actually have done the exact same
thing, Kent, where I'm like, oh, that
00:15:08.575 --> 00:15:11.760
probably is a reflective of the overall
service that I'm gonna be getting.
00:15:13.920 --> 00:15:16.680
Kent Dodds: And maybe it's not
like it, it might be, it might not
00:15:16.680 --> 00:15:19.830
be, but it doesn't actually matter
cuz what matters is, did you go?
00:15:19.930 --> 00:15:28.600
And so yeah, it does impact the
customer's impression of you.
00:15:29.730 --> 00:15:30.449
Sam Brace: Absolutely.
00:15:30.480 --> 00:15:34.290
And when, and I think what's also
important, like whenever I thought
00:15:34.290 --> 00:15:38.699
about the Core Web Vitals as well,
is that they're normally done because
00:15:38.790 --> 00:15:42.480
Google is looking at it from a sense of
trying to make the best user experience.
00:15:42.480 --> 00:15:45.569
It's not based upon trying to hit
some score that's arbitrary and
00:15:45.569 --> 00:15:47.339
doesn't have significant value to it.
00:15:47.610 --> 00:15:52.530
They're looking at to make sure that when
we're saying this has XYZ score to it,
00:15:52.530 --> 00:15:58.380
or 123 score to it, it's indicating some
factor of quality as overall associated.
00:15:58.640 --> 00:16:02.880
So I think that's what you've ultimately
done with this overall experience to
00:16:03.240 --> 00:16:06.750
be able to provide these low quality
image placeholders, be able to do
00:16:06.750 --> 00:16:10.645
the work to make sure the layout
shifts aren't constantly shifting.
00:16:11.555 --> 00:16:13.980
To say that you did, to
increase the quality.
00:16:13.980 --> 00:16:17.280
And I think that's one thing that people
should look at from an episode like this,
00:16:17.280 --> 00:16:23.010
is that if you're trying to increase the
quality of their overall web presence, a
00:16:23.010 --> 00:16:26.880
lot of the practices you did here who are
directly applicable to things they could
00:16:26.880 --> 00:16:28.599
possibly do for their content as well.
00:16:29.485 --> 00:16:29.675
Becky Peltz: Yeah.
00:16:29.675 --> 00:16:29.845
Yeah.
00:16:30.005 --> 00:16:34.785
They're unleashing tons of crawlers on
the web and these things need to act fast.
00:16:34.785 --> 00:16:38.475
And if those crawlers are waiting
for images to load before they can
00:16:38.475 --> 00:16:42.535
figure out what the content is, that's
gonna be a problem for them, too.
00:16:43.165 --> 00:16:45.405
It works both ways.
00:16:46.245 --> 00:16:49.905
It's like machines are
sensitive to it as humans.
00:16:52.755 --> 00:16:55.125
Sam Brace: So what I wanna jump
into, so
I'm, what I'm showing
00:16:55.130 --> 00:16:58.725
here is the blog post that kind of
inspired this overall conversation.
00:16:58.725 --> 00:17:01.725
So if people are saying, I wanna
follow along, you just have to go
00:17:01.725 --> 00:17:05.535
to the kentcdodds.com and make sure
that you're looking for the "building
00:17:05.535 --> 00:17:10.455
an awesome image loading experience"
post that you put out in late 2021.
00:17:11.159 --> 00:17:15.629
But you can see here this video that
you created is articulating exactly
00:17:15.629 --> 00:17:21.209
what you ultimately have as the result
of this effort, where it's making sure
00:17:21.209 --> 00:17:27.329
that the image has a place, it's showing
a low quality, blurred version of it,
00:17:27.419 --> 00:17:31.860
and then the full image will eventually
come in, and that's what we're calling
00:17:31.860 --> 00:17:33.629
the low quality image placeholder.
00:17:33.659 --> 00:17:36.040
Am I correct about that overall summary?
00:17:36.850 --> 00:17:37.040
Yeah.
00:17:37.600 --> 00:17:38.520
Kent Dodds: That's the basic idea.
00:17:39.389 --> 00:17:39.870
Sam Brace: Okay.
00:17:39.870 --> 00:17:43.980
So looking at this overall situation
here, I think the first section
00:17:43.985 --> 00:17:47.459
that we can see that you're touching
upon is the overall layout shift.
00:17:47.459 --> 00:17:49.989
As we mentioned, we don't want
it where you have text and it's
00:17:50.010 --> 00:17:53.669
jumping to be able to bring in
the overall space for the image.
00:17:53.850 --> 00:17:58.560
We want it where you have the
layouts make, it's almost static.
00:17:58.920 --> 00:18:02.010
It's where things should be in
certain places at certain times.
00:18:02.340 --> 00:18:06.370
It looks like you were able
to do that with Tailwind.
00:18:06.750 --> 00:18:09.300
Talk to me about this overall
plugin that you had here that was
00:18:09.300 --> 00:18:10.530
helping with the layout shift.
00:18:11.070 --> 00:18:12.085
Kent Dodds: Yeah, sure.
00:18:12.965 --> 00:18:15.510
The principle is aspect ratio.
00:18:15.930 --> 00:18:21.384
So you don't know necessarily how big the
image is going to be a lot of the time.
00:18:22.205 --> 00:18:25.114
But you might know the
aspect ratio of the image.
00:18:25.944 --> 00:18:31.395
So because the, you might say, I want
the width to be 90% of the viewport.
00:18:31.415 --> 00:18:33.705
The viewport could be
any number of pixels.
00:18:34.284 --> 00:18:37.594
But you know the aspect ratio
of the width and the height.
00:18:38.014 --> 00:18:45.445
And Tailwind actually now supports aspect
ratio as a built-in feature of Tailwind.
00:18:45.445 --> 00:18:47.834
So you don't have to
include a plug-in anymore.
00:18:48.684 --> 00:18:54.165
But the idea is just using that class
name and it's, I should also say that
00:18:54.165 --> 00:18:57.465
aspect ratio is a built-in feature of
the browser that Tailwind is just using.
00:18:58.574 --> 00:19:04.665
But yeah, so that aspect ratio just
will say, "Hey, I know that the image
00:19:04.665 --> 00:19:08.415
isn't here yet, but when it is, this is
how much space it's going to take up"
00:19:08.725 --> 00:19:11.600
relative to how wide it is or whatever.
00:19:11.600 --> 00:19:14.490
And so then the browser can
say, "okay, I'll just leave
00:19:14.495 --> 00:19:16.860
that much space for that image".
00:19:16.860 --> 00:19:19.470
And so when the image shows
up, it just pops in place and
00:19:19.470 --> 00:19:20.590
doesn't have to move anything.
00:19:21.220 --> 00:19:24.860
So that's actually a really,
even if you're not doing the nice
00:19:24.929 --> 00:19:29.590
placeholder or anything like that,
that by itself is really useful.
00:19:29.860 --> 00:19:33.879
It can be kinda tricky if you don't know
what the aspect ratio is going to be.
00:19:34.229 --> 00:19:37.030
So if you're thinking about Instagram
and you got pictures that are all
00:19:37.030 --> 00:19:39.460
sorts of different, you've got this
grid and there are pictures coming in
00:19:39.460 --> 00:19:41.510
all over the place that can be tricky.
00:19:42.250 --> 00:19:47.020
The solution to that really is to just
store the aspect ratio as part of the
00:19:47.020 --> 00:19:52.870
data for the for the images that you're
displaying so that when you server
00:19:52.870 --> 00:19:56.649
render or when you end up starting to
render those images, you can include
00:19:56.655 --> 00:20:00.700
that because it, there's really no other
way to solve this particular problem.
00:20:00.700 --> 00:20:04.394
That's precisely what aspect ratio
CSS property was created for.
00:20:04.935 --> 00:20:09.280
And it is definitely better than
having pictures pop in place cause even
00:20:09.280 --> 00:20:12.229
if we're talking about that sort of
grid of photos, you're gonna have one
00:20:12.739 --> 00:20:14.590
pop in and then one above it pop in.
00:20:14.590 --> 00:20:16.659
And so that shifts this one
down and they're, they'll just
00:20:16.659 --> 00:20:17.770
be going all over the place.
00:20:17.774 --> 00:20:18.909
It just does not feel good.
00:20:19.210 --> 00:20:23.290
So aspect ratio is the solution to
content layout shift for images.
00:20:24.375 --> 00:20:28.155
Becky Peltz: And I noticed you linked
to the article on setting height
00:20:28.155 --> 00:20:29.685
and with on images is important.
00:20:29.715 --> 00:20:32.565
Again, because for a while
people went away from that.
00:20:32.565 --> 00:20:36.405
There was, initially height equals
blah, what width equals blah.
00:20:36.405 --> 00:20:39.705
And then the browser could figure out
the aspect ratio that you were going for.
00:20:40.095 --> 00:20:42.185
But people stopped doing that.
00:20:42.635 --> 00:20:49.795
And a lot of it probably because we went
from, just a desktop to a mobile and it
00:20:49.795 --> 00:20:55.275
didn't really make sense in that respect,
but this is a really good point here.
00:20:57.395 --> 00:21:00.240
Sam Brace: What it also seems like
it's directly tied to the next
00:21:00.240 --> 00:21:03.879
point that you raised here when
you're working on responsive images.
00:21:03.979 --> 00:21:08.939
Because aspect ratio, of course,
is based upon the actual ratio.
00:21:09.000 --> 00:21:11.754
It has nothing to do with
pixel width or pixel height.
00:21:12.185 --> 00:21:16.290
So when we're saying we want it to be,
let's say, a three by two aspect ratio
00:21:16.500 --> 00:21:20.310
that we're gonna be able to allocate
the space for, that's gonna be three
00:21:20.310 --> 00:21:26.129
by two for tablet, for desktop, for
mobile, or maybe you need it to change,
00:21:26.129 --> 00:21:29.070
but it's indicating what it should
be based on these different areas.
00:21:29.070 --> 00:21:33.209
So I think it's leading us into the
conversation about what you've done here
00:21:33.330 --> 00:21:38.129
with making sure that everything you are
doing when it comes to this effort also
00:21:38.129 --> 00:21:40.520
is tied to responsive design as well.
00:21:42.120 --> 00:21:42.370
Kent Dodds: Yeah.
00:21:43.169 --> 00:21:49.515
So if I'm on a desktop with a huge 5K
monitor with this ridiculous resolution,
00:21:49.515 --> 00:21:54.435
then I can load an image that's,
really high quality and, pixel perfect.
00:21:54.435 --> 00:21:55.534
And that's awesome.
00:21:55.965 --> 00:21:59.555
The problem is that's just
a ton of pixels, and that's
00:21:59.555 --> 00:22:01.794
a lot, a very big image.
00:22:02.535 --> 00:22:07.485
And then if I shrink that down to
something that I can see on a device and
00:22:07.485 --> 00:22:09.225
I'm using the exact same image either way.
00:22:09.895 --> 00:22:14.659
Then I am, basically what the device
is doing is throwing away a bunch
00:22:14.659 --> 00:22:16.990
of pixels that it doesn't need.
00:22:17.540 --> 00:22:20.254
It can't display that
many pixels on the device.
00:22:20.254 --> 00:22:23.750
Anyway, so it'll look really
nice and crisp, but there's a
00:22:23.750 --> 00:22:25.820
lot of wasted download there.
00:22:27.000 --> 00:22:32.659
And the web platform comes in clutch
for us again with the sizes and source
00:22:32.659 --> 00:22:35.050
set attributes on the image tag.
00:22:35.610 --> 00:22:38.300
This was something new for me
when I was working on my site.
00:22:38.300 --> 00:22:39.860
I'd never used these properties before.
00:22:40.830 --> 00:22:44.720
But the basic idea is these
are configuration options that
00:22:44.720 --> 00:22:47.510
say so we'll start with sizes.
00:22:48.830 --> 00:22:54.805
It's a comma separated list of basically
you could think of it as a tuple.
00:22:54.825 --> 00:23:00.555
So you've got an array of first the media
query that should match and then the
00:23:00.555 --> 00:23:03.635
width of the image at that media query.
00:23:04.085 --> 00:23:09.115
And I can say for small sizes, then this
is how wide the image should be, for
00:23:09.415 --> 00:23:11.175
bigger sizes, this is how wide and so on.
00:23:11.715 -->
00:23:18.000
And so I'm going actually in the blog post
here, I'm going the opposite direction.
00:23:18.110 --> 00:23:21.695
Big size, this is how big or how wide
the image is gonna be and so forth.
00:23:22.125 --> 00:23:26.555
I only know that because I know that
the CSS that I've applied and so I
00:23:26.555 --> 00:23:32.445
added this later on and I just pulled
up my site locally and looked at
00:23:32.445 --> 00:23:35.175
how wide the image was at different
breakpoints, and then just said,
00:23:35.175 --> 00:23:40.005
here's the size of the the image or
the width that it's gonna be here.
00:23:40.395 --> 00:23:48.560
So then the source set says, here is the
URL for when the screen is at this size.
00:23:48.920 --> 00:23:55.085
So if the screen is this big, then this
is the URL to get that sized image.
00:23:55.425 --> 00:24:02.345
That allows you to really fine tune
which image is loaded for a given
00:24:02.345 --> 00:24:08.825
screen size which avoids the wasted
bytes and ultimately results in
00:24:08.825 --> 00:24:11.885
a much faster loading experience.
00:24:12.695 --> 00:24:12.875
Becky Peltz: Yeah.
00:24:12.875 --> 00:24:16.135
And with your sizes, because they're
always concerned, really they're really
00:24:16.310 --> 00:24:18.195
focusing on width rather than height.
00:24:18.195 --> 00:24:23.985
You're gonna see that the size that gets
assigned is really based on the width.
00:24:24.084 --> 00:24:28.125
So you, you have a width of 50, then
you're gonna get 50 and width 30, 30.
00:24:28.635 --> 00:24:29.665
So feeling that.
00:24:30.155 --> 00:24:30.285
Kent Dodds: Okay.
00:24:30.805 --> 00:24:34.695
Yeah I'm not sure if there's a way to
switch it so that it goes by the height,
00:24:34.725 --> 00:24:38.385
because if you wanted a horizontally
scrolled thing or something, I don't
00:24:38.385 --> 00:24:40.175
know, people come up with funny things.
00:24:40.175 --> 00:24:43.725
I don't know what the world of
VR says about all of this stuff
00:24:44.115 --> 00:24:48.160
is very width centric or, the
way that we build most websites.
00:24:48.710 --> 00:24:52.515
But yeah, this works out
well for 99% of people.
00:24:53.535 --> 00:24:54.025
Becky Peltz: Yeah.
00:24:54.030 --> 00:24:54.225
Yeah.
00:24:54.225 --> 00:24:54.795
No, totally.
00:24:56.325 --> 00:24:59.655
Sam Brace: So in looking at this, so
now scrolling down to the post, you
00:24:59.655 --> 00:25:03.305
can see that now that we've understand
like source and source set that we
00:25:03.805 --> 00:25:08.025
covered at this point, we can see how
this is being done for a blog post
00:25:08.025 --> 00:25:12.555
like yours, where we're looking at the
overall URLs that are coming from here.
00:25:13.025 --> 00:25:17.910
And of course now I'm starting to see
Cloudinary and for his first case.
00:25:17.910 --> 00:25:22.080
So talk to me about what's ultimately
happening in this situation, because I
00:25:22.085 --> 00:25:25.560
can see that you're declaring the whiffs
as we've talked about, but then you're
00:25:25.560 --> 00:25:30.990
also doing certain other things that are
tied to this overall place that looks
00:25:30.995 --> 00:25:35.910
to be at least longer in URL compared to
what you have for the initial example.
00:25:36.210 --> 00:25:37.540
So talk to me about that.
00:25:38.580 --> 00:25:38.970
Kent Dodds: Yeah, sure.
00:25:39.070 --> 00:25:44.310
My Cloudinary URLs, this is one of
the things that I just love about
00:25:44.310 --> 00:25:48.770
Cloudinary, is the capability to
transform the images on demand.
00:25:49.475 --> 00:25:57.660
And what's cool about this is because
I have q_auto and f_auto, this will
00:25:57.870 --> 00:26:02.360
not only give me well, and then of
course I have that w_ that specifies
00:26:02.375 --> 00:26:03.660
the width of the image that I want.
00:26:04.040 --> 00:26:08.790
But this gives me not only the right
size of image, but even the right
00:26:08.790 --> 00:26:13.425
quality and format based on whatever
browser is requesting this image.
00:26:13.985 --> 00:26:18.020
Which is just awesome because we
have a bunch of different formats
00:26:18.370 --> 00:26:25.500
whether it be a GIF or a PNG or a
JPEG or a WebP or AVIF, all sorts of
00:26:25.500 --> 00:26:28.200
formats that various browsers support.
00:26:28.620 --> 00:26:33.270
And it's impossible for me to know
at development time what browser
00:26:33.270 --> 00:26:36.140
is going to be requesting this,
cause it's literally all of them.
00:26:36.370 --> 00:26:41.280
And having Cloudinary be able
to dynamically serve the proper
00:26:41.310 --> 00:26:45.439
image at request time is awesome.
00:26:45.580 --> 00:26:49.630
And it should be noted also that we
do still have the regular source,
00:26:50.070 --> 00:26:56.310
attribute and that I just sent to like
the middle between all of these sizes.
00:26:56.310 --> 00:27:00.270
So if your browser doesn't support the
source set and sizes attributes, then
00:27:00.270 --> 00:27:06.480
sorry, you're just gonna get like a middle
of the road thing here which is probably
00:27:06.485 --> 00:27:08.010
your experience on the entire web.
00:27:08.270 --> 00:27:12.389
If your browser is that old, it's gonna
be a pretty poor experience anyway.
00:27:13.600 --> 00:27:17.850
But but yeah, so I have a bunch
of different sizes based off
00:27:17.855 --> 00:27:22.680
of what made sense for wherever
I'm rendering this image.
00:27:22.680 --> 00:27:26.490
This one in particular is the
header image that I have on my blog.
00:27:27.915 --> 00:27:30.885
Sam Brace: And then looking at this
so I can see here you have very clear
00:27:30.885 --> 00:27:34.665
widths that you've declared when it
comes to this, and as you said, like your
00:27:34.665 --> 00:27:40.365
source in here is in between the range
that you have between 280 and 3,100.
00:27:40.845 --> 00:27:43.065
But how are you getting those sizes?
00:27:43.265 --> 00:27:46.425
Is that just saying double the
next one and then going it
up?
00:27:46.425 --> 00:27:48.555
Or is there tools or
utilities that you're using?
00:27:48.735 --> 00:27:50.955
Kent Dodds: Yeah, I wish there
were tools and utilities and there.
00:27:50.955 --> 00:27:51.975
There may be now.
00:27:52.325 --> 00:27:55.935
But when I was writing this I didn't
know of anything, so I literally just
00:27:55.935 --> 00:27:57.825
pulled up my site, opened up the dev.
00:27:58.920 --> 00:28:03.210
And then just resized it every now
and then, and just said that, that
00:28:03.210 --> 00:28:04.260
looks like a pretty good size.
00:28:04.260 --> 00:28:10.650
And then I grabbed what that size
was and I have the next block of
00:28:10.650 --> 00:28:16.410
code here is the get image props that
accepts what I call an image builder.
00:28:16.410 --> 00:28:19.740
It's just a special little
function that allows me to generate
00:28:19.740 --> 00:28:22.420
these URLs, cuz who's gonna
write that URL by hand, not me.
00:28:24.050 --> 00:28:29.820
And then I can specify the widths
that I care about for this particular
00:28:29.820 --> 00:28:34.635
image and the sizes, as well as any
additional transformations I wanna make.
00:28:35.064 --> 00:28:42.590
And with that I can very easily
just say, here are the different
00:28:42.590 --> 00:28:46.530
widths that I want to be concerned
about for this particular image.
00:28:46.590 --> 00:28:48.990
And these are the sizes
when those widths matter.
00:28:50.270 --> 00:28:53.990
And yeah that ends up working out.
00:28:54.370 --> 00:28:56.640
If you scroll down a little
bit further, you can see an
00:28:56.640 --> 00:28:58.230
example of using that utility.
00:28:59.490 --> 00:29:05.040
It ends up being a relatively
simple way to to manage this.
00:29:05.280 --> 00:29:10.340
Though there are some tools that I
mentioned at the bottom of the blog post
00:29:10.940 --> 00:29:13.530
that can make this process even easier.
00:29:13.530 --> 00:29:16.350
I'm not sure exactly how they
accomplish that, because I feel like
00:29:16.350 --> 00:29:20.730
every image experience is gonna be
actually a little bit different.
00:29:21.660 --> 00:29:26.340
But yeah, this is what I came up with
and it's been running on my site for
00:29:26.429 --> 00:29:27.840
quite a while now, and it works great.
00:29:28.649 --> 00:29:31.230
Becky Peltz: Yeah, and it's nice that
you've codified it because if you
00:29:31.230 --> 00:29:34.980
decide you wanna change those widths,
you just change a few numbers here
00:29:34.980 --> 00:29:39.539
in your code and you can spin up a
whole other set of responsive images.
00:29:39.979 --> 00:29:40.899
Kent Dodds: Yeah, mhmm.
00:29:41.759 --> 00:29:44.250
Sam Brace: Now, one thing that, I
saw a comment just come through here
00:29:44.250 --> 00:29:48.270
and saying "this approach would work
potentially amazing for videos too".
00:29:48.330 --> 00:29:52.050
Based on your experience, do you feel
like that's correct, or do you feel like
00:29:52.054 --> 00:29:53.820
there's any caveats to that statement?
00:29:54.750 --> 00:29:58.889
Kent Dodds: Yeah, I actually I'm guessing
I haven't looked in this, but I'm guessing
00:29:58.889 --> 00:30:01.209
that videos also have a source set.
00:30:01.709 --> 00:30:03.915
And sizes props.
00:30:03.915 --> 00:30:04.965
I can't imagine why they wouldn't.
00:30:05.355 --> 00:30:12.855
And Cloudinary also has support
for on demand video as well.
00:30:12.855 --> 00:30:16.035
So I can't imagine why you
wouldn't use this for that.
00:30:16.245 --> 00:30:18.615
I don't have a lot of use
cases for video on my site.
00:30:18.615 --> 00:30:23.465
Normally I just embed a
YouTube or something like that.
00:30:23.955 --> 00:30:25.665
Cuz yeah, I just don't do it enough.
00:30:26.625 --> 00:30:31.185
But yeah, it sounds like that would be
a pretty good solution for that as well.
00:30:31.785 --> 00:30:32.205
Sam Brace: Excellent.
00:30:32.205 --> 00:30:34.905
And yeah and shout out to the
community for being able to address
00:30:34.905 --> 00:30:37.335
things like this as we're be going
through this overall process too.
00:30:38.145 --> 00:30:41.745
So it seems like some of this was
inspired, I know you mentioned
00:30:41.745 --> 00:30:45.705
Gatsby earlier, but also this was
inspired by what Unsplash has been
00:30:45.710 --> 00:30:47.255
doing with your placeholder process.
00:30:47.325 --> 00:30:52.275
Talk to me about this and maybe what
did you extrapolate from what Unsplash
00:30:52.275 --> 00:30:55.725
is doing to be able to keep going
down this process with your own blog?
00:30:56.685 --> 00:30:57.215
Kent Dodds: Yeah, sure.
00:30:57.215 --> 00:31:05.055
Unsplash is like probably the
pinnacle of image display on the web.
00:31:05.055 --> 00:31:09.705
Like they, they do just a silly
amount of work on displaying images.
00:31:10.245 --> 00:31:16.935
And so when I moved away from using
Gatsby and I still wanted to have this
00:31:16.935 --> 00:31:21.915
nice load loading experience I tried
to figure out, okay, so how do I have a
00:31:21.915 --> 00:31:27.014
nice placeholder that I used to have with
Gasby and I thought about the SVG thing.
00:31:27.044 --> 00:31:30.165
But SVGs sometimes look really funny.
00:31:31.004 --> 00:31:32.425
They do not.
00:31:32.445 --> 00:31:34.335
I mean they're very small
and that's quite nice.
00:31:34.340 --> 00:31:40.855
And they, server render fine which
is also nice, but yeah, the images
00:31:40.875 --> 00:31:43.905
can sometimes or the placeholder
can sometimes look very odd.
00:31:44.415 --> 00:31:53.235
And so I I've seen Unsplash and Medium and
others will have this placeholder that's
00:31:53.240 --> 00:31:55.565
just like a blurred version of the image.
00:31:56.145 --> 00:32:01.500
And what I discovered as I was reverse
engineering what they were doing, I
00:32:01.500 --> 00:32:05.750
would look at what was server rendered,
and it turns out they server render
00:32:05.754 --> 00:32:07.330
the primary color of the image.
00:32:07.330 -->
00:32:10.380
So they do some pre-processing
of the image, determine
00:32:10.399 --> 00:32:11.540
what the primary color is.
00:32:12.070 --> 00:32:18.180
And then they also and that's what
ends up being so server-rendered.
00:32:18.230 --> 00:32:21.170
Then another thing that they do,
they pre-process the image to
00:32:21.260 --> 00:32:22.995
create what's called a blur hash.
00:32:23.034 --> 00:32:25.700
And this is actually,
it's an open source thing.
00:32:25.700 --> 00:32:32.229
You can go grab it yourself with the
blur hash is like 30 characters max of
00:32:33.110 --> 00:32:38.780
just random, seemingly random characters
that somehow, it just is magic to me.
00:32:38.780 --> 00:32:43.090
But they somehow represent a
blurred version of the image.
00:32:43.290 --> 00:32:44.750
It's like total magic.
00:32:44.750 --> 00:32:45.889
I don't understand how this works.
00:32:45.889 --> 00:32:51.090
Becky Peltz: Base64, a Base64 version
of a blurry image that they can move in
00:32:51.090 --> 00:32:53.720
quickly, but it has to be a small string
00:32:54.400 --> 00:32:54.920
.
Kent Dodds: Yeah.
00:32:54.980 --> 00:32:58.770
It's actually, it's not even a base
64, because they're using characters
00:32:58.770 --> 00:33:01.165
that are not base 64 characters.
00:33:01.455 --> 00:33:07.639
Some cool algorithm that
somebody figured out.
00:33:07.639 --> 00:33:12.360
And what they do though is they
feed this into a canvas and then
00:33:12.365 --> 00:33:17.910
the canvas can draw out the image
based on that that blur hash.
00:33:18.240 --> 00:33:22.590
So what's interesting though,
or unfortunate is that
00:33:22.590 --> 00:33:24.090
canvas doesn't server render.
00:33:24.680 --> 00:33:28.020
There are probably people doing some
mad scientist stuff to make canvas
00:33:28.020 --> 00:33:29.440
sort of server render in some ways.
00:33:29.440 --> 00:33:31.910
But yeah, that, that's just not a thing.
00:33:32.390 --> 00:33:34.200
There's no server rendering of canvas.
00:33:34.590 --> 00:33:40.580
And so that's why they have their
three-step process of first server
00:33:40.580 --> 00:33:43.860
render the primary color, and then
show the blurred version with blur
00:33:43.860 --> 00:33:45.600
hash and then the final image loads.
00:33:45.990 --> 00:33:49.440
Now, this is actually not a big
problem for oh, and the other thing
00:33:49.440 --> 00:33:52.020
is the blur hash library is not small.
00:33:52.020 --> 00:33:53.940
It's not huge, but it's not small either.
00:33:54.240 --> 00:33:57.030
So that's another thing to consider
when we're talking about making
00:33:57.030 --> 00:34:02.080
things fast and load as little
JavaScript as possible and all that.
00:34:02.500 --> 00:34:06.430
This isn't a big problem for
Unsplash because lots of the time,
00:34:07.100 --> 00:34:10.210
people will show up to the site
and then they'll click on images.
00:34:10.210 --> 00:34:13.480
And if they've already got everything
loaded, then we're not server
00:34:13.480 --> 00:34:14.620
rendering those images anymore.
00:34:14.620 --> 00:34:16.960
Now we're rendering
them on the client side.
00:34:17.139 --> 00:34:22.695
So you actually will not see the full
primary color displayed like we see here
00:34:23.125 --> 00:34:27.730
when you're on Unsplash, because you
typically are, you go to unsplash.com
00:34:27.730 --> 00:34:30.699
and then you click on an image and
you, they already have the blur hash
00:34:30.699 --> 00:34:34.150
right there, so they don't have to
server or render the the primary color.
00:34:34.750 --> 00:34:38.530
So for me though, lots of times
people just land on my blog post.
00:34:38.530 --> 00:34:40.569
In fact, most of the time they do.
00:34:40.569 --> 00:34:44.830
So I didn't want to have this three
step process where we're displaying the
00:34:44.830 --> 00:34:48.699
primary color first, cuz it just, it felt
wasteful and a lot of the time the people
00:34:48.699 --> 00:34:52.000
wouldn't even see the blurred version
anyway, cuz Cloudinary's CDN is very fast
00:34:52.270 --> 00:34:54.245
and so we're gonna get the image anyway.
00:34:54.665 --> 00:35:02.109
And so having that three steps
just didn't make any sense to me.
00:35:02.399 --> 00:35:05.609
Yeah, that was honestly just
a fun learning experience.
00:35:05.609 --> 00:35:09.299
I didn't actually use any of
their techniques myself because
00:35:09.975 --> 00:35:14.095
I didn't want to to do the canvas
approach or the primary color thing.
00:35:15.205 --> 00:35:17.205
Sam Brace: One question I have
about the primary color thing.
00:35:17.205 --> 00:35:22.634
So if I go back up to the overall script
that we're showing you here, and you can
00:35:22.634 --> 00:35:25.484
see that we have these transformations
and you have the background call on
00:35:25.484 --> 00:35:28.575
this case, is that the primary color
coming through in that situation?
00:35:28.964 --> 00:35:30.264
Kent Dodds: Yeah, that's a great question.
00:35:30.334 --> 00:35:36.825
So I think that is just
for transparent images.
00:35:36.854 --> 00:35:40.685
Like I have a couple blog posts that
have a transparent background and
00:35:40.685 --> 00:35:44.725
I decided at some point that they
just look funny, to be transparent.
00:35:44.745 --> 00:35:47.274
And so I can't remember
what color that is.
00:35:47.535 --> 00:35:52.015
But it was just like a good
background color that's generally
00:35:52.015 --> 00:35:54.765
use or good for anything that
has a transparent background.
00:35:54.964 --> 00:35:58.955
No there's no I'm not like
determining what the primary
00:35:58.955 --> 00:36:00.705
color is and putting it in there.
00:36:00.765 --> 00:36:01.464
That's hard coded.
00:36:02.070 --> 00:36:03.690
Sam Brace: No, but I still
like this approach though.
00:36:03.690 --> 00:36:04.980
Cause it's a flat color.
00:36:04.980 --> 00:36:06.780
It's showing this is
where something should be.
00:36:06.780 --> 00:36:09.810
So it may, it makes sense why you
would do this type of
a transformation.
00:36:09.815 --> 00:36:13.110
So it may not be exactly like
what we saw with Unsplash, but
00:36:13.680 --> 00:36:15.170
it is showing similar purpose.
00:36:17.700 --> 00:36:20.520
So moving on to you.
00:36:20.580 --> 00:36:24.600
So now we've gone through the overall
process here of talking about what
00:36:24.600 --> 00:36:29.010
you've gone and done and we can
break down some of this, but we've
00:36:29.010 --> 00:36:30.990
touched upon Base 64 encoding.
00:36:31.555 --> 00:36:35.424
For those that aren't fully
aware of what we even mean when
00:36:35.424 --> 00:36:36.294
we say something like that.
00:36:36.294 --> 00:36:40.645
What is Base 64 encoding and why would
you even wanna do something like that?
00:36:41.865 --> 00:36:47.504
Kent Dodds: Yeah base 64 encoding
is just a way to represent
00:36:47.754 --> 00:36:49.634
binary data as a string.
00:36:50.115 --> 00:36:54.805
And like in, in particular
as like a string that's using
00:36:54.805 --> 00:36:55.975
characters that we recognize.
00:36:56.435 --> 00:37:04.464
But the particular nicety of base 64
is that it can be used as the source
00:37:04.464 --> 00:37:06.174
attribute for an image element.
00:37:06.475 --> 00:37:08.960
It can actually be used as a source
attribute for a lot of things.
00:37:09.190 --> 00:37:14.640
There's another place on my website,
it's the Call Kent podcast where you can
00:37:15.000 --> 00:37:19.720
actually record yourself asking a question
and that will save to my database.
00:37:19.720 --> 00:37:23.520
And then I record my response later, and
then that turns into a podcast episode.
00:37:23.790 --> 00:37:24.490
It's actually very cool.
00:37:24.600 --> 00:37:31.560
And I use Base64 encoding to set the
source attribute of an audio tag so I can
00:37:31.560 --> 00:37:33.930
preview what they've recorded and stuff.
00:37:33.930 --> 00:37:42.120
So you can use Base64 to encode just about
anything into what is a readable string
00:37:42.120 --> 00:37:44.725
and it's not necessarily really small.
00:37:45.255 --> 00:37:51.475
But interestingly, that that audio
file that I create when people record
00:37:51.475 --> 00:37:56.095
themselves in the Call Kent podcast, I
tried saving it to my database as binary,
00:37:56.095 --> 00:38:00.475
and I then I tried saving it to my
database as Base64 and Base64 was smaller.
00:38:00.475 --> 00:38:04.105
So I probably did something wrong, but I
was, because I was very surprised by that.
00:38:04.615 --> 00:38:09.965
But that's how it's saved in my database
today is I'll save it as Base64.
00:38:09.985 --> 00:38:18.955
With that the binary data that I
want to turn into Base64 is a blurred
00:38:18.955 --> 00:38:21.415
version of the image, my placeholder.
00:38:21.475 --> 00:38:23.405
I want to turn that into Base64.
00:38:23.695 --> 00:38:28.285
And the reason that I wanna do that is
so that I can render my blog post with
00:38:28.285 --> 00:38:32.545
that Base64 hard coded as the source
attribute so that the browser doesn't
00:38:32.545 --> 00:38:36.225
have to actually make any request
to display that placeholder image.
00:38:37.055 --> 00:38:40.484
And yeah, that's the entire reason
that we're doing Base64 at all.
00:38:40.484 --> 00:38:44.355
Because if I what's cool with Cloudinary
is I can just say, "Hey, give me an
00:38:44.355 --> 00:38:48.615
image that has a width of a hundred
and give it the effect of a blur of a
00:38:48.615 --> 00:38:50.774
thousand", whatever that unit means.
00:38:50.774 --> 00:38:51.524
I don't know what it means.
00:38:51.524 --> 00:38:55.024
I tried a bunch of
numbers and that worked.
00:38:55.325 --> 00:38:57.325
Becky Peltz: Best way to figure it out.
00:38:57.345 --> 00:38:57.975
Kent Dodds: Yeah, exactly.
00:38:58.335 --> 00:39:03.855
And then and I also specified
the format as WebP, just because
00:39:03.855 --> 00:39:05.005
this is my server doing it.
00:39:05.005 --> 00:39:08.305
So I can't rely on whatever
browsers are requesting this.
00:39:09.825 --> 00:39:16.240
Anyway, I make a fetch request on the
server at runtime to this, that gives me
00:39:16.240 --> 00:39:23.319
back the image data, which I then encode
with Base64 and then set as the source
00:39:23.859 --> 00:39:29.589
property of my image as the background of
the image that's going to be loaded later.
00:39:29.859 --> 00:39:36.129
So the drawback of using Base64 versus the
blur hash is Base64 is 10 times bigger.
00:39:36.299 --> 00:39:41.299
In, practice it's 10 times
bigger of, a couple characters
00:39:41.319 --> 00:39:42.520
is actually not a whole lot.
00:39:42.520 --> 00:39:46.689
Like you look at the size of this blog
post, it's, it's just a little drop in
00:39:46.689 --> 00:39:49.089
the bucket, but it still is not the best.
00:39:49.089 --> 00:39:51.210
And so I wish I could avoid this.
00:39:52.120 --> 00:39:57.040
But for the use cases that I have,
it's definitely the best option.
00:39:58.799 --> 00:40:01.575
Becky Peltz: It's just like a lot
of channels on the web only can
00:40:01.575 --> 00:40:05.925
deal with text, if you want to put
an image in a email or something,
00:40:06.245 --> 00:40:09.285
sometimes it has to be Base64 encoded.
00:40:09.955 --> 00:40:10.275
Kent Dodds: Yeah.
00:40:10.275 --> 00:40:12.625
They don't want to load remote stuff
00:40:13.255 --> 00:40:13.375
Becky Peltz: Yeah.
00:40:13.845 --> 00:40:16.575
Kent Dodds: But this wasn't the
end of everything because one
00:40:16.575 --> 00:40:21.254
thing I noticed was, and you
scrolled to it for a second there.
00:40:21.584 --> 00:40:27.254
The blurred image looked really bad,
like very pixelated, because what
00:40:27.254 --> 00:40:31.865
I did was I took it only a hundred
pixels, so it was a hundred width.
00:40:32.225 --> 00:40:35.085
So not a hundred pixels, but
it was width of a hundred.
00:40:35.215 --> 00:40:42.285
And then blurred that, and then I upscaled
it to 10x, a thousand pixels width.
00:40:42.645 --> 00:40:46.185
And so that just made it
look,
even though it's blurry, it looked
00:40:46.185 --> 00:40:48.194
pixelated, just didn't look very good.
00:40:48.734 --> 00:40:53.850
And luckily there is an awesome
filter that you can apply to a div.
00:40:53.850 --> 00:40:59.205
So I put a div on top of, positioned
absolutely on top of this image where
00:40:59.205 --> 00:41:01.424
the backdrop filter to set a blur.
00:41:01.705 --> 00:41:06.134
And then so I blur it from
Cloudinary and then I blur it
00:41:06.134 --> 00:41:08.734
further from the browser to give it.
00:41:09.265 --> 00:41:11.075
Becky Peltz: You have a tiny blur.
00:41:11.095 --> 00:41:13.730
You expand it and then you
make the browser blur it.
00:41:13.730 --> 00:41:14.450
So that's.
00:41:14.455 --> 00:41:14.669
Kent Dodds: Yeah.
00:41:14.669 --> 00:41:16.390
Yeah, exactly.
00:41:16.720 --> 00:41:20.509
And I actually, now that I say
that I didn't think about just
00:41:20.515 --> 00:41:23.569
saying, "Hey, Cloudinary, give me
a small image and then I'll just
00:41:23.569 --> 00:41:25.464
have the browser blur that myself".
00:41:25.464 --> 00:41:27.935
But maybe I could have tried that.
00:41:27.935 --> 00:41:29.839
But it's working now, so why bother?
00:41:29.839 --> 00:41:32.689
Sam Brace: And that's one way we look
at it is it's like not everything always
00:41:32.689 --> 00:41:34.369
has to be a hundred percent Cloudinary.
00:41:34.369 --> 00:41:38.539
It's where with CSS, other things
you can come up with amazing results.
00:41:38.539 --> 00:41:39.689
And this is a proof of that.
00:41:39.689 --> 00:41:41.149
So we're a piece of the pie.
00:41:41.149 --> 00:41:43.609
We're not the only pie that's there.
00:41:43.609 --> 00:41:44.269
So that's good.
00:41:44.269 --> 00:41:45.059
Kent Dodds: Now I want pie.
00:41:45.079 --> 00:41:46.939
Sam Brace: You can see the
immediate difference here too.
00:41:46.939 --> 00:41:51.859
Like you're, you can see like the
rings of this are very distinct.
00:41:51.859 --> 00:41:55.189
It's, it almost has a muddy
look to it with the amount of
00:41:55.299 --> 00:41:56.419
moving you're seeing there.
00:41:56.719 --> 00:42:00.470
And then when you did the work
that you did, everything's smooth.
00:42:00.729 --> 00:42:04.379
It's very hard to tell even from the
background what I'm looking at here.
00:42:04.849 --> 00:42:05.924
Which is the point of blur.
00:42:06.194 --> 00:42:07.634
So it's a good, it's
very good what you did.
00:42:09.694 --> 00:42:10.604
Kent Dodds: Yep.
00:42:10.604 --> 00:42:15.930
That, was actually that,
that worked out really well.
00:42:15.930 --> 00:42:20.774
But it still wasn't quite what I wanted
because what I was looking for was
00:42:20.774 --> 00:42:25.819
you have the blurred image and then
it fades into the finished image.
00:42:26.774 --> 00:42:31.644
And what we had at this point was you have
the blurred image and then when the actual
00:42:31.664 --> 00:42:34.124
image loads, it just takes its place.
00:42:34.515 --> 00:42:35.504
And that doesn't look too bad.
00:42:35.535 --> 00:42:37.995
It's fine, but I wanted
it to fade into place.
00:42:38.295 --> 00:42:45.059
This is tricky because there's no API in
the browser from HTML that says, "Hey,
00:42:45.059 --> 00:42:47.029
apply this class when it's ready to go".
00:42:47.029 --> 00:42:51.899
Of course, there's a JavaScript way
to do that, but there's no HTML way
00:42:52.319 --> 00:42:54.479
to say, "on load, do this thing".
00:42:54.539 --> 00:43:01.439
And what I had to do was I, and of
course like already we've gotten a
00:43:01.439 --> 00:43:03.749
couple of things in here that I'm
like, yeah, I definitely want turn
00:43:03.749 --> 00:43:06.209
this into a component so I don't
have to do this all over the place.
00:43:06.479 --> 00:43:09.539
So I made this blurrable image
component, and so the code that
00:43:09.539 --> 00:43:13.680
we're looking at now is an example
of that blurrable image component.
00:43:14.079 --> 00:43:17.849
Where you passed the Base64 URL.
00:43:17.849 --> 00:43:21.599
That's the blur data URL that
we see as the prop there.
00:43:22.229 --> 00:43:25.269
We have our aspect ratios there as well.
00:43:26.179 --> 00:43:32.205
And then we have our image, the
element, that you're supposed to be
00:43:32.205 --> 00:43:37.125
rendering here and there's the get
image props there as well for doing our
00:43:37.125 --> 00:43:39.044
different sizes and all of that stuff.
00:43:39.664 --> 00:43:45.694
So the actual implementation of
the blurrable image component is a
00:43:45.694 --> 00:43:50.954
little bit further down, and this
does some pretty interesting things.
00:43:52.384 --> 00:43:52.894
Becky Peltz: Yeah.
00:43:53.464 --> 00:43:53.744
Kent Dodds: Yeah.
00:43:53.954 --> 00:43:54.494
Sorry.
00:43:54.584 --> 00:43:57.314
Did you have a question
about the usage though?
00:43:58.144 --> 00:43:59.704
Becky Peltz: No, I just said this is cool.
00:43:59.764 --> 00:44:01.534
I like how you did this.
00:44:01.694 --> 00:44:02.244
Kent Dodds: Yeah.
00:44:03.154 --> 00:44:06.884
So the blurrable image component it
takes that image, it takes the blur
00:44:07.154 --> 00:44:10.534
data URL, and then the rest of the props
that it takes are just whatever else
00:44:10.534 --> 00:44:11.914
you can apply to in an image element.
00:44:11.944 --> 00:44:13.004
We'll just pass those along.
00:44:13.684 --> 00:44:19.714
And so what we have to do in JavaScript
because we, there's no HTML way to
00:44:19.964 --> 00:44:23.964
do this as we have to maintain some
state to say whether or not the image
00:44:24.204 --> 00:44:26.314
the final loaded image is visible.
00:44:26.734 --> 00:44:31.294
And then I use that visible
value to determine what class
00:44:31.294 --> 00:44:32.344
names should be applied.
00:44:32.374 --> 00:44:36.184
So this is all React's nice and
declarative model where we can
00:44:36.544 --> 00:44:39.524
re-render, and now the, here are the
class names that it should be now.
00:44:40.394 --> 00:44:45.094
So
you'll notice on line 33, I'm cloning
the image element that they gave me.
00:44:45.094 --> 00:44:49.294
So , we have the react element that's
the image element that they created.
00:44:49.504 --> 00:44:53.314
I'm actually going to not render
that directly and instead create
00:44:53.314 --> 00:44:55.174
a new one that's a copy of that.
00:44:56.354 --> 00:44:59.989
That I have a reference to
that's the ref prop there.
00:45:00.229 --> 00:45:05.179
And then I have a class name that's going
to be all the classes that they provided.
00:45:05.359 --> 00:45:08.879
Plus I want to transition the
opacity so I can animate that.
00:45:09.059 --> 00:45:15.739
So I can transition in and then I set the
opacity to zero if it's not yet visible.
00:45:16.179 --> 00:45:18.649
And then we'll get to that
use effect here in a second.
00:45:18.649 --> 00:45:21.699
But then where I render,
I need to render the div.
00:45:21.769 --> 00:45:25.039
I'm gonna put all of the the
rest of the props on that.
00:45:25.039 --> 00:45:32.129
So I guess those that rest is not the
image element, it's the div element props.
00:45:33.079 --> 00:45:36.559
So yeah, I, I render a div around
all of this to keep them together.
00:45:37.629 --> 00:45:43.279
If there is a blur data URL honestly,
I shouldn't make it so you can render
00:45:43.279 --> 00:45:46.669
one of these without that, because
why would you use this component
00:45:46.669 --> 00:45:49.309
if you didn't have a blur data URL?
00:45:50.029 --> 00:45:53.829
But if that does exist, then
I will render the blur image.
00:45:54.329 --> 00:45:57.899
So that is the source is the Base64.
00:45:58.239 --> 00:46:00.949
The class name is gonna have
the same class name as the image
00:46:00.949 --> 00:46:03.269
that you're providing, so it has
the same sizes and everything.
00:46:03.809 --> 00:46:07.789
And then the alt text because
we care about screen readers.
00:46:08.119 --> 00:46:12.979
And then we have that backdrop blur
you URL to give it a smooth blur.
00:46:13.599 --> 00:46:17.539
And then next to that we
render our JS image L and then
00:46:17.539 --> 00:46:19.189
the no script image there.
00:46:19.189 --> 00:46:24.379
So in case the, this is very
rare but if somebody has disabled
00:46:24.379 --> 00:46:27.374
JavaScript on my site, I still want
them to be able to see the images.
00:46:27.454 --> 00:46:30.879
And so we'll just render the
image as it is and it will work.
00:46:30.879 --> 00:46:31.819
And I've tested that.
00:46:31.819 --> 00:46:32.239
That works.
00:46:32.239 --> 00:46:36.979
And so yeah that's the basics.
00:46:37.029 --> 00:46:40.279
Now the trick is how do we
know when we should remove
00:46:40.279 --> 00:46:42.889
that opacity zero class name?
00:46:43.399 --> 00:46:45.129
And so that's what the use effect is for.
00:46:45.739 --> 00:46:49.769
If you go a little bit above, like
in the middle of the blur image
00:46:50.149 --> 00:46:55.159
component, there's this use effect
where we say first we do some early
00:46:55.159 --> 00:47:02.299
returns, like if the ImgElRef, if
we don't have a current DOM Node of
00:47:02.299 --> 00:47:04.874
that image, then that's unexpected.
00:47:04.874 --> 00:47:07.564
We'll just return that,
that will never happen.
00:47:08.144 --> 00:47:10.874
But, I mean it could, and we don't
want bad things to happen if it does.
00:47:10.874 --> 00:47:17.034
So I guess and then the
jsImgElRef.current.Complete.
00:47:17.424 --> 00:47:21.094
That .current is just a DOM Node
reference to the image element.
00:47:21.264 --> 00:47:26.264
And so .complete is a property on an
image element that says whether or
00:47:26.264 --> 00:47:27.584
not that image is finished loading.
00:47:27.884 --> 00:47:29.894
So if we have finished loading,
then we're just gonna return.
00:47:29.894 --> 00:47:30.834
We're all done.
00:47:30.884 --> 00:47:32.174
We've done this before, it's fine.
00:47:33.594 --> 00:47:40.354
And it then we say add event
listener on that image element, Load.
00:47:40.354 --> 00:47:45.784
So when that load has finished, then
we're going to set visible and we're
00:47:45.784 --> 00:47:49.384
putting that inside of a set timeout
for a good reason that I can't remember,
00:47:49.474 --> 00:47:53.674
and I probably should have wrote a code
comment to explain why we're doing that.
00:47:53.914 --> 00:47:55.204
I remember putting it there.
00:47:55.204 --> 00:47:57.134
I just don't remember why I did it.
00:47:57.664 --> 00:48:00.844
Just putting it on the next ticket
to the event loop for some reason.
00:48:00.934 --> 00:48:03.454
I just can't recall
why that was necessary.
00:48:04.774 --> 00:48:06.109
So anyway, that, that's a basic idea.
00:48:06.109 --> 00:48:10.364
We're fundamentally we're just
saying when this image has finished
00:48:10.384 --> 00:48:14.654
loading, then let's set it to
visible so that it will fade in.
00:48:14.904 --> 00:48:20.384
So it's actually a lot of work just
for the simple fact that I wanted
00:48:20.404 --> 00:48:25.084
to be able to have it fade in
rather than just magically appear.
00:48:25.534 --> 00:48:31.384
And that the bulk of this component is
for that particular feature, we could
00:48:31.754 --> 00:48:36.304
probably remove everything from line 14
to line 41 if I didn't care about that.
00:48:37.019 --> 00:48:37.169
Yeah.
00:48:37.329 --> 00:48:39.739
Becky Peltz: When you do have
timing considerations here cuz
00:48:39.739 --> 00:48:41.449
you're rendering really two images.
00:48:41.449 --> 00:48:44.749
You've got your blurrable image and
then you, in the background, the
00:48:44.749 --> 00:48:47.989
other, the real image is loading
and you need to know when it's done
00:48:48.049 --> 00:48:50.029
before you can do your transition.
00:48:50.029 --> 00:48:55.399
So you do, you are working with some
things that you have to think about there.
00:48:55.669 --> 00:48:55.999
Kent Dodds: Yeah.
00:48:56.599 --> 00:49:00.879
Now what's kinda interesting about
this is I ran into some
problems.
00:49:01.459 --> 00:49:05.209
First of all, it makes me a little
uncomfortable that I require
00:49:05.209 --> 00:49:07.519
JavaScript for my images to be seen.
00:49:07.969 --> 00:49:13.309
So if we have to wait until the JavaScript
shows up before we can actually get that
00:49:13.429 --> 00:49:17.689
opacity zero class off, cuz we, we render
that opacity zero class on the server.
00:49:17.689 --> 00:49:24.949
So you will not see this image until
React does its thing and I can say,
00:49:25.079 --> 00:49:26.739
okay, re-render without that class name.
00:49:27.289 --> 00:49:28.989
That makes me feel uncomfortable.
00:49:29.309 --> 00:49:34.579
And it actually played out in
in production where I had some
00:49:34.579 --> 00:49:38.089
sort of error with my site where
the JavaScript errored out.
00:49:38.094 --> 00:49:41.989
And so this code never ran, and so
people could only see the blurred image
00:49:42.909 --> 00:49:44.709
only the stuff that was sever rendered.
00:49:45.189 --> 00:49:49.999
And the no script stuff on line
54 doesn't work in that case
00:49:49.999 --> 00:49:53.929
because scripts are available,
they're just, they failed to run.
00:49:54.129 --> 00:49:56.869
And so I don't really like that too much.
00:49:56.869 --> 00:50:00.899
And I just moved on and it was fine.
00:50:00.899 --> 00:50:03.929
And this only happened once and
so it wasn't a really big deal.
00:50:04.369 --> 00:50:09.649
But it does make me feel uncomfortable
that I have to wait for JavaScript to
00:50:09.649 --> 00:50:14.659
load and then be parsed and then executed
before we can actually remove that
00:50:15.359 --> 00:50:18.079
visible zero or opacity zero class name.
00:50:19.199 --> 00:50:24.664
Yeah, that's just unfortunate
because the image could actually
00:50:24.669 --> 00:50:29.054
have finished loading before the
JavaScript has even been loaded itself.
00:50:29.354 --> 00:50:31.034
And so we're showing a blurred.
00:50:31.724 --> 00:50:35.479
A blurred placeholder when we could
just be showing the full image
00:50:35.479 --> 00:50:36.499
and that would be a lot better.
00:50:36.679 --> 00:50:40.459
On top of that, if the browser has
already cashed the image and you just
00:50:40.459 --> 00:50:46.309
go up and hit refresh on the page you're
going to see the blurred image until
00:50:46.309 --> 00:50:48.019
the JavaScript is evaluated and stuff.
00:50:48.259 --> 00:50:51.619
Where, what I would prefer is that
you don't see a blurred image.
00:50:51.969 --> 00:50:56.824
So what our status quo is now is
you always see a blurred image and
00:50:57.044 --> 00:51:00.289
you'll see a flash of blurred state
and then you'll see the full image.
00:51:00.289 --> 00:51:03.499
And I would much rather say if the
image is in the browser cache, it
00:51:03.499 --> 00:51:06.659
should just instantly show, I don't
even care about showing a placeholder.
00:51:07.309 --> 00:51:11.449
And so I left it this way for a long
time and then like two months ago,
00:51:11.449 --> 00:51:13.819
you all reached out to me and said,
"Hey, we want to talk about this cool
00:51:13.819 --> 00:51:17.749
blog post", and in the back of my mind
I'm thinking, "Oh shoot, there's that
00:51:17.749 --> 00:51:19.069
one thing I don't like about this".
00:51:21.259 --> 00:51:25.999
Two days ago, two days ago, right
before we did this, I spent a
00:51:25.999 --> 00:51:27.749
little bit of time investigating.
00:51:28.909 --> 00:51:31.624
This this loading experience
to make it a little bit better.
00:51:31.734 --> 00:51:35.744
And so that's the next
section here is fading faster.
00:51:36.174 --> 00:51:39.154
Yeah, I said, and really that's it.
00:51:39.154 --> 00:51:40.924
That was how I ended my blog post before.
00:51:40.924 --> 00:51:44.404
And then I added, except now that
it's 2023, I decided to improve one
00:51:44.409 --> 00:51:48.484
more thing, and that's to make it
fade faster, to solve this problem of
00:51:48.634 --> 00:51:50.254
what if the JavaScript fails to load?
00:51:50.254 --> 00:51:51.454
What if something goes wrong?
00:51:51.784 --> 00:51:57.534
And the fact is because html doesn't
support any mechanism for updating or
00:51:57.934 --> 00:52:00.834
for saying, I want to fade this image in.
00:52:01.394 --> 00:52:02.824
We have to do it in JavaScript.
00:52:03.474 --> 00:52:11.884
But, I don't want to tie all of this
logic into that particular bunch of
00:52:11.884 --> 00:52:16.264
JavaScript that happens within the
react hydration and all of that.
00:52:16.654 --> 00:52:20.344
I would a rather just have a little
bit of JavaScript because it's really
00:52:20.344 --> 00:52:25.444
not a lot that says when this load
thing happens, just remove that class.
00:52:25.684 --> 00:52:31.414
And so that's exactly what I do in
theory, this is as easy as it should
00:52:31.414 --> 00:52:33.524
be, is you just add an on loan prop.
00:52:33.844 --> 00:52:36.394
I realize there are a lot of
people who are looking at me right
00:52:36.394 --> 00:52:39.884
now and saying, "you're doing
inline JavaScript, you're a joke".
00:52:40.364 --> 00:52:43.234
"That's even worse than inline styles".
00:52:43.419 --> 00:52:44.569
And it is.
00:52:45.559 --> 00:52:51.039
This is the quintessential, like perfect
use case for something like this.
00:52:51.039 --> 00:52:56.169
It's the simplest amount of JavaScript I
can imagine for for this type of use case.
00:52:56.529 --> 00:53:01.979
I could also do render another script
element that does the same thing,
00:53:01.979 --> 00:53:04.009
but I don't know, look at line 5.
00:53:04.029 --> 00:53:04.569
That's easy.
00:53:05.369 --> 00:53:06.579
There's nothing complicated about this.
00:53:07.449 --> 00:53:11.169
Unfortunately, there is something
complicated about this because React does
00:53:11.169 --> 00:53:16.809
not like inline JavaScript like this and
it will not render it will not render
00:53:16.814 --> 00:53:20.409
these prompts and instead it will give
you an error that says
you need to use
00:53:20.409 --> 00:53:23.199
the on load prop with an actual function.
00:53:23.709 --> 00:53:25.719
And so that is annoying.
00:53:26.289 --> 00:53:27.399
That's really unfortunate.
00:53:27.889 --> 00:53:28.719
Becky Peltz: There's nowhere.
00:53:29.139 --> 00:53:31.479
Kent Dodds: Cause now I'm like
right back into the React thing
00:53:31.484 --> 00:53:33.479
and I have to wait for all of
React to hydrate and all of that.
00:53:33.559 --> 00:53:38.049
So, I did a fair bit of
work to make this this work.
00:53:39.199 --> 00:53:43.669
That is a little involved and I don't
think it's necessary for you to dive in.
00:53:43.669 --> 00:53:47.704
You can look into the commit that
I linked to a little bit below
00:53:48.974 --> 00:53:52.709
to dive into how I made this work
cause it is kind of complicated.
00:53:52.729 --> 00:53:57.859
But at the end of the day, I was able to
make a really awesome experience where if
00:53:57.864 --> 00:54:02.359
you're on the page and you hit refresh,
so the image is already in your cache,
00:54:02.539 --> 00:54:05.599
you do not see a flash of loading state.
00:54:05.649 --> 00:54:10.669
And it just it instantly
just shows the image.
00:54:10.749 --> 00:54:14.259
And I think that is a much
better user experience.
00:54:15.429 --> 00:54:19.489
Yeah, you, if you click on that, yeah, you
can see on the left side it's flashing.
00:54:19.489 --> 00:54:22.359
Each one of them is hitting the
refresh button at the exact same time.
00:54:23.019 --> 00:54:25.984
But the left side is flashing
the blur state and the right
00:54:25.984 --> 00:54:29.794
side, you don't see anything like
that, so much better experience.
00:54:29.944 --> 00:54:32.794
Some people actually comment on
this and they say, "I actually
00:54:32.794 --> 00:54:35.404
like seeing the blur state, cause
it shows me that it refreshed."
00:54:35.554 --> 00:54:38.194
And I'm thinking "You've
been conditioned, my friend.
00:54:38.254 --> 00:54:38.644
That's wrong.
00:54:39.134 --> 00:54:40.784
You don't like it.
00:54:41.344 --> 00:54:42.674
You don't like it."
00:54:43.204 --> 00:54:45.124
So anyway, there you go.
00:54:45.124 --> 00:54:50.074
That's how I did nice placeholder and an
awesome loading experience on my website.
00:54:50.844 --> 00:54:51.334
Becky Peltz: Yeah.
00:54:51.434 --> 00:54:51.834
Sam Brace: Amazing.
00:54:51.874 --> 00:54:54.929
Becky Peltz: It's so interesting how
there's such a battle with wanting
00:54:55.094 --> 00:54:58.774
to use JavaScript to help you make
things work, but then JavaScript
00:54:58.954 --> 00:55:02.104
takes long to load, so for performance
reasons you don't wanna use it.
00:55:02.614 --> 00:55:02.974
Yeah.
00:55:03.494 --> 00:55:04.444
It's kinda like you're torn.
00:55:05.194 --> 00:55:07.774
Sam Brace: So, a couple questions for
you, Kent, about this overall thing.
00:55:07.779 --> 00:55:11.524
So, obviously we're using React for a
lot of the things that we're showing in
00:55:11.524 --> 00:55:16.384
this case, but could you take similar
concepts that we did here or maybe
00:55:16.384 --> 00:55:21.874
identical concepts and apply it to other
frameworks, let's say Vue or Angular
00:55:21.874 --> 00:55:26.619
other things, or is this like where unless
you're using React, this is impossible.
00:55:27.099 --> 00:55:28.289
Kent Dodds: Yeah, that's a good question.
00:55:28.289 --> 00:55:32.259
There's nothing in here that I'm
doing that is exclusive to React.
00:55:32.259 --> 00:55:34.249
This is all web platform stuff.
00:55:34.249 --> 00:55:37.619
Arguably it might even be easier in
other frameworks because of that on
00:55:37.619 --> 00:55:39.479
load thing that I was talking about.
00:55:39.479 --> 00:55:41.604
React just really, doesn't
want you to do that.
00:55:42.684 --> 00:55:47.379
Like I said, I could do an inline script
or a script tag that does the same thing
00:55:47.469 --> 00:55:48.909
and that maybe I'll switch to that.
00:55:49.569 --> 00:55:54.249
Because you can't actually the
content security policy doesn't
00:55:54.249 --> 00:55:59.289
work very well with inline scripts
JavaScript or attribute scripts.
00:55:59.649 --> 00:56:02.059
Which, yeah, so I should probably
change it for that reason.
00:56:02.059 --> 00:56:06.699
But yeah, actually at the bottom of
the post there, I have that little Ps
00:56:07.259 --> 00:56:14.039
there's this unpic image component that
is a framework agnostic implementation,
00:56:14.329 --> 00:56:15.929
very similar to what I'm doing.
00:56:16.719 --> 00:56:22.759
They actually don't do a Base64 and
instead use CSS gradients to accomplish
00:56:22.759 --> 00:56:24.319
a blurred version of the image.
00:56:24.409 --> 00:56:27.979
It's very interesting and they
have implementations in all
00:56:27.984 --> 00:56:28.999
sorts of different frameworks.
00:56:29.729 --> 00:56:35.269
They also support a lot of different image
CDNs, including Cloudinary and others.
00:56:35.789 --> 00:56:42.079
Look, I wish this existed when
I was building mine, but now I
00:56:42.079 --> 00:56:44.029
have this cool blog post where
I can explain how it works.
00:56:44.999 --> 00:56:49.159
Becky Peltz: Yeah, no it's just a neat,
watching you come up with a solution
00:56:49.159 --> 00:56:53.959
in this, and I'll just share too, that
like the Cloudinary React SDK does have
00:56:53.959 --> 00:57:00.624
a placeholder plugin that you as it kind
of starts out blurry and it turns full
00:57:00.624 --> 00:57:01.999
resolution while you're watching it.
00:57:02.269 --> 00:57:05.959
But again, you're loading somewhere
JavaScript to make that happen.
00:57:06.709 --> 00:57:08.834
Sam Brace: And I, I actually love
the shout out you're doing for the
00:57:08.834 --> 00:57:12.134
unpic side of things because I can
look at just the contributor to
00:57:12.134 --> 00:57:15.704
list here, and there's some really
awesome people that are tied to this.
00:57:15.974 --> 00:57:20.804
Looking at Zach, who's tied to
Eleventy here,
our friend Elad who's
00:57:20.809 --> 00:57:24.284
tied to Stackbit, like there's a
lot of good minds that are putting
00:57:24.284 --> 00:57:26.954
contributions into this particular thing.
00:57:27.554 --> 00:57:32.365
I agree it's a great place to be able
to start handling multi framework
00:57:32.455 --> 00:57:35.174
imagery and responsive aspects of it.
00:57:35.204 --> 00:57:35.785
So it's great.
00:57:38.024 --> 00:57:40.919
So, one question that did come up in
the community that I wanna address
00:57:40.919 --> 00:57:44.489
here, because a lot of things that we
covered here, of course they're, in my
00:57:44.489 --> 00:57:46.739
opinion, I would say advanced topics.
00:57:46.739 --> 00:57:49.859
You're doing things where you're almost
like optimizing what's already been
00:57:49.864 --> 00:57:52.979
optimized with some of the things that
you've gone through, this process stuff.
00:57:53.309 --> 00:57:58.859
But, let's say that I'm a fairly new
JavaScript developer or someone thats new
00:57:58.859 --> 00:58:04.169
to web development, where would I be going
to learn how to do more of these things?
00:58:04.169 --> 00:58:08.789
And I'm not trying to give you a softball
like, "Hey, queue up Epic or React and
00:58:08.789 --> 00:58:09.959
all the great work you're doing there."
00:58:10.109 --> 00:58:10.739
But please do.
00:58:10.889 --> 00:58:14.669
But in the same sense, like where, is
there any spaces where people can be
00:58:14.674 --> 00:58:18.269
getting to better understand what's
happening with the web, particularly
00:58:18.269 --> 00:58:21.089
with JavaScript development that you've
come across that have been helpful?
00:58:21.689 --> 00:58:27.089
Kent Dodds: Yeah, I have a blog post
about experience and getting experience
00:58:27.089 --> 00:58:30.239
as a web developer, cause this is a very
common question, how do I get better?
00:58:30.239 --> 00:58:34.319
And the answer sounds pretty obvious.
00:58:35.579 --> 00:58:37.739
You get experience by having experiences.
00:58:40.139 --> 00:58:43.589
You really just have to you, you
can spend all day on Twitter.
00:58:43.589 --> 00:58:46.019
You can spend time on
YouTube watching videos.
00:58:46.019 --> 00:58:51.749
You can spend, buy a really
great course like Epic React when
00:58:51.749 --> 00:58:53.264
Epic Web comes out, Epic Web.
00:58:53.264 --> 00:58:56.279
And that's all good.
00:58:56.799 --> 00:58:59.269
You should be doing those
things some of those things.
00:59:00.220 --> 00:59:04.329
But really you don't get experience
until you have those experiences.
00:59:04.879 --> 00:59:11.219
I strongly advise just spending a ton of
time working on actually building stuff.
00:59:12.489 --> 00:59:16.144
And subscribing to newsletters
is good for keeping up.
00:59:16.514 --> 00:59:21.359
I've got a really great Discord
community that you can come in and
00:59:21.359 --> 00:59:22.889
keep up with what's going on in there.
00:59:23.449 --> 00:59:27.179
Staying involved on Twitter and
stuff, that's also really good.
00:59:27.989 --> 00:59:30.499
To be involved in that.
00:59:31.529 --> 00:59:36.174
So all of these things are
useful to give you a sense of
00:59:36.194 --> 00:59:37.734
what's going on in the ecosystem.
00:59:38.134 --> 00:59:41.204
But then you have to take that
and actually build something.
00:59:42.524 --> 00:59:46.494
Sam Brace: A hundred percent, and
I'll plug your Discord community.
00:59:46.514 --> 00:59:50.234
I've become a recent member of it myself,
and I think it's a great place to be
00:59:50.264 --> 00:59:54.464
hearing about these conversations, but
to further your point, it's where if
00:59:54.464 --> 00:59:56.894
you hear something that kind of tickles
your brain and you're like, oh, I wanna
00:59:56.894 --> 01:00:00.524
learn more about this, then yeah, do
your job to learn about it, but then
01:00:00.644 --> 01:00:02.294
get your hands dirty and get into it.
01:00:02.294 --> 01:00:04.454
And that's the only way that
you're gonna be able to grow,
01:00:04.544 --> 01:00:06.284
in my opinion as a developer.
01:00:06.284 --> 01:00:10.154
You, you have to if you always say
good writers write a lot, the same
01:00:10.154 --> 01:00:12.194
thing, good coders code a lot.
01:00:12.254 --> 01:00:16.634
And it doesn't mean that every line you
write is gonna be beautiful, but sometimes
01:00:16.639 --> 01:00:18.914
it will be, and it all comes experience.
01:00:18.944 --> 01:00:22.294
Becky Peltz: I think its sort of like
any kind of like an athletic event,
01:00:22.294 --> 01:00:25.694
if you wanna be prepared for it, or
if you wanna prepare for it, you just
01:00:25.694 --> 01:00:30.014
have to do a lot of it, it sounds like
every day you have to dedicate time
01:00:30.014 --> 01:00:33.285
to massaging that and building it up.
01:00:34.794 --> 01:00:35.694
Sam Brace: Excellent, Kent.
01:00:36.075 --> 01:00:40.394
I'm inspired and I, and of course we've
already shown the blog post extensively
01:00:40.394 --> 01:00:44.354
to all the places that people can
understand what's happened and be there.
01:00:44.624 --> 01:00:47.674
I'll also point out in, gimme a
little bit more detail there too,
01:00:47.704 --> 01:00:54.644
but you have a GitHub repository that
is focused on just the overall blog
01:00:54.644 --> 01:00:58.095
presence that you have here, and I'm
sure that a lot of the things that
01:00:58.095 --> 01:01:02.174
you have that you're showing here are
available through this overall repo.
01:01:02.174 --> 01:01:06.194
But what, like, why did you ultimately
decide to expose everything you
01:01:06.194 --> 01:01:08.495
have for your website in this repo?
01:01:09.504 --> 01:01:10.265
Kent Dodds: It's easier.
01:01:12.494 --> 01:01:12.764
Yeah.
01:01:12.764 --> 01:01:18.825
So my, my content is actually
inside of the website itself.
01:01:18.825 --> 01:01:22.245
So there's the content directory
and that's all my pages, all of my
01:01:22.250 --> 01:01:23.504
blog posts, everything is in there.
01:01:23.504 --> 01:01:30.805
And I do that because the, it's just a
lot easier to manage the contributions
01:01:30.825 --> 01:01:35.305
when I have like typos and stuff, people
contribute I have hundreds of contributors
01:01:35.310 --> 01:01:37.105
to my blog posts through that mechanism.
01:01:37.675 --> 01:01:42.015
And then my, having my site open
source just makes it a lot easier
01:01:42.015 --> 01:01:43.365
for me to answer people's questions.
01:01:43.495 --> 01:01:44.715
They'll say, how do you do this?
01:01:44.715 --> 01:01:47.165
And I'll just say, here's
the file where I do that.
01:01:47.165 --> 01:01:53.225
And so yeah, the entire site is
open source and it I'll I'll also
01:01:53.424 --> 01:01:58.545
mention that my website is not
your typical developer portfolio.
01:01:58.605 --> 01:02:03.975
And if what you're building as a developer
portfolio, do not use my website as
01:02:03.975 --> 01:02:10.065
a template because it is way over
scoped for what you're trying to do.
01:02:10.355 --> 01:02:15.540
And that scope brings along a lot more
complexity than you need for your site.
01:02:15.870 --> 01:02:21.385
So start use somebody else's because
I've got three SaaS products that
01:02:21.385 --> 01:02:25.335
I or three things that I could turn
into SaaS products on my website.
01:02:25.705 --> 01:02:28.290
That you definitely don't need on yours.
01:02:30.450 --> 01:02:31.230
Sam Brace: Completely fair.
01:02:31.230 --> 01:02:33.200
And it, it's good to get
people of those caveats.
01:02:33.200 --> 01:02:34.560
I completely agree.
01:02:34.950 --> 01:02:38.490
And I think we've also one thing I
always ask before we end one of these
01:02:38.490 --> 01:02:41.640
conversations, Kent, is where people
should be going for more information.
01:02:41.640 --> 01:02:46.109
I think we've made it pretty clear,
kentcdodds.com is your main portal
01:02:46.109 --> 01:02:47.670
for all things that are tied to you.
01:02:48.089 --> 01:02:51.890
But is there any other places where
you find that you're more active?
01:02:52.129 --> 01:02:55.600
Are you more on Twitter or
LinkedIn or other places?
01:02:55.600 --> 01:02:59.399
Or if you wanna get like the the
latest that's coming from you?
01:03:00.690 --> 01:03:00.990
Kent Dodds: Yeah.
01:03:01.279 --> 01:03:07.319
I'm most active on Twitter and I always
share stuff to the Discord community.
01:03:07.629 --> 01:03:10.269
They typically get the
exciting stuff first.
01:03:11.190 --> 01:03:15.870
And then the, my mailing list that you
can find, just kentcdodds.com, scroll
01:03:15.870 --> 01:03:19.799
down to the bottom you can or just
sign up for an account there and you'll
01:03:19.805 --> 01:03:20.970
be put on the mailing list as well.
01:03:22.100 --> 01:03:29.509
But yeah I'm doing remote workshops and
stuff like that I, yeah, I recommend yeah
01:03:29.730 --> 01:03:36.200
your signed up looks like, cause you,
you signed in, but yeah, so that, that
01:03:36.200 --> 01:03:41.069
little image on the right there turns
into a form if you're not signed in.
01:03:43.269 --> 01:03:43.729
Okay.
01:03:44.390 --> 01:03:48.600
So yeah, the, that's probably
the mailing list is the best way
01:03:48.600 --> 01:03:49.980
to not miss anything, for sure.
01:03:51.119 --> 01:03:51.559
Sam Brace: Excellent.
01:03:52.229 --> 01:03:56.879
Kent, once again, I'm inspired even past
what I read of the blog post, getting
01:03:56.879 --> 01:04:02.250
to hear your introspective review of
how you got done, what you got done, and
01:04:02.250 --> 01:04:03.810
also getting the business case of it.
01:04:03.810 --> 01:04:05.769
So, keep up the good work, Kent.
01:04:05.790 --> 01:04:08.730
Obviously there's lots of people that are
tied to the communities and the work that
01:04:08.730 --> 01:04:12.270
you're doing, but we love what you're
doing here at Cloudinary, so keep it up.
01:04:13.049 --> 01:04:13.680
Kent Dodds: Thanks a lot.
01:04:13.680 --> 01:04:14.339
I appreciate that.
01:04:15.480 --> 01:04:15.960
Sam Brace: Excellent.
01:04:15.960 --> 01:04:18.440
So Becky, I had wanted to ask you.
01:04:19.350 --> 01:04:20.040
Becky Peltz: Yes?
01:04:21.060 --> 01:04:23.189
Sam Brace: What is our
big takeaway from this?
01:04:23.279 --> 01:04:26.069
There's a lot of things that are
bubbling up my mind by what's yours.
01:04:26.160 --> 01:04:30.689
Becky Peltz: I think that Cloudinary
needs to create an e_kentdodds effect.
01:04:32.640 --> 01:04:35.839
So we don't have so much JavaScript.
01:04:35.839 --> 01:04:37.830
His process is just wonderful.
01:04:37.830 --> 01:04:40.810
And I think the effect is something
that anybody could appreciate.
01:04:41.450 --> 01:04:45.020
And he does use one of our
effects, the blur effect.
01:04:45.230 --> 01:04:48.690
But then he has that little bit of
magic in it that gives you something
01:04:48.690 --> 01:04:51.750
before, and then it transitions into it.
01:04:52.360 --> 01:04:57.149
Yeah it's definitely something if you're
putting images on your site, think
01:04:57.189 --> 01:05:00.799
about something like this or use this.
01:05:01.680 --> 01:05:02.080
Sam Brace: Yeah.
01:05:02.430 --> 01:05:07.850
It's one of the things that we've seen
other great guests talk about some similar
01:05:07.850 --> 01:05:11.330
stuff, like when we had Brad Garropy on,
he was talking about cumulative layout
01:05:11.330 --> 01:05:14.180
shift and being able to understand it.
01:05:14.180 --> 01:05:18.570
But it's where this is kind of taking
what Brad did which was kind of
01:05:18.590 --> 01:05:22.070
creating a simple placeholder for
it and really doing a lot with it.
01:05:22.100 --> 01:05:26.600
Being able to tie in the blur effects
and then being inspired for the different
01:05:26.600 --> 01:05:30.830
places on how we can maybe incorporate
background colors as we saw so, and
01:05:30.830 --> 01:05:34.430
being able to evaluate what is the
right choice for your overall presence.
01:05:34.640 --> 01:05:39.140
But it is to say that the more
you
can create an optimal experience for
01:05:39.170 --> 01:05:44.120
the visitor or the user or the person
that's diving into your content as
01:05:44.120 --> 01:05:47.510
Kent showed, you can really do it
in a really fun way and make sure
01:05:47.510 --> 01:05:51.290
it also helps out your presence from
how search engines and others see.
01:05:52.169 --> 01:05:55.379
Becky Peltz: Yeah, and I think too,
like just the idea he got inspired by
01:05:55.439 --> 01:05:59.039
what he saw on Unsplash, that you could
see something on the web that you like
01:05:59.279 --> 01:06:03.419
and you can actually take it, tweak it,
write your own code for it and make it
01:06:03.419 --> 01:06:08.890
even better, so it's great to, to be
aware of that inspiration out there.
01:06:09.710 --> 01:06:11.759
Sam Brace: I completely agree.
01:06:11.999 --> 01:06:17.249
And talking about further inspiration,
Becky, we have future and past episodes.
01:06:17.249 --> 01:06:20.459
They'll always be at
cloudinary.com/podcasts.
01:06:20.759 --> 01:06:23.819
So if you took something away from a
conversation that me and Becky just
01:06:23.819 --> 01:06:27.240
had with Kent, please make sure that
you're checking out other episodes
01:06:27.240 --> 01:06:28.830
that are happening to be in the space.
01:06:29.129 --> 01:06:33.480
And of course, those episodes are gonna
be on all the places where you typically
01:06:33.484 --> 01:06:38.520
will like and subscribe to podcast content
such as YouTube, the Cloudinary Academy,
01:06:38.629 --> 01:06:41.700
Spotify, Apple Podcasts, Google Podcasts.
01:06:41.700 --> 01:06:45.750
There's so many out there, but
it's where we do have hopefully our
01:06:46.220 --> 01:06:48.870
presence in those different places,
wherever you like to consume content.
01:06:49.500 --> 01:06:54.270
And similarly, I recommend continuing
the conversations about this overall
01:06:54.299 --> 01:06:56.640
content in the Cloudinary community.
01:06:56.879 --> 01:07:01.319
That's gonna be at
community.cloudinary.com and as you can
01:07:01.319 --> 01:07:06.029
see, when we take a look at this, this is
going to be where you have lots of forum
01:07:06.035 --> 01:07:10.950
based tools, but also if you're an active
Discord user, we do have a lot of members
01:07:11.009 --> 01:07:16.140
of the community that are also having more
real time conversations in that space.
01:07:16.575 --> 01:07:20.294
And so if you're a forums person, if
you're a Discord person, if you're
01:07:20.294 --> 01:07:23.894
both, it gives you options to be
able to continue the conversations
01:07:23.934 --> 01:07:27.615
about what you've just heard about
in our conversation with Kent and
01:07:27.944 --> 01:07:31.305
have that possibly affecting the
way that you're building out your
01:07:31.309 --> 01:07:32.865
next software development project.
01:07:34.564 --> 01:07:38.704
Becky, before we let everybody go,
any final words, any final thoughts?
01:07:39.754 --> 01:07:43.095
Becky Peltz: Yeah, I just, it's amazing
what's going on in the community and
01:07:43.095 --> 01:07:47.334
to meet somebody like Kent Dodds who is
so involved and in into so many things.
01:07:47.334 --> 01:07:51.294
I think I'm thinking, I'm gonna go sign
up for his newsletter, let's just say.
01:07:52.264 --> 01:07:54.754
Sam Brace: Becky, thanks for
being a part of this as always.
01:07:54.785 --> 01:07:58.635
And thank you, all of you that are
listening and watching this DevJams
01:07:58.660 --> 01:08:04.084
episode on behalf of everybody at
Cloudinary, thank you, and we hope to see
01:08:04.084 --> 01:08:08.404
you at the next DevJams episode, and where
we're we gonna profile another developer
01:08:08.404 --> 01:08:12.679
that is building inspiring, innovative,
exciting projects, and of course
01:08:12.679 --> 01:08:14.539
using Cloudinary for an aspect of it.
01:08:14.899 --> 01:08:15.679
Take care everybody.
01:08:15.739 --> 01:08:16.279
We'll see you soon.