►
Description
GitLab Product Marketing Manager Brian Glanz details the ways GitLab can help dev teams avoid the perils of complicated DevOps toolchains.
Read more about our product vision: http://bit.ly/2IyXDOX
Learn about FOSS & GitLab: http://bit.ly/2KegFjx
Get in touch with Sales: http://bit.ly/2IygR7z
A
A
We're
like
a
thousand
people,
just
short
of
a
thousand
employees
and
I
had
to
check
again
today,
because
yesterday
it
was
in
62
countries,
and
today
it's
63,
because
it's
another
day,
why
not
we're
in
63
countries,
I
googled
really
hard
for
that
image,
so
I
hate
to
waste
a
perfectly
good,
welcome,
slide.
I
know
it's
getting
a
little
late
for
a
welcome,
but
part
of
what
I'm
here
to
do
is
actually
just
to
generalize
the
conversation.
A
little
bit.
A
Tell
you
a
little
bit
more
about
gitlab
the
company,
the
software
and
I
believe
it
was
actually
promised.
I
would
talk
about
DevOps
tool
chains,
so
I
will
it's
true:
I
am
Brian
glands
and
there
I
am
I,
actually
did
tweet
something
at
the
hashtag,
because
why
not?
It's
pretty
cool
out
there
at
gitlab?
We
work
where
we
live
instead
of
needing
to
live
where
we
need
to
work
and
I
happen
to
live
in
like
the
building
out
the
window.
A
But
I
have
this
urge
to
say,
welcome
to
get
lab
at
the
top
of
the
talk,
because
I've
been
in
your
seat
many
times
and
lots
of
other
companies
and
what
you
know
whether
it's
over
at
the
spheres.
Actually
that
way
or
like
further
that
way,
I
was
down
at
X
the
innovation
labs,
the
research
and
development
labs
at
Google
and
I'm
reminded
of
a
time
a
buddy
of
Mines.
A
Given
the
remarks
at
the
top
of
the
of
the
day
there
and
largely
an
on
Google
audience
and
he's
got
this
big,
like
Hindi
film
narrator
voice
like
Amitabh
Bachchan,
and
he
says
the
start
of
it-
welcome
to
X.
You
know
I'm
just
like
goosebumps,
because
it's
a
super,
dramatic
setting
and
and
occurs
to
me
that
this
building,
which
is
just
a
building-
but
you
know
the
Space
Needle-
is
kind
of
like
get
labs
building
today
and
we
don't,
we
don't,
have
a
building.
You
know
those
thousand
people
in
63
countries.
A
They
don't
go
to
any
one
office.
We
don't
have
a
headquarters
to
welcome
you
all
to,
but
if
you
get
more
than
a
few
of
us
in
the
same
place
and
at
the
same
time,
because
we're
also
asynchronous
and
all
our
work
by
default,
and
then
customers
and
users
and
contributors
at
that
point
like
somewhere
in
there
we've
every
right
to
say
this
is
get
lab
right
now.
So
so
yeah
welcome
to
get
lab
and
that's
a
little
bit
of
context
about
the
company.
You've
heard
a
little
bit
about
me.
A
I
was
in
fact
a
developer
and,
as
a
consultant,
I'm
thinking,
you
know
for
all
the
different
operations
I
was
inside
of
more
than
a
hundred
different
clients
of
different
sizes
over
the
years.
I
don't
know
of
another
one
who
dog,
who
did
quite
as
aggressively
and
in
all
the
same
ways
as
gitlab
does
and
that
that
I
I
sort
of
bring
up
because
it
was
occurring
to
me
like
how
do
we
get
away
with
it?
A
They
also
use
the
product
to
run
the
company
and
that'll
come
back
around
and
actually
be
relevant
in
one
of
these
slides.
Let's
pull
at
that
DevOps
question
with
software
delivery
and
this
question
you
have
been
told
to
think
about
so
many
times
in
recent
years.
How
often
do
you
release
and
I
like
this
needle
for
kind
of
pulling
at
the
thread?
I'll?
Do
this
a
few
times
in
these
slides
I?
A
Think
of
the
answer
for
yourself
and
then
we'll
go
survey
says
and
we'll
show
you
the
answer
from
lots
of
other
developers
or,
in
some
cases,
lots
of
other
folks
in
IT,
on
the
ops
side
or
in
security.
Actually
how
many
people
are
developers
here,
I'm
looking
around
and
already
know
some
of
the
answers,
yeah
just
good
to
know
quite
a
lot
of
the
room
which
makes
sense.
A
So
how
often
do
you
release
I
mean
we've
all
been
told
and
I've
must
have
told
people
a
thousand
times
it
should
be
more
often,
but
in
case
this
is
small
I'm
gonna
walk
over
here
and
do
so
twenty
fourteen
to
eighteen
over
five
years.
This
is
a
question
asked
by
Forrester.
These
are
you
know
their
data?
This
is
their
analysis,
I'm
just
bringing
it
to
you.
We
all
know
we
should
be
releasing
more
often
or
so
we've
been
told,
but
many
teams
are
stuck
I.
A
Think
stuck
is
a
fair
word
there
over
those
five
years.
I'm
actually
really
surprised.
There
wasn't
a
lot
more
movement
on
that
question,
but
if
you
zoom
in
on
2018
and
then
do
a
2019
version.
Finally,
like
a
little
bit
of
loosening
up
and
Chris
Kondo
the
principal
on
this
subject
and
related
subjects
at
Forrester,
this
is
him
drawing
a
box
and
saying
target
zone.
I
I,
don't
disagree
if
I.
A
With
Chris
I'll,
let
you
know
but
I,
don't
generally
speaking,
nor
in
this
case,
so
there's
a
lot
of
questions
about
why
I
mean
even
like
why?
Why
so
stuck,
but
also
like
why
release
more
often
matters
I
think
it's
just
a
it's
an
aspect
of
being
agile,
not
like
agile
methodologies
per
se.
But
it's
like
are
you
fleet
of
foot?
A
Are
you
ready
to
react
to
an
opportunity
when
it
presents
itself
to
you
know
an
incident
that
requires
releasing
to
respond
to
to
your
competition
more
quickly,
releasing
something
that's
better
and
sooner
than
you
expected
over
some
of
these
same
years,
Forrester,
2013,
15
and
17.
We're
asking
just
developers
in
general.
Are
your
organization's
using
an
agile
methodology,
never
mind
which
flavor
2013
hath
we're
saying
that
fewer
than
25%
of
their
teams
we're
using
agile
and
that
script
really
flipped
by
2017,
exactly
half
that
is
right
and
saying.
B
A
More
than
75%
we're
using
agile
but
here's
another
one
of
those
survey
says
so
when
you
ask,
are
you
using
agile,
oh
yeah
and
lots
of
movement
over
those
four
or
five
years?
But
if
you
ask
them
the
specific
method
level
I
mean
just
think
of
your
own
answers
to
these,
and
it
doesn't
really
matter
what
you
call
them
like.
Do
you
do
stand-ups?
Do
you
do
Sprint's?
Do
you?
You
know
when
you
ask
people
more
specifically,
are
you
actually
using
these
practices
associated
with
modern,
app
development,
yeah
yeah?
A
That's
what
I
remembered
quite
a
gap
right,
if
you
ask
people
like,
are
you
using
agile
or
if
you
asking,
are
you
doing
some
of
these
specific
things
associated
with
one
or
the
other
one
of
the
other
agile
methodologies?
Not
so
much,
and
let's
look
to
the
other
side
of
DevOps
and
ask
in
this
case
and
the
next
few,
some
IT
professionals
with
responsibility
over
tool,
chain
management
and
they're,
telling
Forrester
too
many
tools
creates
friction
kind
of
obvious
from
I
guess
a
little
bit
of
my
consulting
bias.
A
A
So
sure.
There's
a
lot
of
there's
a
lot
of
rub
there,
plenty
of
friction
to
go
around
who's,
actually
feeling
it
is.
The
next
question
put
to
the
same
IT
professionals
here:
who's
responsible
for
maintaining
all
of
that,
keeping
it
all
working
yeah
the
developers
we
all
kind
of
know
that,
but
conveniently
31
plus
19
is
50.
So
exactly
half
of
these
organizations
know
they
have
a
problem
to
the
extent
that
they
have
teams
devoted
to
keeping
these
things
working,
DevOps
teams,
internal
tools,
teams.
A
Yeah
labor
intensive,
so
let's
pick
up
just
a
little
bit
of
how
the
integration
actually
is
done
and
the
way
I
read
this
one
is
that
you
want
to
be
here
right,
out-of-the-box
solution,
integrated
end-to-end
and
that
that
jives,
with
the
sort
of
one
in
five
being
in
the
old
promised
land
here,
I,
don't
know
what.
Incidentally,
I
don't
know
how
to
read
this
last
one.
A
Our
tool
chain
is
not
integrated,
so
it's
it
is
it
tool
chain,
I'm,
not
sure
what
that
means
makes
Li
small
small
answers
there,
but
you
know
maybe
it's
wonderful,
maybe
it's
like.
Oh,
we
use
one
tool,
so
it's
not
an
it.
You
know
IT
people
that
you
know.
Maybe
it's
like
in
the
days
of
you
know
the
sneakernet
right
you'd
put
data
on
a
thing
and
walk
it
across
the
office
and
your
sneakers.
A
Thankfully
they
were
asking
the
smart
people
this
question.
This
is
a
little
convoluted
we're
looking
at
of
the
so
the
benefits
you
will
rule
you
will
realize,
or
do
you
anticipate
realizing
if
you're
in
that
Promised
Land,
if
you're
in
that
one
in
five
with
a
fully
integrated
tool
chain
out
of
the
box-
and
this
is
a
man
I-
think
some
obvious
ones
right,
like
yeah
I
improve
developer
productivity,
we
just
saw
the
other
side
of
that
coin.
A
Increased
revenue
I'm
impressed
that
pops
is
high
on
that
list,
so
these
respondents
are
quickly
connecting
those
dots
between
simplifying
release.
Releasing
more
often
increasing
revenue,
easy
enough
for
them
to
connect
the
dots
I
like
this
one,
improved,
developer,
job
satisfaction,
partly
because
I
still
get
recruited,
which
is
totally
inappropriate
but
still
get
recruited
as
a
developer
and
the
messaging
and
those
things
says
stuff,
like
you
know,
it's
a
developer's
paradise.
You
can
use
any
tools
you
want.
A
A
So
in
this
case
we're
only
actually
asking
a
subset.
These
are
the
folks
who
actually
have
an
out-of-the-box
tool
chain
management
system
and
then
of
the
benefits
they
have
realized,
which
do
they
seeing.
How
do
they
see
having
the
greatest
impact
on
their
business,
an
ability
to
deploy
to
any
cloud
somewhat,
to
my
surprise,
really
pops
their?
Although
I'm
not
surprised
at
all
that
three
and
four
would
agree,
they
don't
want
to
get
locked
in
I
mean
who
wants
to
be
locked
in
and
why
is
multi-cloud
important
I
mean
I.
A
I
think
this
is
fairly
self-explanatory,
but
it
also
occurs
to
me
that
we're
standing
in
an
enormous
lightning
rod
in
the
middle
of
cloud
city
and
I
don't
want
to
get
struck
down,
but
yeah,
don't
let
big
cloud
lock.
You
in
right,
of
course,
they're
developing
lots
of
tools
that
are
intentionally
going
to
work
a
little
more
smoothly
if
you're
also
yeah
locked
in.
We
all
kind
of
know
that,
but
it's
nice
to
see
that
and
correlated
with
these
other
data
in
these
responses.
So
what
can
you
do?
A
C
A
Work,
you
know,
I'm
gonna
turn
the
corner
on
this
all
this
lines
up
extremely
well
with
having
one
tool
to
do
as
much
of
this
for
you
as
possible.
So
let's
talk
about
git,
lab
and
Hayden
talked
about
this.
Some
and
and
some
of
these
slides,
just
flesh
it
out
even
a
little
bit
more
good
lab
is
for
developers
sure
that's
where
it
started
for
and
by
developers
with
source
code
management.
Only
at
some
point
there
was
a
big
debate
there
weren't
a
whole
lot
of
people
necessarily
in
the
debate.
At
that
point.
A
It
does
this
one
thing
extremely
well,
but
as
soon
as
they
did
integrate
them,
it
was
obvious
at
least
they're
in
that
bubble,
that
what
the
benefits
were
and
that
they
were
going
to
go
toward
developing
things
for
the
full
DevOps
lifecycle.
It
was
just
clear
to
them.
It
was
I
think
initially
a
choice
made
based
on
their
own
needs
for
efficiency.
They
wanted
to
maintain
one
codebase.
They
wanted
to
have
one
database.
A
A
A
And
how
bad
is
it
really?
It's
pretty
bad.
So
when
you
look
at
some
of
these
sources
like
the
source
on
the
5.2
Billy
spent
on
DevOps
tools
in
2018
that
source
projects,
15
plus
Billy
being
spent
in
2023
and
still
like
almost
9
and
10
organizations
are
disappointed
with
their
DevOps
initiatives
and,
and
so
you've
got
this
stuff
that
you
know
the
marketing
people
like
me
now
will
say
it
will
dissolve.
You'll,
digitally,
dissolve
your
silos
and
then,
ironically,
because
you've
bought
so
many
tools.
A
Don't
know
at
this
point
that
we
need
to
say
a
whole
lot
more
about
this
particular
slide.
We've
all
got
enough
context,
except
that
I
would
add
single
user
interface
to
that
I
mean
just
occasionally
as
a
dev
doing
ops,
that's
invaluable
to
me,
and
I
only
have
so
much
brain
ram.
So
if
I'm
trying
to
chase
down
an
incident
or
something
unless
I
can
Louis
I
can
do
in
the
way
of
context,
switching
the
better
for
me
this
and
and
all
of
the
maturity
related
to
this.
A
This
is
just
one
click
off
of
our
homepage
and
and
I'm
sure
everybody
in
here
has
you
know
more
detailed
interest
in
a
lot
of
these
areas.
The
fact
that
it's
all
up
here
is
some
of
its,
of
course
labeled
is
coming
soon.
But
it's
not
to
say
it's
it's
complete
by
any
by
any
stretch,
I
think
we
can
say
more
so
than
anyone
else
that
that
is
a
complete
DevOps
platform
doesn't
mean
everything's,
feature
complete,
but
we're
pretty
serious
about.
A
Whether
you
work,
forgivable
or
not,
any
informed
opinion
is
as
much
a
contribution
as
if
as
a
feature
or
a
fix
and
there's
a
lot
of
debate
about
like
at
what
point
are
you
lovable
I
would
say,
review
apps
I
mean
I
love
our
review,
apps
I
know
if
customers
buying
the
product
just
for
that
and
we
say
they
love
it.
So
this
is
a
little
conservative
for
my
taste.
A
This
guy
David
chimes
and
he
works
in
an
ops
and
insecurity
and
says
this
day
already
came
for
me.
There's
reading
it
for
the
people
in
the
back
again
doesn't
necessarily
mean
we're
all
the
way
there,
but
I
think
we
can
already
say
this
as
well.
I
very
much
do
it's
been
a
year
or
two
since
we've
been
seriously
adding
to
the
security
portion.
A
These
are
all
really
big
deals
now
that
I'm
looking
at
this,
these
aren't
just
like
features
here
in
there,
the
up
and
to
the
right
this
sort
of
pickup
of
the
pace
it
it's
here,
I
would
say,
like
I
bring
it
here.
Partly
just
to
say,
you
could
doubt
whether
we'll
actually
be
able
to
be
feature
complete
or
lovable
in
appreciable
number
of
those
different
categories
in
a
few
years.
A
A
I
hit
the
dashboard
just
off
of
this
and
its
really
interesting
to
click
through
just
in
time
to
throw
a
couple
more
things
in
here,
we've
even
got
organizations
hiring
people
to
contribute
so
that
that
all
is
part
of
how
it's
coming
together
and
just
to
put
a
bow
on
it.
The
company's
mission
formally
is
everyone
can
contribute.
A
Even
they
use
get
lab
every
day
to
do
their
jobs,
that's
how
we
get
away
with
being
completely
remote
and
and
asynchronous
by
default,
and
and
still
hold
it
all
together
and
pretty
well,
and-
and
so
this
is
already
true
for
us-
we
want
it
to
be
true
for
everyone
and
and
that's
part
of
what
it
means
for
everyone
can
contribute,
there's
even
sort
of
a
more
profound
level
to
it.
Company
does
a
lot,
for
you
know,
educational
users
and
for
open
source
projects
gives
a
lot
of
weight
for
free
and,
of
course,
so
much.
A
The
good
lab
wants
to
make
this
a
readwrite
world
I
really
like
that
version
of
it.
This
version
of
it
is
great
too.
That's
all
I
brought
for
conversation
happy
to
go
back
and
answer
questions
about
any
specific
slides.
We
should
also
broaden
this
up
and
let
anybody
from
get
lab
or
anywhere
else
answer
questions.
F
E
You
Bryan
we're
gonna
turn
this
into
an
open,
AMA
right.
So
there's
a
lot
of
get
laberd's
here,
so
we're
gonna
help
Bryan
out.
If
you
have
a
question,
ask
it
that's
what
we're
here,
for
we
still
got
this
place
for
I.
Think
I,
don't
know
when
it
shuts
down
maybe
an
hour
and
a
half
hour.
There's
still
some
drinks
there's
still
some
food,
but
this
is
your
chance
to
ask
a
question
we'll
walk
around
and
it
said,
ask
me
anything
right.
So
it's
an
AMA.
Anyone
have
any
questions.
All
right!
F
Promise,
it's
not
too
terrible.
I
worked
in
sales
enablement
for
just
a
little
while
at
a
big
sales,
org
and
part
of
that
was
doing.
Mine
chair
events,
I
have
a
challenge
at
Disney
where
a
lot
of
product
managers,
project
managers
specifically
say
hey.
Why
would
I
use
gitlab
I
mean
it's
got
some
of
these
things,
but
yours
like
my
tool
of
choice
and
smartsheet,
and
these
other
things
that
PMS
are
usually
indoctrinated
into
so
I
guess.
My
question
to
get
lab
would
be.
E
Can
you
go
present
at
this
customer
and
just
kind
of
walk
through
your
workflow,
your
daily
workflow?
And
why
and
a
lot
of
it
was
just
hey-
I
needed
a
place
to
just
kind
of
organize
all
this
stuff
that
it
coming
at
me.
That's
better
than
email
right,
I
mean
which
is
not.
You
know,
that's
a
pretty
low
bar
right
and
then
just
to
be
able
to
pass
work
to
other
people.
When
there's
you
know
other
people
contributing
back
to
it.
It's
a
conversation.
E
It's
just
not
lost
an
email,
and
so
since
we
had
that
and
get
lavage,
it's
made
sense.
I've
had
other
customers.
Ask
the
same
thing
and
everyone's
a
little
unique
I
think
it's
just
smart
to
find
some
solution
where
you
can
collaborate
and
everyone
can
kind
of
contribute
and
there's
kind
of
an
audit
trail
of
what's
going
on,
that's
my
answer
to
this
question:
does
anyone
else
want
to
jump
in
Oh
known
as
dojo?
If
your.
C
So
my
take
on
that
is,
as
with
everything
else
at
gitlab,
it's
an
iterative
process
and
we've
gotten
to
a
point
now,
where
I
think
we've
satisfied
a
lot
of
end
users
or
engineers
or
developers
needs,
and
the
next
evolution
of
that
the
next
iteration
is
to
get
feedback
from
those
project.
Managers
who
say
I
can't
live
outside
of
JIRA,
so
we
are
actively
seeking
that
feedback.
So
it
would
be
great
if
we
could
interface
with
people
like
that
that
have
that
stance
saying
this
isn't
gonna
work
for
me.
C
G
H
B
I
I
I
think
we
did
just
recently
roll
out
some
like
progressive
diploma
capabilities,
and
so
you
can
target
certain
percentages
of
users,
and
so
we
are
iterating
there,
and
so
it
kind
of
will
depend
on
how
mature
and
robust
but
pre-chat
you
need,
but
essentially
we're
on
a
trajectory
they're
on
future
flags
and
we've
been
iterating
on
it
across
the
last
couple
months.
So
it's
continued
to
get
better
and
yeah
it'll
depend
on
sort
of
way.
I
E
Great
question
on
our
roadmap:
there's
probably
an
epic
about
future
flags
and
I,
would
highly
recommend
you
contribute
and
say
I
like
this
I.
Don't
like
that,
and
please
do
this
and
the
more
people
that
raise
their
hand
the
make
the
easier
it
is
for
Josh
to
help
steer
the
ship.
That's
how
I
would
say,
but
that's
a
great
question.
I
don't
know.
Maybe
Hayden
looks
like
he's.
Gonna
get
creative.
He
might
pull
that
up.
I,
don't
know
any
other
questions.
I
got
a
question,
it's
more
like
a
quiz.
E
E
D
I
Thanks
so
I
get
live.com,
we
are
releasing
weekly
now,
so
we
have
a
new
website
up
at
our
about
go
to
calm,
slash
releases,
slash,
get
lab,
calm
weather.
You
can
see
like
what
features
shipped
to
get
lab
comm
that
aren't
yet
available
in
the
get
lab
like
self
managed
release
package.
So
you
can
check
that
out.
It's
possible.
They
might
be
behind
the
feature
flag,
so
they
might
not.
I
They
might
be
merged,
but
not
totally
deployed
yet,
but
that's
how
easily
I
check
out
like
what's
coming
and
yeah,
so
we're
weekly
we're
working
on
driving
that
down
to
be
more
quick
to
be
more
rapid
and
acceptably.
We
I
think
we're
tackling
some
of
the
availability
challenges
on.com
first
before
we
keep
on
driving
forward,
but
we're
at
weekly
now
and
we
in
to
keep
on
going,
but
we
want
to
make
sure
we
keep
it
up
first
and
then
on
self-managed
I.
I
Think
we
feel
like
a
monthly
release,
is
about
the
right
cadence
for
folks
as
far
as
a
monthly
feature
release
and
then
it's
it's
pretty
quick
for
most
self-managed
releases,
but
we
actually
find
that,
like
30
percent
of
users
are
essentially
within
n
minus
one
of
the
release.
So
it's
pretty
good
and
I.
Think
it's
like
just
under
50
percent
or
within
and
like
completely
at
minus
3
yeah.
H
I
We
keep
a
close
eye
on
that,
but
make
sure
upraise
are
reliable,
people
are
taking
them,
but
I
think
we
feel
pretty
comfortable.
That's
a
good
cadence,
but
love
feedback
as
far
as,
if
you
want
feature
releases
faster
or
or
if
that's
about
right
or
how
fast
people
can
sort
of
ingest
upgrades
at
this
point
in
time,.
J
E
You've
earned
another
drink.
Okay,
any
other
questions,
all
right
we
are
here.
It
is
raining
like
kind
of
hard.
So
good
luck
getting
out
of
here,
you
could
have
another
drink.
You
could
have
some
more
food.
If
you
have
more
questions,
what
we
really
want
you
to
do
is
contribute
communicate
collaborate
with
each
other.
Apparently,
if
it
starts
with
the
letter
C,
that's
kind
of
what
we
do
now
with
events
like
theirs
contribute
commits
what
was
today
connect
write
whatever
I
mean
so
we'll
eventually
run
out
of
C
words
and
come
up
with
something
else.
E
E
E
Kyle
James
on
LinkedIn
he's
wide
open
for
a
meet
up
and
happy
to
share.
What's
going
on
at
Disney
and
we're
waiting
for
his
new
channel,
my
kids
paid
for
three
years
with
their
allowance.
They
just
keep
asking
me
when
is
it
coming
I'm
kidding?
So
this
is
just
another
tip.
If
you
ever
want
to
give
your
kids
an
allowance,
I
use
$2
bills,
so
they
can't
use
it
in
vending
machines
because
I'm
an
evil
dad,
but
anyways
yeah
here
comes
hatin.
B
We
decided
not
to
get
involved
in
the
get
led
meet
ups
because
we
want
the
community
to
draw
those
these
gitlab
connect.
Events
are
kind
of
the
equivalent
of
a
git
lab
in
sponsored
meetup.
So
that's
you
can
consider
this
kind
of
a
meet-up
but
they're
true
meetups,
pretty
much
run
by
the
gitlab
community.
So
we
we
generally
stay
hands-off
yeah.
E
There's
like
a
process,
I
have
one
I'm
setting
up
in
Minneapolis
for
my
customers
and
I'm,
letting
them
drive
it
and
own
it.
Like
we
just
kind
of
here's,
the
template,
you
go
we're
out
of
it
kind
of
situation.
So
Kyle
just
you
know
it
sounds
like
you
just
took
it
all
on
here
today.
It's
recorded
so
yeah.
E
E
Okay,
all
right
good
stuff,
any
other
questions,
comments,
feedback
all
right,
like
I,
said
we're
here
for
a
while,
there's
still
coffee
beer
wine.
Whatever
else
you
like,
thank
you
for
coming
out,
go
ahead
and
put
a
round
of
applause
for
yourself
for
coming
out
today.
Right,
you
skipped
out
on
work.