►
From YouTube: CEO 101 - Public Stream
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
B
A
Thanks
for
asking
the
most
important
thing
is
that
the
handbook
is
up
to
date,
like
most
knowledge
bases,
I've,
seen
that
other
companies
got
out
of
date,
and
so
what
which
I
get
lab
is
do
things
handbook?
First,
so
you
change
the
handbook
and
then
you
communicate
the
change.
It's
not
something
you
do
after
the
fact,
because
then
you
tend
to
forget
it
so
and
if
there's
a
change,
you
don't
send
two
paragraphs
of
text
in
the
email
or
you
don't
give
a
presentation.
You
just
link
to
the
change
you
made
to
the
diff.
A
So
people
understand
what
changed.
So
that's
the
most
important
thing
we
do
another
thing:
we
need
to
do
a
bit
more
split
pages
up,
for
example,
you
go
to
our
sales
page
in
the
handbook.
It's
way
too
long.
It's
because
people
are
not
super
comfortable
making
new
pages
so
splitting
that
up
helps
and
across
linking
making
sure
that
we
don't
duplicate
things,
but
we
just
have
a
cross
link
to
the
other
location
where
it's
defined.
It
may
be
a
link
back
Christy
yeah,
you
wanna
verbalize,
your
question,
yeah.
C
A
Things
thanks
for
being
interested
in
that,
and
thanks
for
asking
and
I
forgot
to
say
everyone
welcome,
I'm,
a
bit
thrown
off
because
we
started
a
bit
late,
but
welcome
to
get
laughing's
for
things
are
choosing
to
work
here,
reinforcing
our
values
we
do
in
a
bunch
of
ways.
First
of
all,
like
culture
is
values,
so
our
culture
is
our
values.
A
A
Questioning
them
saying,
hey
is
this:
this
is
correspond
with
the
values
because
I
think
it
isn't
really
rhyme
with
this
or
that
and
then
one
things
to
help
raise
visibility
is
to
kind
of
post
video,
so
you
should
all
be
getting
an
account
on
get
weapon
filtered
on
YouTube
and
it's
it's
always
awesome
to
see
someone
kind
of
post
like
a
I'm
now
a
weekend
at
collab-
and
this
is
my
experience
so
far,
so
it's
a
feel
that
you
can
post
anything.
You
want.
A
D
Christine
and
I
were
typing
at
the
same
time,
roughly
so
similar
to
Christine's
question
I
was
curious
about
how
so
get
labs.
Culture
was
was
I.
Think
for
many
of
us
a
huge
draw,
and
it
certainly
was
in
in
my
case,
how
do
you
see
our
ability
to
support
that
that
culture
across
the
the
transition
to
being
a
public
company?
How
do
you,
how
do
you
see
we
can?
We
can
support
that
and
what
are
the
most
important
things
to
keep
as
we
grow
yeah.
A
E
A
So
the
handbook
was
public
because
we
started
as
a
in
the
beginning
of
get
out
the
open
source
community
around
get
members
was
everything
and
we
just
started
with
a
few
people
and
I
always
found
that
it's
a
big
risk,
if
you
become
a
commercial
company
to
either
lose
the
community
where
people
are
not
and
excited
anymore
or
to
even
have
like
rivalry
between
the
two.
So
I
figured
one
of
the
ways
to
reduce
that
friction
between
the
wider
community
and
the
company
is
to
at
least
be
very
open
about
what
you
do.
A
The
the
credit
values
at
a
certain
point
we
had
13
values
and
I
could
name
three
to
four
of
them
and
most
people
in
the
company,
even
less
so
nobody
knew
so.
It
was
clear
we
had
to
consolidate
so
with
jon
hamm,
my
CEO
coach.
We
wrote
all
of
them
down
and
we
tried
to
group
them,
and
then
we
did
some
checks,
for
example,
seeing
whether
they
prevented
the
five
dysfunctions
and
a
few
other
things
like
hey.
These
are
things
every
company
should
probably
pay
attention
to
and
that
we
came
up
with
this
pattern.
A
F
Hi
SID,
thank
you
so
much
for
the
welcome.
So
my
question
is
around
diversity,
one
of
the
values
here
at
get
lab
and
I'm
curious.
How
do
you
yourself
personally
define
diversity
and
and
what's
your
vision
for
seeing
it
implemented
at
its
best
here
at
gitlab,
I
feel
like
we're
already
very
diverse,
but
I'd
love
to
hear
your
perspective
on
how
much
more
you
see
us
becoming
diverse,
and
what
does
that
look
like
to
you?
Yeah.
A
One
important
thing
which
someone
once
told
me
is
like
you
shouldn't
apply
to
everything.
So
sometimes
things
are
yeah
they're
different,
but
it's
a
pretty
frivolous
thing
and
in
that
case
don't
don't
invoke
diversity
because
it
means
something
a
bigger
and
more
substantial.
I
think
the
thing
that's
most
challenging
still
for
us
is
is
having
more
underrepresented
groups
at
Caitlyn.
So
for
me,
that's
that's.
The
primary
focus
of
everywhere
we
can
still
improve
them
on.
A
Both
and
and
also
you
added
that
you
will
update
the
the
part
of
the
head
book
that
counts
are
pages,
so
thanks
for
that,
I
do
think.
The
main
reason
it's
growing
is
that
we're
just
expanding
as
a
company
and
we're
getting
more
process
in
place
to
make
sure
we
all
work
together
efficiently.
So
it's
a
great
thing,
but
there's
also
some
of
the
new
sections
are
less
succinct.
Then
they
could
be.
A
A
A
I,
don't
think
we
are,
but
I,
don't
think
it's
a
big
problem
right
now
over
time
it
becomes
a
bigger
problem
and,
and
it
tends
to
calcify
it
tends
to
cause
like
the
most
important
information
to
be
hard
to
find,
because
there's
these
irrelevant
parts
that
are
there,
it's
not
such
so
much
information.
That
is
a
needed,
but
it
is
not
as
important
as
some
other
things.
So
kind
of
balancing
that
is
gonna
be
very
important.
A
G
A
Yes,
although
it's
very
important
as
a
company,
we
don't
measure
and
measure
our
success
in
the
right
way.
There's
a
saying
in
in
computer
science
and
measuring
progress
by
lines
of
code
is
by
measuring
the
quality
of
an
aircraft
design
by
the
weight,
like
you
want
as
few
as
possible,
so
we're
gonna
make
sure
that
we
understand
it's
grated.
Collab
is
now
more
and
more
team
members.
We
want
to
keep
the
company
as
small
as
possible
like
hiring
to
solve
problems.
A
G
A
H
There
are
several
meetings
where
we're
sort
of
repeating
ourselves,
or
you
know,
with
introductions,
and
certainly
you
had
your
Q&A
earlier
as
much
as
I'm
sure.
We
also
appreciate
the
time
that
you're
spending,
specifically
with
us
right
now,
I
was
just
curious.
Are
you
getting
something
out
of
this
as
well?
Well,.
A
Thanks
for
asking
well
it's
fun
to
meet
all
the
new
people.
That's
that's
the
first
thing.
The
second
thing
is
this:
is
public
stream,
so
things
you're
wondering
about
imagine
other
people
considering
joining
Gilad.
They
wonder
about
the
same
stuff
and
we
get
to
tell
them
before
head
and
then
very
frequently.
A
question
gets
asked
where
I'm
like
we
should
document
that
better
and
most
of
the
time
I
do
that
straight
in
the
meeting
so
I
tend
to.
We
tend
to
improve
things
and
I
could
even
imagine.
A
We
now
have
two
shadows
joining,
so
maybe
they
see
an
opportunity
to
add
something
to
the
relevant
part
of
the
handbook
regardless
you
should
be
there
or
here
not
sure,
we've
seen
something
yet
fabiana's
going
to
update
a
number
of
posts
and
with,
for
example,
the
the
credit
story.
Is
that
noteworthy
should
I
be
cut
out
of
this
video
and
embed
it
on
our
values,
page
on
our
culture,
page
I.
Don't
think
it
was
that
good
of
a
story,
but
it
happens
all
the
time
so
I
think
it's
I,
think
it's
great
and.
A
Imagine
having
doing
this
like
just
the
sheer
efficiency
of
being
able
to
record
this
and
publish
this
I
really
appreciate
that
and
the
only
concern
there
is
that
please
do
ask
the
hard
questions.
Don't
don't
hold
back
on
anything
or
any
concerns
you
have,
because
it's
because
it's
published
Zak
right,
you
have
the
next
one
I.
I
A
A
So
here
you
see
that
the
hardest
to
and
financial
controls
are
hard
audits
and
things
like
that.
The
hardest
thing
is
top
of
the
funnel
modeling.
So
that's,
basically
the
prediction
of
your
future
revenue.
Do
you
know
how
much
revenue
you're
gonna
generate
next
quarter
and
the
quarter
after
that?
That's
hard
because
you're
not
in
control
like
that's
customer
signing
signing
up
for
things,
not
you
you're,
making
a
decision,
so
it
tends
to
be
that
cost
is
much
more
in
control
than
income.
So
then
I
think
it's
first
note.
A
J
So
just
come
off
me
there
yeah.
So
my
question
is:
what
do
you
see
as
the
next
sort
of
trends
shaping
the
way
developed
teams,
work?
I,
guess
you
know
in
brackets
you
could
put
sort
of
team
collaboration,
I've
been
doing
a
bit
of
reading
and
it
seems
that
previously
there
was
a
preference
for
people
to
use
and
tools,
individual
tools
and
now
moving
towards
a
single
application.
What
do
you
kind
of
feel
is
the
next
sort
of
I
guess
stage
or
development
of
hard
about
team's
work,
yeah.
A
Thanks
for
that,
I
think
we're
still
early
in
the
single
application
phase.
It
tends
to
be
when
there's
more
innovation
going
on
that.
You
start
you,
you
see
like
more
diversity
in
the
ecosystem,
more
different
solutions,
more
different
companies
and
then,
as
an
industry
kind
of
matures,
it
gets
consolidated
and
I.
Think
that's
what
happening
in
DevOps
like
we
had
the
blossoming
of
many
different
tools:
everything
from
portfolio
management,
to
feature
flags,
etc,
and
now
we
see
the
consolidation
led
by
us
and
then
it
probably
Microsoft
following
the
first
follower
that.
A
Still
has
many
many
years
to
play
out
I
think
there's
the
most
companies
right
now,
I
still
use
like
50
different
DevOps
tools
throughout
the
company
I
think
there's
a
long
way
to
go
before
before
that's
consolidated,
and
then
then
it
tends
to
be
that
it's
mostly
not
the
same
aspect
or
not
the
same
industry.
That
then
gets
kind
of
unbundled
again,
mostly
it's
an
adjacent
thing,
and
then
what
that
adjacent
thing
is
I,
don't
know,
I!
Think
for
now
you
see
much
more
that
AI
ml
and
data
start
becoming
much
more
important.
A
You
see
an
explosion
of
tools
there
to
manage
that
life
cycle.
Thinking
about
tools
like
cube
flow,
so
I
think
that's
probably
the
next
frontier,
where
there's
still
now
more
more
tools,
especially
around
like
compliance
training,
preventing
black
boxes,
understanding
biases,
where
we're
still
privacy,
things
we're
still
very
early
there.
So
that's
I,
foresee
there
more
tools
and
an
only
Dan
consolidation
in
the
DevOps
tools,
consolidation.
That
seems
to
be
a
trend
for
like
the
next
ten
years.
But
it's
hard
to
predict
thing
is
especially
in
the
future
interesting.
Thank
you.
K
A
Are
we
have
a
buyer
based
open
core
model?
Maybe
someone
can
add
a
link
to
that
to
the
section
on
the
CEO
pricing
page,
for
that,
what
it
means
is
that
we
price
our
features
based
on
who's,
the
what
user
cares
the
most
at
the
feature
and
if
that's
an
individual
contributor,
it's
great
to
open
sources,
because
they
can
contribute
back
to
the
feature.
Individual
contributors
tend
to
be
the
people
who
contribute
back
to
them.
A
If
it's
a
feature
aimed
at
and
exactly
if
it
tends
to
be
paid,
which
is
helpful
because
they
tend
to
contribute
less
back,
but
also
they
tend
to
have
a
larger
budget
and
I
think
it
took
us
a
couple
of
years
to
kind
of
figure
out
this
split.
But
so
far
is
it's
been
a
great
way
to
make
sure
that
we
have
a
steady
stream
of
both.
But
we
kind
of
pick
the
right
pricing
tier
for
each
for
each
feature,
including
the
pricing
tier,
which
is
like
open
source
great.
They
do
Jeremy
yeah.
E
L
Said
so,
I
joined
the
UX
team
last
week
and,
as
you
know,
we're
working
on
kind
of
a
beautify,
the
UI
project
and
so
I
wanted
to
just
kind
of
pick.
Your
brain
and
my
question
specifically,
is
what
adjectives
would
you
use
to
describe
the
user
experience
and
visual
design
of
the
product
today
and
how
would
you
like
it
to
be
described
in
the
near
future?.
A
A
Maybe
not
supposed,
but
the
story
version
of
this
is
that
we've
been
masters
of
complexity
like
even
attempting
to
put
the
entire
DevOps
lifecycle
on
a
single
application.
That's
that's
quite
a
tall
order
and
I
think
we've
succeeded
at
that,
and
we're
now
for
for
people
who
aren't
familiar
with
either
gate
lab
or
github
people
said
tend
to
say
that
the
gate
lot
navigation
is
better,
even
though
we
have
a
lot
more
functionality.
We
need
to
cram
in
there.
So
I
think
that's
been
an
amazing
achievement
and
very
part
of
the
team
for
doing
that.
A
I
think.
The
reason
that
our
product
is
a
bit
rough
is
that
our
UX
department,
our
designers,
our
researchers,
they
tend
to
focus
on
the
new
functionality
for
making
we're
making
so
many
new
things,
and
we
need
so
much
input
that
that
that's
where
the
focus
has
been
and
Christy
is
helping
the
department
to
focus
more
on
the
heavily
you
stuff.
So
not
doesn't
the
new
things
at
the
edge,
but
the
stuff
that
are
in
the
center
that
are
not
changing
rapidly.
A
A
Experiment,
I'm
is
spent,
then
another
thing
has
been:
we
kind
of
assumed
that
the
viewers
are
already
knows
what
you
do
and
then
we
want
to
be
there
for
them.
We
have
a
will
to
win
in
like
onboarding
the
users,
and
then
we
have
kind
of
make
it
more
beautiful
and
using
a
single
design
system
and
a
pajama
system
throughout
the
application,
we're
still
in
the
early
phases
of
that.
But
that's
showing
a
lot
of
promise.