►
From YouTube: Building secure, cloud native apps - Open Source Friday
Description
Discover the magic of container slimming -
✨Smaller footprint
✨Enhanced performance
✨Fortified security
Join Nnenna Ndukwe on Friday, June 2nd at 1 pm ET to unlock the incredible benefits of Slim.AI!
A
A
A
A
It's
basically
a
stream
that
we
do
every
Friday
talking
to
different
maintainers
core
contributors
or
developer
Advocates
within
the
open
source
space
about
their
projects,
to
learn
more
about
like
how
we
can
get
involved
into
open
source
and
to
learn
more
about
their
Journeys
as
well.
If
my
Wi-Fi
is
a
little
bad
I
apologize
or
if
there's
like
noise
in
the
background,
I
am
at
a
conference
right
now
and
I
tried
so
hard
to
find
like
a
quiet
space,
but
it
wasn't
that
easy.
A
Oh
just
saying,
hi
to
some
people
in
the
chat
I
see
Laura
thanks
for
tuning
in
Laura
we
have
some
people
saying
they're
tuning
in
from
San
Diego
and
India
I
always
like
to
highlight
them.
But
enough
talking
about
me,
we
have
a
specialist
today
and
I
would
love
for
her
to
introduce
herself
hello.
B
How
are
you
doing
so
I'm,
Nina
Nina
and
jukui
and
I'm
a
developer
Advocate
at
slim,
AI.
A
Nice
awesome
and
like
y'all,
don't
know,
but
nana
and
I
go
go
way
back.
We
went
to
the
same
coding
boot
camp
together
and
it's
been
a
crazy
Journey.
Now
we're
both
developer
Advocates.
Do
you
want
to
talk
just
a
little
bit
about
your
your
journey
into
Tech
or
or
even
into
Deborah?.
B
B
We
have
histories
studying
computer
science
together
at
bu
at
one
point
but
yeah
my
journey
really
began
when
I
started
like
teaching
myself
how
to
code
before
joining
the
coding,
bootcamp
and
then
straight
after
that,
I
you
know
launched
into
fintech
startup
company
then
was
in
edtech
at
O'reilly
media
and
then
found
my
way
into
the
cloud
native
space
now,
which
is
like
super
new
to
me
and
really
exciting,
so
started
off
as
a
curious
person
who
wanted
to
learn
how
to
code
became
the
software
engineer,
and
then
you
know,
along
that
Journey
I'd
always
like
documenting
my
experiences
like
I
would
document
like
the
things
I
was
learning
at
coding,
bootcamp
and
things
like
that
through
writing
and
content
creation,
and
involving
myself
in
the
local
and
Global
Tech
ecosystem
by
speaking
on
panels,
and
so
I
was
like.
B
You
know
it
would
be
super
cool
I'm
doing
this
in
my
free
time
for
free,
wouldn't
it
be
awesome
to
actually
do
this
as
a
part
of
my
job.
How
can
we
combine
the
technical
side
of
myself
and
the
creative
side
and
then
that's
when
I
did
a
little
digging
and
found
out
that
developer
advocacy
was
a
thing
and
I
was
like
this?
Is
a
dream
come
true?
It's
a
little
scary
that
this
is
even
possible
and
so
yeah
here
I
am
I
found
my
way
into
a
slim
Ai,
and
it's
been
awesome.
A
I
love
it
I
love,
it
I
feel
like
a
lot
of
people
fall
into
the
Deborah.
Similarly,
where
they're
like
I
I,
like
coding,
I,
was
curious
about
coding,
but
I
want
to
be
able
to
like
learn
like
I
want
to
be
able
to
connect.
My
other
skills
with
this
Laura
said
the
career
change.
A
The
career
changer
to
developer
advocacy
pipeline
is
so
real.
Me
too
I
feel
that,
but.
A
B
B
How
can
we
make
containers
more
secure
and
in
turn,
how
can
we
reduce
the
amount
of
vulnerabilities
in
containers,
make
them
more
secure
and
then
make
them
smaller,
and
those
could
be
like
the
the
product
of
that
could
be
the
best
version
of
your
container
image
to
ship
to
production,
and
so
that
is
what
slim
toolkit
allowed
for
people
for
a
developers,
devops
folks
to
do,
and
then
from
that
open
source
project
that
stemmed
into
the
the
foundation
for
the
platform
that
we've
built,
which
is
super
exciting
and
slim
toolkit,
was
recently
accepted
into
the
cloud
native
Computing
foundation
cncf.
B
And
so
it's
a
project
there
and
there's
many
contributors.
So
that's
how
it
started
and
that's
where
we're
at
now
is
this
sort
of
a
SAS
platform,
as
well
as
the
command
line
interface
and
a
Docker
desk
top
extension
that
allows
developers
to
easily
optimize
their
containers
and
make
it
more
secure
and
then
ship
that
to
production.
A
That's
awesome,
I
didn't
know,
y'all
had
so
much
going
on
in
addition
to
getting
into
the
the
cncf
ecosystem.
That's
really
awesome.
Just.
A
So,
for
me,
like
I,
want
to
just
so
for
me:
I,
don't
really
when
people
say
cloud
native
I,
don't
really
know
what
they
mean
like
so
I
was
just
curious
like
if
you
would
be
able
to
explain
it
like
in
your
own
words
or
what
from
you,
what
you've
understood
as
Cloud
native
to
be
because
I'm
like?
Is
it
just
like
a
Cloud
app
like
I?
Don't
really
know
what
they
mean
when
they
say
cloud
native.
B
Yeah
I
like
to
think
of
it
as
like,
using
resources
or
computational
resources
that
are
not
necessarily
from
you,
but
from
other
places
like
Microsoft,
Azure
or
AWS.
So
that's
like
that's
as
simple
as
I
can
put
it.
It's
like
a
software,
that's
using
these
resources
from
other
other.
You
know,
companies
or
you
know
things
like
that.
So
that's
how
I
like
to
describe
it,
and
maybe
that's
too
simple.
B
Maybe
that's
not
maybe
that's
not
technical
enough,
but
sometimes
it's
good
to
keep
it
in
very
high
level
when
you
think
of
it
just
to
help
you
like
process
what
it
is,
but
yeah,
it's
a
it
was
it's
a
new
space
for
me,
I
would
say
so
like
when
I
started,
learning
about
it,
I'm
I'm,
very
new
to
it
so
I'm
kind
of
approaching
it
as
that
like
explain
it
to
me,
like
I'm,
five,
that's
kind
of
the
stage
I'm
in
which
I
think
is
a
very
like
interesting
perspective,
especially
being
especially
when
people
are
slowly
or
actually
very
rapidly
getting
into
the
space
and
a
lot
of
the
experts
in
this
space
still
have
questions
too
about.
B
You
know
how
containers
really
work,
and
you
know
Docker
and
files
and
all
of
this
stuff.
So
it's
really
exciting
to
be
in
this
and
to
learn
as
much
as
I
can
from
people
who
are
also
still
trying
to
learn
so
much.
A
Yeah
no
I
actually
I
liked
your
explanation.
It
was
simple
something
I
could
follow,
rather
than
using
a
whole
bunch
of
words
thanks
for
asking
this,
and
she
also
said
like
that
makes
so
much
more
sense
now.
So
we
appreciate
it.
A
So
what
like,
what
attracted
you
to
because
I
usually
ask
maintainers
like
why?
Why
were
you
inspired
to
like
build
this
product,
but
I
know
you're,
not
the
maintainer
of
the
product,
so
like
What
attracted
you
or
inspired
you
to
be
like
you
know
what
I
do
want
to
like
get
into
this
space
because
I
know
you
said
you
came
from
edtech
and
other
like
Industries
and
then
I
know
you're,
like
I
know,
you
have
like
a
front-end
developer
background.
Yes,
yeah.
B
Yeah
I
feel
like
so
when
I
was
learning
about
anything
related
to
Cloud
native
or
containers.
I
thought
that
this
particular
concept
this
product
of
how
can
we
make
it
smaller?
How
can
we
make
it
more
secure
to
me
that
seemed
like
a
really
good
Mission,
especially
hearing
more
and
more
about
how
devops
engineers
and
developers
really
struggle
to
manually.
B
There's
this,
like
General
sentiment,
that
it
is
hard
to
remove
vulnerabilities
from
containers,
and
sometimes
there
are,
when
you're,
trying
to
get
something
out
to
production
you're
trying
to
ship
something
of
depending
upon
the
industry
that
you're
in,
if
it's
pretty
strict
right,
that
your
ability
to
shift
to
production
is
going
to
be
blocked
because
maybe
there's
some
major
vulnerability.
That
puts
your
platform
at
risk
and
puts
your
customers
at
risk.
So
I
think
the
mission
of
removing
vulnerabilities
manually
is
what
people
to
typically
do
most
devops
Engineers.
Do
that's
really
hard?
A
I
I
love
that,
like
it
is
focused
on
security,
because
I
think
that
is
something
that
developers
May,
sometimes
throw
under
the
rug
or
whatever,
though
like
it's
too
hard
like
every
like
it's
too
much
fuss,
at
least
at
the
startups
I've
been
at
because
I'm
not
I've
not
been
at
like
Enterprise
companies
that
are
like
this
is
going
to
be
blocked,
like
I've,
often
been
at
companies
where
they're
like
we're
just
gonna
ship
it
like
who
cares
like
we'll
deal
with
it
later
and
then
that
gets
thrown
under
the
rug,
and
then
it
puts
companies
in
a
vulnerable
state.
B
I
totally
agree,
and-
and
it's
interesting
like
thinking
about
that
from
like
the
developer
perspective,
it's
like
I,
don't
want
anything
to
slow
me
down.
I
want
to
be
able
to
shift
fast,
build
fast,
break
things
and
fix
it,
and
just
keep
moving
like
iterate,
so
I,
one
of
the
big
things
that
I
want
to
do
more
of
as
a
developer.
Advocate
is
kind
of
explain
more
to
the
everyday
developer.
How
important
security
is
and
how?
How,
when
you
pay
attention
to
it,
don't
see
it
as
something
that
is
going
to
slow.
B
You
down,
see
it
as
when
you're
leveraging
the
tool
that
was
built
off
of
explain
toolkit
right,
then
you
are
able
to
actually
speed
up
your
development
process
and
you're
able
to
do
more
and
build
more
and
build
it
safer.
So
that's
an
angle
that
I
really
want
to
attack
more
just
to
like
bring
awareness
to
that.
A
I
love
that
no,
that
that's
that's
a
really
good
goal
s
so
I,
don't
know
if
you're,
oh,
actually,
yeah,
if
you're!
Okay,
do
you
want
to
quickly
switch
over
to
giving
us
a
demo
or
some
kind
of
explanation,
so
we
can
visually
see
it
because
I'm
excited
about
like
the
tooling
that
it
has,
and
it
makes
a
ton
of
sense
to
me.
Yeah.
B
Yeah
it's
my
is
my
screen
shared
right
now.
Can
you
see
the
GitHub?
Yes,
repo,
okay,
so
yeah
we're
in
the
slim
toolkit
repo
and
here's
a
little
bit
of
an
explanation
of
kind
of
what
I
was
just
talking
about.
You
can
optimize
your
experience
with
containers
make
them
smaller.
This
is
open
source.
B
It
was
created
by
Kyle
Quest,
who
is
the
CTO
here
at
slim
Ai,
and
then
we
kind
of
give
a
very
detailed
overview
of
the
different,
the
you
know,
the
explanation
of
how
it
all
works
and
the
different
commands
that
you
can
leverage
and
then
this
graphic
I
think
is
very
useful
to
kind
of
describe
how
the
thing
works.
B
Once
I'm
done
explaining
this
graphic,
then
I'll
go
into
the
platform
form
and
you
can
see
how
things
look
visually
like
the
vulnerabilities
and
a
comparison
between
the
you
know,
a
Public
Image
like
nginx,
for
example,
and
then
the
slimmed
version
of
that.
So
you
can
see
what
what
all
of
that
looks
like,
but
this
graphic,
yes,
what
yeah.
So
if
that
sounds
cool,
that's
what
we
can
do
totally
totally
good
sorry!
So
oh
no
worries
this.
B
So
this
graphic
kind
of
explains
how
the
process
of
slimming
what
we
do
is
we
can
take
your
container
right.
You
can
pull
down
your
container
and
what
we
do
is
we
inject
sensors
into
your
container,
and
we
call
that
an
instrumented
version
of
your
container.
What
these
sensors
are
going
to
do
is,
when
you
run
your
container
image
right,
we're
going
to
collect
all
of
the
intelligence,
everything
that
we
find
out,
that
your
container
needs
in
order
to
run
smoothly
safely
in
production,
and
it
through
testing.
B
All
of
that,
then,
once
you
stop
your
container,
we
are
able
to
take
that
sensor
data
and
on
our
platform,
we're
able
to
show
you
how
the
the
hardening
process,
when
you
harden
the
container,
we're
able
to
build
a
new
version
of
your
container
that
has
a
removed
a
bunch
of
the
unnecessary
files
and
packages
from
your
container,
and
so
that
ends
up
removing
vulnerabilities
and
making
it
smaller.
So
that's
kind
of
what
this
graphic
describes,
and
this
is
what
it
looks
like
on
the
platform.
B
So
this
is
kind
of
like
the
home
page
of
the
platform.
It
lays
it
out
pretty
generically
for
you
just
to
get
an
idea.
It's
like
a
three-step
thing.
Connection
registry
will
run
our
vulnerability
scanners.
We
have
multiple
open
source
scanners
that
we
leverage
to
give
you
an
assessment
of
the
vulnerabilities,
the
packages
that
are
in
in
your
container
and
then
we
take
you
through
the
vulnerability
removal
process
by
hardening
and
securing
your
container.
So
what
I
love
about
this
is
that
we're
able
to
connect
to
different
Registries
everybody's
using
something
different.
B
We
want
to
be
able
to
accommodate
as
many
folks
as
we
can.
That's
why
you
see
Docker
Hub
here
as
I
see
GitHub
here,
hey
digitalocean,
Google
AWS,
all
of
that
fun
stuff
down
here.
This
is
my
own
profile
down
here.
You
can
see
that
I
have
connected
I've
hooked
up
my
own
GitHub
and
as
well
as
Docker
Hub
to
to
the
slim
platform.
B
I,
don't
know
if
you
could
see
this
really
well,
but
right
here
you
can
see
the
nginx,
so
I
was
able
to
on
the
platform
you
can
search
for
public
images
or
you
can
use
go
into
your
own
private
images
that
you'll
have,
but
you
can
copy
over
the
public
images
into
your
own
registry
and
then
take
a
look
at
what
it
looks
like
so
I'm,
looking
at
the
nginx
latest
version
of
nginx
and
I
get
a
summary
of
all
of
like
the
vulnerabilities
and
their
different
risk
levels
and
what's
going
on
in
the
packages,
I
can
take
a
look
at
files
and
you
know
all
of
the
metadata
that
I
need,
and
this
is
the
information
that
I
think
really
empowers
you
to
discover
what
how
what
the
before
is
of
a
container
image
that
you
want
to
use
for,
building
an
app
and
then
the
after
and
here's
is
the
comparison.
B
I
don't
know
if
this
is
a
little.
Is
that
better.
B
Awesome,
so
this
is
a
an
overview
of
a
comparison
of
the
latest
version
of
nginx
and
the
slimmed
version,
so
this
is
really
cool
once
you
have
gone
through
the
whole
process
of
hardening
the
container
on
the
platform.
This
is
what
you
could
expect
to
see.
You'll
see
the
reduction,
a
significant
reduction
in
vulnerabilities
went
from
105
to
23
files.
The
amount
of
files
is
way
smaller
now
and
the.
B
Like
the
size
of
the
container
itself
went
from
142
megabytes
to
23.,
that
is
super
huge
I,
think
and
I
think
that
in
general,
when
you're
using,
you
can
then
use
this
latest
slim
version
of
nginx
to
build,
go
off
and
build
something
right.
So
it's
smaller,
it's
probably
going
to
run
faster.
It's
going
to
build
faster.
All
of
that,
so
that's
kind
of
a
very
general
overview
of
things
and,
of
course,
there's
all
of
these
different
there's
all
these
different
other
tabs.
B
B
A
That
was
really
good.
We
have
a
I
have
a
question,
but
we
also
have
a
question
in
the
chat.
I
hope
it's
not
like.
So
keep
in
mind.
Everyone
like
Nina's,
more
more
newer
to
the
company.
So
if
we
have
like
follow-up
questions,
maybe
we
could
like
follow
up
with
other
people
who
are
on
the
team.
But
someone
said
interesting:
how
can
we
ensure
the
docker
image
functions
as
expect
functions
as
expected
after
swimming
some
sort
of
regression
task
or
something
that
happens?
They're
asking
I,
guess
yeah.
B
So
the
whole
idea,
that's
a
very
great
question.
By
the
way.
The
whole
idea
is
that,
when
you
leverage
slim,
the
way
that
it
would
work
is
that
it's
integrated
into
your
crcd
pipeline
right.
So
you
want
this
to
be
a
part
of
your
whole
testing
experience.
Testing
is
something
that
we
always
encourage
in
general,
I.
B
Think
in
the
engineering
space
in
the
devops
space,
so
yeah,
you
can
run
your
tests
to
make
sure
that
everything
is
functioning
as
expected,
and
also
you
can
connect
to
something
like
GitHub
actions
or
right
so
like
when
you
commit
when
you
you
commit
something
and
you
push
it
as
a
part
of
that
whole
build
process
is
that
we
can
then
inject
the
slimming
process
into
that,
so
that
you
get
a
smaller
version
of
so
like
there.
B
The
whole
idea
is
that
you
are
definitely
encouraged
to
be
testing
always
to
make
sure
that
everything
works,
but
the
way
that
it's
built
is
that
we
want
to
make
sure
that
the
sensors
are
collecting
the
data
to
know
what
would
need
what
would
be
needed
to
run
so
that
you
aren't
breaking
anything
after
you
have
that
newer,
smaller
version,
a
more
secure
version
of
your
container,
so
it's
all
supposed
to
be
part
of
the
whole
CI
CD
pipeline.
That's
where
you
want
this
to
be,
and
a
part
of
testing.
A
That
was
a
good
question
and
a
really
great
answer.
That
makes
a
lot
of
sense.
My
particular
question
that
maybe
it's
a
little
simple
but
I
was
just
curious
like
when
it
shows
you
the
vulnerabilities.
Does
it
give
details
about
like
what
exactly
the
vulnerability
is
like?
If
you
click
it
does
it
say
like
this?
Is
this
and
like
this
is
the
reason
why
it'll
be
bad
for
you
or
something
okay,
yeah.
B
Yeah,
so
here
you
can
get
the
so
here
you
can
see
the
scanners
that
were
utilized
and
they're
slightly
different
results,
because
every
scanner
gets
gets
slightly
different
results
and
sometimes
Engineers
will
kind
of
like
battle
with
each
other
about
like
if,
if
these
are
accurate
or
not,
so
that's
why
we
like
to
have
multiple
scanners,
but
here
you
can
see
them
from
the
vulnerability
report,
a
whole
summary
of
exactly
what
the
vulnerability
is.
If
there
is
a
fix,
that's
available,
whether
that's
known
or
not,
and
then
we
also
have
a
link
to
the.
B
Let
me
see
where
this
goes.
We
have
a
linked
exactly
all
of
the
information
that
you
would
need
about
what
this
CDE
is
and
how
critical
it
is
where
it's
coming
from,
which
package
the
history
of
all
of
that
and
all
of
the
affected
software.
So
that's
the
data
that
we
think
is
super
important
to
be
able
to
show
folks.
You
know
just
to
give
all
that
for
deeper
insight
into
exactly
what's
happening,
and
why
that's
why
you
can
see
the
summaries
here
that
are
listed
as
a
part
of
this
report.
A
Awesome
I
love
it
and
then
like
if
they,
when,
when
we're
fixing
vulnerabilities,
is
there
like
a
select
all
and
it
just
does
all
of
them
or
you
have
to
pick
each
individual
one
and
be
like
I
want
to
make
sure
that
this
one
gets
resolved.
I
know
this
is
a
really
specific
question.
Just
curious
yeah.
B
So
you
you
don't
have
to
do
anything.
Slim
is
doing
all
of
that,
for
you
I
think
when
it
comes
to
the
hardening
process.
There
is
a
way
there
are
configuration
steps
before
we
actually
do
all
the
work
to
remove
the
ones
that
we
can
from
your
system,
and
that
means
that,
if
you,
maybe
you
don't
want
your
actual
like
app
like
front
and
app
any
of
those
files,
anything
like
that
to
be
touched,
then
we
can
go
through
you.
B
Can
you
have
the
ability
on
the
platform
to
deselect
like
hey,
hi
I,
don't
want
these
I,
don't
want
the
slimming
process
to
be
affected
by
or
to
affect
or
touch
any
of
these
files.
So
you
can
decide
that
if
you
want
to
be
that
granular
or
detailed
on
your
own,
if
not
generally,
then
we
will
just
be
able
to
move
through
your
container
image
and
remove
stuff
on
our
own.
B
A
Awesome,
thank
you.
That
makes
like
no
yeah
I
was
like
how
automatic
goes
automatic
stuff,
but
that
makes
a
lot
of
sense.
I
only
have
like
one
more
question
about
the
platform,
and
then
we
can
switch
more
to
if
you're,
okay
with
it,
like,
maybe
like,
like
how
you're
thinking
about
like
strategy
for
def
roller
you're,.
A
Like
journey
and
experience,
my
only
last
question
is
like:
are
there
any
like
upcoming
features
that
that
people
can
look
forward
to
in
slim
and
then
how
also?
How
can
they
get
involved
in
contributing
to
the
project.
B
Yeah
so
I
think
there's
a
lot
there's
a
lot
that
we're
trying
to
work
on
with
slim
to
make
it
more
than
just
oh,
we
want
to
slim
your
containers.
We
want
to
harden
your
containers
and
make
them
safer.
B
What
we
want
is
to
provide
more
data,
more
insight
into,
what's
really
going
on
into
your
container
and
to
be
able
to
present
that
in
the
the
UI
and
improve
the
developer
experience
and
then
the
the
next
thing
beyond
that
is
kind
of
taking
up
more
of
the
whole
software
supply
chain
pipeline
that
whole
process
the
whole
management
of
software
supply
chain.
We
want
to
attack
it
at
multiple
angles
than
just
being
able
to
see
your
vulnerabilities
be
able
to
automatically
remove
them,
and
so
that's,
like
the
major
things
on
the
horizon.
B
I
would
say
that
are
unfolding
is
not
just
being
a
small
part
of
a
software
supply
chain,
but
having
an
entire
platform
and
management.
That's
more
end
to
end
and
we'll
see
how
things
unfold
and,
like
you
know
the
next
year
or
so,
but
I'm
really
excited
about
that
I.
Think
it's
a
big
type!
It's
a
big
project!
They're
big
goals,
but
we
do
have
some
amazing
people
very
smart
people
working
here,
so
I'm
I
trust
in
them.
A
Yeah
and
it's
super
needed
for
this
industry
and
then
like
how
could
people?
Oh
man,
sorry
about
the
noise
I,
don't
know
if
y'all
here,
but
how
can
people
contribute
like,
let's
say
they're
like
yo
I?
Have
the
great
idea
like
do
you
all
have
open
issues?
Do
you
have
docs
or
or
some
good
first
issues
for
people
to
join
in
on.
B
But
yeah,
that's
how
you
can
contribute
right
here.
People
have
contributed,
people
have
ideas
when
you
join
our,
we
have
a
Discord
Community
people
bring
up
issues
that
they
find
on
there
and
so
yeah.
Anybody
is
able
to
be
a
part
of
this
project
and
I'm
glad
that
it
started
off
as
open
source
because
I
think
that
that's
super
important
and
and
we
want
to
be
able
to
be
a
collaborative-
and
this
is
the
way
that
you
can
do
that
so
yeah.
B
If
you
have
the
link
and
you'll,
be
able
to
do
that
and
be
able
to
get
involved.
A
Yeah,
so
I
can't
so
just
for
the
folks
watching
I
can't
actually
paste
the
link
into
our
like
chat
just
because
limitations,
but
basically
you
see
it
on
the
screen.
It's
github.com
slim
toolkit,
slash
slim.
If
you
wanted
to
get
involved,
I
always
loved.
Like
you
said,
when
projects
are
open
source,
because
that
means
it's
more
for
the
community,
it
means
they're
listening
to
like
the
the
people
using
it
like
the
actual
users.
So
that's
awesome
all
right,
so
I'm
gonna.
A
Devrel
awesome
cool
all
right,
so
my
my
like
question
to
you
is
just
like:
I
have
never
like
my
only
devrel
job
has
been
at
GitHub
and
GitHub
is
already
a
really
established
product.
They
already
like
kind
of,
were
naturally
doing
their
own
developer
advocacy
before
they
even
had
a
team,
and
then
I
came
in
on
an
already
built
team.
A
But,
like
you
started
out
at
a
startup
in,
like
you
know
a
a
lesser,
it's
not
as
popular
right
yeah,
it
probably
will
be
so
I'm
just
curious
about
like
what
strategies
have
you
used
because
I
know
softball
strategies
look
different
from
like
company
to
company,
depending
on
size,
depending
on
like
if
it's
open,
source
or
private
or
whatever.
You
know,
I'm
just
curious
about
like
what?
What
things
that
do.
You
think
you're
gonna
try
to
hit
first
to
help
Advocate
and
build
the
community.
B
Yeah
I
think
there's
so
many
I
mean
it's
a
big
question
right,
because
there's
so
many
components
to
devrel
right
and
every
company
is
different.
So
I
think
that
my
my
job
is
really
it's.
It's
always
evolving
right,
there's
different
priorities
depending
upon
how
the
it's
it's
a
startup
right.
So
we
are
moving
fast,
we're
evolving,
fast,
we're
breaking
things.
We're
fixing
we're
shifting
and
I.
Think
one
of
the
biggest
jobs
for
me
is
to
figure
out
what
I
need
to
focus
on
mostly
depending
upon
the
stage
that
we're
in
right.
B
So
there
might
be
a
time
where
I
need
to
focus
way
more
on
just
community
and
connecting
with
others
and-
and
you
know,
encouraging
people
to
build
things
using
slim
and
then
there
are
other
times
where
I'm.
Just
like
you,
where
we
realize
that
content
is
the
biggest
thing
and
I've
been
focusing
a
lot
on
content
and
contributing
to
documentation
really
building
out
our
docs
and
making
it
easier
for
people
to
just
jump
in
and
be
able
to
get
value
out
of
the
tool
out
of
the
the
platform
or
the
CLI.
B
All
of
that,
in
a
very
short
amount
of
time,
so
I
when
you
talk
strategy
it
it's
it's
always
it's
always
changing
I
would
say,
but
there
are
different.
You
know
pillars
of
course,
there's
the
community
there's
a
Content
creation.
There's
also
that,
like
networking
aspect
of
it
and
collab
operating
with
other
Dev
Rel
folks
so
and
speaking
at
events,
I
was
just
at
kubecon
EU
by
the
way,
and
that
was
amazing
in
Amsterdam.
That
was
the
Amsterdam
for,
like
I,
don't
know
nine
ten
days.
B
That
was
an
amazing
opportunity
to
meet
other
Dev
Advocates
and
also
to
be
able
to
connect
and
talk
with
people
who
had
very
specific
problems
on
their
team
that
they're
looking
to
solve
using
our
tool.
So
it's
a
it's
a
balance
of
different
things.
It
can
feel
like
it's
a
little
all
over
the
place,
but
I
think
as
time
goes
on
and
I
get
more
acclimated
to
the
different
types
of
responsibilities
that
a
Dev
Advocate
has
that
I
will
have
a
better
understanding.
B
I'll
have
a
more
like
meticulous
and
mapped
out
like
strategy,
but
I
do
like
to
who
is
it
the
San,
Julian
and
other
people
that
I
like
to
read
or
watch
like
content
from
there's
also
John
o'baken
I'm,
a
part
of
the
community
leadership,
Corps
group
and
a
lot
of
other
community
leaders
who
are
in
that
group
as
well,
where
we're
learning
about
different
Community
strategy
to
build
a
great
Community
around
your
open
source
project
or
your
tool,
their
software
that
you've
built.
B
So
that's
one
of
the
big
things
I
think
that
has
been
super
helpful
is
like
we're
all
Community
leaders,
and
we
have
this
huge
responsibility
to
build
something
great
and
meaningful.
How
in
the
world
do
you
do
that?
And
how
do
you
do
it
well
and
and
jono
is,
you
know,
obviously
he's
a
Pioneer
and
he's
been
incredibly
resourceful
through
this
whole
new
experience,
I
kind
of
answered
your
question.
We
kind
of
didn't.
A
No,
no,
it
was
good,
like
I'm,
really
glad
that
you've
had
people
like
that's
that's
how
I've
learned
too
right
just
from
talking
to
other
Deborah
leaders
and
being
like
how
have
you
approached
things
and
like
just
just
observing
their
careers
and
like
even
at
a
larger
company
at
like
GitHub
I'm
still
like
wow.
This
strategy
keeps
switching
so
quickly,
like
first
we're
doing
this
I'm
like
okay.
Now
we
gotta
like
move
to
this
next
thing,
so
like
I,
I
relate
and
I
understand,.
A
B
A
Yeah
when
I
first
started
I
think
I
was
like
more
heavily
focused
on
open
source
and
like
beginners
in
general,
for
like
different
things
in
open
source
or
even
just
introducing
them
to
get
but
I.
Think
as
as
the
economy
has
shifted
and
the
industry
has
shifted
and
github's
become
more
of
a
leader
in
AI,
especially
generative
AI.
It's
like
getting
a
co-pilot
is
the
thing
that
we
want
to
introduce
people
to
is
the
thing
that
we
want
to
to
to
to
like
help
lead
the
industry
in
in
going
in
that
direction.
B
A
A
I
was
I
was
also
like
Curious,
like
how
like
what
are
like
I,
don't
know
if
you
know,
since
you're,
so
you're
you're
still
fairly
new
and
still
like
onboarding
into
the
the
community,
but
like
what
are
the
challenges
you've
seen
so
far
as
a
developer,
Advocate
that
like
like
that
the
the
developers
in
your
community
are
facing
and
that
you're
like
oh
man,
maybe
we
need
to
solve
this
like?
Are
they
like
struggling
to
understand
the
importance
or
like
how
to
leverage
it
or
whatever.
B
Yeah
I
think
one
of
the
things
is:
it's
like
getting
immediate
value
out
of
the
tool
and
I
think
that
it's
less
about
the
tool
itself
and
more
about
how
how
we're
documenting
how
to
use
it.
Everybody
is
using
different
programming
languages,
different
software
tools,
different,
you
know,
CI
CD
tools,
and
how
can
we
clearly
explain
how
to
leverage
slim,
no
matter
what
tooling
system
that
you're
using
and-
and
that
is
going
to
that's
a
challenge
because
it's
possible
to
do
it.
It's
just
a
matter
of.
B
Can
you
map
this
out
in
a
very
obvious
way
like
and
and
so
that
I
can?
You
know,
hold
my
hand
like
this
is
a
case
where
you
definitely
want
to
be
handheld
and
get
through
it.
So
I
think
that
it's
going
to
be
a
big
responsibility
of
mine
to
focus
a
lot
on
information
architecture
for
our
docs,
to
make
sure
that
we
are
able
to
explain
if
you're,
using
this
tool,
if
you're,
using
this,
if
you're,
using
GitHub
or
you're
using
Docker,
Hub
you're
using
Jenkins
or
GitHub
actions.
B
Here's
how
to
hook
everything
up
from
beginning
to
end.
So
everything
can
run
smoothly.
That's
going
to
be
a
big
responsibility
of
mine,
or
it
is
there's
a
big
docs
project
that
I'm
focusing
on
along
with
my
manager
and
other
folks
to
make
sure
that
we
can
explain
this
very
easily
and
make
sure
people
get
value
out
of
it.
A
Love
it
and
I
think
I
relate
with
you,
I
think
things
like
like
products
like
code,
spaces,
I,
think
I
think
it's
harder
for
us
to
show
the
value
of
it,
because
people
are
like
okay,
they
opened
up
a
code
space
but
like
how
do
you
set
up
a
Dev
container
and
there's
all
these
platforms
and
tools?
It's
like
okay,
setting
up
a
Dev
container
for
a
python
project
that
also
has
like
is
using
like
AWS
or
whatever.
A
It's
very
like
specific
things
to
be
able
to
lead
people
to
really
see
that
value.
Loris
said
left
a
comment.
I
think
this
is
like
in
reference
to
what
we
were
talking
about
AI.
She
said:
I
asked
chatgpt
to
write
a
cover
letter
for
me
and
it
gave
it.
My
I
gave
it
my
CV
and
it
straight
up.
Lied,
decided
I
went
to
Stanford
instead
of
the
university
on
my
CV
and
Native
jobs.
I've
never
had
I
feel
pretty
safe.
B
I
love
that
that
is
hilarious,
Stanford.
That's
amazing,
yeah.
Definitely
don't
use
that
resume,
but
yeah,
but
I
I
think
we're
a
long
ways
away
from
from
it
being
something
that
could
threaten
our
jobs.
But
I
am
never
going
to
put
anything
past
technology,
so
I've
always
keep
it
in
the
back
of
my
head
to
stay
many
steps
ahead
as
much
as
I
can.
A
And
I'm,
using
like
I'm
like
let's
talk
about
the
ethics
of
it
and
then
also
like
talking
about
like
how
do
we
leverage
AI
so
that
it's
not
making
up
lies
or
like
what
people
call
hallucinations
where
it's
like?
How
do
we,
like
figure
out
how
to
prompt
it
to
make
sure
we
get
like
that?
Those
like
desired
results
that
we
want.
My
other
questions
to
you
are
just
like:
what's
been
like
the
most
fulfilling
or
rewarding
part
of
being
a
developer
Advocate
at
slim
AI,
for
you
so
far,.
B
I
think,
let
me
just
throw
many
things
honestly,
I
think
being
able
to
doing
things
like
this.
This
is
what
I
love
being
able
to
collaborate
with
people
like
you
in
the
space
and
to
bring
awareness
to
amazing
projects
that
are
changing
the
landscape
of
Technology.
You
have
that
kind
of
like
networking
aspect
with
other
developer
Advocates.
B
It's
super
cool,
being
able
to
figure
out
how
to
communicate
and
convey
the
the
value
of
a
product
through
speaking
through,
like
Workshop
type
of
things,
I
think
that
is
amazing
and
it's
exciting.
It's
challenging
through
video
content.
All
of
that
stuff,
that
is
on
the
horizon
for
me
or
that
I
have
dipped
into
recently
with
joining
the
slim.
It
feels
very
rewarding
and
I
think
it's
a
very
it's
a
it's
a
challenge,
it's
a
type
of
challenge.
B
That
is
where
you
have
to
be
very
responsible,
and
you
have
to
be
very
thoughtful
and
inclusive
and
empathetic
and
I
love
that
it
can
stretch
them
bounds
of
my
personality
and
my
comfort
zones
in
order
to
help
others
in
order
to
serve,
and
that
is
what
has
been
really
exciting
about
about
this
job.
Is
that
I
getting
paid
to
serve
others
and
improve
their
experiences?.
A
Yeah
I
love
that
me
too,
I'm
like
it
has
to
make
me
think
different
things
like
I've,
like
I've,
had
to
think
a
lot
more
about
maintainers,
even
though
I
I
haven't
had
that
experience
of
communicating
I'm,
like
that's
so
interesting
like
and
then
I
have
to
give
talks
on
how
to
be
a
better
man
to
maintainer.
Even
though
I'm
not
a
maintainer
I'm
like
I
gotta,
listen
to
them
to
figure
out
so
I
I
relate
with
that.
A
That
experience
it's
it's
awesome
and
then
I
guess
how
has
being
working
as
a
developer
Advocate
at
slim
by
impacted
your
understanding
of
like
security
and
container
optimization,
because
that's
really
something
like
I
I
try
to
like
avoid
just
a
little
bit.
It
sounds
scary.
I'm,
like
I'm,
good
I'm,
gonna,
focus
on
what
I
know
right
right.
A
Sorry,
don't
know
why
it
got
muted,
I,
think
I
think
my
headphone
dropped
up.
What
would
they
saying
I
was
saying:
how
has
your
your
understanding
of
security
and
containerization
evolved
or
been
impacted
as
you've
been
working
here
as
a
developer
advocate.
B
I
mean
so
obviously
coming
into
it.
I
didn't
really
know
much
I
never
had
to
interact
too
much
with
containers
being
more
of
a
front-end
developer.
I
mean
I
left
that
stuff
for
that
hard
stuff
for
the
devops
folks
and
I
happily
did
but
now
being
in
this
is
like
I,
am
really
forced
to
just
get
step
outside
of
my
comfort
zone
and
to
learn
something
totally
new
and
to
do
it
like
I
said
before,
alongside
other
people
who
are
experts
right
part
of
it.
B
So
this
is
my
my
ADHD
brain
is
weaving
off
into
different,
like
tangents,
when
I
promise
I'll
bring
it
around
full
circle
at
some
point
part
of
this,
so
this
stuff
is
this
stuff
is
hard,
like
you
said,
you're,
just
like
I'm
kind
of
trying
to
avoid
it.
This
is
just
really
confusing,
but
there
are
experts
in
this
space
that
I
and
just
focused
on
relying
on
like
the
the
people,
are
creating
content
around
this
people
are
really
wanting
to
educate
folks
on
all
things
security
and
to
me
that
is
what
is
exciting.
B
Is
that
I'm
always
learning
something
new
every
single
day
and
the
experts
themselves
are
learning
something
new
every
single
day?
So
to
me
that
is
encouraging.
You
can
look
at
it
from
a
point
of
you
can
look
at
it
from
oh
I'm
super
intimidated
or
you
can
change
your
perspective
and
look
at
it
as
this
is
opportunity
right
and
if
I
can
show
up
being
receptive
being
humble
and
being
curious.
B
This
is
actually
a
super,
exciting
thing
that
I
don't
know
anything
because
I
know
I'm
about
to
learn
so
much
and
I'm
about
to
empower
myself
and
then
to
be
able
to
turn
around
and
Empower
others.
So,
like
that's,
how
I
like
to
look
at
it
is
opportunity,
it's
scary,
but
there's
so
much
opportunity
on
the
other
side
of
that
is
growth.
So
that's
kind
of
how
I
see
it
that's
my
perspective.
Hopefully
that
made
sense.
I.
A
Love
that
no
yeah
yeah
opportunity,
I,
like
that
and
I
think
I-
think
that's
that's
a
good
way
to
face
problems
head
on
I
think,
especially
in
in
technology.
You
know
we
could
either
feel
nervous
and
get
imposter
syndrome
or
we
could
be
like
this
is
a
moment
that
I'm
Gonna
Learn,
like
maybe
I'll,
look,
feel
dumb,
sometimes
or
be
confused,
but
like
this
is
this
is
the
experience
of
growth
like
this
is
the
same
thing
as
when
we
were
learning
to
code.
We
were
like
what's
going
on,
but
yes.
B
We're
doing
that
whole
thing
all
over
again:
it's
not
and
just
even
becoming
a
developer
Advocate.
It's
like
you're
doing
that
whole
learning
process
all
over
again
and
you
just
have
to
I
just
and
also
like
there's
the
whole
honesty
component.
I,
don't
know
if
I
already
mentioned
that
it's
like
showing
up
honest,
like
hey
I,
am
new
to
this.
B
So,
like
that's,
that's
my
angles
and
I
am
new
to
this
I'm
learning
in
public
and
I'm,
going
to
do
my
best
and
I'm
excited
and
I
think
that
people
really
resonate
with
that
when
you
just
show
up
not
making
it
seem
like
you,
you
know
everything
that
you're
supposed
to
know
everything.
That's
I,
think
that's
more
relatable
I,
don't
know!
How
do
you
feel
about
that.
A
A
Users
are
tired
of,
like
the
whole,
like
like
promotion
like
this
is
fake,
like
you
know,
even
with
like
the
beauty
industry
right
like
at
first,
it
was
just
nice
to
see
people
like
put
on
makeup,
and
this
was
their
first
time
trying
it
out,
and
then
it
turned
into
like
oh
this
person's
getting
paid
to
do
this
or
sponsored
and
now
you're
like
I.
Don't
really
believe
them
is
this
real
and
like
I,
think
it's
the
same
thing
with
with
devrel
too
it's
like?
B
A
B
A
Yeah,
okay,
so
we're
we're
nearing
the
end.
I'm
just
gonna
ask
some
like
fun,
very
non-technical
questions
that
I
tend
to
ask
yes,
so
my
first
one
is
like:
what's
the
first
programming
language,
you
learned.
B
A
You
ever
use
that
okay
I'm,
not
even
trying
to
be
weird
for
this
random
moment,
but
I
think
we
like
we
once
met
or
like
we
moved
warm
months
at
like
the
same
Meetup
or
something
and
then
like
you
pulled
out
code.
Had
me,
I
was
still
in
I.T
and
you
were
like
I'm
doing.
Python
and
I
was
like.
Oh
my
gosh.
What
is
Python's
right,
yeah
I,
love
that
how
many
years
ago
was
that
I
don't
even
know.
A
B
Yeah,
no,
that
those
co-county
and
all
that
was
super
helpful,
but
I
just
think
it's
so
funny
how
it
was
like
python
instead
of
like
you
know,
maybe
something
that
has
like
visual
feedback
like
HTML,
but
I
was
like,
let's
just
jump
into
it.
Let's
build
a
game,
it
was
super.
A
It's
okay,
I
learned,
I,
learned
sequel
because,
like
RCC
was
like
oh
we're
doing
like
a
certificate
program
for
SQL
and
like
you
can
do
it
for
free
and
then
I
was
like
sitting
there
doing
a
whole
class
like
I.
Don't
get
how
this
like
shows
up
on
your
website
like.
B
B
A
B
A
Yeah
and
very
more
very
relatable,
yeah
next
question:
if
money
wasn't
an
issue,
how
would
you
ideally
spend
your
time,
but
it
doesn't
have
to
be
a
job,
but
it
could
be.
B
Okay,
if
money
were
an
issue
I,
okay,
so
I
would
be
writing
a
lot.
I
would
be
speaking
too
and
I
would
be.
I'd
want
some
kind
of
like
high
up
type
of
board
level
position
honestly,
as
some
a
few
non-profit
organizations
that
really
I
really
really
resonate
with
I
would
be
volunteering
a
day
in
day
out
speaking
on
panels,
you
know
advocating
and
being
on
the
ground,
but
also
helping
like
financially
or
whatever
it
is.
B
A
A
My
other
question
is
I
I
recently
added
this
question,
because
someone
in
the
chat
had
asked
this
question
like
what
is
something
like
you
learned
today.
It
could
be
technical.
It
could
be
something
simple
like
learn:
how
to
make
things
I.
B
What
did
I
learn
today?
It's
I
mean
this
is
probably
not
technical.
B
B
I
can
only
I
only
have
to
do
like
20
to
30
minutes,
and
so
there's
like
a
sequence
of
movements
that
I'm
like
super
excited
about
it's
tough,
but
it
just
gets
the
job
done
it's
like
kind
of,
instead
of,
like
you,
know,
weight
lifting
until
like
failure
and
and
so
that's
a
short
amount
of
time,
but
then
your
body's
just
like.
Oh
that's
what
we're
doing
okay
and
you
tone
up
super
quickly,
so
not
totally
not
technical,
but
I'm
super
into
fitness.
B
Anybody
who
knows
me
who
has
lurked
on
like
my
social
media,
please
do
not
knows
that
I.
Am
that
I'm
super
into
that
too,
and
I
think
that
that's
also
it
ties
in
pretty
nicely
with
the
dev
life.
It's
like.
Oh
remote,
work,
life
or
hybrid
work
life.
How
can
I
make
sure
that
I'm
taking
care
of
myself
and
like
still
remaining
fit
and
eating
healthy
and
being
sharp,
so
yeah
I
like
to
talk
about
that?
A
lot.
A
A
A
A
B
B
What
I
think
yours
is
is
more,
that's
that's
more
correct
in
English
right,
it's
a
g
is
next
to
a
vowel
or
or.
A
B
A
Funny
no
I
love
I
love
to
hear
like
the
different,
like
separations
I,
feel
like
a
lot
of
times
like.
Maybe
the
older
generation
is
like
it's
GIF
and
then
like
with
the
younger
generation.
It
like
switches,
sometimes
they're
like
oh
I'll,
I'll,
say
Jeff
or
GIF
or
or
some
of
them
say
Jeff
and
then
Laura
said
she
relates
to
what
else
like
I
came
into
Deborah
I
was
a
technical
writer
before
I
became
a
deaf
advocate,
so
yeah.
B
A
A
B
A
That
was
a
good
one.
Are
there
any
last
things
before
we
wrap
up
that
you
want
to
promote
what
I
don't
know
if
y'all
hear
that,
but
someone
is
just
like
banging
a
big
boxes
or
something,
but
any
last
things
you
want
to
promote
or
or
remind
people
about
anything
that
we
should
check
out
that
you're
coming
up
on
or
something
about
Slim
yeah.
B
So
if
anyone
is
able
to
play
around
on
the
portal,
you
just
authenticate
yourself
with
like
GitHub
or
anything
like
that
to
sign
up
and
sign
in
and
connect
and
registry
and
just
yeah
start
swimming
containers
start.
You
know
running
like
assessments,
vulnerability
reports
and
seeing
what
is
really
going
on
inside.
Your
containers.
A
Nice
so
I'll,
try
to
like
repeat
some
of
the
stuff:
I
didn't
get
all
the
links
but
go
to
sleep.
Ai.
Try
it
out,
connect
your
registry
and
get
those
vulnerabilities
fixed,
also
I,
think
I,
think
they'll
get
like
the
Twitter
and
other
social
media
platforms
from
that
website.
A
Slim
Ai
and
then,
if
you
want
to
contribute
or
add
any
extra
observe,
if
you
find
the
bug,
go
to
github.com,
slim
toolkit,
slash
slim
or
give
it
a
star
if
you're,
if
you're,
like
I'm,
not
able
to
contribute
I
feel
like
the
star
is
always
helpful.
Thank
you
so
much
to
thank
you
to
to
the
audience
for
tuning
in.
Thank
you
so
much
Nina
as
well
for
for
coming
and
sharing
your
time
and
your
knowledge.
I'm
really
excited
for
your
journey
tune
in
next
time
to
open
source
Friday.
A
Next
Friday
I
promise
it
will
be
less
noisy
and
more
organized
and
I
will
have
a
better
camera.
It's
been
a
crazy
day,
so
thanks
y'all
and
I
hope
you
have
a
wonderful
Friday
bye
thanks,
bye.