►
From YouTube: Design Pair Session - 04-13-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
the
design
pairing
session
on
April,
13th
and
I've
added
a
few
things
to
our
agenda,
the
first
one
just
focusing
on
finalizing
the
second
iteration
of
our
glossary
and
getting
it
merged.
A
So
thank
you
all
for
who've
jumped
in
there
so
far,
I
think
the
only
outstanding
was
really
around
the
application
definition,
but
I
think
we're
pretty
much
there,
but
just
wanted
to
open
up
a
bit
of
time
during
this
meeting
to
kind
of
discuss
anything
that
might
be
outstanding.
With
this
Mr.
A
A
Yeah,
so
it
let
me
just
summarize
some
of
the
changes
that
we're
adding
in
here
so
we're
adding
in
definitions
for
application,
configuration
deployment
and
secrets,
I,
believe
Secrets
deployment
configuration
have
all
kind
of
finalized
and
we're
good
with
the
definitions
for
those
application
was
the
one
we
were
running
into
problems
with,
because
the
term
release
in
application
release
has
so
many
different
meanings
that
trying
to
Define
release
in
the
application
definition
was
getting
a
bit
confusing.
A
So
we've
taken
release
out,
we've
replaced
it
with
artifact,
as
that's
more
like
all,
encompassing
of
what
this
means,
but
that's
that's
kind
of
the
summary
of
what
has
happened
in
this
Mr
so
far,.
B
A
A
Cool
I
think
I
think
we're
probably
good
to
merge
that
in
and
then
get
started
on
the
next
one
next
week.
V3
of
this
so
I
do
not
have
merge
right
so
Victor
you
can
do
the
honor
doing
this.
B
A
I,
don't
have
anything
major
for
this
week,
design
wise
because
it
was
kind
of
focused
on
getting
the
16-0
plan
finalized
and
everything
done
with
the
1511
plan.
But
I
do
have
one
ask
I'm
looking
to
sub
in
real
or
believable
data
into
our
group
level,
environments,
dashboard
and
I
was
hoping.
I
could
partner
with
someone
to
kind
of
figure
that
out
I've
called
out
Andre,
because
I
know
you
had
worked
with
this
style
of
kind
of
setup
before
but
open
to
anyone
who
might
be
able
to
help
with
that.
A
D
That
depends
on
actually
how
much
time
do
you
expect
from
me
Emily.
A
A
Yeah
not
I'd,
say
probably
Max
half
an
hour
of
your
time.
A
And
that
kind
of
wraps
it
up
with
my
stuff,
but
now
I'm
passing
it
over
to
see
if
anyone
else
has
any
outstanding
design.
Stuff
I
could
help
with.
A
I
agree:
that's
why
I
didn't
have
very
much
for
this
one,
because
most
of
my
1511
stuff
has
been
wrapped
up
so.
B
B
So
what
I
started
to
think
about
is
that
is:
do
we
have
anywhere
documented
the
current
available
state
of
the
deployment
or
a
deployment
job
where
I
don't
even
know
or
environments,
because
what
I've
seen
is
that
we
have
plenty
of
issues
around
States,
not
working
as
we
expect
them
to
so
I
think
it
would
be
important
for
us
that
for
the
design
Sprint
we
know
the
available
State
and
we
can
either
discuss
based
on
them
or
we
can
add
more
States
as
part
of
the
design
Sprint,
so
that.
B
Yeah
I
would
expect
here
more
engineering
documentation
so
like
that,
is
it's
not
just
what
we
document
for
our
user,
but
really
what
what's
happening
behind
it.
So
what
are
the
states
that
we
store
in
the
models?
Is
there
any
constraints
around
them
and
stuff
like
that?
Is
it
documented
anywhere
or
we
would
need
to
to
look
for
it
in
the
code
base.
B
A
C
C
Api
by
the
way,
like
an
enum,
so
it's
just
an
enumeration
of
all
those
listed
States,
but
it
doesn't
necessarily
give
good
details
as
to
what
each
date
means,
the
idea
being
that
we
named
them
well
enough
that
it
should
be
pretty
obvious,
but
it
never
really
is
so
yeah.
C
A
Since
this
is
kind
of
our
in-between
week,
meeting
I
can
give
people
a
bunch
of
time
back.
If
there's
nothing
else,.
A
Well,
thanks
all
for
helping
merge
the
next
iteration
of
the
glossary
look
forward
to
the
next
the
few
terms
coming
in
next
week.
So
we're
trying
to
get
this
all
done
before
we
do
a
design
Sprint.