►
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
The
ama
you
mentioned
wanting
to
be
sas
first,
which
makes
sense,
and
you
want
better
reliability,
usability,
speed
and
marketing,
but
that
seems
a
little
counterintuitive
to
iterating
quickly,
releasing
somewhat
bare
features
and
then
iterating
based
on
customer
feedback.
Reliability
should
always
be
there,
but
you
typically
sacrifice
the
other
three
to
some
extent.
How
do
we
achieve
your
vision
and
still
iterate
quickly.
A
Yeah
thanks
for
the
question
and
as
usual,
our
iteration
value
is
not
intuitive.
That's.
Why
we're
it's
the
only
value
we
have
office
hours
about?
I
do
think
that
you
can
combine
iteration
with
these
things,
so
I'll
do
a
I'll
go
one
by
one
and
try
to
name
an
example
so
usability.
A
A
A
A
A
Would
you
rather
do
that,
all
at
the
same
time
or
one
by
one
I
much
rather
do
it
one
by
one,
because
then
I
have
one
problem
at
a
time,
instead
of
only
problems
at
a
time
which
can
interact
with
each
other,
it
makes
it
just
harder
to
diagnose,
and
if
I
think
about
speed,
I
think
speed
is
something
that
you
definitely
should.
Iterate
anytime,
I've
been
as
a
programmer
faced
with
a
performance
problem.
A
C
Yeah,
hey
thanks
sid,
so
my
question
was
as
the
organization
scales
and
we
pursue
new
certifications
and
come
under
like
new
regulatory
requirements
as
we
expand.
How
do
you
think
we
best
embrace
iteration
without
causing
confusion
for
the
overall
team
and
and
frustration
with
kind
of
an
ever-changing
bar
to
meet?
I
think
specifically
like
you're
the
in
the
handbook.
We
talk
about
two-way
doors
and
reversing
decisions,
also
keeping
in
mind.
C
I
guess
that
compliance
and
regulators
generally
dislike
things
that
move
quickly
and
at
times
it
can
even
feel
like
you
know.
Why
would
we
even
change
this
process,
because
the
overhead
and
the
frustration
that's
going
to
cause
from
a
new
compliance
benchmark
that
we
need
to
meet
is
is
just
not
worth
it
and
how
do
we
manage
that.
A
So
far,
regulators
have
impressed
me
with
their
ability
to
embrace
iteration
an
iteration
at
gitlab
doesn't
mean
like
you.
Just
do
something
and
don't
document
it
in
fact
we're
one
of
the
best
documented
companies
in
the
world
and
one
of
the
big
problems
with
being
compliant.
Is
that
your
documents
say
one
thing
and
you
do
the
other
thing,
and
that
is
what
we're
addressing
by
iterating
like
we
can
we
frequently
make
updates?
A
We
went
to
some
regulators
recently,
let's
say
financial
regulators
and
we
were
like
well,
we
have
this
whole
handbook.
Is
it
a
liability?
How
do
you
think
about
it?
They
love
it.
It's
more
public,
it's
better!
It's
that
that
is.
It
should
be
a
dream
of
any
regulator
to
see
how
we
work.
A
A
Let's
review
them,
but
that
doesn't
mean
you
didn't
implement
those
changes
during
the
last
month
because
we
have
to
be
responding
to
changes
constantly
and
we
can't
have
our
documented
process
be
something
else
in
our
real
process.
That's
what's
happening
at
any
company
that
puts
a
lot
of
roadblocks,
so
switch
from
approvals
to
periodic
reviews
when
needed,
educate
regulators
and
they
they
should
be.
They
should
be
requiring
other
companies
to
work
like
us.