►
From YouTube: Monitor Respond Live Stream Coding 12.10
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
I
mention
the
reflection
in
your
glasses,
sometimes
blocks
out
your
eyes,
but.
B
I
can't
do
anything
about
it,
though
it's
like
simple,
very
different
classes
that
don't
have
the
Bluetooth
anyway
yeah
cool.
So
today
what
we're
going
to
do
is
talk
about
so
we've
almost
finished
our
Emma
there's
only
one
small
problem
left,
but
what
we're
going
to
talk
about
is
how
to
break
down
this
Emma
into
smaller
pieces.
So
accitlab
we
have
a
policy
rule
I,
don't
know
guidelines.
C
B
A
good
one
yeah
so
when,
when
we
say
it's
ready,
when
we
remove
draft
I'll
share
the
screen,
I'll
show
okay.
So
currently
this
Mr
is
in
draft
mode.
So
once
we
remove
the
draft
mode,
we'll
have
a
few
Bots
have
a
look
at
it,
and
one
of
the
Bots
is
going
to
pick
up
that
it's
far
too
big.
B
It's
too
many
changes
to
too
many
files.
So
this
is
a
problem
because
it's
really
difficult
to
review
and
it
means
that
it's
more
likely
that
people
will
just
say
yeah.
It's
fine
look,
looks
good
to
me
right.
So
what
we're
going
to
do
is
try
to
work
out.
How
do
we
break
it
into
smaller
pieces
so
that
each
piece
is
actually
reviewed
properly
and
thoroughly
and
yeah?
That's
it!
B
So
we'll
talk
about
how
to
break
that
down
and
then,
after
that,
if
we've
got
time
we'll
look
into
what
this
last
remaining
problem.
B
So
what
we
need
to
work
out
is
what
which
changes
that
we've
done
can
stand
alone
by
themselves
so
which
changes?
Can
we
merge
where
once
it's
merged,
everything
still
works?
B
So,
for
example,
we
cannot
merge
like
I,
don't
know
like
we
can't
just
merge
the
changes
on
Insta
tabs,
because
one
the
router
won't
have
been
used
to
the
test
footwork,
you
can't
add
the
tests
and
have
them
fail.
So
there's
still
going
to
be
a
fairly
large
Mr
at
the
end
of
this,
but
we'll
see
how
we
can
break
it
down
further.
B
So
one
thing
I
wanted
to
ask
was
so
we're
changing
like
we're
changing
the
routing
here
to
say
that
when
someone
lands
on
ID
slash
timeline,
we
go
to
the
component,
but
if
we
merge
that
by
itself
it
won't
break
anything,
but
it
will
put
in
like
unused
logic.
A
A
It
slightly
changes
so
before
when
normally
you'd
go
to
like
issues,
slash
incident,
slash,
ID,
slash
timeline
and,
and
the
current
Master
like
before
this
Emma
that
goes
to
a
404,
page
yep
and
then
after
this
change.
That
would
take
you
to
like
the
summary
tab
of
the
incident.
A
A
B
C
B
Yeah,
but
we
can't
test
this
yet
I
mean
we
can
just
test
it
in
that
like.
Is
it
a
404
page?
No,
it's
not,
but
like
we
can't
test
it.
It's
going
to
go
to
the
right
tab.
Foreign
won't
be
in
place
if
we
just
merge
this.
A
But
it
probably
does
make
sense
to
have
that
in
the
test
anyway,
that
you
navigate
to
the
navigate
to
one
of
these
routes
and
verify
that
it
actually
does
go
to
the
right
page.
Okay,.
A
B
A
C
A
More
tests,
at
least
yeah.
A
Handle
that
we
also
want
to
handle
the
issues
wrap,
which
you've
already
mentioned
in
another
comment:
s
yes,
which.
B
A
A
Project
routes
file,
so
I'm
just
going
to
look
that
up.
Okay
to
see
if
there
are
any
specs
for
that
yep.
A
Foreign,
so
there
actually
is
a
there's.
A
file
called
project,
routing
speak,
which
had
believed
tests
that
file,
but
what's
interesting,
is
that
there's
no
mention
of
incidents
in
there.
Yet,
even
though
we
have
an
incident
route
already,
but
so
it
kind
of
seems
like
that
was
sort
of
left
untested.
B
A
Something
oh
okay,
handle,
though
those
are
slightly
different
tests.
We
have.
We
have
like
an
end-to-end
test
Suite
that
runs.
A
It
doesn't
run
on
every
merge
request
because
it's
like
quite
large
and
intent
tests
always
take
longer
because
you've
kind
of
run
things
in
like
a
real
browser
and
stuff,
so
the
yeah,
those
like
true
into
interests,
that's
what
they'll
be
working
on.
Okay
and
yeah.
We
typically
don't
add
those
ourselves
that
kind
of
like
managed
by
the
automated
test.
Engineers
specifically.
A
A
A
B
A
Yeah
yeah
and
features
like
it
can
do
things
like
it
could
create
an
on-call
schedule,
then
create
an
incident
chick.
There
check
that
someone
was
paged
and
then
checked
there
like
a
change
in
the
escalation
status,
was
reflected
in
the
timeline.
So
that's
like
several
parts
of
several
different
features,
all
acting
together.
Oh
yeah,
whereas
a
feature
spec
would
be
more
like
we,
we
load
the
incident
timeline
page
and
we
check
that
it
actually
requested
the
right
data.
A
And
our
our
guidance
is
that
for
feature
specs,
we
typically
test.
We
don't
test
every
scenario
we
just
test
like
kind
of
the
happy
path
for
new
features,
yeah.
A
Made
sense,
I
think
Indian
tests
is
even
smaller
and
Scott
in
that,
without
providing
real
values,
whether
like
testing
or
whether
they're
providing
the
most
value
I
think
is
when
they're
testing
the
interaction
of
several
parts
of
the
application
in
making
sure
that
they're
working
properly
together.
C
B
A
C
A
Features
specs
what
the
engineers
add.
A
A
C
A
The
other
thing
would
be
to
investigate
adding
a
a
route
yeah
a
route
speak
you
like
a
unit
test
for
the
wrap
itself,
I'm,
not
sure
why
we
don't
already
have
an
incident
test
in
there,
but
a
lot
of
the
other
routes
seem
to
be
tested
directly.
So
yeah.
C
B
Cool
as
opposed
to
a
virtual
Dom,
which
we
do
in
jest
right.
A
Yeah
capybara
can
run
with
an
actual
browser,
but
I
don't
know
what
order
users
by
default
in
our
in
our
GDK.
If
you
just
it,
definitely
doesn't
seem
to
open
a
browser.
B
C
B
So
maybe,
while
we're
together,
we
can
talk
about
how
to
break
out
the
work
between
us
I
think
that
would
be
the
most
effective
use
of
our
time
and
yeah
interesting
to
work
out
how
to
separate
the
Mr
I've
just
done
this
once
and
it
was
pretty
confusing.
So
it'd
be
interesting
to
go
through
it
with
you
and
think
about
it
properly,
because
yeah.
A
B
So
yeah
so
I
guess
the
The
Wider
question
is
even
with
something
like
the
router
like
so
it's
being
implemented
here.
Sorry,
it's
being
set
up
here
in
the
router
Js
and
then
it's
being
added
in
indexes.
B
A
Oh
I
see
in
terms
of
breaking
it
down
to
like
a
more
manageable
change.
Yeah
I
mean
we
definitely
could
I.
Think
generally,
when
you
there's
kind
of
two
reasons
for
breaking
something
down.
A
One
is
that
there's
like
too
much
code,
and
the
other
is
that
there
are
actually
multiple
things
going
on
in
that
you
want
to
separate
into
different
vertical
slices
vertical
being
like
you've,
got
like
a
complete
front
end
to
back
end
change,
so
something
there
something
that
works,
but
the
change
is
like
as
small
as
possible
that
still
provides
something
new
to
the
user.
A
A
C
A
What
the
second
part
is
doing
and
testing
like
if
the
reveal
wants
to
test
it,
they
can.
A
A
And
that
that's
the
benefit
that
having
a
complete
vertical
slice
provides
because
then
you
can
look
at
it
with
the
perspective
of
how
it's
being
used
yeah.
But
that
said,
it's
totally
totally
not
uncommon
that
we
that
that
I
see
like
changes
like
this
being
merged
without
any
sort
of
visual
change,
because
it's
still
it's
still
better
to
to
have
like
a
small
number
of
changes.
A
If,
if
the
Mr
is
getting
too
big
yeah
and
it
does
help,
I
think
it
does
help
with
the
review
yeah,
so
yeah
I
think,
let's,
let's
think
about
that
as
an
option,
but
we'll
try
and
find
a
way
to
to
break
it
up
vertically.
If
that's
possible,.
B
Okay,
I
did
a
small
amount
of
refactoring
that
can
certainly
go
by
itself.
B
Changing
the
translation,
so
instead
of
using
this
string,
exported
the
translations.
So
this
is
an
easy
Breakout.
B
How
do
you
say
some
of
the
functionality
from
the
tab
back
into
here?
So
a
good
example.
Is
this
incident
metrics
tab
so
because
I
wanted,
because
using
tabs
it
does
some
funny
things
when
you
have
the
tab
within
the
component.
So
previously
this
component
internet
metrics
tab,
rendered
the
tab
itself
yeah.
But
it's
a
little
bit
again
like
gitlab
tabs
doesn't
like
that.
C
B
Yeah
I
can't
remember
exactly
what
was
happening,
but
there's
just
a
couple
of
things
that
were
just
not
quite
right.
Well,.
A
C
A
Of
the
tabs
are
here,
some
of
the
tabs
are
in
the
charts
component,
so
yeah,
if
you
had,
if
you
were
shallow,
mounting
and
you're
trying
to
test
like
the
VF,
whether
it's
actually
rendering
or
not,
whether.
C
A
Is
stopping
the
render
that
would
be
a
bit
weird
too
it's
nice
for
it
to
just
be
consistent,
I
guess,
yeah.
B
Yep
yep
for
sure
yeah,
yeah,
so
I
think
it
mainly
moved
the
translations
like
this,
because
in
the
timeline
tab
it
was
already
using
translations
and
then
I
thought
wow.
Okay,
I
want
to
keep
that
so
now
we
need
to
move
it
around.
So.
B
I
think
it's
worthwhile
sounds
good,
but
these
sort
of
refactoring
that
can
easily
go
by
itself.
A
B
A
Yeah,
if
this
If
This
Were
a
much
bigger
email
been,
it
might
make
sense
to
do
this
to
things
separately.
So
yeah.
B
C
B
B
I
did
ask
as
well
I
changed
this
to
a
chat.
I
do
I,
don't
think
it
changed
anything
visually.
A
C
A
That's
a
good
it's
a
good
point,
because
it
does
change
the
the
HTML
structure,
but
I
think
I've
done
this.
This
exact
thing
before
as
well,
and
the
only
I
think
the
only
way
that
would
affect
something
is
if
we
had
some
CSS
that
was
expecting
not
a
div
underneath
about
multiple
or
something,
but
no
the
tabs
component
is
is
generic
enough
that
it's
fine
with
the
extra
layer.
C
B
But
yeah
also,
if
you're,
adding
a
div
like
this
in
react,
you
would
do
an
empty
empty
component.
That's
what
it's
called.
A
When
you
want
to
have
multiple
children,
but
yeah
multiple
component
components
or
elements
at
the
top
level,
yeah.
B
A
There
was
actually
another
way
which
is
to
I
believe
it's
called
a
functional
view
component
or
stateless
for
your
component.
I'm
just
gonna.
Look
at
the
exact
right
terminology.
A
When
you
use
like
a
render
function,
you
can
sensitive
writing
an
actual
template
and
the
template
language.
You
can
write
a
component
as
a
function
and
well
as
a
component
as
a
object
that
has
a
render
function
and
the
render
function.
You
can
Define
multiple
children
without
a
single
wrapper
and
I've
seen
that
done
in
our
code
and
I
believe
we
have
even
done
it
once
or
twice.
For
that
exact
reason.
C
A
It
would
didn't
work
having
an
extra
layer
of
like
a
div
or
something
that
does
nothing
like
an
example
would
be
if
the
if
the
parent
has
flicks
styles
on
it,.
A
And
you
want
like
evenly
space
items
in
a
list
or
something
or
and
a
child
component
is
the
list
having
an
extra
wrapper
might
interfere
with
the
styles
and
especially
if
the
parent
is
a
third
party
component.
You
maybe
can't
control
whether
like,
where
exactly
those
styles
are
being
added.
A
B
B
A
Yeah,
kids,
Works,
yeah
I
think
that's
that's
an
interesting
idea.
Could
we
could
we
implement
the
react
fragment
component
in
vue.js
for
the
purpose
of
being
over?
There
removes
that
layer.
Sometimes
I
would
guess
that
if
that's
possible
someone's
already
done
that
and
published
it
as
an
npm
module.
B
I
did
find
an
mpm
module.
That
was
just
a
view
fragment,
but
yeah
certainly
seemed
Overkill
for
what
I
wanted
it
for.
C
A
In
this
case,
I
think
it
doesn't,
it
doesn't
affect
this
email.
So
no.
A
B
B
A
B
B
It
includes
this
setting
up
the
router
so
that
you
can
navigate
to
that
page
and
also
in
the
somewhere
else.
Where
was
it
here
in
the
issue
issuables
helper
to
provide
the
current
path.
C
B
A
A
Just
to
verify
that
a
a
white
box
test
level
the
new
routes
work,
even
though
they
don't,
even
though
it
won't
navigate
you
to
the
right
tab.
It'll
just
load
the
I've,
just
like
the
normal
incident
page.
So
what
I
guess?
But
this
one
picks
us
on
yeah
I'm
talking
about
sort
of
adding
those
changes
and
then
adding
a
capybara
test
that
navigates
to
those
new
routes
that
we've
added
up
or
maybe
just
one
of
them,
because
we
don't
have
to
test
every
path
with
a
white
box
level.
A
C
A
Want
to
check
that
that
works,
maybe
in
a
white
box
test,
so
we
can
extend
the.
We
can
extend
that
initial
test
that
we
add
for
the
for
the
back-end
routes.
C
B
B
A
Where
it
belongs,
with
yeah
with
the
client-side
router
changed,
probably
yeah,
it
depends
how
much
you
want
to
split
it
up
like
you.
Could
you
could
literally
just
add
that
one
line
Plus
a
helper
spec
update,
because
I
think
the
helper
speak
will
possibly
fail
without
a
change
as
well,
I,
absolutely
and
then
oh
yeah
yeah.
So
just
the
just
the
help
of
change
and
then
help
us
pick
change.
A
It
depends
how
much
you
want
to
break
it
up.
This
is
where
it
sort
of
yeah
yeah.
If
I
were
doing
it
I
would
it
depends
on
the
size
of
the
email,
but
this
might
be
breaking
it
up
a
bit
too
much
yes,
but
it's
like
as
an
exercise
of
how
to
break
things
up.
A
This
is
definitely
an
option
yeah
so
and
if,
if
this
were
like
a
really
big
Emma
with
a
lot
of
changes
that
touches
a
lot
of
code
to
the
point
where
it
is
hard
to
hard
for
it
really
hard
for
a
reviewer.
A
This
is
something
you
could
do.
You
could
break
out
yeah
just
the
changes
in
the
helper
and
the
spec
changes
for
the
helper,
and
you
could
just
deliver
that
it
doesn't
add
anything
to
the
front
pin
by
itself,
but
it
does
so
it's
not
like
a
vertical
slice,
but
it
is
a
functional
change
that
you
can
do
that
doesn't
rely
on
anything
else.
It
will
break
anything
else,
so
you
can
definitely
ship
it
with
no
problem
and.
A
Yeah
and
because
it's
got
tests
we'll
want
to
update
the
tests,
the
other
in
the
other
side
of
it
is
that.
A
Like
it
is,
it
is
sometimes
nice
to
split
helper
changes
out
in
like
a
really
big.
Ever
often
we
would
do
this
will
be
behind
a
feature
flag
if.
C
A
Was
necessary
as
well
there's
also
a
way
to
break
things
down.
It
can
help
help
a
lot.
If
you
put
things
by
the
future,
though.
C
A
This
case
yeah
in
this
case
I,
don't
think
it
needs
a
feature
flag
necessarily
but
say
we
wanted
to
heads
like
part
of
the
changes
and
it
wasn't
possible
to
do
that
without.
A
C
A
B
A
B
A
So
we,
when
you
say,
merging
into
the
Epic,
do
you
mean
like
onto
a
separate
branch?
So
you
have
multiple
emails
into
that
branch,
yeah
that
there's
totally
another
another
way
of
doing
development,
something
that
with
decided
against
at
get
there
in
favor
of
feature
Flex
yeah,
there's
a
I
think
there's
a
good
explainer
on
the
feature.
Flake
pay
page
throughout
this
yeah.
A
It's
it's
probably
worth
distinguishing
that
there's
two
there's
two
different
types
of
feature:
Flags,
there's
there's
feature
Flags
where
there
is
some
actual
reason
to
turn
a
feature
on
and
off.
That
would
be.
That
would
be
like
a
long-term
feature
flag.
B
A
A
Yeah
and
a
key
property
of
those
feature
Flags
is
that
that
as
short-lived
as
possible,
you
wanna
you
want
to
create
the
feature
flag,
incrementally
merge
the
changes
that
you
have
to
and
then
as
soon
as
it's
as
soon
as
it's
functional
enough,
that
it's
providing
value
to
the
user
and
it's
not
breaking
anything,
then
you
remove
that
the
feature
flag
for
development
entirely
from
the
air.
So
you
you
delete
it
from
the
code.
You
remove
it
from
you.
Remove
the
database
entry
with
it's
been
flipped
on.
C
B
Okay
makes
sense,
yeah
thanks
thanks
for
the
explanation,
it's
really
interesting,
really
helpful
Okay,
so
projects
were
discussed
instead
of
metrics
tab.
This
is
just
more
refactoring
and
the
associated
spec.
So
that's
good,
and
then
this
spec.
B
This
is
the
main
spec,
and
this
is
the
ee
spec
and
in
the
ee
spec
it
only
checks.
This
metrics
tab
is
that
in
the
difference,
whereas
this
one
tests
a
lot
more.
So
that's
why
we
need
to
update
so
many
things.
C
A
And
there's
been
a
slight
refactor
of
of
that
spec
file
as
well.
Yeah.
A
Yeah,
the
the
signature
of
the
mountain
component
method
has
changed
slightly,
so
that
that
is
also
something
that
you
could
split
information.
A
Yeah
yeah,
so
the
view
spec.
A
Slight
refractor
yeah
yeah
exactly
yeah
another,
it's
another
one
that
if
we
were
breaking
down
a
larger
email.
C
B
B
Okay,
that
makes
sense
to
me
so
so
then
we
have
a
couple
of
easy
ones,
so
these
could
be
together.
Let
me
see.
B
B
B
All
right
so
yeah,
this
is
fine
back
in
routing.
It
doesn't
rely
on
anything
else.
Yeah
upper
change
doesn't
rely
on
anything
else
and
rapping
doesn't
rely
on
anything
else.
So
actually
of
Russian
relies.
B
B
B
C
A
A
In
terms
of
routing,
so
it
would
be
like
a
learning
exercise
for
me.
A
A
Bullet
point
as
well:
I
think
some.
C
B
B
Just
comment
that
now
and
then
we
can
finish
this
stream
and
then
we'll
talk
about
how
to
schedule
those.