►
From YouTube: UX Showcase – Code Search
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
So
I
assume
that
most
of
you
are
familiar
with
where
you
can
go
to
do
a
code
search
in
gitlab,
but
for
those
of
you
who
aren't
when
using
the
search
within
our
top
nav
bar,
which
is
in
that
first
image
here
at
the
top,
and
you
perform
your
search,
you'll
notice.
That
code
is
one
of
the
first
tabs
available
on
arriving
at
the
global
search
results.
Page
seen
down
here
from
here,
users
can
search
through
a
specific
project
or
group
to
find
code
results
within
those
specified
repositories.
A
We
also
know
that
the
experience
of
searching
for
code
could
be
better.
We
have
various
issues
that
have
both
been
created.
You
know
internally
through
dog
fooding.
You
know,
as
well
as
from
our
customers
regarding
areas
where
we
are
currently
not
meeting
expectations
as
well
as
in
addition,
you
know
there
are
capabilities
that
we're
aware
of
that.
A
Are
you
know
needed
as
well
as
offered
by
some
of
our
competitors,
that
we
haven't
quite
yet
made
available
to
our
users,
and
so
knowing
that
we
want
to
put
a
focus
on
code
search
here
in
the
future,
I'm
wanting
to
ensure
that
we're
solving
our
users
most
immediate
needs.
First,
we
decided
to
start
with
some
research,
and
this
will
really
help
us
in
identifying.
You
know
where
we
can
add
the
most
value
and
impact
for
our
customers.
First.
A
So,
for
example,
you
know
what
are
some
of
the
reasons
they're
choosing
to
search
in
gitlab
versus
like
their
local
ide
or
vice
versa,
and
you
know
once
they
find
the
code
they're
looking
for
you
know
what
are
they
typically
doing
next,
the
answer
to
these
types
of
questions
really
will
help
us
to
identify
ways
in
which
we
can
solve
some
of
the
current
problems
they're
facing
what
the
jobs
are
trying
to
do,
as
well
as
get
them
to
the
information
that
they're
looking
for
a
bit
quicker.
A
Secondly,
we
wanted
to
identify.
You
know
what
information
is
most
important
to
users
within
the
results
of
a
search.
This
way
we
can
ensure
to
prioritize
that
information.
We
display
in
the
results,
as
well
as
make
sure
any
additional
information
that
we
begin
to
add
in
is
actually
valuable
and
validated
with
our
users.
A
A
So
you
know
today
we
offer
a
few
options
for
filtering
code
results
and
it's
not
really
very
discoverable
to
users
as
through
syntax
within
the
search
field.
So
we
needed
to
understand
you
know
not
only
what
types
of
things
that
they
were
wanting
to
be
able
to
filter
by
you
know,
but
also
how
they'd
want
to
be
able
to
do
that
or
expect
to
do
that.
A
So,
although
the
majority
of
these
sessions
focus,
you
know
primarily
on
problem
validation,
there
was
a
portion
towards
the
end
of
each
session.
That
was,
you
know,
a
bit
more
evaluative
in
nature,
where
we
gather
some
feedback
on
the
current
experience
as
well.
A
So
through
these
sessions
we
gathered
a
large
wealth
of
insights
for
us
to
address,
and
the
question
really
was
you
know.
Where
do
we
begin
and
so
to
determine
this?
I
went
through
and
I
set
up
a
prioritization
activity
with
the
global
search
team.
A
We
were
able
to
schedule
the
first
portion
of
this
activity
as
a
synchronous
session,
with
the
ability
for
asynchronous
collaboration
following
that
and
to
set
up
the
stage
for
this
activity.
I
first
created
a
2x2
matrix
with
the
x-axis
representing
user
value
and
the
y-axis
representing
the
level
effort.
A
I
then
worked
with
my
pm
john
mcguire
to
stack
rank
those
insights
along
the
x
asset
axis,
based
off
of
what
we
heard
from
users
trying
to
research
as
well
as
additional
feedback.
We
had
heard
from
other
customer
conversations,
and
this
ranking
you
know
could
of
course
be
adjusted
once
we
brought
in
the
entire
team,
but
it
was
a
good
starting
point
for
us
to
begin.
A
We
then
got
together
with
the
whole
team
to
review
the
insights,
and
you
know,
although
they
already
had
access
to
dovetail
and
the
recordings
and
the
insights
this
gave
us
the
chance
to
discuss
it
all
together
as
a
team
as
well
as
you
know,
build
empathy
together
for
the
problems
that
our
users
are
facing.
A
Additionally,
we
worked
with
the
engineering
team
to
move
those
insights.
You
know
up
or
down
along
the
y-axis,
based
on
general
expectations
regarding
level
of
effort
for
development,
since
concrete
solutions
were
not
yet
really
in
place,
and
this
was
more
of
a
rough
estimation
for
us
to
use
it
also,
you
know,
allowed
us
to
discuss
various
options
that
would
have
large
impacts
on
feasibility
or
effort.
A
And
after
going
through
most
of
the
insights
during
our
session,
we
were
able
to
complete
any
that
were
left
over
asynchronously
and
made
sure
to
capture
any
important
details
within
the
issues
in
gitlab
and
really
the
results
of
this
activity
just
helped
us
to
determine.
You
know
where
to
best
start
in
addressing
these
insights.
A
A
First,
the
items
in
the
bottom
right
corner
are
also
really
high
value,
though
they
require
a
significant
amount
of
effort
to
complete,
and
so
these
are
items
that
we'll
want
to
start
thinking
about
and
preparing
for,
as
well
as
breaking
those
down
into
maybe
some
smaller
interim
chunks
for
us
to
complete
moving
to
the
top
left
quadrant.
A
These
issues,
or
these
insights
are
ones
that
have
less
user
value
and
also
take
up.
You
know
maybe
a
little
bit
less
level
effort
as
well,
so
they
won't
be
prioritized.
Quite
as
early
unless
they're
more
towards
the
right
of
that
quadrant.
A
A
One
thing
that
we're
playing
in
the
future
for
more
work
like
this
is
we're
going
to
make
it
even
more
so
asynchronous
as
it
can
oftentimes
be
difficult
to
ensure.
You
know
that
everyone's
able
to
make
it
to
these
synchronous
meetings,
as
well
as
have
their
voice
heard
with
the
time
differences
that
we
oftentimes
have.
A
A
So
you
know
when
talking
with
users
during
the
sessions
around
use
cases
for
code
search,
they
often
mentioned
how
they
were
looking
to
find
additional
details
around.
You
know
when
the
code
they
were
searching
for
was
last
updated
and
other
details
such
as
like
who
made
the
change.
A
In
addition
to
these
items,
we're
also
preparing
and
breaking
down
some
larger
efforts,
these
items
either
require
a
significant
change
to
how
we
index
code
today,
or
they
require
additions
to
what
we
currently
index
and
store.
A
So,
what's
next
we're
going
to
be
continuing
to
move
forward
with
the
code
search
insights,
mainly
based
off
of
that
prior
prioritization
activity
that
I
just
showed
you
we've
also
gained
some
additional
front-end
help
to
assist
us
in
implementing
some
improvements
to
the
top
navbar
search
field,
as
well
as
updates
to
the
projects
and
group
filters
on
the
global
search
results
page
really
to
make
locating
projects
and
groups
within
those
drop-downs
a
lot
easier,
because
there's
often
issues
today
with
actually
finding
specific
projects
or
even
groups
today,
within
those
dropdowns.