►
From YouTube: Understand the general authoring experience
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
Hi
everyone
in
this
research
we've
tried
to
understand
the
general
authoring
experience
for
our
users.
We've
done
that
mainly
because
we
are
working
on
creating
a
dedicated,
ci
cd
home
and
we
are
bringing
all
the
available
authoring
features
under
the
same
roof
and
we
want
to
better
understand
what
is
the
current
experience
for
the
existing
users.
A
A
Now,
because
it's
the
topic
of
this
research
is
to
understand
the
general
experience
we
didn't
do
like
a
deep
dive
into
each
step,
although
each
step
does
deserve
its
own
research,
and
this
is
definitely
something
I
plan
to
do,
and
but
still
we
wanted
to
understand
the
big
picture.
A
Now,
let's
jump
into
the
inside
of
this
research
yeah,
I
think
one
inside
which
is
key
to
understand
is
that
in
this
research
we
wanted
to
talk
to
the
people
that
actually
ride
the
pipeline,
but
on
the
way
we
learn
just
there
are
those
organizations
when
there
is
a
devops
or
developer
that
is
in
charge
on
writing
the
code
and
then
building
the
pipeline
and
deploy
the
application
to
production
and
then
monitor
it.
But
then
again,
there
are
organizations
that
have
a
division.
A
That
is
like
a
central
theme
that
provide
the
guidelines
on
how
to
write
pipeline,
create
and
maintain
the
template.
Sometimes
they
even
run
the
actual
template
the
lecture
pipeline,
and
there
are
different
business
units
in
the
organization
that
devops
and
engineers
are
in
charge
on
writing
the
pipeline.
Sometimes
they
run
the
pipeline.
Sometimes
they
write
the
pipeline
and
then
submit
it
to
the
central
team
and
the
central
team
do
the
actual
running
of
the
pipeline.
A
Now
it's
it's
important
to
understand
the
relationship
between
those
two
personas
because
well,
first
of
all,
those
our
our
assumption
is
that
the
this
division
happens
normally
on
our
large
account
and
large
enterprise.
We
did
saw
it
in
some
of
our
accounts
and
we
do
have
a
dedicated
research
to
understand
the
job,
to
be
to
be
done
by
the
by
the
enterprise
users,
but
still
understanding
this
division
and
understanding.
The
relationship
is
important
because
those
two
personas
has
different
needs
and
different
requirements.
A
So
when
we
come
to
talk
to
our
users,
it's
important
to
first
identify
if
there
is
such
a
division
in
the
organization
and
if
it
is
who
am
I
talking
to?
Am
I
talking
to
the
central
team?
Can
I
talk
to
the
devops
and
the
engineers
maybe
create
a
separate
set
of
questions
for
both
teams?
Definitely
something
we
are
going
to
follow
up
in
the
coming
interviews
and
research.
A
The
next
one
is
the
user
they
like
to
ride
their
pipeline,
especially
when
they
start
writing
the
pipeline
in
a
dedicated
code,
editor
like
vs
code
and
more-
and
I
think
one
insights
that
we
can
so
one
thing
that
we
can
take
into
account
and
improve
is
improve
the
authoring
experience
for
those
users.
So
we
can
definitely
when
we
are
building
some
of
our
features
like
a
syntax,
highlighting
validation,
autocomplete.
We
can
definitely
think
about
those
users
and
maybe
maintain
an
external
schema
that
we
can
use
by
gitlab
and
can
be
used
by
other
code.
A
A
A
And
when
writing
pipelines,
user
user
users
normally
update
multiple
files,
we
didn't
have
a
single
user
that
says
that
they
are
updating
a
single
file.
It
was
like
a
minimum
of
two
files
up
to
even
10.
something
we
need
to
think
about
when
we
are
designing
our
authoring
experience
and
although
there
are
like
multiple
files
and
multiple
dependencies,
users
still
prefer
to
have
their
pipeline
written
in
a
single
file
and
like
sometimes
they
have
to
use
multiple
file.
But
their
personal
preferences
is
to
have
like
a
single
file,
and
this
is
definitely
something
we
can.
A
We
can
act
on
and
maybe-
and
we
do
have
an
issue
for
that,
and
maybe
something
we
can
think
about
how
to
let
how
to
make
sure
our
users
will
be
able
to
at
least
view
some
sort
of
a
merged
version
of
our
pipeline
of
our
pipeline
files.
Yeah.
Those
were
the
main
highlights
and,
of
course
you
can
go
over
the
research
and
read
all
of
that,
and
if
you
have
any
other
questions,
please
let
me
know
thanks
and
bye,.