►
From YouTube: Code Quality Vision Deep Dive 09.25.2019
Description
A deep dive on the vision page of Code Quality (https://about.gitlab.com/direction/verify/code_quality/) with James and Jason.
B
A
A
So
category
vision
for
code
quality
is
part
of
the
product
vision
for
verify,
overall,
which
also
ties
them
up
into
you:
the
direction
for
CI
CD,
but
this
is
very
focused
on
the
part
of
the
verify
pipelines
which
are
around
automatically
doing
code,
quality
analysis
on
pipelines
and
then
making
that
visible
in
various
places.
All
of
our
category
vision
pages
follow
the
same
or
similar
format
to
this
one.
Where
there's
a
little
bit
of
a
description
of
the
code
quality
feature,
it
would
a
lot
of
your
categories.
A
James
are
going
to
be
ones
that
you
need
a
little
bit
of
love
and
could
use
some
expansion,
and
already
you
know
yeah.
This
is
a
true
statement
about
what
code
quality
is
that
we
could
probably
talk
a
little
bit
more
about
what
the
future
is
and
what
our
philosophy
code
quality
is
to
expand
on
this
and
make
it
a
little
bit
more
comprehensive
shouldn't,
be
like
a
novel,
but
maybe
a
paragraph
or
two
would
be
more
useful.
This
is
sort
of
like
a
a
little
bit
of
placeholder
content.
A
Now
they
all
have
an
issue
list
which
I'll
open
here
and
these
this
is
just
all
of
the
items
open
with
the
code
quality
label.
It's
interesting
here
to
sort
things
by
popularity.
If
you
want
to
see
what's
upcoming,
you
can
sort
by
milestone
view
date
as
well,
create
a
date.
You
can
find
some
older
things
as
well,
and
it's
really
good
when
you're
thinking
about
quality,
if
you
haven't
done
it
already
just
to
read
through
this
entire
again,
it's
not
so
long,
there's
only
80
items
in
it
that
you
can.
A
There's
a
UX
research
issue
where,
if
you
wanna
do
UX
research
on
any
of
these
topics,
mister
shared
across
verify,
but
you
you
can
request
that
with
the
UX
team
there
and
anybody
who
is
maybe
a
customer
or
user
who
wants
to
see
what
we're
doing
they're
also
able
to
jump
in
there
and
then.
Finally,
in
this
little
intro
section,
we
have
a
public
epic,
which
is
basically
because
our
webpages
don't
have
a
discussion
thread
at
the
bottom.
This
serves
that
purpose.
A
They
aren't
super
highly
used,
but
make
sure
that
you,
like
me,
have
a
notifications
on
on
these.
So
there's
somebody
comments
in
there.
You
get
it.
You
probably
already
knew
based
on
subscribing
to
labels
yeah,
but
maybe
not
actually
cuz
I
see
this
doesn't
have
the
labels
in
it.
Okay,
it's
probably
the
case
and
all
of
them
by
the
way
and
then
and
then
I'll
introduce
the
sections
first
before
we
dive
into
them.
The
what's
next
in
Y
is
of
all
the
things
that
we
might
be
working
on.
A
What
is
the
one
most
important
thing
and
as
a
product
manager,
you
have
several
categories,
so
you
know
you're
going
to
be
spread
out
a
little
bit
and
thinking
about
these
things,
it's
great
if
we
look
a
little
further
ahead
and
have
plans
about
what
we're
going
to
do
over
a
longer
period.
But
the
most
important
thing
you
need
to
do
is
product
manager,
for
every
one
of
your
categories
is
truly
know
what
that
one
most
important
thing
is
that
we
want
to
do
next,
and
the
reason
for
that
is
things
are
gonna
change.
A
You
can
make
plans
and
they
can
inform
your
decision-making.
That's
great,
but
not
picking
the
right
next
thing
to
work
on
based
on
all
the
criteria
that
are
available
to
you
and
you're
sensing
mechanisms
means
you're
off
track
from
the
start,
and
that's
actually
where
we
we
have
this
year
highlighted
so
centrally,
and
then
the
rest
of
these
items
inform
that
so
there's
a
maturity
plan.
All
of
our
categories
have
a
maturity
level
and
they
all
then
next
maturity
level
that
they
can
achieve.
A
We
always
try
to
keep
the
plan
here
about
what
the
items
that
we
think
are
in
the
backlog
that
are
going
to
bring
us
to
that
next
level
of
maturity
and
there's
some
definition
to
maturity.
Here
it's
important
to
be
thinking
about
the
competitive
landscape
and
what
what
competitors
are
doing
in
this
space
and
the
customer
success
and
sales
teams
counsel
be
a
source
of
inspiration.
A
Customers
directly
internal
customer
is
also
very
important,
as
we
prioritize
dogfooding
and
in
the
top
vision
item
is
the
one
that
really
is
owned
by
you
as
the
product
manager.
It
can
be
something
that
customers
maybe
aren't
thinking
about.
Yet
it
can
be
something
that's
going
to
be
a
foundation
for
what
you
build
on
in
the
future,
but
it's
something
that's
really
coming
from
you
as
a
product
manager.
Sometimes
there's
duplicates
between
these
sections
and
that
can
be
totally
normal,
especially
for
a
planned
category.
A
A
B
How
would
you
differentiate
between
the
items
of
the
maturity
plan
and
the
items
in
the
vision?
It
seems
to
me
like
there's
some
duplication
or
overlap
between
those
those
two
areas,
so
yeah
assume
that
they're
both
there
for
a
reason,
but
would
love
a
deeper
dive
on
why
they're
both
there
how
they
differ
yeah.
A
A
You
know
pragmatic
thing
to
get
divided
by
actually
know
that
I'm
kind
of
talking
this
out,
though
I
think
that
maybe
this
one
supporting
Microsoft
is
really
part
of
being
viable,
but
you,
as
a
product
manager,
can
kind
of
think
that
through
and
make
that
decision
it
can
be
in
both.
But
I
think
that
this
is
clearly
a
vision
item.
That's
kind
of
like
how
your
future
for
the
for
the
category
that
isn't
part
of
the
next
steps
of
getting
just
getting
this
thing
Bible
so
that
guitars.
A
A
A
A
Backstage
means
that
the
engineering
team
is
driving
some
change,
but
it's
not
something
that
a
customer
is
going
to
see.
Okay,
so
it's
important
for
refactoring
or
for
how
something
is
implemented
or
maybe
reliability
or
performance.
It
could
be
a
lot
of
different
things,
but
it's
not
a
customer
facing
future
okay
cool
thanks.
A
Like
it's
actually
looks
like
the
secure
team
is
implementing
it,
so
maybe
it's
something
that
they're
implementing,
so
they
can
build
some
other
feature
on
top
of
it.
I'm
actually
not
super
familiar
with
what
it
is,
but
the
next
thing
that
looks
like
we're
doing
four
code
quality
are
these
two,
which
are
scheduled
for
the
same
release,
supporting
down
net
code
coverage
results
and
the
CIB
for
code
quality,
which
are
both
alumni
maturity
plan?
Oh
and
this
one
as
well,
which
I
think
is
also
on
the
maturity
plane.
A
So
it
looks
like
the
plan
is
in
12s
I've
been
to
do
everything,
that's
on
the
majority
plan
and
one
reason
which
is
maybe
realistic.
Maybe
not,
but
that's
that's
the
current
plan.
So
then
I
think
what
we
would
say
coming
back
here
what's
next
and
why
is
actually
focusing
on
maturity?
Make
sure
that
you
really
look
some
of
these
may
be
sitting
in
12
s
11,
just
because
they
were
kind
of
like
moved
out
to
a
future
release
evaluated
later.
A
But
if
those
were
to
stay,
then,
then,
what's
next
and
why
is
in
12s,
7
or
in
are
in
the
next
release,
where
we
touch
code
quality,
we're
going
to
be
bringing
up
category
to
the
next
maturity
level
by
delivering
these
three
things,
and
then
we've
explained
what
we're
doing
and
why
we're
doing
it.
I.
B
B
A
A
So
good
question
I:
don't
there
isn't
an
answer
for
it?
It's
just
probably
an
oversight.
So
the
solution
is
that
either
some
of
those
will
get
pulled
out
of
12.7,
which
would
actually
be
here
and
actually
will
be
here.
That's
the
last
really
it's
this
fiscal
year
and
then
this
has
been
accurate
or
those
will
stay.
And
then
we
should
update
the
categories
that
yamo
to
note
that
on
january
22nd
we
will
have
bumped
code
quality
up.
A
I
think
what
had
happened
is
that
at
one
point
we
had
too
many
categories
that
were
bumping
up
maturity
in
v4
because,
like
everything
for
the
year
that
didn't
make,
it
was
slowly
getting
moved
forward
and
it
was
just
there
was
no
way
we
were
gonna
do
all
of
it
in
q4.
So
we
did
a
exercise
where
we
scaled
that
back
and
I
probably
just
forgot
to
then
unschedule
some
of
the
items
that
were
in
12s
7.
Ok,
because
I
knew
you
were
starting
and
you
would
think
it
would
be
wonderful
for
me.
A
B
A
B
Legit
customer
feedback
through
customer
inner
use
and
some
actual
quantitative
numbers
of
how
people
are
using
the
feature.
So
we
have
better
road
map
into
based
on
where
we
want
to
go
vision
wise.
What
are
the
actual,
pragmatic
things
to
do
so?
Yeah
I'll
pull
those
items
out
at
12
7
and
then
we
groom
them
with
those
thoughts
in
mind
in
couple
of
releases,
I
think
yeah.
A
A
A
A
A
Even
if
you
have
no
more
requests
open,
you
can
see
the
code
quality
on
your
master
branch
yeah,
and
so
that's
a
just
nice
basic
feature
that
will
help
bring
in
this
the
Bible
a
see
IBEW
for
code
quality
is
a
similar
view.
It
doesn't
make
me
have
any
markups
in
here
yet
so
you'll
want
to
work
with
me
or
somebody
else.
If
you're
gonna
keep
the
schedule
for
told
us,
I
mean
to
show
a
CI
specific
view,
that's
again
not
related
to
the
disc
but
related
to
the
current
quality
of
the
code.
A
So
this
is
about
showing
how
you're
going
to
change
code
quality
in
the
dip,
which
will
be
pretty
cool.
So
here
there
is
a
screenshot
in
this
one.
So
it's
saying
on
this
line,
your
code
quality
does
not
pass
go
fund,
which
is
like
the
analyzer
for
the
formatter
forego,
and
you
can
see
it
right
there
in
line
in
the
diff,
which
is
pretty
cool
another
one
here.
B
B
A
For
sure,
showing
it
first
and
then
blocking
on,
it
is
way
to
do
that,
but
yeah
and
then
there's
again
some
question
when
you're
familiar
with
the
backlog.
It's
not
necessarily
true
that
these
really
are
the
most
important
things
to
bring
the
category
up
to
maturity
slate.
You
have
to
think
about
that
and
talk
to
customers
in
order
to
come
up
with
your
own.
Maybe
this
is.
A
As
you,
we
have
a
competitive
analysis
as
well
for
as
your
DevOps,
it
last
analysis
you
drove
this.
They
have
a
lot
of
different
plugins
that
you
can,
you
can
get,
but
they
don't
offer
it
built-in
and
the
way
that
we
do.
But,
of
course
we
don't
know
forgotten
so
for
as
your
DevOps,
then
that's
that's
not
great,
but
we
we
talked
about
that
here.
A
A
Yeah
and
then
this
issue,
so
it's
a
perp,
so
this
is
kind
of
like
that
master
one.
No,
this
is
the
master
one.
So
maybe
this
issue
needs
a
little
bit
of
grooming
as
well.
I
think
that
we've
discussed
not
just
showing
the
quality
on
master,
but
on
any
branch
that
you
have,
which
is
what
actually
is
referred
to
here.
So
it's
described
here
as
a
per
branch
view
for
how
cool
quality
progresses
over
time,
but
the
issue
description
is
saying
master,
and
so
that's
something
to
tie
up.
B
A
B
A
A
A
A
This
one
customer
success,
if
you
showing
instance,
wide
code
statistics,
I,
think
that
actually,
this
probably
needs
to
move
to
a
different
category
now
I
think
we
have
like
ace.
We
have
a
category.
That's
like
about
this
sort
of
thing.
I
came
here
with
all
right
now,
embarrassingly,
no
but
yeah
I
think
that
this
actually
belongs
somewhere
else.
I
think
you
might
be
part
of
the
create,
but
I'm
not
sure.
Okay,.
A
Yeah
just
ask
if
they're
familiar,
if
they're
working
on
something
like
that,
but
you
can
see
how
it's
actually
pretty
close
to
code
quality.
It's
exactly
quality.
What
sort
of
statistics
that
come
out
of
code
quality
but
I
think
that
for
you,
the
you
know,
seeing
code
quality
over
time
on
different
branches
is
really
your
metric.
That's
more
interesting
and
relevant
to
code
quality
than
just
sort
of
like
general
developer
code
statistics.
A
So
maybe
this
is.
This
is
one
there's
one
to
come
out
and
look
for
a
new
new
customer
success
sales
issue
that
will
drive
engagement,
their
most
popular
item,
yeah
I,
probably
stole
the
most
popular
59
upvotes.
So
this
is
one
that
we
should
be
considering
it's
currently
in
the
backlog,
but
maybe
maybe
worth
doing
senior
compare
em
our
code
coverage
to
target
branch?
Okay.
So
this
yet
another
one!
That's
talking
about
relative
code
quality
and
how
you're
changing
code
quality
over
time,
but
yeah.
A
B
A
If
you
do
find
duplicate
issues
always
keep
the
hype
more
highly
uploaded
one
don't
mark
the
highly
uploaded
one
as
a
duplicate
of
a
low
uploaded
one.
They
may
have
changed
this
there's
a
feature
request
for
it,
but
I
don't
think
that
they
have
implemented
yet
where
uploads
from
a
duplicate
issue
are
not
transferred
to
the
new
issue,
which
is
unfortunate.
A
B
A
Again,
I'll
talk
about
the
same
thing
is
what
people
want.
It's
it's
the
case
for
mrs
for
sorry
for
categories
who
are
sort
of
at
the
minimal
level
in
getting
two
viable,
like
everybody
mostly
wants
almost
the
same
things
in
order
to
get
it
to
be
usable
and
then
moving
the
vision
forward,
again
same
issue
and
then
providing
that
net
support
which
we
covered
in
the
you
know
competitive
analysis
as
well
also
really
really
important
for
the
company
we're
trying
to
do
better
by
our
windows,
customers
we're
adding
Windows
runner-up
support,
we're
doing
more.
A
You
know
the
powershell
executor,
we're
doing
a
lot
around,
making
sure
that
everything
works
great
for
Windows
user
and
so
prioritizing
that
stuff
is
important.
Tim
is
also
prioritizing
things
around
the
NuGet
package
package
manager,
which
is
something
that
Windows
users
are
using.
So
all
of
that
helps
helps
tell
our
multi-platform
story,
which
is
one
of
the
themes
in
the
CI
CD
strategy:
okay,
yep
and
that's
it
so.
B
A
That
well
it's
if
all
of
these
are
kind
of
like
your
next
things
or
each
of
the
topics
so
for
the
maturity
plan.
The
next
thing
to
do
is
bring
us
a
viable.
So
it's
we
may
not
do
that
for
two
years,
but
it
is
the
next
thing
for
bringing
the
category
five.
The
top
vision
item
is
your
next
vision
item.
We
may
not
do
it
for
two
years,
but
it's
unlikely,
but
but
it's
still
your
top
next
vision.
A
A
I
don't
know:
Tim,
hey
is
working
on
improving
the
dashboards
per
category,
and
so,
if
you
were
able
to
send
him
some
page
view
metrics
those
will
start
to
be
collected
and
then
those
will
come
in
a
new
dashboard.
Okay,
there
is
a
there
is
a
dashboard
already
I
think
that
Brendan
made
for
verify
that
has
some
metrics
in
it.
Okay,.
B
A
B
B
A
And
we
can,
we
can
check
in
on
any
of
those
anytime
as
well.
If
you
want
also
feel
free
to
schedule
another
maybe
hour,
and
we
can
try
and
knock
out
as
many
of
the
other
categories
as
you
have,
because
there'll
be
a
little
bit
less
repeating
in
some
of
the
mark,
also
very
short,
yeah
and
then
yeah.
You
can
start
thinking
about
relative
prioritization.
Once
all
these
things
to
you,
because
that's
that's
an
interesting
aspect.
Yeah.