►
From YouTube: “Solving the Bottom Turtle”: Writing a book on SPIFFE in 10 days using Book... - Barbara Ruehling
Description
“Solving the Bottom Turtle”: Writing a book on SPIFFE in 10 days using Book Sprints - Barbara Ruehling, Umair Khan
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2021 Virtual from May 4–7, 2021. Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
A
Awesome
yeah
thank
you
for
inviting
us
to
talk
about
this
book
that
we
sprinted
in
10
days.
A
I'm
a
book,
sprint
facilitator
and
also
the
ceo
of
our
little
company
book,
sprints
books,
friends
started
in
open
source
software
when
our
founder,
adam
hyde,
experimented
with
floss
manuals
and
tried
to
make
writing
documentation,
collaborative
and
fun
and
fast
and
came
up
with
this
five-day
process.
A
Then
it
moved
to
big
tech,
but
also
academia,
open
educational
resources,
government
reports,
we've
sprinted
books
on
basically
anything
but
we're
still
really
happy
to
make
books
on
open
source
projects
so
yeah.
I
was
really
happy
when
hpe
invited
us
to
to
do
a
book
sprint
on
on
spiffy
inspire
this
year.
A
We
couldn't
meet
in
person
anymore,
so
our
five-day
process
is
now
a
10-day
virtual
sprint
process,
but
it
still
works
really
phenomenally
because
the
the
riders,
in
this
case
we
had
12
riders,
they
really
put
in
long
hours
and
across
different
time
zones
and
a
lot
of
hard
work
to
still
make
a
book
in
in
this
time
frame.
A
If
you
want
to
move
to
the
next
slide,
I
can
give
you
just
a
very
quick
impression
of
what
that
may
look
like.
In
the
background.
You
see
our
brainstorming
board,
so
what
we
would
usually
do
in
a
room
full
of
white
boards.
We
now
do
online
and
yeah,
so
we
brought
together
12
writers
for
10
days
to
first
brainstorm
and
come
up
with
a
concept
for
the
book
structure
that
and
start
writing
and
revising
the
content.
A
So
everything
has
been
going
through
yeah,
12,
pairs
of
hands
and
eyes
and
fact
checked
and
rewritten
and
restructured
over
and
over
again
until
we
come
up
with
a
book
that
you
see
on
the
right.
The
right
side
is
just
two
example
pages.
The
book
has
200
pages
and
80
diagrams.
All
of
that
done
within
those
same
10
days.
A
So
I
was
the
facilitator.
I
have
absolutely
no
content
knowledge,
but
I
I
guided
the
group
of
writers
through
this
entire
process,
helped
them
to
stay
on
track
and
stay
productive
and
in
the
background
I
have
a
team
of
copy
editors
and
book
production
experts
who
make
all
those
diagrams
copy
edit.
The
content,
the
layout
of
the
book
in
real
time
during
those
same
10
days,
so
everything
is
ready
to
be
published
immediately
so
yeah.
The
book
was
launched
about
a
week
ago
and
today
is
our
first
little
presentation,
which
is
really
exciting.
A
Some
of
the
authors
I
see
here,
which
is
amazing-
maybe
you
may
you-
can
introduce
them
quickly.
B
Yeah
absolutely,
I
think
this
was
my
first
book
sprint,
but
I
think
andres
is
a
master
of
book
sprints.
Now
he
has
done
multiple
of
these,
so
he
was
the
first
person
to
bring
this
idea
up
as
well.
Eventually
we
went
with
it.
He
convinced
us.
I
think
it
was
a
goo
like
from
a
person
who
did
the
book
sprint
for
the
first
time
it
was.
It
was
a
great
experience
initially.
B
Many
of
them
are
renewed
in
the
specific
community
in
the
security
circle
like
emily
fox
and
a
bunch
of
others,
all
of
them
had
some
sort
of
experience
within
the
domain
right
either
they
were
like,
I
said,
security
experts,
or
they
had
run
similar
things
like
ian
and
michael
and
netflix.
In
the
past,
or
they
had
some
operational
experience
with
spiffy
inspire
as
well,
when
their
organizations
with
frederick
and
eli
to
name
a
bunch.
B
So
again
it
was
a
great
experience.
It
was
and
we
feel,
like
it,
solves
a
real
problem
for
someone
who's
looking
to
learn
about
spiffy
again,
we
wrote
the
book
with
the
perspective
of
hey.
This
is
how,
if
you
want
to
get
started
on
specific,
these
are
the
key
concepts
you
need
to
learn.
What
was
the
rationale
behind,
starting
specifically
in
the
first
place,
key
concepts
like
barbara
mentioned,
what
was
amazing
was
we
were
able
to
generate?
I
think
50
plus,
I
don't
know
the
exact
number.
B
I
know
you
had
it
on
the
last
slide.
Tons
of
list
80
illustrations
done
and
a
lot
of
them
are
open.
Source
are
available
to
the
community
as
well.
We
make
it
available
if
anyone
wants
to
use
those
illustrations
to
convince
their
bosses,
or
you
know,
preach
spiffy
within
their
organization.
They
are
feel
free
to
do
so.
So
we
also
covered
some
things
like
benefits,
for
if
an
engineer
likes
the
concept-
and
they
want
to,
you
know,
build
the
case
for
it
for
their,
you
know,
boss
or
on
the
business
side.
B
There's
some
content
around
that
too,
and
it
also
covers
slightly
advanced
topics
like
you
know,
deployment
strategies
and
integrating,
especially
with
other
tools
and
how
this
compares
with
other
tools
as
well.
Also
a
big
thank
you
to
to
some
of
the
practitioner
stories
that
were
submitted
bobby
from
anthem,
ryan,
from
uber
germany
from
pinterest,
michael
and
matt
from
square.
But
amongst
a
few
that
submitted,
you
know
some
real
practitioner
stories
as
well,
that
you
know
people
can
get
some
deeper
insights
around
that
again.
We
are
excited
about
this
book.
B
Hope
you
find
it
useful.
I
think
we
already
have
over
a
thousand
downloads
in
the
last
week
and
we
haven't
even
promoted
it
that
much
the
link
is
available.
We'll
have
different
versions
of
this
book
available
soon
as
well.
Both
are
hard
copy
and
we're
trying
to
get
a
kindle
version
of
it
as
well.
B
But
you
know,
like
I
just
mentioned,
think
of
as
a
book
of
you
know,
people
who
are
trying
to
you
know
adopt
the
journey
going
from
zero
to
production
with
spiffy
right
and
you'll
hear
a
lot
about
this
turtle.
You
probably
saw
the
turtle
in
all
the
slide
decks
too
so
we
made
so
the
name
of
the
turtle
is
zero.
The
turtle
naturally
builds
on
a
concept
around.
You
know
how
spiffy
solved
for
the
you
know:
secret
zero
problem
or
the
bottom
turtle
problem
as
well.
B
So
you'll
see
that
a
lot
in
presentations
that
I
think
andreas
recently
did
at
a
couple
of
shows
as
well.
So
we're
super
excited.
If
you
have
feedback
in
the
in
the
book,
let
us
know
we'll
be
in
a
few.
Every
few
months
we
are
looking
to
revise
that.
Of
course
the
project
is
changing
and
it
will
be
available.
B
Yes,
we
can
definitely
add
to
this
book
and
we'll
have
like.
I
said
a
second
edition
and
we'll
add,
you
know
a
lot
more
stuff
too,
as
well
and
contributions
are
welcome.
C
C
Thanks
for
sharing
this
umerian
barbara,
it
was
quite
a
journey
to
write
this.
It
was
a
very
interesting
process,
just
eliciting
the
knowledge
from
everyone's
head
capturing
it.
I
left
and
chat
some
of
the
framing
folks
who've
started
reading
it
see
it,
as
is
it's
a
companion
guide
and
the
journey
from
zero
to
production.
So
if
you're
not
clear
where
to
get
started,
you're
still
wrapping
your
head
around
the
concepts
it
can
help
you
with
that.
C
If
you
are
further
along
and
understand
spiffy,
but
are
having
a
hard
problem,
convincing
your
peers
or
convincing
your
team
or
finding
that
business
justification,
you
can
find
some
tools
there
and,
if
you're
past,
that
stage
and
you're
just
ready
to
deploy
and
need
to
like
reason
around
deployment
strategies
how
to
tackle
different
applications,
different
systems,
how
to
reason
about
it
holistically,
there's,
there's
quite
a
bit
there
as
well
as
how
does
it
fit
into
the
rest
of
the
ecosystem
and
integrating
with
with
other
systems.