►
From YouTube: 3 08 Advocate for GitLab Intro
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
There
is
one
type
of
mistake
that
we
can
make
that
we
really
want
to
avoid,
and
that
is
our
last
topic
today,
which
is
wow
we're
like
ahead
of
schedule,
speaking
badly
about
people
teams,
products
inside
gitlab,
and
I
had
a
really
interesting
conversation
about
this
with
another
support
engineer
recently.
So,
if
relevant
I'll
bring
up
what
what
was
involved
in
that,
but
it
helped
me
to
see
that
that
this
is
not
as
straightforward
as
I
might
have
thought
right.
It
can
be
complicated
to
do
this.
Well,.
A
So
once
again,
I'm
going
to
start
with
the
negative
give
us
a
picture
of
where
we
don't
want
to
be
so
things
not
to
say
or
sorry
not
things
not
to
say.
That's
the
next
slide.
This
one
is
why
we
want
to
speak
highly
so
if
you're
blaming
the
product,
you're
powerless
to
fix
the
problem
right,
oh,
that
part
of
the
product
has
never
worked
yeah.
You
know
it's
still
out
there
and
you
can
try
it,
but
it
doesn't
work
well.
What
does
that
mean?
Well,
how
can
I
fix
that?
A
It
just
doesn't
work
so
they're
wasting
their
time
and
working
with
you
you're,
powerless
if
you're
blaming
another
person
or
team,
oh
as
it
turns
out
you're,
powerless
again
because
you're
saying
it
wasn't
me,
I
did
my
stuff.
This
person
didn't
get
back
to
me.
That
person
gave
me
the
wrong
advice
this
whatever
it
is.
Somebody
else
did
this.
A
A
The
concept
called
loyalty
to
the
absent.
I
think
I
got
that
term
right
right.
It
means
you
know.
Kindness
is
not
just
what
you
show
somebody
to
their
face.
It's
all
the
time,
so
we're
going
to
blame
other
people
if
we're
going
to
treat
them
badly
insult
them,
lay
things
on
them.
If
we
won't
do
it
to
their
face,
let's
not
do
it
when
they're
not
there
and
by
the
way.
That
also
makes
you
powerless
to
fix
the
problem,
because
now
the
customer
doesn't
trust
you.