►
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
It
was
fun
that
was
yesterday
anyway.
Let's
do
this,
so,
yes,
the
the
opening
part
will
be
edited
out
of
the
youtube
uploads.
So
don't
worry
about
that.
So
happy
monday
hope
everybody
had
a
good
weekend
or
as
good
as
you
can.
If
you
are
a
us
sports
fan
and
follow
a
small
event
that
happened
yesterday,
condolences
to
you
if
you
ended
up
on
the
wrong
side
of
things
and
congratulations
if
you
ended
up
on
the
right
or
you
just
enjoyed
a
good
game,
we'll
get
into
the
announcements.
A
So
two
folks
are
out
you
gotta
as
far
as
when
those
are
occurring.
So
if
you
need
them,
get
them
in
advance
the
I
am
going
to
be
intentionally
doing
a
better
job
at
getting
these
recordings
up
on
youtube.
I
I
blasted
12
of
them
up
to
youtube
on
friday,
and
so
I
polluted
the
get
lab
timeline
as
most
recent
updated
videos
with
all
of
us
going
back
to
the
early
september,
the
and
but
anyways
that
was
just
fun.
A
The
big
impactful
thing
to
be
aware
of
bug:
slos
they
used
to
be
driven
off
of
prior
of
the
priority
fields.
Now
it's
off
of
severity
and
so
and
how
those
slos
are
defined
as
available
in
the
link
from
that
documentation
and
the
last
one
is
the
splitting
of
the
common
library
that
is
getting
to
the
point
where
there's
a
we're
ready
to
start
rolling
that
out
to
a
whole
bunch
of
analyzers
that
is,
and
so
everybody
get
ready.
A
There's
gonna
be
a
lot
of
reviews
coming
out
in
order
to
use
the
new
split
approach,
as
opposed
to
one
big
one,
big
framework,
all
right
with
that
I'll
get
into
the
agenda,
and
so
hopefully
everybody
had
a
chance
to
take
a
look
at
this
late.
Last
week,
I
I
know:
we've
been
feedback
heavy.
I
know
that
we've
had
annual
reviews
and
we're
just
now
coming
out
of
that
particular
cycle.
A
However,
the
last
time
we
did
quarterly
career
framework
reviews
was
back
in
late
october
and
it's
been
three
months
so
it's
time
to
do
it
again.
So
my
my
commitment
to
you
all
is
that
I
keep
the
the
what
we're
judged
against
locked
for
a
calendar
a
year.
Well,
it
rotates
with
this
one.
So
the
impactful
changes
for
this
r
is
that
the
spreadsheet
that
we
have
it
used
to
be
possible
to
be
all
the
way
up
to
demonstrating
excellence
or
demonstrating
strength
and
everything
also.
A
But
that
is
where
we
entered
into
a
comparison
against
your
peers.
That's
gone.
Those
are
no
longer
possible
ratings,
either
you're
consistently
doing
this
you're
inconsistently
or
you're,
not
doing
it
at
all,
and
so
that
way
we're
keeping
it
so
that
it's
just
your
performance
as
opposed
to
making
it
a
comparison.
A
And
the
other
bit
of
this-
and
this
is-
is
something
that
you'll
find
back
on
in
an
october
agenda.
Is
that
you're
going
to
get
additional
feedback
on
one-on-one
templates
on
a
quarterly
basis?
Far
from
a
strengths,
areas
of
improvements
or
or
opportunities,
I
think,
is
the
way
that
we
used
it
on
and
framed
it
on
annual
reviews,
training,
job
knowledge
and
so
forth.
A
All
of
this
is
to
do
twofold
number
one
give
you
actionable
feedback,
and
the
other
is
to
make
this
more
directly
map
to
what
we
are
increasingly
using
for
annual
review
documentation
just
because
I'll
make
it
fit
what
we've
been
doing,
but
I
want
to
make
it
more
obvious,
and
so
that's
the
that's
the
catalyst
for
these
changes.
A
There
is
on
the
updated
template.
There
is
one
field
where
I
have
deviated
from
what
we
have
written
as
a
company
and
it
only
impacts
staff
engineers
I
there
is.
There
is
one
particular
field
that
has
been
the
subject
of
much
debate
for
a
year
a
year
and
a
half
about
staff
engineers
partnering
with
engineering
managers
to
assign
people
tasks.
I've
changed
it
so
that
it's
more
about
helping
shape
requirements
in
advance
of
refinement
and
and.
B
A
A
Okay,
silence:
I'm
terrified
silences.
Y'all
are
good
y'all
ready
to
do
this,
so
I'm
going
to
schedule
these
out
for
a
couple
of
weeks
from
now
and
we'll
and
we'll
we'll
and
we'll
we'll
we'll
see
how
this
new
framework,
our
new
approach,
fits
and
we'll
do
it
this
way
for
the
for
the
rest
of
this
year,
all
right,
lucas,
floor's
yours,
sir.
B
So
I
was
just
sharing
this
in
case.
Anyone
misses
it,
but
julian
finished
the
gap,
analysis
for
bandit
rule
coverage
and
some
grep
worth
looking
over,
even
if
not
working
on
that
initiative,
it's
kind
of
interesting
stuff
to
see
how
one
of
our
tools
measures
up
against
semgrap
and
how
you
go
back,
go
about
analyzing!
That
data.
A
I
shared
this
privately,
but
I'll
go
ahead
and
put
it
here
as
well.
I'm
very
curious
what
the
false
positive
rate
looks
like
for
some
grip
compared
to
bandit
now.
Thankfully,
some
grip
is
a
rules
engine,
so
we
can
that
we
can
augment
rules
and
we
can
contribute
back
that
way
as
well.
So
that's
that's
that's
useful,
but
I
was
a
little
surprised
by
the
output
of
this.
So.
C
Yeah
one
one
plus
and
I'll
write
this
down
here
in
a
second
too,
is
that
julian
actually
wrote
rules
to
cover
the
gaps
it
they'll
just
need
metadata.
C
So
so
there
will
be
a
little
bit
of
real
work
to
refine,
but
I
asked
for
clarification
to
make
sure
I
understood
that
correctly
as
well,
as
that
would
also
prove
the
feasibility
of
moving
forward
with
some
grip
as
a
replacement,
but
yeah.
I
think
false
positives
too.
I
mean,
if
you
know,
maybe
less
than
100
coverage
is
the
right
thing,
because
it
you
know,
really
lowers
you
know
fp
or
something
like
that,
but
be
good
to
dig
into
that.
A
little
deeper.
A
That
seems
to
be
the
direction
that
we're
heading
here
within
sas
and
the
larger
ast
community,
which
I
think
is
a
good
maturation
step.
If
I
were
to
and
I'm
not
trying
to
spin
it,
I'm
just
making
a
corollary
here,
the
it's.
A
It's
going
to
be
fascinating
to
to
see
how
all
this
stuff
fix
shapes
out,
but
I'll
be
quiet,
but
anyway,
I'm
just
curious,
and
I'm
I'm
wondering
if
that's,
I
think,
I'm
agreeing
with
you,
but
at
the
same
time
I'm
also
grateful
that
we
can
augment
more
clearly
with
this.
D
I
was
able
to
ask
some
questions,
so
we
went
through
how
gitlab
is
is
buzzing,
how
you
can
imported
budget
to
a
gitlab
analyzer.
So
there
are
the
notes
for
anyone
who
wants
to
take
a
look,
and
I
think
he
recorded
it,
which
once
that
is
up
on
youtube.
I
will.