►
Description
In modern industry, every company has a software development organization that must develop websites, mobile apps and other software. Imagine a world where our systems’ software is updated; becoming liquid so that products and services are continuously updated without human intervention
Join Baruch Sadorgusky, Head of developer relations at JFrog as he walks you through JFrog’s origins and how JFrog set its mission to transform the way enterprises manage and release software updates; making making endless software versions a thing of the past - with liquid software that flows continuously and automatically from build all the way through to production.
A
A
Who
is
the
head
of
developer
advocacy
at
jfrog
and
very
happy
to
have
you
here
and
what's
interesting?
Is
today's
topic
is
going
to
be
all
about
what
is
liquid
software
so
baruch?
Thank
you
for
joining
us
here
today.
What
exactly
did
you
mean
when
you
titled
this?
What
is
liquid
software
because,
frankly,
I
want
to
know.
B
A
B
A
B
A
B
So
yeah
I've
been
with
jfrog
for
nine
and
a
half
years
almost
and
for
for
a
longest
time.
Most
time,
most
of
this
time
for
seven
years
I
was
the
only
person
in
in
official
developer
relations
capacity.
The
thing
is
developer
relations
that
everybody
do
it.
So
I
cannot
say
I
was
the
only
one
who
did
developer
relations
because
everybody
do
developer
relations,
whether
they
want
it
or
not,
whether
they
think
about
it
or
not.
In
the
end,
they
were
all
in.
B
We
all
affect
the
relationship
between
the
company
and
the
developers
and
the
users,
but
I
was
the
only
one
who
was
who
like
had
anything
to
do
with
developer
relations
in
their
title.
I
was
the
only
developer
advocate
now
we
grew
a
lot
and
we
have
an
entire
team
of
developer
relations
which
contain
different
roles,
not
only
developer
advocates,
but
also
community
builders
and
and
engineers
full-time
engineers,
and
that
deal
with
partners
integrations
and
user
experience.
A
A
B
A
When
we
get
to
go
finally
to
kubecon,
which
is
the
one
coming
up
in
la
which
hopefully
will
be
in
person,
I
think
everybody
should
swing
over
to
the
jfrog
booth.
They
honest
to
god.
They
have
the
best
quality,
t-shirts
and
they're
they're,
definitely
worth
wearing
and
not
turning
into
a
a
shop
rag
in
your
garage
like
most
of
the
other
ones.
A
B
Yeah,
the
company
is
actually
more,
the
company
itself
been
around
since
2009,
so
it's
12
years,
but
the
the
name
jfrog
is
even
it's
even
older.
It's
been
around
since
2006
when
the
first
version
of
a
art
factory
came
out
and
and
it's
interesting
how
every
time
you
have
some
kind
of
weird
name
or
a
fancy
name,
people
always
have
a
story
right.
So
the
one
that
I
keep
thinking
about.
It's
black
duck,
for
example.
B
So
when
we
asked
the
founders
of
black
duck,
they
told
us
a
very
touching
story
about
actual
duck
that
was
hurt
on
the
property
of
one
of
the
founders
and
he
was
a
young
kid
and
he
kind
of
nurtured
this
dog
to
to
to
health
and
everything
else
and
and
since
then
it's
kind
of
a
black
duck.
We
tried
to
come
up
with
a
story
in
in
in
hindsight
when
people
started
to
ask.
So
why
jfrog?
But
you
know
what
one
of
our
co-founders
in
french
and
they
have
a
weird
relationship
with
frogs.
B
They
eat
their
legs,
so
I
wasn't
sure
we
weren't
sure
if
we
can
come
up
with
something
that
will
be.
That
will
be
authentic
enough,
like
what
we're
gonna
say:
fred
ate
some
french
legs
frogs
and
legs,
and
this
is
why
it's
frog
doesn't
sound
so
good,
but
truth
to
be
told
when
we
just
started.
You
have
landman
another
co-founder
of
jeffrook
started
this
project
in
artifactory.
B
He
looked
for
a
name
for
kind
of
a
space
or
an
organization.
It
wasn't
a
company
like
that.
That
will
be
catchy
that
will
be
we
we
can
play
with
with
graphics
and
social
and
stuff
and
also
have
like
a
domain
and
a
twitter
handle
that
that
was
available.
Jay
back
then
really
stood
for
java.
That's
a
that's
a
right
observation,
because
the
software
we
were
all
before
before
jfrog,
we
were
all
in
the
java
consultancy
shop.
So
java
was
our
expertise
back
then,
and
artifactory
is
written
in
java
and
also
back
then.
B
The
only
thing
it
did
was
supporting
java
maven
build
tool,
obviously
a
lot
of
water
in
under
the
bridge.
Since
then,
now
it's
it's
incredibly
universal
support.
27
different
package
types
all
the
way
from
development
to
the
ops
concerns,
and
you
know
all
the
modern
programming
languages
and
also
all
the
package
tools
on
the
on
the
operating
system.
Side
and
the
new
services
in
the
jfr
platform
are
not
even
written
in
java
anymore,
but
but
yeah
jfrog
has
has
history.
A
A
People
can
ask
questions
for
baruch,
put
them
into
the
chat
down
below
and
they'll
magically
pop
up
over
here
onto
our
bridge,
so
we'll
be
able
to
address
them
and
and
we'd
like
to
we'd
like
to
challenge
everyone
to
this
is
called.
This
is
called
stump.
This
is
called
the
stump
the
baruch
hour.
I'm
told
that
there's
no
question
too
tough
for
baruch
and
anyone
who
can
stump
baruch
is
going
to
get
one
of
their
very
own
jfrog
t-shirts.
It
might
not
be
this
one,
but
we'll
definitely
get
a
2012
edition.
B
A
B
A
Okay,
no
problem,
so
first
great
question
from
me:
ow
just
bang
the
funny
bone,
perfect
timing,
so
you're
here
on
our
tv
show
the
open
shift
commons
briefings
operator
hours.
It's
not
a
mistake
right.
I
mean
your.
Your
technical
people
have
been
working
with
ours
to
test
and
certify
your
software
on
the
red
hat
portfolio.
It's
good
for
customers,
it.
You
know
it
sends
that
message
of,
like
you
know
the
reese's
peanut
butter
cup
moment
of
better
together
my
chocolate,
your
peanut
butter,
you
know
jfrog
and
open
shift.
A
Is
you
know
better
than
sliced
bread?
So
you
know
we
were
interested
in
helping
to
promote
your
company,
your
agenda
and
getting
visibility
for
your
products
on
top
of
our
portfolio.
What
is
you
know
your
open
source
story?
Yeah
I
mean
every
company
has
an
open
source
story.
You
know
I'm
I'm
at
re.
You
know
we're
at
red
hat.
We've
been
here
for
I've
been
here
for
since
2002,
so
I
guess
like
21
years,
you
know,
red
hat
has
a
pretty
solid,
open
source
story.
A
B
Right
so
we
started,
as
I
already
mentioned,
as
as
an
open
source
tool,
2006
artifactory
and
you
can
download
it
and
and
have
a
proxy
for
your
maven,
artifacts
and
maven
builds
since
then,
a
lot
of
time
passed
and
we
still
have
the
the
the
open
source
version
and
that's
obviously
the
most
downloaded
and
the
most
used
in
in
in
all
the
software
that
the
jfrog
provides
is
the
is
the
artifactory
open
source?
It's
still,
it's
still.
B
We
we
stopped
measuring
downloads
long
time
ago.
We
have
this
number
and
it's
in
the
millions
every
year
it
doesn't,
it
doesn't
mean
anything.
It
doesn't
mean
anything
just
because
you
know,
as
as
our
ceo
used
to
say,
my
grandma
can
download,
artifactory
and
and
he's
right,
but
but
it's
also
a
tool
which
is
a
part
of
a
lot
of
a
pipelines
and
tool
chains,
and
that
means
that
there
are
might
be
a
lot
of
robots
that
download
it
time
and
time
again
to
set
up
their
their
their
pipeline.
B
Yeah,
it
is
a
big
number,
it
is
a
big
number,
but
again
we
don't
know
why
we
don't
know
how
many
of
them,
using
it
and
being
like
honest,
open
source.
We
don't
really
know
a
whole
lot
about
those
users.
We
don't
have
any
you
know
call
home
or
they
don't
feel
any.
There
is
no
paywall,
so
they
just
go
ahead
and
grab
it
and
use
it.
And
then
this
is
the.
B
This
is
the
open
source
part
now
in
as
the
time
passed,
we
felt
that
first
of
all,
we
we
went
very,
very
cloud
native.
I
I
think
the
the
the
or
or
cloud
first
should
I
say
the
the
first
usage
that
you
think
about
how
do
we
use
jfrog
software
should
be
in
our
perspective,
you
use
it
in
cloud,
you
use
it
in
service,
you
select
the
right
cloud
and
we
support
all
of
them,
including
obviously
openshift,
and
you
select
the
right
region.
B
You
select
the
right
setup
and
then
you
just
consume
it
as
a
cloud
and
this
obviously
conflicts
with
this
downloadable
open
source
version
right,
because
downloadable
open
source
means
it's
not
as
a
service.
So
we
started
to
think:
how
can
we
maintain
the
accessibility
and
the
ease
of
use
of
the
open
source
version
just
download
and
use
it
with
with
the
cloud?
B
And
this
is
how
we
now
have
the
the
free
tier,
which
is
fully
blown
artifact
jeffrey
platform
for
whatever
it
is
cost,
if
you
buy
it
for
on-prem,
but
you
can
use
it
in
the
cloud
for
free
up
to
up
to
certain
limits.
So
this
is
kind
of
also
what
we
try
to
give
back
to
the
community
now,
since
we
have
that
and
it's
not
really
open
source,
because
it's
a
service
right.
B
The
question
is
okay:
how
do
we
keep
giving
back
to
the
open
source
community
because,
obviously,
all
of
our
software
uses
80
open
source
components
like
every
other
software
component
in
the
world
right?
We
use
everything
from
a
bunch
of
frameworks
and
and
and
libraries,
and
then
we
decided
we
want
to
give
on
top
of
free
tier
even
more.
B
A
I
wanted
to
to
basically
say,
though,
like
like:
what
do
you
guys
do
right?
I
mean
you've
been
there
for
nine
and
a
half
years.
You
know
what
you
do.
I
think
the
majority
of
the
people
out
there
understand
what
artifact
management
is,
but
maybe
not
right
so
like
what
is
it
that
jfrog
does
for
the
end
user.
B
From
this
point
onward,
we'll
run
on
jfrog
java
platform,
we
will
build
your
code
on
jfrog
pipelines,
which
is
our
ci
and
cd
tool.
Then
you
will
have
jfrogartifactory
as
the
backbone
of
your
pipeline,
and
you
will
take
this
artifact
test
it.
Whatever
this
test
is,
is
it
qa
security
licensing
performance,
whatever
you
will
test
it
and
when
you're
happy
with
it,
you
are
going
to
promote
it
to
the
next
repository
in
jeffree
factory,
the
tests
themselves,
the
security
and
the
licensing.
B
We
are
going
to
help
you
testing
your
dependencies,
your
third-party
dependencies,
both
for
security
vulnerabilities
and
for
license
compliant
using
jfrog
x-ray,
and
in
the
end
of
the
day
we
again
with
j4
pipelines,
the
cd
part
of
it
will
deploy.
Your
will,
distribute
your
application
to
whatever
the
end
compute
is.
B
If
it's
openshift
it
will
be
deployed,
the
containers
will
be
deployed.
If
it's
internal
distribution,
it
will
replicate
to
the
right
instances
of
jeffree
artifactory
for
other
developers
to
use
if
it's
edge
computing,
it
will
be
delivered
to
artifactory
edge
and
then
using
p2p
to
the
to
the
compute
itself.
Whatever
the
distribution
is,
we
will
take
care
of
distribution
as
well,
so
everything
from
source
to
the
runtime
we
can
help
you
deliver
faster.
B
A
When,
when
when
I
started
here
in
2002,
I
was
a
solutions
architect
and
they
were
one.
I
was
one
of
five
in
the
whole
company
and
you
know
we
would
travel
all
around
the
world
and-
and
I
would
you
know,
be
going
and
going
you
know-
I
do
a
tour
through
singapore
and
then
over
to
japan
and
make
my
way
back
or
maybe
to
go
through
australia
or
whatever,
but
we
we.
Actually.
A
They
wanted
to
be
in
the
business
of
focusing
on
their
core
business,
which
was
whatever
commercial,
banking
or
building
the
best
tennis
shoes
or
whatever
it
was
so.
I
I
totally
get
it.
You
know
early
on
in
new
technologies,
there's
always
people
who
are
like
I'm
gonna.
Do
it
myself,
I'm
going
to
you
know,
but
you
know
having
people
like
jfrog
who
are
like
you
know,
just
use
our
tooling
and
then
you
guys
go
focus
on
your
core
business
makes
a
lot
of
sense.
A
B
A
Okay,
so
howard
how's
business-
I
mean
you
guys
have
one
of
the
best
t-shirts
around
you've
got
a
tremendous
amount
of
momentum.
You
know,
there's
a
lot
of
you
know
art
being
written
about
jfrog
but,
like
you
know,
how's
business,
are
you
know?
If
you
look
at
companies
that
were
trending,
you
know
take
docker,
for
example,
docker
the
company,
not
docker
the
technology.
You
know
they
were.
A
You
know
the
shiny
object
for
years.
You
know
docker
docker,
docker,
docker
docker
and
you
go
to
dockercon
and
you
know
docker
had
this
huge
booth,
but
they
weren't
really
able
to
convert
that
into
a
viable
business.
So
is
jfrog
just
a
lot
of
hype.
Do
you
guys?
Just
have
you
know
nice?
You
know
purple
backgrounds
and
and
frogs
on
shirts,
or
are
you
folks
actually
becoming
a
dominant
player
out
there
that
that
customers
can
really
rely
on
to
run
to
help
run
their
business.
B
We
went
public
about
half
a
year
ago
and
I
think
not
that
I'm
a
big
expert.
It
was
a
successful
ipo
so
and
and
and
today
when
people
think
about
artifact
management,
they
think
about
either
jfrog
or
jfrog
artifactor
in
particular.
So
I
think
this
this
question
has
been
answered
profoundly
in
the
last
at
least
five
six
years
and
the
most
interesting
answer
to
that
is
that
now
everybody
are
doing
it,
and
I
remember
back
in
the
day
the
whole
concept
of
artifact
management
was
met
with
a
lot
of
skepticism.
B
Why
do
you
even
care
about
the
binary
artifacts?
I
mean
you
have
your
source.
This
is
the
most
important
thing
you
have
it
in
your
subversion
and
you
can.
If
you
need
like
a
you,
just
build
it
and
put
it
in
production
done.
There
is
no.
There
is
no
artifact
to
manage
and
we
along
other
players
in
the
industry,
I
would
say,
defined
this
domain
of
artifact
management,
defined
it
with
with
a
lot
of
sweat
and
blood.
B
But
in
the
end
of
the
day
today,
it's
something
that
you
you,
you
install
jeff
roger
to
factory
or
you
get
a
service
versus
jeffrey
to
factory
as
the
prerequisite
for
doing
anything
together
with
your
github
account
and
whatever
you
want
to
use
for
a
for
continuous
integration
and
your
runtime
platform.
This
became
a
standard
in
how
you
develop
software,
and
this
is,
I
think,
the
biggest
change
that
that
happened
in
the
last
decade
and
in
our
in
our
corner
of
the
industry.
B
A
B
The
other
yeah,
so
so,
if
you
ask
me,
I'm
I'm
not,
I'm
obviously
not
very,
very
biased,
and
I
I
will
obviously
argue
that,
yes,
obviously
we
are
the
best.
There
are
some
objective
reasons
to
use
jfrog
comparing
to
to
to
others,
and
one
of
the
reasons
that
me
personally
is
very
important.
I
I
find
it
very
important
is:
I
will
give
you
maybe
three
reasons:
real
quick.
The
first
is
universal.
B
Whatever
technology
you
want
to
use,
jeffree
platform
will
support
it,
and
this
is
very
important
because
we
don't
want
to
dictate
you
as
being
just
a
part
of
your
pipeline.
We
don't
want
to
dictate
you
how
you
write
your
code,
how
you
build
your
code?
What
stack
are
you
running
with?
What
is
your
deployment
target?
What
cloud
you
want
to
use?
B
One
of
the
reasons
why
the
shift
from
hey-
I
just
have
a
source
code,
and
I
build
it
and
throw
it
in
production
actually
happened
to
hey.
I
need
to
manage
my
artifacts
is
the
understanding
of
the
industry
that
there
are
tons
of
questions
that
you
might
have
to
answer
about
your
artifacts
in
any
point
of
life
before
you
deploy
it
during
the
pipeline
after
you
deploy
it?
B
When
you
operate
it
when
you
monitor
it,
the
more
you
know
about
your
artifacts
the
better,
and
this
is
why
we
in
jeffrog
pour
tons
of
effort
into
getting
you
as
much
metadata
about
your
artifacts
as
possible,
how
they
were
created
from
what
sources,
using
what
tools
in
which
point
how
the
promotion
went.
What
decisions
did
you
make?
Why
did
you
make
those
decisions
who
made
those
decisions?
B
This
is
something
that
also
becomes
very,
very
relevant
kind
of
the
same
of
the
first
one.
We
want
to
support
you,
whatever
your
right.
Topology
is,
but
not
only
for
your
stuff,
but
also
for
our
staff
as
well
the
cloud
being
cloud
first
and
starting
the
conversation
with
hey
here's,
the
service
just
use.
It
is
obviously
great
and
important,
and
that's
another
advantage
over
some
of
our
competitors,
but
also
being
able
to
recognize
hey.
You
want
it
on
prem.
Here
you
go
you
we
have
that
as
well.
B
A
A
It
can't
be
anything
like
do
you
think
it's
going
to
snow
this
weekend
and
actually,
by
the
way,
speaking
of
snow
this
weekend
tomorrow,
we're
getting
eight
inches
during
the
day
and
another
three,
so
we're
getting
11
inches
of
snow
tomorrow
night,
but
any
any
interesting
questions
that
are
not
about
how
much
snow
mike
wait's
getting
at
his
at
his
summer.
House
drop
them
in
chat
there
and
we
will
ship
a
shirt
off
to
you.
A
A
So
what
about
you
know
what
about
kubernetes
and
you
know,
are
like
this
is
one
of
the
questions
we
talked
about
when
you
and
I
were
going
over
this
concept
of
doing
the
show
a
couple
weeks
ago.
You
know
like
it's
sort
of
like.
Are
we
there
yet,
like?
I
said
I've
been
here,
I'm
as
old
as
dirk
I've
been
here
since
when
red
hat
had
260
employees-
and
you
know
there
was
you
know,
linux
was
hot.
You
know
way
back
in
the
day
and
then
it
became
you
know.
A
Virtualization
with
zen
and
kvm,
and
vmware
sort
of
you
know
ran
away
with
the
ran
away
with
with
that
one,
you
know
then
openstack
became
like
the
big
hot
topic
and
it
was
like
the
openstack
conference
and
everyone
was
flying
around
those
were
hosted.
You
know
what
were
they
two
two
times
a
year
and
portland
tokyo
all
over
the
place,
then
that
kind
of,
like
just,
became
this
little
niche
thing
for
telco,
and
then
there
were
containers
and
it
was
like
docker
docker
docker
docker
containers
aren't
really
new
right.
A
I
mean
containers
have
been
around
for
as
long
as
me.
Right
I
mean
there
was
solaris
zones,
they
had
containers,
just
people
couldn't
figure
out
how
to
use
them
or
manage
them,
and
then
you
know,
containers
kind
of
stopped
being
the
focus.
Now.
It's
kubernetes
right,
kubernetes,
kubernetes
connections
and
you
know
orchestration
management
and
everybody
was
trying
to
get
in
on
this
game
kind
of
like
the
openstack
thing
right.
This
technology
shows
up
and
there's
like
20
different
vendors
and
everyone's
going
to
become
the
openstack
vendor.
A
A
Do
you
think
that
that
where
we
are
now
baruch
is
just
another
sparkly
moment,
and
do
you
think
that
that,
like
all
this
hype
and
everyone's
getting
ready,
we're
going
to
go
off
to
kubecon
in
los
angeles
in
october
and
everyone's
going
to
go,
get
their
new
j,
frog
shirt
and
two
years
from
now
we'll
be
sitting
there
saying
wow
man
remember
that,
like
we
all
thought
like
kubernetes
was
like
the
end
game
and
now
we're
off
on
to
you
know
you
know
name
your
like.
Are
we
there?
B
B
B
Containers
are
not
exactly
build
on
virtualization,
but
learned
a
lot
from
virtualization
kubernetes
exists
because
of
containers,
etc,
etc.
So
I
don't
think
those
are
kind
of
things
that
we
play
with
and
this
and
then
throw
away
those.
Those
are
the
things
that
we
play
with
and
then
take
it
to
the
next
level
and-
and
this
trend
will
obviously
continue.
B
B
A
B
A
B
A
This
is
this
is
my
this
is
my
I
just
I
watched
I
watched
the
the
the
tonight
show
with
jimmy
fallon
last
night.
I
don't
know
if
anyone
watched
that,
but
it
was,
it
was
hilarious.
You
know
he
does
these
things
where
he
has
people
zoom
in
from
their
house
showing
off
their
talent,
and
there
was
like
one
woman
was
like.
I
can
sound
like
a.
I
can
sound
like
a
seagull.
She
was
actually
calling
in
from
like
spain
or
something
anyways.
So
this
is
our
buzzword,
bingo,
victor
fictioner
fact,
microservices
and
serverless.
B
Instead,
there
are
diff,
more
important
aspects
like
the
api
centric,
the
serviceability,
the
being
able
to
the
resilience,
the
scalability
and
others
which
are
much
more
important
traits
of
microservices
than
the
fact
that
they
are
micro,
but
it's
definitely
a
thing
that
the
architecture
this
the
microservice
architecture
is
one
of
the
cornerstones
of
being
a
cloud
native
which
is
probably
another
one
on
your
list
we'll
get
to
it
soon.
Serverless.
B
B
A
B
Yeah
again
cloud
native
is
is
a
fact,
and
the
name
in
this
one
actually
annoys
me
a
little
bit
less,
although
maybe
it's
still
not
perfect.
For
me,
cloud
native
is
a
collection
of
patterns
and
microservices
architecture
being
one
of
them
that
actually
makes
the
application
run
better.
I
would
say
on
the
cloud:
it's
it's
more
suited
for
the
cloud
and
when
I
say
the
cloud,
that's
where
the
problem
with
the
name
is,
it
doesn't
necessarily
have
to
be
in
the
cloud.
B
It's
just
a
set
of
practices
of
how
we
treat
software.
The
fact
that
you
know
it's
observable
and
we
can
scale
it
and
we
can
replace
parts
of
it
as
as
it
moves,
and
we
can
commission
and
decommission
and
recommissions
part
of
it.
So
it's
it's
again
set
of
practices
that
makes
our
software
better
and
the
fact
that
we
kind
of
came
into
this
conclusion
through
the
cloud
is
is
secondary,
but
it's
stuck
in
the
name.
A
Okay-
and
you
know
the
the
whole
microservices
thing
I
wanted
to
bring
that
up
because
we
had,
we
did
a
show
a
couple
weeks
ago
and
we
were
talking
about
microservices
and
the
the
partner
of
ours
that
was
on.
You
know,
made
an
api
gateway
and
a
service
mesh
offering
and-
and
I
I
believe
that
you
know
that
type
of
tooling
is
going
to
be
absolutely
mandatory,
as
containers
do
get
smaller
and
smaller
and
smaller
and
smaller
and
smaller
over
time.
It's
like
trying
to
manage
an
infinite
number
of
galaxies.
A
But
then
again
it
was
someone
in
the
government
space,
so
they
probably
have.
They
probably
have
very
weird
internal.
You
know
reasons
for
doing
that.
So
what
about
you
know
for
18
months
out?
You
know
we
were
talking
about.
Are
we
there,
you
know
is:
is
kubernetes
the
container,
the
openstack,
the
linux
of
the
day?
You
know:
where
do
you
see
computing
being
in
in
18
months?
Our
container
is
going
to
be
tiny.
Is
the
service
mesh?
You
know
offerings
going
to
be
something
that's
going
to
be.
A
B
B
How
can
we
make
sure
that
this
cluster
operates
correctly,
when
actually,
they
run
different
types
of
different
versions
of
software?
There
are
very
a
lot
of
very
interesting
engineering
challenges
that
come
with
the
edge
problem
space
and
it
will
definitely
impact
of
how
we
develop
our
software
for
the
for
the
better.
A
Okay,
we've
got
12
minutes
left
and
I
I
know
that
we
wanted
to
talk
about
some
aha
moments
and,
or
you
know,
war
stories,
you're
you're
really
well
plugged
into
your
business
you're.
Obviously
you
know
being
head
of
the
developer
advocacy.
You
know
team
there
at
at
jfrog.
You
probably
have
heard
a
lot.
Can
you
you
want
to
tell
us
about
some
aha
moments
or
some
some.
You
know
war
stories
that
you
wanted
to
share
with
people.
B
B
Obviously,
we
have
software
that
solves
a
real
world
problem
right.
I
speak
with
people.
I
hear
what
problems
they
try
to
sell
to
to
solve.
I
see
how
our
software
clearly
answers
this
need
and
I
explain
to
them
how
it
helps,
and
this
is
where
I
expect
rational
human
beings
to
think
about,
and
they
say
yeah.
You
know
what
baruch
you're
right.
This
software
is
going
to
make
our
life
easier,
and
this
is
my
aha
moment-
and
this
is
what
I
take
back
to
the
business
and
say
hey.
B
I
need
to
look
for
some
software.
That
will
help
me
doing
it,
and
you
know
what
I
remember
baroque
mentioned
something
about
jeffrog.
Let
me
check
it.
Oh,
it
fits
and
then
what
a
great
idea,
but
that
was
the
idea
of
this
individual,
very,
very
rarely
they
will
come
back
to
me
and
say:
hey
baruch,
remember
this
conversation
that
we
had
you
were
right.
B
Jfrog
is
what
I
actually
need,
and
now
I'm
starting
using
it
most
of
the
time
it
will
be.
Like
hey
baroque,
you
tried
to
push
me
this
jeff
rock
stuff.
When
I
didn't
need
it,
it's
good
that
I
then
kind
of
refused
to
use
it
because
I
didn't
need
it
then
now
the
situation
is
completely
different
and
I,
by
myself
came
to
the
conclusion
that
jeffrey
is
the
right
thing
to
do
so.
I
did
it
and
it's
not
kind
of
your
your
achievement.
B
If
you
wish
and
that's
okay,
I
mean
I
really
don't
mind
as
long
as
in
the
end
of
the
day,
people
come
to
the
same
conclusion:
it's
it's
completely
fine
and
more
of
everything.
It's
the
aha
moment
for
me
that
you
really
cannot
push
the
solution
into
a
throat
of
other
people,
even
if
this
is
objectively
the
right
way
for
them
to
do.
This.
Realization
should
really
come
internally
and
I
think
there
is
a
movie
about
that
called
inception.
This
is
what
I
like
to
think
about.
The
developer.
B
A
Sure
yep,
let's
talk
about
swamp
up,
it's
it.
I
went
there
once
it
it's
it's
a
developer.
It's
the
people's
show,
as
opposed
to
like
bankers,
walking
around
people
carrying
suits
and
bags
and
stuff
right.
I
know
it
was
at
it
was
at
a
it
was
at
a
winery
in
santa
barbara
about
four
years
ago.
Do
you
remember
that
one
yep
yeah
it?
I
went
there.
A
Yeah,
it
was
at
some
some
winery.
It
was
really
cool
yep.
What
you
know
for
people
who
go
and
and
again
it's
not
a
customer
conference.
It's
not
people
carrying
you,
know,
suitcases
and
you
know
like
briefcases
around.
You
know
what
what's
the
overall
experience
at
swamp
up?
It's
it's
coming
up
here
in
the
in
the
not
so
distant
future,
and
this
this.
This
is
your
chance
to
put
in
that
gratuitous
plug
for
you
for
your
event
here,
because.
B
Yeah,
so
thank
you
for
for
building
it
up
like
officially
and
and
yeah
so
swamp
up
is,
is
a
user
conference
as
opposite
to
a
customer
conference,
as
you
mentioned,
and
that
our
users
are
developers
our
ops
people
are
engineers
in
the
end
of
the
day,
so
this
is
the
conference
for
them
and
what
I
have
the
honor
to
be
the
head
of
the
content
committee
for
the
last
six
swamp
ups.
There
were
six,
so
all
all
of
them
and.
A
B
Absolutely
mike
absolutely,
you
will
have
to
wait
for
it
for
for
next
year,
because
this
year's
agenda
is
already
built.
But,
yes,
I
expect
you
to
submit.
I
also
have
a
very
sweet
spot
for
for
for
speakers
from
redhead
and
chris
one.
Let
me
lie
on
this
one.
So
yeah
we
try
to
make
the
content
useful
for
engineers.
That's
that's
our
main
goal.
B
We
have
an
amazing
events
team
and
their
main
goal
is
to
make
it
fun
and
pleasurable
for
for
everybody
attending
a
one
when
we
could
do
it
in
real
life.
Four
conventions
out
of
five
took
place
in
the
winery
in
napa,
and
that's
because
we
started
to
drink
wine
in
the
morning
and
we
actually
never
stopped.
B
So
yeah,
yeah
and
and
this
year
it's
it's,
unfortunately
still
still
online.
It's
going
to
be
awesome
conference,
but
you
have
to
bring
your
own
wine.
Hopefully
next
year
we'll
be
able
to
meet
again.
I
hope
it
will
again
be
in
in
napa
in
a
winery
with
this
amazing
experience.
Talking
about
content
this
year
was
really
hard.
We
got
more
than
150
submissions,
for,
I
think,
like
a
27
slots,
it
was.
B
A
Okay,
we
have
just
a
couple
minutes
left
what
what
is
the
the
one
thing
that
you
should
be
sharing
with
people
that
are
watching
live
today
and
also
for
the
ones
that
are
going
to
be
watching
the
recordings
on
youtube
and
linkedin
and
so
forth
that
you
know
after
we
hang
up
here,
your
your
major
or
your.
You
know
your
cto
isn't
going
to
call
you
and
say:
baruch.
You
had
an
hour
to
talk
about
anything.
You
wanted
around
architecture,
man,
art
fact
management,
and
why
didn't
you
talk
about
the
following
two
things?
B
A
B
And-
and
this
is
something
that
I
really
want
to
treat-
that
the
viewers
of
of
our
show
on
top
of
t-shirts,
the
the
concept
of
liquid
software
was
explained
in
a
book
with
the
same
name,
liquid
software
that
was
written
by
two
co-founders
of
jfrog,
your
fred
simon.
You
have
lanman,
and
yours
truly-
and
I
want
to
give
this
book
for
whoever
wants
to
get
it
for
for
free.
B
I
will
make
sure
to
ship
a
physical
hard
copy
to
whoever
contacts
you
mike
or
contact
the
show
through
whatever
and
whatever
channels
you
you,
you
feel
right,
and
you
can
also
dm
me
on
twitter.
I'm
edubarok
on
twitter
and
my
dms
are
open.
Pinned
me.
I
will,
I
will
ship
your
book,
so
you
will
be
able
to
learn
more
about
liquid
software.
A
A
B
B
A
A
No,
no
that's
fine,
but
but
to
just
rehash
anyone
who
wants
a
copy
of
baruch's
new
book
liquid
software
shoot
me
an
email
just
wait
at
redhat.com,
w-a-I-t-e,
redhat.com
and
we'll
be
sure
to
get
a
copy
of
his
latest
book
out
to
you.
We
are
coming
up
on
the
end
of
the
hour,
so
I'm
gonna
do
what
I
like
to
call.
A
A
Baruch
sidorsky,
nine
and
a
half
years
at
jfrog.
You
know
well
entrenched
even
before
that
with
the
other
founders
of
the
company,
thanks
for
thanks
for
being
on
our
show
here
today,
I'm
really
hoping
that
we
can
do
a
podcast
with
you.
We've
got
a
red
hat
x,
podcast
series
that
we
do
two
or
three
shows
a
week.