WEBVTT

1
00:00:00.208 --> 00:00:05.068
The problem of building developer docs

2
00:00:05.151 --> 00:00:09.757
is not going anywhere. What is Fern?

3
00:00:09.840 --> 00:00:14.552
Fern makes hosting docs and creating
SDKs for other companies.

4
00:00:14.635 --> 00:00:21.390
Very easy with like a plant nature
theme. Literally. Fern everywhere.

5
00:00:21.473 --> 00:00:27.686
All plant lovers here. When I started
at Fern, we were already using Vercel.

6
00:00:27.769 --> 00:00:30.058
However, we were in the middle
of a migration

7
00:00:30.141 --> 00:00:32.147
from the Pages Router to the App Router.

8
00:00:32.230 --> 00:00:37.707
It was going to require an insane amount
of engineering lift to get it from 0 to 1,

9
00:00:37.790 --> 00:00:40.778
and with Vercel we just
skipped straight to one.

10
00:00:40.861 --> 00:00:45.115
There was just no way we were going
to be able to do that without Vercel.

11
00:00:45.198 --> 00:00:51.202
I feel like we ship extremely quickly
and Vercel has a lot to do with that.

12
00:00:51.285 --> 00:00:55.288
It generates like a production preview
within a minute, which is really nice.

13
00:00:55.371 --> 00:01:00.083
When I first came to Fern, I was really
impressed with how fast our front end was.

14
00:01:00.166 --> 00:01:05.170
I remember showing up day one to this
Vercel dashboard that shows me analytics.

15
00:01:05.253 --> 00:01:06.254
It shows me logs.

16
00:01:06.337 --> 00:01:10.632
It shows me every domain that we have live
on a customers for insight,

17
00:01:11.799 --> 00:01:15.511
I learned about Vercel's anomaly
detection because I got a ping in Slack.

18
00:01:15.594 --> 00:01:19.644
I didn't even know that that was a feature
and great. Now I have more work to do.

19
00:01:19.727 --> 00:01:22.182
Let's go! The Vercel
team is extremely helpful.

20
00:01:22.265 --> 00:01:24.642
If I run into an issue
that I'm not sure about,

21
00:01:24.725 --> 00:01:27.477
I can directly communicate
with the Vercel team.

22
00:01:27.560 --> 00:01:33.523
I mean, I know Phil, Phil has helped
us out when we've had problems.

23
00:01:33.606 --> 00:01:38.281
I've gotten on calls with a bunch of
people deeply compassionate of our own use

24
00:01:38.364 --> 00:01:40.611
case, and they want to see us succeed.

25
00:01:41.489 --> 00:01:44.489
So previously, for a customer
going from one tab to another,

26
00:01:44.572 --> 00:01:49.326
it was taking anywhere from 3 seconds
to 5 seconds, which is just way too slow,

27
00:01:49.409 --> 00:01:54.538
painfully slow. One of the things that
Vercel gave us was a Speed Insights tab.

28
00:01:54.621 --> 00:01:56.771
From there, I was able
to find the critical

29
00:01:56.854 --> 00:01:58.717
data points that I could use to make

30
00:01:58.800 --> 00:02:03.211
tab navigations a lot faster. Thank
you, Vercel, for making this easy.

31
00:02:03.294 --> 00:02:06.088
Making it fast. Some
magic is happening there.

32
00:02:06.171 --> 00:02:12.737
It feels like all of the dreaming we tend
to do is also on Vercel's roadmap as well.