►
From YouTube: UX Showcase - Using GitLab to manage my plan
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
A
Inside
my
head
and
the
head
of
all
procrastinators.
He
describes
two
characters:
a
rational
decision
maker
who
cohabits
with
an
instant
gratification
monkey,
I'm
sure
all
the
procrastinators
watching
this
have
seen
the
fantastic
ted
talk
or
read
the
article
while
they
should
have
been
doing
something
else.
But
if
you
aren't
a
procrastinator,
you
should
definitely
check
them
out.
I've
put
the
links
here
and
yes,
I
did
get
distracted,
preparing
this
showcase
and
ended
up
reading
them
all
again.
A
The
rational
decision
maker
isn't
trained
to
deal
with
the
instant
gratification.
Monkey
and
life
can
often
play
out
like
this
at
gitlab.
However,
things
can
play
out
a
little
bit
differently
as
there's
so
much
cool
stuff
to
do
a
constant
stream
of
rabbits
to
chase
into
holes,
chances
to
collaborate
and
cool
things
to
learn
and
unlimited
opportunities,
all
of
which
the
instant
gratification
monkey
tells
me
are
good
things
to
do
so.
What
happens
is
at
the
end
of
the
week?
A
I
know
I've
been
busy
helpful
and
productive,
but
I
can't
remember
what
I've
done
or
perhaps
more
worryingly,
I
can't
remember
what
I've
agreed
to
do
in
the
future,
so
here's
the
journey
of
how
I'm
trying
to
tackle
that
using
gitmo
to
manage
my
plan.
I
hope
this
exploration
is
useful
to
you
and
you're
able
to
learn
from
my
pain
and,
if
you're
up
for
it,
I'd
love
to
offer
you
the
opportunity
to
help
me
design
my
life
and
help
me
to
avoid
a
to-do
hellhole.
A
A
A
Even
joining
gitlab
starts
with
a
list
327
items
with
gratifying
check,
boxes,
making
sure
a
joiner
does
everything
from
changing
their
passwords
to
add
a
picture
of
their
pet
to
the
team
page,
the
instant
gratification
monkey
loved
it,
but
by
week
two
when
I
started
being
pinged
in
issues
by
my
two
different
groups
eager
to
get
started,
I
knew
the
onboarding
issue.
Honeymoon
couldn't
last
there's
no
shortage
of
options
for
creating
lists.
A
I've
heard
suggestions
for
all
sorts
of
tools,
things
todoist,
remember
the
milk
trello
reminders
app
or
my
personal
favorites
notion
and
pen
and
paper,
but
at
gitlab
we
are
rightly
encouraged
to
use
the
one
devops
platform
to
do
its
thing.
So,
let's
take
a
look,
as
I
mentioned
earlier,
when
I
joined
gitlab
six
months
ago,
it
all
started
as
a
list,
but
to
be
more
accurate.
There's
two
lists
and
this
continued
to
grow
sprawling
across
multiple
issues.
A
As
I
tried
to
get
up
to
speed
with
the
company
and
the
two
different
groups,
I
was
working
with,
I
quickly
lost
track
of
things.
I
knew
I'd
been
busy
and
productive,
but
I
couldn't
remember
what
I've
done
and
if
I
hadn't
been
able
to
do
it
straight
away,
there
was
a
real
risk
of
it
being
lost
at
times.
A
A
I
had
my
first
breakthrough
when
I
saw
sun
jung's
tables
and
another
soon
after
when
I
saw
how
jeremy
uses
issues
instead
of
markdown
files,
I
wondered
if
I
could
remix
these
ideas
together
to
try
and
create
something
that
could
work
for
me.
Here's
my
first
attempt
at
putting
it
all
together
some
metadata
at
the
top
some
stuff
I've
agreed
to
do
in
the
middle
and
a
lot
of
other
stuff
I
needed
to
do
and
the
stuff
I
actually
ended
up
doing.
A
My
issues
start
life
the
milestone
before
empty,
but
with
a
comment,
titled
potential
work
when
a
request
comes
into
work
on
something
in
a
future
milestone.
I
estimate
the
effort
and
add
it
to
this
table,
so
I
don't
forget
it.
These
accumulate
in
the
current
milestone,
ready
to
be
combined
with
my
capacity
estimation
for
the
planning
season
of
import
and
optimize.
A
But
estimation
is
hard
and
that's
probably
a
topic
for
another
showcase.
So,
during
a
milestone
by
day,
one
ish,
I've
populated
my
issue,
template
with
planned,
leave,
agreed
work,
additional
to-do's
and
anything
else
for
the
current
milestone.
A
I
try
and
keep
this
part
up
to
date,
so
the
deliverables
reflect
the
current
status
and
any
unplanned
work
gets
locked.
Occasionally,
this
unplanned
work
should
really
have
been
scheduled
with
a
weight
so
I'll.
Try
and
document
that
here
too,
something
I'm
also
experimenting
with,
is
having
a
daily
to-do
list
and
it
does
a
reasonable
job
of
keeping
the
instant
gratification
monkey
away,
but
I
can
sometimes
forget
about
the
big
stuff
in
the
deliverables
table.
A
A
When
I
started
that
kit
lab
our
very
own
petro
advised
me
to
start
my
own
reflective
practice
and
if
you
go
back,
you
can
see
this
item
on
my
to-do
list
for
a
very
long
time,
but
I've
I
found
a
nice
rhythm
for
it
now,
at
the
end
of
the
milestone.
Before
I
close
my
issue,
I
look
back
at
what
I've
done
and
write
down
what
went
well,
what
didn't
go
so
well
and
any
new
ideas.
A
It
would
have
been
impossible
if
I
hadn't
been
able
to
look
back
at
these
issues.
My
favorite
achievements
were
all
things
I
completely
forgotten
about
forgotten
about,
and
it
was
a
breeze
to
flick
through
the
planned
and
unplanned
work
contemplating
how
much
I'd
learned
and
grown
over
the
past.
Six
months
present
me
is
very
grateful
for
surpassed
me
for
writing
it
all
down.
Along
with
some
diary
entries,
I
wrote
about
certain
issues
detaining
my
moods
thoughts
and
feelings
of
different
things
at
the
time.
A
So
this
is
how
I'm
using
gitlab
to
manage
my
plan,
and
it's
helping
me
keep
my
instant
gratification
monkey
occupied
and
I
enjoy
the
opportunities
it
gives
me
to
live.
Our
transparency,
efficiency
and
collaboration
values
documenting
what
I've
potentially
agreed
to
do
in
upcoming
milestones.
Help
me
manage
my
capacity
and
reduces
the
chance
of
over-committing
using
gitlab
to
scope
my
days
and
track.
A
My
commitments
helps
me,
keep
on
track
and
allows
others
of
you
into
my
work
and
a
reflective
practice
helps
me
become
a
better
designer
and
colleague
through
introspection,
and
course,
correction,
but
I
wish
there
was
better
ways
of
linking
these
boards
and
planning
issues
to
the
two
groups.
I
work
in
and
I'd
really
like
a
smarter
way
of
keeping
the
issue
statuses
up
to
date.
I
wish
I
was
better
at
estimation,
and
I
wish
I'd
set
a
definite.
A
I
could
set
a
definition
for
my
progress
and
a
way
to
see
that
over
time,
but
this
is
not
the
only
way.
I'm
sure
you
have
your
own
ways
and
I've
seen
others
use
markdown
other
apps,
their
own
personal
issue
boards
and
slack
reminders
and
emails.
So
if
you're
doing
something,
that's
working,
I'd
love
to
see
it,
please
share
it
with
me
or
in
the
ux
co-working
slack
channel
and
if
you've
got
any
ideas
for
how
I
can
design
my
life
better.
Please
collaborate
with
me
over
in
my
current
milestone
issue.
A
B
I
was
just
really
impressed
that
dan
does
a
retro
for
himself.
I
mean,
there's
no
excuse
for
us
not
to
go
and
drop
comments
in
the
ux
right
so
now,
and
it's
really
great
that
he
documents
his
own
learnings
to
inform
the
future
improvements
that
he
might
want
to
make
to
the
process
that
he's
following
so
yeah.