►
From YouTube: Design Pair Session - 04-27-2023
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
Hey
everyone:
this
is
the
design
peer
session
on
April
27th,
and
the
first
thing
on
the
agenda
is
really
to
finalize
our
final
addition
to
the
glossary,
which
is
rollouts
so
Victor
I
added
some
of
your
questions
to
the
doc
and
I
thought
this
would
be
a
great
time
to
kind
of
discuss
through
them
and
try
and
finalize
this
up.
B
Yeah,
that
would
be
cool
if
you
can
do
that.
So,
first
of
all,
if
she
didn't
follow
the
Mr
closely,
this
started
to
define
the
release
term,
but
she
rightfully
pointed
out
that
rollout
might
be
a
better
term
suggest
rollouts
here,
and
my
question
is
that
we
have,
if
I
will
try
to
show
it
in
the
view
app
that
at
the
top
of
the
page
we
have
now
entity
dependency.
B
B
How
would
I
visualize
the
rollout
where,
where
does
it
exist
actually
and
that's
how
I
got
to
those
questions,
namely
to
to
these
like
I,
have
no
idea
and
I
would
love
to
discuss
this
with
you.
If
you
have
any
opinion
like
how
it
works
today,
that
could
be
interesting
as
well
and
how
we
wanted
to
work
whatever.
C
B
C
B
C
C
And
roll
out
of
like,
for
example,
Canary
rollouts
or
some
like
blue
green
deployment,
stuff,
like
that,
it's
more
like
we
had
the
previous
version
of
the
artifact
and
we
gradually
transferred
traffic
to
the
new
one.
I
think
conceptually.
Those
two
are
different
because,
with
the
feature
Flags,
usually
some
manual
action
is
required,
and
this
first
like
or
like
the
canary
deployment
and
stuff
like
that.
C
C
A
C
B
I
I,
don't
know
for
sure
so
like
like,
because
if
it's,
if
I'm
still
stupid,
Canary
I
I
have
one
deployment
currently
Time
Zero
I
have
one
deployment
in
production.
I
start
my
canary
I
have
two
deployments
in
production:
one
serves
100
to
the
traffic
and
I
start
to
move
more
and
more
traffic
to
the
new
one.
B
B
So
both
are
in
the
production
environment.
They
run,
they
serve.
Users
and
I
modify
a
different
intersection
element.
B
B
Because
for
the
future
effect,
it's
like,
but
I
mean
for
the
feature
thing
I'm,
not
sure,
because
that
would
mean
that
I
have
an
environment.
I
have
a
deployment
with
a
specific
feature
like
switched
X,
then
I
roll
out
a
new
deployment
and
that
should
receive
the
same
feature
of
like
values.
Actually,
so
it's
it's
a
status
so
feature
flags
are
status
of
the
environment
and
not
of
the
deployment
the
deployment
just
uses
those
internally
while
the
canary
is,
is
this
Shear
state.
A
B
B
Yeah
cool
that
was
already
useful,
I
wanted
to
bring
one
topic
here.
Some
of
you
might
have
seen
it
already.
I
have
to
find
it
first.
B
B
A
week
ago,
week
ago,
two
weeks
ago,
on
this
school
I
asked
about
the
environments
and
deployments.
B
States
and
I
created
state
tree
I
think.
B
That's
Linked
In
the
docs
now
and
I'm
going
to
appreciate
on
screen
as
well,
so
this
one,
what
I
did
it
doesn't
want
to
reflect
anything
that
what
we
have
today,
even
though
it
started
from
this?
This
was
shared
I.
Think
during
this
call
a
couple
of
weeks
ago.
B
It
was
you
can
relate
to
that.
Basically,
it's
a
bit
more
it
more
Rich
than
that
list,
but
the
idea
was
to
to
see
what
state
deployment
or
environment
might
be
at
and
how
the
two
relate
to
each
other.
I
wanted
to
know
this,
as
you
can
see
in
preparation
for
the
design
Sprint,
but
since
they
turn
out
to
be
used
in
other
places
as
well
and
and
I
would
love
to
hear
your
feedback
like
the
first
question
would
be
whether
what
you
see
do
you
see
any
issues
in
there?
A
I
first
up
want
to
say
thanks
for
putting
this
together,
because
I
knew
of
all
these
states,
but
just
seeing
them
in
like
an
actual
diagram
of
how
they
all
connect
to
each
other
and
where
they
all
end
is
really
helpful,
because
I,
don't
think
I
had
that
visual
before
so
just
seeing
how
they
all
tie
together
is
really
helpful.
This.
A
B
Is
where
it's
different?
Actually,
where
most
differences
exist
because
like
we
only
have
jobs
and,
and
that
makes
it
difficult
to
to
map
a
hierarchy
to
I
think
somewhere
here,
I
I
write
write
about
it
that
yeah
that
basically
progressing
State
means
the
deployment
is
deploying
or
terminating
like
here
and-
and
this
is
clearly
something
that
doesn't
exist
today,
and
this
means
as
well
that
the
provisioning
state
could
happen
without
a
deployment.
A
A
B
B
A
Yeah-
and
we
run
into
this
in
some
of
the
user
testing
too,
where
people
at
first
glance
mistake
the
deployment
status
for
the
environment
status
just
based
on
how
everything's
laid
out,
and
they
completely
miss
that
top
level
like
stopped
available
status.
So
there's
like
that
visual
disconnect
in
the
UI
right
now
that
takes
a
little
while
to
get
used
to.
B
And
yeah
it
was
I
would
really
love
to
hear
the
critics.
If
anything,
because
that
would
be
helpful
to
hear
I
was
saying
like
this
morning.
There
was
an
issue
where
Timo
and
Emily
interacted
on
the
top
form
topic
like
that.
You
can't
rerun
redeploy
with
our
form
and
and
I
was
thinking
better.
That,
for
example,
would
fit
this
setup
for
and
I
think.
The
other
issue
is
that
the
edit
is
an
extra
comment,
not
here,
but
in
a
different
place.
B
B
A
Yeah
I
I
have
to
find
the
I
was
talking
to
forgetting
his
name
during
our
category
maturity
scorecard,
but
he
had
a
full
rundown
of
why
the
redeploy
feature
as
it
works
right
now
does
not
work.
A
C
B
A
Cool,
no
thanks
for
bringing
that
in
I.
Don't
have
any
critiques
so
far,
but
I
do
think.
This
is
something
that
we
can
kind
of
rethink
in
the
ideation
phase
of
the
design
Sprint
when
we
do
get
to
that
point,
and
it
might
be
something
that,
for
some
of
those
initial
talks
or
initial
background
info
is
something
that
would
be
helpful
to
have
presented
to
people.
A
A
Well,
with
I've
mostly
been
planning
on
planning
the
design,
Sprint
and
figuring
out
our
solution,
validation,
recruitment,
so
I
don't
have
a
lot
of
UI
stuff
to
share
during
this,
but
Anna
or
Andre.
Do
you
have
anything
that
you
wanted
to
discuss.
A
B
The
discussion
was
great
with
me
tonight.
It
makes
a
lot
of
stuff
now
I
can
I
can
expand
the
page
based
on
that,
and
that
should
be
good,
and
my
plan
with
the
glossary
moving
forward
is
to
to
bring
back
the
release
term,
because
otherwise
we
just
cause
conclusion
that
we
don't
have
a
definition,
even
though
it's
hidden
in
the
comments
and
the
other
and
well
basically,
that's
it.
B
For
now
and
after
that,
I
was
thinking
that
I
wish
you
that,
for
example,
this
drawing
as
well
I'm,
not
convinced
whether
it's
needed,
but
otherwise
I
think
we
are
basically
done
with
the
with
the
glossary
corner
and
that's
good.