►
From YouTube: Interview with GitLab Product Manager Darren Eastman
Description
Interview with GitLab Product Manager Darren Eastman shares his journey from a Computer Science Major from the University of Texas Austin to a Product Manager at GitLab.
A
All
right
darren
how
you
doing
today,
all
right
all
right,
so
thank
you
for
participating
in
this
interview.
What
I
hope
to
do
is
just
ask
you
a
few
questions
about
yourself,
your
process
and
how
you
got
to
this
point
in
your
career.
Ask
you
a
few
questions
about
your
particular
career
path.
What
brought
you
here,
etc
and
just
serve
as
an
informative
sort
of
discussion
for
some
of
the
students
over
at
morehouse
college.
Does
that
work?
For
you?
That's
brilliant!.
A
B
Sure
so
my
name
is
darren
eastman.
Actually,
my
full
name
is
darren
marcus,
rory
eastman,
because
my
parents
thought
it
was
fun
to
give
me
four
names
was
three
names
which
is
just
one,
and
so
it
always
causes
problems
on
different
applications,
because
the
names
always
change,
but
anyway
darren
marcus
foreign
is
my
full
name.
I
was
born
and
raised
in
trinidan's
bagel,
which
is
burning
islands
in
the
caribbean.
It's
an
industrial
island.
I
was
born
here
a
long
time
ago.
B
B
I
don't
even
remember
when
I
first
heard
the
term
software
development.
To
be
honest,
actually
I
think
when
I,
when
I
was
on
my
way
to
college
at
university
of
texas
in
austin
many
many
moons
ago,
I
was
going
to
go
in
and
actually
went
in
with
the
intent
to
be
in
computer
science.
So
back
then
it
was
just
all
around
computer
science.
I
always
knew
I
want
to
do
computer
science.
B
Actually,
no,
I
shouldn't
say
that
before
I
went
to
university,
I
thought
I
wanted
to
become
a
lawyer,
but
then
being
being
from
the
caribbean
and
being
part
of
that
cohort,
especially
the
university
of
texas.
Back
in
those
days,
all
of
the
caribbean
students
will
focus
on
like
now.
If
you
go
to
university
of
texas,
you
have
to
be
in
engineering,
that's
where
that's!
Where.
B
On
the
on
the
quad
and
they're
like
no,
you
have
to
be
engineering,
that's
where
the
money
is
either
petroleum.
Electrical,
mechanical
or
computer
science
is
a
new
thing
or
computer
engineering.
That
sounds
like
yeah.
That
makes
sense
right
so
put
the
law
to
the
side.
Otherwise
I
would
have
been
a
lawyer
today,
I'm
not
making,
maybe
I'm
making
any
money
and
decided
to
go
to
computer
science.
So
back,
that's
when
I
first
cleared
it
to
computer
science
was
within
the
construct
of
going.
You
know,
as
I
became
a
freshman
in
college.
B
That's
a
really
great
question.
I
didn't
know
what
computer
science
was.
I
knew
it
was
going
to
be
interesting.
I
knew
I
wanted
to
kind
of
figure
out
programming
and
all
of
the
things
created
computer
science.
What
it
was
like
the
first
year
at
the
university
of
texas
was
very,
very
difficult:
being
a
computer
science
our
first
year
at
utf,
I'm
not
sure
if
it's
changed
now
but
back
then
there
were
so
many
kids
wanting
to
be
computer
science
major.
So
that's
an
entry-level
computer
science
undergrad!
B
You
go
into
this
classroom,
but
I
forget
how
many
I'm
going
to
make
up
a
number
now.
That's
probably
not
completely
accurate,
let's
say
100
kids
and
you're,
just
like
this
weed
out
class
and
you're,
getting
like
programming
assignments
every
day,
every
week,
quizzes,
and
so
it's
really
really
difficult,
especially
because
it's
new
right
and
back
when
I
was
an
undergrad
in
college.
We
probably
had
less
exposure
than
kids
today
in
terms
of
being
able
to
just
reach
out
on
the
internet
and
kind
of
figure
out
things
way
before
they
even
get
to
college.
B
I
think
this
is
accurate.
Hopefully
I'm
not
making
up
these
numbers,
but
I
think
at
the
time
with
folks,
hotels
would
say
that
it
was
the
store
that
sold
the
most
apple
computers
across
the
united
states.
This
was
before
apple
had
apple
stores
right,
and
so
we
were
a
huge
apple
retailer
and
be,
and
I
just
fell
in
love
with
so
my
day,
job
was
going
to
class
in
the
morning.
B
You
know
most
of
my
classes
trying
to
be
in
the
morning
going
computer
science
class
in
the
afternoon
just
basically
working
as
a
techie
at
this
campus
computer
store
learning
everything
about
computers,
networks,
the
early
internet
at
a
time
we're
still
down
the
moments
bbs's,
and
so
that's
kind
of
my
initial
experience
in
terms
of
hey
being
a
computer
science,
major
and
parallel
kind
of
being
exposed
to
all
things
that
were
happening
in
the
in
the
industry.
If
you
were,
then
they
said
what
would
you
know
in
the
show
at
that
time?.
A
And
so
even
let's
take
us
back
to
when
you
were
a
student
right,
what
was
sort
of
the
talk
of
the
town,
if
you
would
about
what
the
future
of
future
of
computer
science
was
going
to
be
for
those
people
who
were
heading
into
software
development?
What
were
some
of
the
career
paths
or
career
trajectories
or
even
companies
that
people
were
like
this
is
the
ideal
company
to
work.
You.
B
You
know,
I
thought
you
know,
that's
an
interesting
question
we
were
just
I
don't
know,
I
don't
think.
Maybe
we
were
just
not
that
great
students.
I
don't
really
have
great
conversations
honestly.
You
know
look
at
me
for
me,
and
maybe
it
was
just
me
because
I'm
an
introvert
you
go
to
class
math
class
or
whatever
it
is,
do
what
I
do
in
class
get
my
homework,
and
but
the
conversations
I
was
having
about
career
was
actually
happening
at
my
job
on
campus
and
those
conversations
were
interesting
because
we
were
kind
of
like
it
was.
B
It
was
kind
of
one
of
those
sort
of
like
lightning
kind
of
things
right
about.
It's
happened
made
this
happen
at
one
point
in
time
in
the
in
the
universe,
the
right
convergence
of
events
right
here
you
are
you're
going
through
this
job
and
the
folks
are
figuring
out
how
to
set
up
the
first
networks.
The
folks
are
figuring
out
how
to
actually
deploy
the
first
worldwide
websites
to
the
campus,
the
focus
I
helped
right
and
we
were
just
kind
of
part
of
that
discussion.
We
weren't
even
saying
hey.
B
I
want
to
go
work
for
company
a.
We
just
knew
that
we
were
doing
this
cool
thing
that
and
it
was
fun
and
then
so
you'll
be
sitting
around
one
day.
I
might
be
sitting
here
with
sharif
one
day
and
he's
my
co-worker
on
the
technical
support
line,
helping
this
humongous
campus
solve
whatever
the
problems
you're
trying
to
solve,
and
we
saw
all
kinds
of
problems
right.
We
would
fix
printers
we'd
fix,
macs
we'd
set
up
networks
right.
We
fixed
your
modems.
B
We
do
everything
right
right,
like
professors,
so
I'm
gonna
be
having
a
conversation
with
you
one
day
and
then
tomorrow,
oh
sharif
got
a
call
to
go.
Look
adele
this
hot
startup,
that's
like
blazing
trails
in
north
austin.
Oh
that's
cool
right!
Oh
he's!
No
longer
he's
no
longer
taking
any
classes.
He's
gonna
go
for
that!
Oh
that's
interesting!
Oh,
you
know
jane
just
left
because
she
did
a
great
design
job
and
is
she
gonna
finish
underground,
not
sure?
B
B
I
think
I
wasn't
having
good
conversations
with
my
computer
science
peers,
my
the
friends
that
were
in
petroleum
engineering
and
electrical
they
were
having
more
of
those
like
hey
after
I
finish
my
petrol
engineering
degree,
I'm
going
to
go
work
for
you
know
like
shell
or
whatever
right.
The
folks
I
was
hanging
out
with
who
were
just
just
floating
in
this
ether
and
just
like
having
things
happen
to
us.
It's
really
interesting.
A
B
That's
that's
what
gets
interesting
so
I'm
plugging
around
having
a
great
time
paying
for
school
right.
Luckily,
at
the
time,
tuition
wasn't
as
crazy
as
it
is
now
right,
kind
of
like
floating
in
another
cycle,
I'll
take
some
classes
here,
having
more
fun
working
here,
and
so
I
did
it
for
quite
a
few
years.
Trying
to
like
figure
out.
Am
I
gonna
finish
my
cs
degree
or
not
right,
right
kind
of
like
one
of
those
yeah?
B
B
B
Yeah,
I'm
just
being
on
b
companions.
I
have
just
exactly
what
happened
right
and
so,
even
though
I
was
working
at
the
campus
of
business
for
those
years,
I
somewhere
along
the
line
like
in
mid-90s.
Just
to
give
you
a
sense
of
how
I
am.
I
had
my
first
internship
working
for
apple,
so
I
left
the
campus
computer
store
because
apple
was
like
paying
us
a
bunch
of
them
money
to
go
work
at
their
their
help
desk
a
support
center
that
had
just
opened
up
in
north
austin.
B
So
I
was
like
well
that's
cool.
They
bring
a
bunch
of
cash
for
this
just
to
30
pounds
of
extra
macintosh.
So
I
took
that
game
that
lasted
for
about
a
year
when
I
was
still
taking
classes
at
ut
that
ended
well
for
you
at
youtube
for
a
little
bit
and
then
all
of
a
sudden
one
of
my
friends
was
like
hey
motorola
is
building
this
new
factory,
this
new
fab,
the
fabrication
of
the
power
pc
chips
at
the
time
it
was
mid,
90's,
apple
and
I'm
sure
if
steve
jobs
had
got
back
there.
B
So
I
got
a
job
working
in
that
and
what
was
called
bat
one
for
motorola
semiconductor
as
a
network
systems,
engineering
geek
as
part
of
this,
this
team
that
was
responsible
for
the
networking,
the
technology
infrastructure,
for
this
massive
manufacturing
plan.
So
we
ran
the
networks.
We
ran
the
computers,
we
ran
the
printers,
we
ran
the
factory
floor,
we
ran
the
mainframes
and
manufacturing
systems,
and
that
was
my
first
kind
of
job
while
kind
of
in
college.
B
A
C
B
So
that's
why
I
became
a
professional
and
somewhere
along
the
lines.
I
decided
I
needed
to
finish
up
my
degree
and
I
just
wrapped
up
my
little
last
degree
did
some
computer
science
courses,
but
that's
kind
of
the
short
answer
to
your
long
answer
to
your
short
question
about
my
first
quote-unquote
job.
Okay,.
B
A
B
Yeah,
so,
on
a
day-to-day
basis,
just
before
the
school,
for
example,
I
had
an
hour-long
conversation
with
an
existing
gitlab
customer,
a
large
enterprise
and
so
day-to-day
interactions.
You
may
have
a
conversation
with
a
customer,
in
this
case
the
conversation
with
the
customer
with
the
customer
and
the
sales
team
that
supports
our
customers.
Hey
we're
we're
using
github
at
scale,
in
this
case
at
scale
being
very
called
correctly
over
1600
users.
B
B
The
technical
result
from
that
conversation
would
be
hey,
I'm
going
to
reach
back
out
to
that
customer
and
give
them
some
very
specific
guidance
in
terms
of
best
practices.
Hey.
We
think
you
might
want
to
configure
your
your
platform
this
way,
but
part
of
the
results
of
that
conversation
will
inform,
probably
things
we
need
to
do
on
the
product
side.
B
So
some
of
the
challenges
you're
having
in
terms
of
figuring
out
the
security
setup
for
like
how
many
different
groups
that
they
have
and
how
these
groups
have
to
do
certain
software
development
processes,
that's
probably
going
to
inform
potential
new
features
in
the
product
as
well
right,
other
conversations
that
you
have
on
a
day
by
day
basis.
I
had
a
conversation
this
morning
with
a
designer
for
gitlab
unforget,
lab
runner,
and
the
conversation
was
about
a
new
feature
that
we
were
adding
into
the
ui.
And
so
how
does
this
figure
feature?
Gonna?
B
Look
how
customers
gonna
interact
with
it?
Are
we
making
the
right
decisions,
and
so
the
end
result
of
those
decisions
will
actually
show
up
in
the
end
product
in
a
couple
of
releases
as
a
user,
you
will
see
this
new
feature
in
the
end
product.
That's
just
like
a
smattering
of
some
of
the
kind
of
conversations
that
one
might
have.
A
B
Think
that's
a
great
way
to
put
it
and
then
specifically
a
git
lab,
and
I'm
doing
I'm
going
to
do
a
really
bad
job
of
summarizing
the
git
clip
handle
for
product
management
right
now.
So
excuse
me
right
now
what
I
like
about
gitlab
and
again
bad
summarization,
because
it's
really
well
written
in
a
handbook.
B
Github,
is
very
prescriptive
and
very
has
a
very
well
defined
sort
of
requirements
and
expectations
for
what
a
product
manager
does
or
is
responsible
for,
and
they
get
clever.
As
you
know
sure,
if
we
use
the
term
dri
or
directly
responsible,
individual
everything
right
and
so
at
gitlab,
we
expect
product
managers
to
own
their
product
right.
B
You
are
responsible
for
prioritizing
the
right
features
that
gets
built
right,
you're
responsible
for
having
the
conversations
with
customers
and
dealing
with
customer
inspirations,
you're
responsible
for
ensuring
that
the
continued
growth
in
terms
of
users
for
your
particular
sliver
of
the
product.
In
my
case
the
runner
are
you,
are
you
making
us
is
diary
making
the
wrong
decision
decisions
to
ensure
that
we're
seeing
user
growth?
You
know
right
on
a
month
over
month
and
a
quarter
of
a
quarter
basis,
so
you
have
a
lot
of
responsibilities
as
a
product
manager
at
gitlab.
A
Right
right,
yeah
awesome.
So
if
I
let's
take
a
step
back
too,
so
you
were
a
cs
major
right,
so
a
lot
of
your
responsibility
was
sort
of
dealing
with
code.
What
made
you
choose
this
particular
career
path
of
now
moving
and
becoming
a
product
manager,
as
opposed
to
someone
who
just
writes
code
every
day.
Oh.
B
Gosh
a
great
question:
you
know
I
always
think
and
that's
the
thing
about
careers,
and
that
was
like
my
kids
actually
may
ask
me
the
same
question.
I
think
all
right
if
you
chose
like,
for
example,
if
you
choose
to
be
in
a
pre-med
major
and
you
choose
to
go
down
the
path
of
becoming
an
adult,
it's
kind
of
a
very
sick
career
path.
Right,
it's
like
hey,
you're,
going
to
go
pre-med,
you
might
go,
become
a
pediatrician
or
you
might
become
a
session
kind
of
pre-ordained.
B
For
me,
it
was
kind
of
not
as
defined
when
I
when
I
was
initially
in
computer
science
and
even
later
on
when
I
was
taking
additional
computer
science
class.
I
love
from
me
personally.
It's
just
me
personally.
I
love.
I
love
knowledge.
I
love
knowing
how
everything
will
I
love
being
able
to
write
code?
I
love
being
able
to
understand
how
computer
chips
work
and
all
that
and
that
sort
of
thing.
But
personally
speaking,
I
hate
debugging
code.
B
I
hate
sitting
here
right
knowing
that
if
this
code
doesn't
work-
and
specifically
when
I
was
writing
having
an
attorney
homework,
I'm
not
going
to
get
a
grade
in
this
class
when
you're
sitting
there
late
at
night
and
the
code
is
not
working
right.
You
have
to
debug
the
family,
otherwise,
what
you're
going
to
turn
in
it's
not
going
to
be
a
great
personally.
I
hated
that,
but
I
love
knowing
how
everything
works.
I
know
I
love
figuring
it
out,
so
I
knew
very
early
on
that.
B
C
B
So
happens
that
for
me
personally,
as
I
I
mentioned
earlier,
when
I
got
the
opportunity
for
the
dell,
it
was
more
in
a
systems
and
systems,
analyst
project
management
role
right,
I
was
testing
embedded
devices.
I
was
testing
computer
chips
to
make
sure
they
were
y2k
compliant.
I
was
creating
the
projects.
Imagine
the
projects
around
that
from
my
sort
of
areas.
B
So,
basically,
when
I
went
to
die,
I
was
responsible
for
testing
all
of
the
embedded
devices
right
in
and
all
of
the
systems
that
were
responsible
for
designing
dell
computers
and
servers
and
network
gear
at
the
time,
and
so
then,
after
successfully
doing
that,
I
got
an
opportunity,
ideally
to
become
a
senior
project
manager.
So
I
was
like
oh
yeah.
B
So
in
roughly
about
2007,
I
got
an
opportunity
to
work
at
dell's
portfolio
management
office.
We
were
building
at
the
time
a
new
services
business
and
so
basically
going
to
opportunity
to
help
build
that
services
business
at
dell
and
after
working
on
that
for
a
year
and
that
services
business
was
very
along
the
lines
of
high
touch
white
glove
type
of
services.
Then
I
got
an
opportunity
to
become
a
product
manager
for
one
of
dell's
acquisitions
dell
had,
in
addition
to
building
a
services
business.
We
just
started
acquiring
software
companies.
B
I
went
back
to
the
masters
at
ut
in
what's
called
technology
commercialization,
so
that's
kind
of
a
one-year
mba
but
very
focused
on
how
to
commercialize
new
technologies
and
bring
them
to
market,
and
then
also
you
know
trying
to
create
my
own
company
as
well,
and
so
I
think
for
me.
I
just
realized
that
that
sort
of
product
management
realm
of
like
being
able
to
work
on
or
conceptualize
new
products
or
services,
it's
kind
of
what
really
fit
me
best
in
terms
of
right.
This
really
works
for
me.
B
C
B
I
hadn't
I
hadn't,
worked
on
a
product
of
sort
of
this
scale
in
terms
of
having
an
engaged
community
before,
like
my
last
set
of
products
at
dell,
for
example,
were
when
used
by
large
enterprises
kind
of
more
your
traditional
sort
of
like
b2c
type
of
sales
motion.
So
this
was
like
really
supply,
but
this
is
interesting,
working
on
an
open
core
product.
Large,
very
you
know
interesting
community
of
users
and
so.
A
B
Tons
of
things
actually
at
a
high
level
one,
even
though,
when
I
was
adele
because
I'm
down
actually,
I
was
working
remote
for
quite
a
few
years,
because
I
moved
to
oregon
in
about
2011..
I
and
I
was
managing
my
products
from
healthy
and
online,
but
that
sort
of
remote
experience
was
different
because
dell
as
a
company
and
even
when
I
moved
to
nike
later
on,
didn't
necessarily
have
a
remote
muscle
like
a
nike.
For
example,
we
have
one
there,
everybody
with
steering
mode,
but
we
didn't
have
the
muscles.
B
You
can
see
the
difference
right
like
some
folks
would
be
remo
and
you
would
be
in
the
in
in
the
office
and
then
the
whole.
You
know
blue
jeans
were
using
blue
jeans.
The
whole
conversation
thing
would
never
work.
So
what
I've
done
on
github
is
just
how
you
actually
work
in
a
fully
remote
way
right
in
a
very
much
showing
remote,
and
some
of
these
processes
you
take
for
granted,
but
actually
having
them
written
down
is
very,
very
helpful.
Okay,
this
is
how
you
do
it.
You
show
up
to
meetings
on
time.
B
You
have
an
agenda,
that's
written
down!
You
follow
the
agenda
right,
a
lot
of
those
things
I
hadn't
really
been
exposed
to
before
because
of
the
experience
of
other
companies
where
that
remote
muscle
wasn't
there.
So
that's
one
and
the
product
management
framework.
I
get
them
in
terms
of
continuously
challenging
us
to
to
reach
to
to
interview
customers
and
to
do
research
and
to
to
get
feedback
and
to
be
the
dri.
That's
also
going
to
learn
the
experience
right
because
you
realize
that
yeah.
This
is
interesting.
I
have
to
own
this.
B
I
have
to
engage
on
this
in
a
very
visceral
way.
I
have
to
be
after
the
present
if,
if
I'm
going
to
be
successful
and
if
my
product
is
going
to
be
so
successful,
so
I'm
going
to
continue
to
learn
and
then
thirdly,
they
get
that
products
interesting.
So,
for
example-
and
I
say
interesting
and
give
you
a
very
a
very
I
mean-
hopefully
an
example
that
folks
can
grasp,
if
you're
the
product
manager
for
say,
like
an
instagram,
it's
kind
of
like
very
clear
what
that
word
is
right.
B
It's
like
oh
instagram
right.
You
know
what
you
can't
know.
What
the
features
are
right.
You're,
sharing
photos
and
you're
doing
all
these
cool
things
right,
but
gitlab.
We
are
different
in
that
our
product
supports
a
whole
plethora
of
different
things.
Right
we
could
be
supporting
a
team,
that's
developing
instagram
or
we
could
be
supporting
our
team
as
developing
whatever
right,
and
so
it's
a
really
really.
If
you
love
technology-
and
you
love
software,
you
love
learning.
B
B
I
think
competing
yeah.
Everything
continues
to
evolve.
I
think
at
a
high
level
sort
of
like
a
broad
level,
we're
all
talking,
obviously
everyone's
talking
about
it
for
months
now,
we're
all
using
it
like
ai
machine
learning,
all
those
things.
I
think
what
we
can.
I
think
a
couple
of
potential
truisms
that
we
can.
We
can
state
without
you
know
stating
something
that's
obviously
going
to
be
proven
wrong
very
quickly
thereafter.
B
C
C
B
So
I
think,
if
you
are
in
this
technology
industry,
what
what
I
think
will
help
you
long
term.
Maybe
I'm
not
answering
questions
about
going
off
on
the
tangent
is
when
I
was
at
motorola
this
vice
president.
At
the
time
this
was
1998
and
he
happened
to
be
african-american,
and
then
I
always
I
remember
his.
I
walked
into
the
office
and
we
were
having
some
changes
and
reductions
in
the
force
and
he
says
at
least
he
looked
at
me
and
it
is.
B
He
had
a
very
thick
accident
forget
where
he
was
from,
or
maybe
I'm
west
africa
or
something-
and
he
looked
at
me
and
says
in
these
times
you
sharpen
your
soul.
What's
that
mean
you're
sharpening
yourself?
I
internalize
it
for
a
bit.
I
was
like
yeah,
he
was
right,
and
so
I
think
the
other
truism
is.
If
you
love
what
you
do
you,
and
especially
in
technology,
just
continue
to
learn
right
and
it's
it's
going
to
be
a
marathon,
not
a
sprint.
B
Some
folks
are
going
to
be
entrepreneurs
and
maybe
get
like
something
happens,
really
really
fast
and
they're
super
successful.
But
for
a
bunch
of
us,
just
hey
it's
you
know
just
continue
to
learn
and
be
there,
because
it's
going
to
be
a
lot
of
competition,
but
it's
also
going
to
be
another
evolution
as
well.
A
B
It's
a
journey
and
you
mean
it's
a
journey
and
I
think
if
a
couple
of
things
is,
if
you
are
passionate
about
whatever
you
do-
and
I
know
this
sounds
kind
of
really
corny
right
and
things
will
happen
in
your
career.
Some
things
will
work
out
well
and
some
things
work
and
you're
going
to
have
great
leaders
and
you're
going
to
have
bad
things.
You
have
good
experience.
B
You
can
have
bad
experiences,
it's
just
a
matter
of
life
right,
okay,
but
I
think,
generally
speaking,
if
you
love
what
you
do
and
you
continue
to
learn-
and
you
know
you
not
every
day
is
going
to
be
like
you
know
my
greatest
productive
day
right,
but
generally
speaking,
when
you
do
the
right
things
for
the
right
reasons
over
time,
things
are
going
to
work
out
for
you
right.
It
may
happen
today.
It
may
not
happen
tomorrow,
but,
generally
speaking,
the
ark
of
the
universe
will
bend
in
your
favor
right.
B
But
if
you're
like
I'm
not
going
to
learn
anything
new,
I
just
graduated
college
and
now
I
know
everything
I'm
not
going
to
keep
doing
my
skills,
I'm
not
going
to
mentor
or
I'm
not
going
to
you
know
continue
to
like
learn,
what's
happening
differently
or
you
know
what
I
mean
then
yeah.
So
I
think
that
long,
the
the
app
will
look
up
for
you.
If
those
things
are
true.
B
A
B
Somewhere
but,
but
maybe
just
buckle
down
and
finish
the
cs
degree
faster
all
right
now
I
look
back.
I
have
so
many
hours,
then
my
wife
did
this.
Like
I
looked
at
my
transcript
from
another
university
I
went
to
after
I
finished
my
liberal
arts
degree
at
youtube.
I
did
not
finish
my
csu
video
on
youtube,
so
I
recommend
yesterday
or
something
that
was
good
about
me.
I
had
only
15
hours
left
and
I
was
like.
B
Leave
that
why
did
I
stop
so?
My
advice
to
my
younger
self
would
be
yeah
you're
having
a
great
time
working
and
you're
having
a
great
time
hanging
out,
but
maybe
you
just
kind
of
focus
a
little
bit
and
just
knock
that
thing
up,
because
it
was
just
15
hours
and
just
get
off
the
plate,
and
it's
done
all
right.
That's
one
one
piece
of,
but
also
truly
honestly,
both
take
the
job
in
1991.
That
was
nice.