WEBVTT

00:00:00.029 --> 00:00:01.690 align:center
If you are in a monorepo

00:00:01.710 --> 00:00:02.871 align:center
environment where you have a bunch

00:00:02.911 --> 00:00:04.853 align:center
of developers, my advice to all

00:00:04.893 --> 00:00:06.013 align:center
would be to have a really

00:00:06.073 --> 00:00:08.155 align:center
nice observability on what your queue

00:00:08.195 --> 00:00:09.796 align:center
health looks like, what your agent

00:00:09.836 --> 00:00:10.537 align:center
health looks like.

00:00:10.757 --> 00:00:12.458 align:center
Have each journey measured.

00:00:12.618 --> 00:00:14.219 align:center
When you have the metrics at

00:00:14.299 --> 00:00:14.820 align:center
that level,

00:00:15.160 --> 00:00:16.541 align:center
And if anything goes wrong, it

00:00:16.601 --> 00:00:18.523 align:center
makes your life very easier to

00:00:18.603 --> 00:00:19.764 align:center
pinpoint and debug.

00:00:19.924 --> 00:00:21.025 align:center
It helps you to come up

00:00:21.045 --> 00:00:23.127 align:center
with like future goals of optimization.

00:00:23.147 --> 00:00:24.488 align:center
The second thing, which I think

00:00:24.708 --> 00:00:26.529 align:center
is not highly speak upon, but

00:00:26.569 --> 00:00:27.710 align:center
I think it's really helpful is

00:00:27.730 --> 00:00:29.352 align:center
having a nice on-call support.

00:00:29.512 --> 00:00:31.093 align:center
Our Monorepo teams does a really

00:00:31.113 --> 00:00:32.674 align:center
good job of supporting our own

00:00:32.734 --> 00:00:33.235 align:center
developers.

00:00:33.755 --> 00:00:35.316 align:center
a developer is struggling with something,

00:00:35.416 --> 00:00:36.716 align:center
they reach out to our Monorepo

00:00:36.736 --> 00:00:38.437 align:center
Slack channel and then they're able

00:00:38.477 --> 00:00:39.697 align:center
to engage with them and they're

00:00:39.717 --> 00:00:40.717 align:center
able to help them out.

00:00:40.898 --> 00:00:42.278 align:center
And then they utilize CI and

00:00:42.318 --> 00:00:44.019 align:center
our SubmitQ team if it's something

00:00:44.059 --> 00:00:45.319 align:center
around the infrastructure failure.

00:00:45.439 --> 00:00:47.180 align:center
So having that also increases developer

00:00:47.220 --> 00:00:50.361 align:center
experience and makes developers life easier

00:00:50.521 --> 00:00:51.821 align:center
on how to utilize and do

00:00:51.861 --> 00:00:53.462 align:center
a development in Monorepo day to

00:00:53.482 --> 00:00:53.602 align:center
day.