►
From YouTube: Beyond Code Live: Session 2
Description
Beyond Code Live is an inclusive event series that amplifies the voices of women at GitLab to inspire success for the wider DevOps community. GitLab team members will showcase their favorite platform “hacks” for managing routine responsibilities outside of programming in each session.
Session 2 speakers included:
Host: John Coglan & Jamie Rachel - Community Relations
"GitLab as a Personal Notebook" by Laura Duggan, @LDuggan - Digital Design
"Designing for Developer Experience" by Veethika Mishra, @VMishhra- UX
"GitLab as a time efficiency tool" Carol Teskey, @CTeskey - People Success
A
A
Okay,
so
again,
welcome
to
beyond
code
today
is
june
17th,
and
this
is
our
second
session
and
you'll
be
hearing
about
some
amazing
hacks
from
some
team
members
of
ours
at
get
lab.
My
name
is
jamie
rochelle
and
I'm
the
evangelism
program
manager
here
at
get
lab
in
the
community
relations
department.
A
B
All
right,
I'm
john,
I'm
also
on
the
community
team
at
get
lab.
I
work
with
jamie.
I
love
meetups.
I
have
been
going
to
get
lab
meetups
since
I
joined
the
company
three
years
ago
and
they're
always
so
much
fun.
I
love
hanging
out
with
all
the
community
members.
So
thank
you
everybody
for
being
here
today
and
my
favorite
movie
is
top
gun
and
I
love
the
music.
I
love
the
airplanes.
B
I
love
all
the
comedy
and
yeah
just
great
nostalgia
in
that
movie.
So
yeah
that
that's
my
my
favorite
movie
awesome
are
we
gonna?
Have
everyone
else
do
intros
now
or
we'll
do
that
before
the
the
talks
begin.
A
At
each
talk,
each
speaker
will
be
able
to
introduce
themselves
and
share
their
favorite
movie
as
well.
So
john,
do
you
want
to
share
about
a
little
bit
about
gitlab
and
what
the.
B
So
we
know
that
this,
you
know
kind
of
meetups
tend
to
attract
people
that
are
new
to
gitlab.
They
can
get,
they
get
live
community,
so
I
just
wanted
to
spend
a
few
minutes
introducing
gitlab
for
folks.
That
may
not
know
much
about
us.
So
gitlab
is
an
open
source
devops
platform.
B
So
you
can
do
everything
from
you
know,
manage
and
plan
the
products
that
you
want
to
build
to
kind
of
monitor
and
make
sure
that
they're
secure.
We
have
ten
stages
of
the
devops
devops
lifecycle
that
we
cover
that
are
listed
in
the
top
row.
There
manage
plan,
create
verify
package,
secure,
release,
configure,
monitor
and
protect.
So
anything
that
you
need
to
do
to
you
know
like
in
your
devops
kind
of
life
cycle
get
lab
covers
we're
open
source,
we're
extremely
transparent,
so
you
can
find
our
company
handbook
online.
B
You
can
watch
recordings
of
team
meetings
on
our
gitlab
on
filter
channel
on
youtube.
You
can
go
to
our
public
issue
tracker
and
follow
all
the
work.
That's
in
progress
on
our
product
and
you
know,
comment
and
engage
with
our.
You
know:
product
and
engineering
teams.
Even
our
people
obscene,
like
uses
public
issues,
and
we
have
carol
from
people
ops
here,
which
is
why
I'm
giving
them
a
shout
and
yeah
it's
like
it's
a
really
cool
place
to
be
it's
a
great
product.
B
We
have
an
amazing
community
with
thousands
of
contributors
who
have
contributed
to
gitlab
whether
it's
code,
documentation
translations,
organizing
meetups,
doing
talks
about
gitlab
speaking
at
meetups.
Speaking
at
our
big
commit
event,
so
really
a
cool
community
to
be
part
of,
and
we
hope
that
you'll
all
continue
to
stay
engaged
with
git
lab
after
today.
A
Thank
you,
john.
So
I'm
going
to
give
a
quick
little
overview.
I'm
not
going
to
read
this
all
to
you,
but
just
what
beyond
code
is
and
where
it
came
from
a
teammate
of
mine,
nerdsy
came
to
me
when
I
first
started
back
in
february
and
said
that
she
wanted
to
engage
and
inspire
women
to
speak
more
and
also
share
different
hacks
and
ways.
We
use
the
platform
outside
of
just
coding.
So
we,
you
know,
brought
our
two
brains
together
and
we
birthed
this
event
called
beyond
code.
A
So
this
is
a
way
to
highlight
all
the
different
ways
to
use
git
lab
outside
of
coding
and
also
highlight
our
women
teammates
as
well.
A
So
today's
overview
we
just
went
over
what
is
beyond
code
and
now
we're
going
to
start
kicking
it
off
and
share.
Some
of
these
amazing
hacks
after
the
hacks
are
shared,
we're
going
to
do
interactive
activity
trivia
and
give
more
information
on
how
to
get
involved
with
gitlab
and
some
upcoming
events
that
we
have
in
conferences
as
well.
C
Sure
so
my
name
is
laura
duggan.
I
will
start
with
my
favorite
movie
as
a
little
icebreaker.
I
would
have
to
say
that
it
is
little
women.
I
know
there
are
a
few
versions
floating
around,
but
the
new
one,
the
greta
gerwig
version,
it's
good
for
like
a
solid
cry.
You
know
it's
a
good
one
and
so
for
my
hack
today,
I'm
going
to
talk
about
how
I
use
gitlab
as
a
personal
notebook.
C
I
am
an
engineer
on
the
digital
experience
team,
but,
prior
to
that
I
was
a
designer,
a
ux
and
graphic
designer,
so
I
wasn't
super
familiar
with
git
or
gitlab
prior
to
being
an
engineer,
and
so,
if
you
want
to
go
to
the
next
slide,
I
will
chat
a
little
bit
about
what
git
is.
First
of
all,
so
it's
a
version
control
software,
so
it
allows
a
lot
of
people.
C
Hundreds
thousands
of
people
to
work
on
the
same
project
at
the
same
time
make
changes
and
it
get
keeps
track
of
which
is
the
newest
version,
the
source
of
truth
and
merges
everyone's
changes
in
so
that
the
latest
version
is
what's
on
the
main
branch
we
use.
This
this
idea
of
branching
so,
prior
to
being
an
engineer,
I
didn't
use
git.
I
was
not
familiar
with
it
at
all,
so
on
the
next
slide
here
I
have
the
challenge
that
I
was
facing.
C
Is
I
wanted
to
get
more
comfortable
with
git
I
wanted
to.
I
knew
that
kind
of
the
three
common
commands,
but
everything
beyond
that
was
was
foreign
to
me.
So
I
wanted
a
way
to
kind
of
mess
around
with
git.
I
wanted
to
use
it
in
my
own
project
that
I
could
accidentally
delete
things
or
see
what
different
commands
did
and
play
around
with
it.
So
that's
what
I
was
looking
for
was
a
way
to
get
comfortable
with
git
and
in
the
next
slide.
I
have
an
opportunity
that
I
you
know
starting
at
gitlab.
C
I
wanted
just
a
quick
place
that
I
could
throw
you
know,
links
or
videos
that
I
wanted
to
watch
later,
a
virtual
notebook
if
you
will-
and
so
I
thought
you
know
this
is
this-
is
a
perfect
opportunity.
I
want
to
keep
track
of.
What's
going
on
in
my
day-to-day,
I
usually
write
down
a
physical
to-do
list
every
morning,
but
why
not
use
gitlab
for
this
this
project
and
have
a
way
to
kind
of
learn
git
at
the
same
time,
so
the
next
slide
yeah
the
hack.
C
I
decided
to
make
a
personal
virtual
notebook
using
gitlab
so
stored
on
gitlab
and
be
able
to
have
all
of
this
accessible
on
gitlab
and
be
able
to
own
something
and
mess
around
with
git
commands
and
not
be
afraid
that
I'm
gonna,
you
know
bring
down
gitlab.com.
C
You
know
so
yeah
this
I'll
go
a
little
bit
into
the.
I
guess
the
points
of
my
hack.
First
of
all,
I
started
by
creating
a
blank
project.
You
can
do
this
right
in
gitlab
in
the
interface
there's
a
project
drop
down
and
you
can
go
right
in
there
and
create
a
blank
project
and
you'll
see
on
this
slide.
There
is
a
section
where
you
can
choose
a
public
project
or
a
private
project
that
only
you
can
see
for
my
purposes.
I
chose
a
public
project.
C
I
I
didn't
have
anything
really
that
needed
to
be
hidden
or
needed
to
be
confidential
and
in
case
anyone
else
wanted
to
kind
of
use.
This
idea
it's
available
for
the
whole
world
to
see
so
yeah
created
the
blank
project
and
then
next
I
added
and
edited
some
files.
So
you
can
also
do
this
right.
Gitlab,
there's
just
a
big,
add
file
button
and
you
can
go
in
there
and
you
just
write
content.
So
you
can
kind
of
see
here
that
I
have
goals,
meetings
and
work
that
came
up
every
single
day.
C
I'll
put
these
three.
This
is
kind
of
my
template
that
I
use
every
single
day
and
for
me
I
use
a
new
one
of
these
templates
every
day,
so
I
have
like
june
1st,
2nd
3rd
4th,
5th,
etc,
and
you
can
edit
this
directly
in
gitlab,
there's
a
big
button
there
that
says
edit
or
use
the
web
ide
and
it's
just
markdown.
So
it's
pretty
simple,
very
readable
for
you
to
just
write
directly
in
gitlab
and
then
this
gets.
C
I
know
this
is
called
beyondcode,
but
if
you
wanted
to,
you
could
clone
this
project,
which
means
that
you
clone
a
copy
of
it
to
your
computer
and
you
do
everything
locally
on
your
machine
and
then
push
it
up
to
gitlab.
This
allows
you
to
make
large
edits.
You
don't
have
to
commit
as
frequently
by
just
cloning
it
on
your
computer
and
at
the
end
of
the
day
you
toss
back
up
to
gitlab
and
they
store
it
for
you.
C
So
this
allows
me
to
play
with
those
git
commands
like
I
was
saying
and
delete
things
and
try
things
and
rebase
things.
There's
all
these
different
commands
that
that
are
available
in
git,
and
I
can
do
that
all
from
my
machine
and
and
have
it
have
a
version
of
it
stored
on
my
machine
and
then
you
can
even
go
as
far
as
to
create
a
generator
that
you
know,
write
a
script
and
creates
a
generator
that
builds
your
template
every
single
day.
C
For
you,
as
you
start
your
day,
you
can
get
crazy
with
it,
but
this
is
a
nice
project
that
I
was
able
to
own
and
and
have
on
my
machine
that
I
wasn't
afraid
to
kind
of
mess
around
with
and
lastly,
on
the
next
slide
this,
since
it's
a
public
project
like
I
mentioned
before,
I
can
share
this
link
to
anyone.
C
If
my
manager
is
wondering
what
I'm
up
to
this
day
this
week
or
today,
or
I
have
teammates
that
wonder
how
busy
I
am
or
what
I've
been
working
on,
or
just
for
my
own
kind
of
personal
checklist
kind
of
see
how
productive
I've
been
this
week,
this
link
is
available.
You
can
go
to
this
link
right
now
and
you
can
kind
of
see
what
I'm
what
I'm
planning
on
doing
today.
C
So
I
can
share
this
with
anyone
in
the
world
and
they
can
see
this
public
project
and
see
what
I've
been
doing.
So
that
is
my.
A
Hack,
thank
you
for
that,
and
actually
does
anyone
have
any
questions
for
laura.
B
I
I
have
one
question
laura,
so
I
know
we
have
issue
templates
and
merge
request
templates
in
gitlab,
where
you
can
have
a
template
when
you
know
that
you'll
follow
anytime
you're,
opening
a
new
issue
or
merge
request.
You
alluded
to
using
like
a
generator
to
create
a
new
file.
So
I
guess
is
that
the
most
efficient
way
to
you
know
create
a
new
file,
or
is
there
the
option
to
have
like
a
file
template
or
something
like
that?.
C
There
would
be
the
option
to
create
templates
issue
templates
or
merge
request
templates.
The
reason
I
haven't
is
because
I'm
the
only
one
using
this
this
project,
so
I
can
commit
directly
to
my
main
or
my
master
branch
myself,
because
I
own
it
I'm
the
administrator,
so
I
can
do
it
without
kind
of
getting
requesting
to
merge.
C
I
don't
have
to
ask
anyone
to
to
request
more,
so
I
don't
have
to
use
those
templates,
but
I
could
I
could
set
that
up
so
that
every
time
that
I
wanted
to
create
a
new
file,
it
would
generate
these
the
goals
and
my
to-do's
and
my
meetings.
It
would
create
that
template
for
me
and
then
I
could
just
merge
up
those
changes
so
yeah.
That
is
another
use
case.
Absolutely
that
that
I
could
implement.
B
C
Yeah
I
have
the
template
stored
on
the
readme,
so
on
the
main
file,
and
I
just
copy
and
paste
it.
One
of
my
co-workers
does
have
a
script
that
he
runs
like
generate
day.
He
runs
a
command
in
his
in
his
terminal
and
a
new
day
pops
up
with
all
of
those
pre-filled
sections
that
he
can
go
in
and
edit
it
and
push
it
up
himself.
B
A
D
Yes,
I
am
all
right,
so
hi
everyone,
I'm
vitika,
I'm
senior
product
designer
with
gitlab
and
my
favorite
movie
is
split
away
and
it's
all
because
of
the
illustration
style,
that's
being
used
that
has
been
used
in
that
movie.
D
It
just
takes
me
to
a
different
place,
all
right,
so
the
team
that
I
work
for
is
pipeline
execution
here
and
that
was
previously
known
as
continuous
integration
and
today,
I'd
be
talking
about
designing
for
a
developer
experience
the
challenges
that
I
face
as
a
designer
in
my
day-to-day
work,
and
there
are
hacks
that
I've
discovered
to
overcome
them
all
right.
D
Yeah,
I'd
first
like
to
highlight
certain
aspects
of
a
developer's
day
in
a
life
that
sets
the
ground
for
what
I
would
be
showcasing
later.
So,
first
of
all
this
field,
the
software
development
field,
is
a
very
competitive
one
and
things
move
too
fast,
even
comprehend,
at
a
normal
pace.
There's
a
lot
of
lot
happening
around
and
what's
trending
today
might
just
become
obsolete
tomorrow.
D
Another
one
is,
there's,
hardly
ever
a
clean
slate
in
a
developer's
job,
so,
besides
their
everyday
work,
they
also
have
to
deal
with
a
lot
of
technical
debt
that
has
occurred
over
time
and,
lastly,
there
might
be
help
available,
but
there's
also
a
lot
of
judgment
around
as
to
what
tools
should
be
used
by
your
pro
versus
novice
and
that's
what
we
call
the
real
developer
syndrome.
D
Yeah,
so
here
on
this
screen,
you
would
see
that
I've
added
a
few
images
from
a
twitter
poll
that
I
conducted
a
few
months
back,
where
I
encourage
participants
to
post
a
picture
of
their
screen
setup,
and
this
gives
a
good
insight
into
what
they're
looking
at
when
they're
working.
So
if
it
is
not
raw
code
they're
looking
at
then
it's
mostly
a
complex
dashboard
and
that
with
a
lot
of
information,
but
in
most
cases
it
is
everything
together.
D
D
So
let's
say
you
make
some
code
changes
and
there's
a
chance
that
you
don't
get
to
see
a
feedback
on
whether
or
not
your
changes
are
effective
until
you
actually
go
ahead
and
merge
it
or
you
execute
your
code.
So,
that's
that's
that
doesn't
leave
a
lot
of
room
for
you
to
make
improvements
while
you're
working
on
them,
but
rather
you'll
have
to
follow
the
same
loop
again.
Secondly,
consuming
information
in
an
abstract
state,
so
most
information
comes
in
abstract
form.
D
The
larger
picture
in
is
it's
very
difficult
to
paint
when
you
cannot
put
a
face
to
most
of
the
things
that
you're
looking
at
and
information
is
just
everywhere
and
lastly,
data
is
spread
across
pages,
so
context
is
broken
down
more
than
often
and
the
flow
gets
disrupted,
and
this
eventually
results
in
you
spending
extra
time
working
on
something
that
could
otherwise
be
completed
sooner
next
slide.
Please.
D
So
the
hats,
so
here
are
the
hacks
that
I
have
discovered
over
time
to
be
so
that
I'm
considerate
of
these
challenges
by
designing
now
hack
number
one
says,
provide
concrete
visual
interaction
for
abstract
data.
So
what
I
figured
is
translating
the
crucial
data
into
perceivable
and
accidental
elements
in
the
ui.
It
can
really
save
a
lot
of
time
for
the
users
it
can
allow
them.
D
This
is
something
that
the
pipeline
authoring
team
at
gitlab
is
working
on,
and
I
just
feel
that
this
makes
a
really
great
example
of
how
visually
exposing
the
semantic
relationships
among
different
elements
in
a
block
of
code,
the
block
of
code,
in
this
context,
being
the
yaml
definition
of
the
pipeline
configuration
it
could
help
make
it
easier
to
work
with
as
well
as
it
could
also
help
in
smoother
onboarding
and
beyond
that.
It
also
makes
it
easier
for
non-engineers
to
you
know,
understand.
D
What's
going
on
in
the
pipeline
configuration
because
now
there's
a
visual
to
it,
let's
move
on
to
hack
number
two.
D
If
you
have
ever
worked
with
sorry
played
with
lego
blocks,
then
you
would
have
realized
that
there's
there's
really
less
room
for
you
to
go
wrong
with
those
and
that's
because
how
they're
designed
the
fear
of
breaking
a
build.
It's
real,
so
to
ease
users
of
this
worry
of
breaking
the
code.
The
operations
must
be
made
fail
soft.
So,
rather
than
failing
with
an
error
message,
it
should
be
the
like.
D
What
we
should
do
is
every
interaction
attempt
to
do
something
sensible,
like
the
output
of
your
action,
should
always
result
in
something
sensible,
even
when
you
provide
an
input,
that's
out
of
range
and
a
good
example
that
I
was
able
to
find
that
too
in
the
ci
area.
Was
this
ability
that
we
added
in
13.7
release
to
pre-populate
variables
when
running
a
pipeline
manually?
D
Moving
on
to
hack
number
three,
this
says
provide
immediate
feedback.
It's
nothing
very
different,
something
that's
very
obvious,
but
it's
really
good
to
be
cognizant
of
this,
so
not
being
able
to
see
immediate
feedback
for
your
actions
has
been
like.
It's
really
a
struggle
right
and
this
kind
of
brings
in
an
extra
delay
in
the
process,
as
you
have
to
take
additional
steps
to
validate
whatever
you're
working
on
the
changes
that
you're
working
on
before
you
move
on
to
the
next
step.
D
So
it's
really
important
that
whatever
actions
users
are
performing,
my
siri
has
suddenly
activated
I'm
so
sorry
yeah.
So
it
does
show
you,
like
your
ui,
does,
show
you
a
feedback
right
there,
while
you're
performing
it,
and
this
lets
me
talk
about
my
favorite
feature
in
gitlab,
which
is
the
review
apps.
I'm
very
thankful
for
that.
What
this
does
is
it
provides
an
automatic
live
preview
of
changes
made
in
a
feature
branch
by
spinning
up
a
dynamic
environment
for
your
merch
request.
D
So
you
will
be
able
to
see
how
your
changes
looks
in
reality
on
the
web
page,
while
it's
still
in
the
merge
request
form
with
without
having
to
go
and
merge
it
before,
and
this
really
saves
a
lot
of
time,
because
you
don't
have
to
wait
for
to
see
the
changes
live
on
your
actual
product
and
follow
the
same
loop
of
genius
again.
D
I
want
to
close
this
presentation
on
a
note
like
I
want
to
quote
john
romero
here
this
is.
You
might
not
think
that
programmers
are
artists,
but
programming
is
an
extremely
creative
profession.
It's
logic
based
creativity
and
with
the
work
that
we
are
doing
here
at
gitlab.
We
just
want
to
make
sure
that
we
provide
our
users
the
time
and
space
to
bring
in
their
creativity
and
their
work.
Thank
you.
A
Thank
you.
That
was
awesome,
definitely
some
stuff
that
I
just
heard
for
the
first
time,
especially
the
review
apps.
Anybody
have
any
other
questions
or
want
the
code
to
explain
something
else
in
great
detail.
E
E
So
I'm
a
product
designer
leading
design
in
a
small
stealth
mode,
startup
in
observability
space.
So
I
have
seen,
though,
as
a
designer,
I
really
find
it
difficult
to
understand
the
nuances
of
the
devops
environment,
and
so
so,
how
do
you
as
a
designer
bridge,
the
gap
between
understanding
the
domain
and
translating
that
into.
D
Design
could
you
repeat
the
last
particular
question
again.
E
Yeah,
so
I'm
so,
even
though
I
am
a
computer
scientist,
okay,
so
how
do
you,
how
do
you
bridge
the
gap
between
understanding
the
complex
domain
that
can
be
developed
or
something
else,
and
how
do
you
translate
that
complexity
into
this.
D
So
over
the
years
I've
worked
on
many
complex
areas.
Even
before
gitlab
I
was
working
on
a
very
technical
product.
So
what
I
really
do
is
I'm
a
visual
thinker.
I
always
like
visualize
something
when
I
read
about
it
and
here
at
gitlab.
I've
been
doing
one
thing
very
consistently:
is
writing
blogs
about
very
complex
topics
and
also
kind
of
putting
drawings
about
them
there?
So,
like?
D
I,
it's
a
good
way
for
me
to
understand
that,
if
my,
how
I'm
interpreting
concept
is
right
or
not,
because
the
blog
posts
they
go
through
an
mr
here
and
that's
where
I
kind
of
solicit
reviews
from
engineers
and
they
really
help
me
to
get
all
the
pieces
in
the
right
places
and
finally,
it
is
produced
as
a
blog
post,
where,
like
all
the
information,
it's
it's
really
in
place
and
it
has
been
working
out
pretty
well
for
me,
but
I
do
take
a
lot
of
trainings
even
on
like
on
linkedin
on
other
platforms,
but
just
that
I
don't
get
get
into
the
extreme
complexity
of
any
concept.
F
A
D
So
what
we
do
is
it
kind
of
it's
a
range
of
problem
and,
like
it's
a
range
that
we
look
at,
because
it
totally
depends
that
the
feature
the
category,
the
state
group
that
we're
working
on
what
stage
is
it
in?
If
it's
something
that's
very
mature,
which,
in
the
case
of
ci
it
is
then
it's
mostly
like
we
often
have
to
work
on
things
just
to
keep
things
stable
while
working
on
new
features
and
we
do
indulge
in
a
lot
of
research
activities
every
quarter
or
every
milestone.
A
Thank
you
and
thank
you
laura
for
adding
some
of
those
links
and
things
for
us
in
the
chat
as
well.
Take
a
quick
reminder
that
we
do
have
a
running
dock,
that
if
there
are
any
additional
questions
that
come
up
throughout
the
other
talks
that
you
could
just
drop
them
here
and
I'm
adding
it
to
the
chat
right
now
and
we
could
go
ahead
and
move
on
to
our
next
hack
of
the
day.
G
Great,
thank
you
hi
everybody.
My
name
is
carol
teske,
I'm
based
in
dublin
in
ireland
and
I'm
about
two
and
a
half
years
here
in
get
club
at
this
stage
and
prior
to
joining
gitlab
I'd,
never
use
get,
never
used,
gitlab,
so
definitely
a
big
learning
curve.
G
For
me,
when
I,
when
I
joined,
I
currently
lead
the
people
success
group
and,
as
john
mentioned
at
the
beginning
from
a
people
group
perspective,
we
also
use
issues
and
try
to
be
as
transparent
as
possible,
so
the
people
success
group
is
learning
and
development,
diversity
and
inclusion
and
belonging
and
our
people
business
partner
group,
which
you
might
know
as
hr
business
partners
in
other
organizations,
and
I'm
excited
to
to
talk
about
the
time
tracking
tool
that
that
I
use
in
gitlab
to
make
me
more
efficient,
essentially,
and
so
with
that
I
think
jamie.
G
We
can
go
on
to
the
next
slide.
So
a
little
bit
of
context
is
one
of
the
competencies
we
have
here
in
gitlab
is
manager.
One
and
part
of
that
is
just
making
sure
that
as
an
individual,
whether
you're
an
individual
contributor
or
your
people,
manager
that
you
you,
you
manage
yourself
and
you
manage
your
own
priorities
so
that
you
can
make
sure
that
you
hit
your
goals,
and
that
is
part
of
that
is
identifying
any.
G
You
know
any
distractions,
time
stealers
blockers
that
might
get
in
your
way
of
being
able
to
achieve
what
you
need
to
and
jamie
we
can
move
on
to
the
next
one
and-
and
part
of
that
is,
I
think,
a
challenge
for
not
being
a
manager.
One
is
what
you
do
with
your
time
like.
So
how
do
you
manage
your
own
time
to
be
as
efficient
as
you
can
to
get
what
you
need
to
get
done,
but
also
to
help
support
your
teams
if
you
are
managing
teams?
G
So
that
was
a
a
challenge
that
I
had
and
especially
when
teams
have
multiple
priorities
that
are
expected
of
them
at
the
same
time,
and
so
we
can
go
on
to
the
the
next
one
and
the
opportunity
here
is
like,
if
you,
if
you
understand
where
your
time
is
being
spent,
you
can
understand
how
to
plan
from
a
capacity
perspective
better,
so
you're,
not
overloading
people.
So
as
a
manager.
You
don't
want
to
be
throwing
too
much
at
your
your
teams
or
individuals,
because
it
can.
G
It
can
lead
to
burnout
but
getting
the
right
balances
to
get
achieving
the
organization
goals,
but
also
being
able
to
allow
the
individual
to
get
the
right
alignment
with
work
and
and
personal
and
and
with
that
also
being
able
to
see.
Are
there
proactive
actions
you
can
put
in
place
so
a
person's
time
might
be
needed
and
you
can
allow
somebody
to
be
more
self-sufficient
and
the
other
opportunity
is
like.
Looking
at
my
own
time
and
saying
what's
distracting
me,
is
it
slack?
Is
it
email?
G
So
that's
a
bit
of
context
there,
so
we
can
move
on
to
the
next
slide
and
what
I
use
for
for
this
is
it's
a
time
tracking
functionality
in
gitlab
and
I'll,
say
thanks
to
rose
one
of
our
pvps
who
introduced
me
to
this,
and
when
you
open
an
issue
on
the
right
hand,
side
there's
a
list
of
different
functionalities,
you
can
use
one
of
them
being
time
tracking
and
on
the
screen
there
on
the
left,
you'll
see
you
can
either
estimate
the
time
or
you
can
put
in
the
actual
time
that
you
spent.
G
I
tend
to
use
the
actual
time
because
it's
more
accurate
and
it
gives
me
a
better
picture.
So
as
an
example,
we
had
our
prep
meeting
for
this
session
last
week.
It
was
50
minutes.
So
in
the
issue
I
had
opened
for
the
beyond
code
you
put
in
I
put
in
forward
slash,
spend
put
in
the
amount
of
time
I
attended
on
that,
and
you
can
see
a
tracking
on
the
right
hand
side.
So
that's
typically
how
it
works.
And
if
we
go
to
the
next
slide,
I
can
show
you
how
it
accumulates
so
periodically.
G
G
So
an
example
of
this
in
gitlab
I
did
on
on
monday.
I
would
have
previously
prior
to
get
lab
used
word
or
pen
and
paper,
so
it's
really
handy
having
a
tool
that
automatically
calculates
the
time
and
you
don't
need
to
go
and
do
it
yourself
and
what
you
do.
G
Is
you
just
as
you're
working
on
something
add
in
what
it
is
the
time
and
then
you
can
see
on
the
right
hand,
side
how
it
accumulates
and
at
the
end
of
the
day
you
see
how
much
time
you
spent
for
me,
then
it's
a
case
of
stepping
back
and
looking
at
you
know.
If
I
was
working
on
something
and
then
I
did
10
minutes
in
slack
and
then
went
back
to
working
on
it.
It's
a
good
way
for
me
to
say:
okay.
G
Well,
you
need
to
block
your
time,
protect
it,
maybe
turn
off
notifications
etc.
So
it's
just
a
way:
I've
seen
or
identifying
that
there's
a
lot
of
meetings
or
an
async
environment.
How
can
you
cut
down
the
meetings
that
you
you
may
not
need
to
attend,
etc.
So,
from
a
personal
perspective,
that's
how
I
use
it
and
then
in.
If
we
go
to
the
next
slide,
we
as
a
team,
we
sometimes
use
it
to
see
where
we're
allocating
time.
So,
on
the
left
hand
side,
this
was
a
track.
G
We
did
for
our
people
business
partners,
so
they
were
spending
a
lot
of
time
working
with
team
managers.
Team
members,
leaders
etc,
and
we
needed
to
see
what
other
projects
they
could
take
on
board,
given
the
time
that
they
were
spending
in
those
areas.
So
we
we
periodically
then
captured
the
time
spent
so
that
we
could
accurately
address
what
else
could
be
be
added
to
their
plates
and
and
see
what
we
can
achieve
and
then,
from
a
div
perspective.
G
We
were
looking
at
getting
a
speaker
in
for
them
for
the
women's
history
month
and
we
wanted
to
see
like
from
an
organizational
perspective.
How
long
does
it
take
to
get
that
organized
so,
as
we
start
to
do
this
in
the
future,
we're
again
looking
at
putting
approximate
times
that
are
needed
to
get
things
organized
in
order
to
be
able
to
to
plan
more
efficiently,
so
that
is
it
really,
in
a
nutshell,
all
about
the
time
tracking
functionality?
I
find
it
super
useful,
and
with
that
I
will
say
thank
you
for
listening.
A
F
I
was
typing
in
the
doc
as
I
was
getting
ready
to
ask
the
question,
but
I
might
just
do
it
here
on
the
stream
itself
for
this
time
tracking.
Are
you
making
your
own
like
an
issue?
That's
just
called
time
tracking,
and
then
you
add
all
your
time
spent
to
that.
Or
are
you
like
doing
it
in
the
individual
issues
that
you
do
work
on.
G
That
would
help
if
I
come
out
from
youth
therapy
jay,
and
so
I
do
both.
So
if
it's
in
the
team,
so
we
would
do
it
in
the
individual
issues
me
personally,
I
might
I
pick
like
say
a
day
and
I'll
just
write
the
date
and
I'll
put
I'll.
Keep
that
it's
a
personal
thing.
It's
like
what
I've
been
working
on
and
the
time
so
I
think
it
works
on
both.
I
want
to
use
it
more
within
the
team,
because
I
really
do
believe
that
it.
F
G
A
Well,
I
want
to
thank
you
all
for
what
you
share
today.
It's
definitely
a
learning
experience
for
me
and
I'm
sure
everybody
else
is
like
taking
notes
on
some
of
the
things
that
we
can
implement
in
our
day-to-day
as
well.
So
with
that
we
are
going
to
move
over
to
slido,
which
is
going
to
be
our
interactive.
If
you
want
to
scan
this
qr
code,
it's
just
a
quick
quiz,
it'll
be
five
questions
and
for
those
who
get
them
all
right
has
potential
to
win
some.
A
B
I
was
just
gonna
add
if
you're
like
me
and
your
phone
is
old
and
the
camera
is
not
so
good.
You
can
also
go
to
slido.com
and
type
in
the
beyondcode2.
A
All
right,
so,
let's
go
ahead
and
get
started
so
first
question:
what
is
the
upcoming?
Oh,
this
might
not
work,
but
if
you're
a
get
lab
snob,
if
you
will,
what
is
the
upcoming
version
of
the
next
release.
A
So
if
you
got
14,
you
are
correct
and
we're
going
to
give
more
details
about
the
upcoming
release.
Later
after
the
trivia.
A
A
A
A
B
Yeah,
I
would
just
add,
like
so
gitlab
for
education
is
for,
like
educational
institutions,
for
research
and
teaching.
So
if
you,
you
know
work
at
a
university,
that
might
be
something
interesting
interesting
for
you.
Gitlab
for
open
source
is
kind
of
might
be
self-explanatory,
but
you
know
for
open
source
projects
that
have
an
open
source
license.
B
We
can
provide
free
access
to
get
labs
top
tiers,
and
that
gets
you
extra
ci
minutes
and
git
lab
for
startups
is
fairly
specific
in
the
types
of
startups
that
we
accept
into
that
program.
So
you
would
need
to
be
a
startup
from
one
of
the
most
recent
y
combinator
batches
and
a
certain
kind
of
limit
to
the
amount
of
funding
that
you
can
have.
B
A
Now,
thank
you
and
then,
if
you
are
interested
in
perhaps
organizing
an
event
or
a
meetup
similar
to
the
one
you
attended
today,
you
could
reach
out
to
myself,
as
I
am
again
the
program
manager
for
the
meetup
program
and
you
can
again
join
and
find
out
more
on
the
gitlab
meetup
page
as
well
and
john.
Do
you
want
to
go
into
detail
on
how
folks
can
contribute.
B
Sure
I
alluded
to
this
in
the
beginning,
but
gitlab's
an
open,
open
core
company,
and
so
we
have
an
open
source
project
that
we
maintain
and
there's
a
number
of
different
ways
that
you
can
contribute
there's
kind
of
the
traditional
code
contributions,
but
you
can
also
contribute
to
our
documentation.
You
can
help
with
translations
of
our
documentation.
B
Engagement
as
it's
listed
on
this
slide
would
be
things
like
the
prior
slide,
organizing
a
meetup
or
speaking
about
gitlab
at
a
community
event
in
communities
that
you're
active
in
or
you
know,
just
other
types
of
kind
of
contributions
that
help
raise
awareness
and
advocate
for
the
use
of
gitlab
and
yeah.
You
can
contribute
project
templates,
so
folks
can
get
started
with
new
languages
and
that's
a
great
kind
of
way
to
become
a
first
time
contributor.
A
A
So
if
you
were
excited
about
some
of
the
things
and
hacks
that
you
learned
today,
please
share
on
your
linkedin
or
twitter
or
other
social
platforms
that
you
do
use
and
hashtag
beyondcode
and
mention
us
at
gitlab.
A
And
do
you
want
john,
do
you
know
more
about?
First.
Look!
I'm
sorry!
I'm
still
learning
in
the
learning
process
so.
B
Yeah,
to
be
honest,
first
look
is
kind
of
something,
that's
that
I'm
learning
about,
but
I
think
that
you
know
like
our
ux
folks
love
hearing
from
our
community,
and
so
first
look
is
just
a
way
for
people
who
are
interested
in
providing
that
type
of
feedback
to
get
early
kind
of
access
to
you
know
some
of
the
new
features
and
designs
that
we're
thinking
about
for
the
product
and
share
feedback
and
help
us
make
it
better
for
everyone,
so
another
great
way
to
contribute
if
you're
not
a
developer,.
B
Yeah
I'll
take
this
one
too.
We
are
super
duper
excited.
We
release
a
new
version
every
month
for
the
last
116
months
in
a
row,
and
next
week
we're
going
to
be
hitting
117
with
an
absolutely
gangbuster
release.
Gitlab
14
we're
actually
dropping
the
dotto
you're
going
to
have
to
follow
us
on
social
media
and
read
the
blog
post
to
see
the
really
cool
design
of
gitlab
14..
B
It's
going
to
be
awesome
and
we're
really
excited
to
celebrate
all
of
the
progress
that
we've
made
in
the
product,
but
also
as
a
community
and
as
a
company,
and
so
we
have
lots
of
great,
exciting
stuff
planned
for
next
week.
So
I
would
encourage
you
to
keep
an
eye
out
for
our
blog
engage
with
us
on
social
media
and
yeah,
we'll
be
also
planning
a
meet
up
around
that.
So
I
know
all
of
you
are
members
of
the
gitlab
virtual
meetup
group.
B
So
please
join
us
for
the
get
lab.
14
meetup
we'll
be
announcing
that
really
soon
but
yeah.
This
is
a
big
release,
big
milestone
for
us
and
we're
super
excited,
and
we
hope
that
you'll
share
in
the
excitement
by
engaging
and
reading
about
it
and
seeing
all
the
great
stuff
that
we've
you
know
accomplished.
As
a
company
in
the
community
in
the
last
13
releases,.
B
And
get
lab
commit
is
coming
up
in
august
and
that's
going
to
be
another
great
place
to
kind
of
celebrate
all
the
cool
stuff
from
gitlab
14,
and
you
can
hang
out
and
hear
from
me
and
jamie
and
lots
of
amazing
community
members
who
will
also
be
part
of
that
event.
So
please
check
out
that
site
and
ticket
you
know
like
registration,
should
be
opening
soon,
so
that'll
be
a
really
fun
community
event
and
definitely
lots
of
great
content
there.
For
people
looking
to
level
up
their
get
lab
game.
A
Thank
you,
john
for
breaking
down
that
and
giving
more
information.
And
that
concludes
our
event
today
and
I
want
to
say
thank
you
for
all
that
participated
into
all
of
our
speakers.
A
I
will
ask
that
you
guys
hold
on
after
we
wrap,
so
I
can
get
a
screenshot
for
our
virtual,
like
a
group
photo,
but
if
you're
able
to
provide
feedback
it'd
be
greatly
appreciated
as
each
event
we
want
to
improve
and
make
sure
that
we're
listening
to
our
community
as
a
gitlab,
that's
one
of
our
values
is
making
sure
that
you
know
we
could
we
put
it
here
to
the
community
and
that
you
guys
are
able
to
contribute,
and
we
provide.
You
know
things
that
you
guys
are
looking
for.
A
So
I'm
gonna
actually
make
sure
that
I
share
that
link
into
the
chat
and
also
there'll
always
be
a
post
event,
email
that
I
will
share
the
youtube
video,
the
feedback
link
and
also
what
else
am
I
sharing?
Oh
the
pdf,
so
you
guys
could
also
see
the
deck
as
well.
So
again,
thank
you
so
much
for
attending
our
beyond
code
session
two
today
and
at
this
point
I'm
going
to
end
recording.