►
Description
Presented by Ben Greenberg, Developer Advocate, Nexmo
"A coding education that not only incorporates Git into its education but forms its educational program around Git produces more resilient and more capable developers who can enter a business landscape and grapple with complex challenges. How does structuring an educational program around Git accomplish that?
As a former technical coach at the Flatiron School I have helped numerous emerging programmers learn the fundamentals of software development and, more importantly, grapple with breaking a problem down into its smallest parts and have done so through using a "Git approach". This not only teaches good version control but cultivates a genuine trouble shooting mindset that can tackle multifaceted problems and issues, both in the code and in the logic underlying a program. Come and discover how Git is not only the premier version control software but is also a powerful educational tool."
About GitMerge
Git Merge is the pre-eminent Git-focused conference: a full-day offering technical content and user case studies, plus a day of workshops for Git users of all levels. Git Merge is dedicated to amplifying new voices in the Git community and to showcasing the most thought-provoking projects from contributors, maintainers and community managers around the world. Find out more at git-merge.com
A
A
Haven't
said
anything
and
you're
already
clapping
I
know
I'm
the
last
talk
before
drinks,
so
I'll
try
and
be
succinct.
It
actually
reminds
me
of
a
true
story
of
a
minister
who
would
get
up
to
give
his
sermon
every
week
and
his
sermon
ago.
10
minutes
15
minutes,
25
minutes,
30
minutes
and
one
week
one
of
his
members
came
up
to
him
and
said
you
know.
That
was
an
amazing
speech.
It
so
inspired
me,
you
know,
I'm
an
executive
on
a
television
show
it's
a
morning
show.
A
Would
you
be
able
to
come
in
and
just
talk
about
what
you
spoke
about
this
morning
and
the
minister
is
like
absolutely
sure,
I'll
come
on
to
your
television
show
and
the
executive
is
like,
but
only
one
problem.
You
only
have
a
two-minute
slot
for
this
production
and
the
minister's
like
yeah
I
can
cut
it
down
to
two
minutes
and
then
she's
like.
A
Can
you
do
that
every
week
also
yeah
so
and
given
that
I'll
try
and
be
as
succinct
as
possible
as
we
talk
about
how
a
get
based
education
cultivates
more
resilient
developers
so
but
first
a
little
bit
about
Who.
I
am,
as
mentioned,
I
am
Ben
hello,
everyone
I'm
the
father
to
two
amazing
kids,
mostly
most
of
the
time.
Amazing
and
I
am
myself
a
second
career
developer,
who
spent
about
10
years
in
a
field.
A
That's
slightly
different,
not
as
a
geologist,
although
that's
awesome,
but
as
a
rabbi
and
a
community
organizer
and
an
educator
throughout
the
United
States
and
I'm
from
Southern
California
lives
in
New,
York
and
now
live
near
Tel
Aviv
in
Israel
and
I
work
as
a
developer
advocate
at
NEX
mo
who
is
heard
of
next
mo
anyone
a
hand.
Yes
awesome.
We
are
a
cloud
communications
platform
powered
by
vonage,
so
musicians,
journalists,
lawyers,
scientists,
sometimes
geologists,
artists,
cashiers
and
yes,
even
rabbis.
What
do
we
all
have
in
common?
A
Well,
what
we
all
have
in
common
is
that
we
are
all
developers
now
and
why
are
we
becoming
developers
we're
becoming
developer
developers
because
we
love
to
learn?
We
love
that
this
field
is
one
that
continually
compels
us
to
learn
new
technologies.
Learn
new
frameworks,
learn
new
languages
if
you're
a
JavaScript
developer,
maybe
you're
learning
a
new
framework
every
other
day.
It's
amazing.
We
love
the
challenge:
that's
inherent
in
this
domain
of
work
continually
coming
to
work
and
approaching
new
business
challenges
with
programmatic
with
engineering
solutions.
We
love
the
community.
A
This
wonderfully
diverse,
eclectic,
warm
and
welcoming
community
that
surrounds
software
development
and
yes
to
be
pragmatic.
We
also
love
the
jobs
in
this
fields.
According
to
nine
states,
Department
of
Labor
employment
of
software
developers
in
the
u.s.
is
projected
to
grow
24
percent
from
2016
to
2020
6,
faster
than
all
other
occupations
in
the
United
States.
A
So
this
is
a
field
with
so
much
potential
out
there
to
really
actually
transform
lives,
to
take
people
to
new
opportunities
to
take
them
and
their
families
to
new
opportunities,
and
so,
as
a
result,
people
are
entering
into
this
field
and
you
might
be
one
of
them
or
you
work
with
them.
Coming
from
diverse
places
from
every
walk
of
life.
A
From
every
conceivable
background
from
every
corner
you
finding
people
who
are
now
software
developers
and
just
as
an
example,
for
example,
in
2017
so
ancient
time,
but
not
so
long
ago,
the
average
boot
camp
graduate
the
average
graduate
of
a
coding
boot
camp.
Well,
11%
of
them
majored
in
business,
in
college
8%
in
psychology
or
philosophy,
5%
of
communications
or
journalism,
6%
of
engineering
and
only
5%
had
that
computer
science
that
CS
degree.
A
So
roughly
around
and
a
lot
of
variation
here,
but
roughly
around
seventy
thousand
US
dollars
is
the
average
salary
there's
people
I
know
who
are
living
on
assistance
who
are
now
taking
care
of
their
families
with
dignity
in
this
career
as
a
software
developer,
and
yet
we
also
know
that
learning
to
code
can
be
really
difficult
and
not
just
Java.
Other
languages,
too,
can
be
really
really
challenging,
especially
if
you
come
like
I
did
from
a
liberal
arts
background,
you
are
trained
to
think
about
problems
in
different
ways.
A
You
have
different
methodologies,
different
approaches
to
tackling
and
creating
solutions,
and
this
field,
this
domain
area
work
requires
in
some
ways
different
skill
sets
requires
a
different
I
requires
a
paradigm
shift,
a
different
way
of
approaching
challenges.
So
is
there
a
tool
that
can
help
future
developers
become
resilient
developers?
A
All
this
pacing,
it's
great
resilience,
Chadd
developers
who
can
create
resilient
solutions
to
really
challenging
problems
that
arise
at
on
the
job.
So,
a
little
while
ago,
I
sent
out
a
survey
to
the
wider
community
asking
some
basic
questions
around
their
experience
with
how
it
was
or
not
incorporated
in
their
developer.
A
Education
and
I
receive
responses
from
people
who
win
through
CS
backgrounds
and
college
people
who
were
boot
camp
graduates,
people
who
are
self-taught
developers
from
all
around
the
world,
actually
majority
from
North
America,
but
also
from
Europe
and
Africa
and
Asia,
and
received
some
really
interesting
responses.
Things
like
learning
to
use
some
form
of
version
controls
necessary
to
develop
the
confidence
needed
to
build
your
code
and
collaborate
with
others.
It
gives
better
accountability,
it's
easier
to
roll
back
changes
and
work
collaboratively.
A
It
helps
me
feel
comfortable
to
change
having
version
control
and
a
good
workflow
is
important
to
review
my
commits
and
find
where
I
made.
The
wrong
move
is
valuable
and,
although
I'm
a
novice,
it
seems
to
standardize
the
mechanism
for
sharing
work
which
I
appreciate
and
it
makes
the
process
more
efficient.
And,
lastly,
it
allows
you
to
go
back
to
see
my
iterations
of
my
code
over
time
and
it
also
saves
my
bleep
when
I
break
things.
So,
accountability,
confidence,
iteration
iterative,
Ness
collaborate
and
a
good
workflow.
A
These
are
not
just
he
catchphrases
I'm,
not
just
shouting
DevOps
kubernetes.
These
are
actually
amazing
skill
sets
which
are
sometimes
come.
Naturally,
there
is
a
little
bit
of
a
natural
talents
here,
but
also
things
that
can
be
learned
can
be
acquired
can
be
developed
and
I
really
believe
are
integral
to
what
it
means
to
take
on
git
as
an
essential
part
as
an
essential
part
of
one's
developer,
education.
So
an
example
because
we
obviously
have
to
concretize
this
a
little
bit.
A
So
an
example
from
the
Flatiron
school
is
heard
of
the
Flatiron
school
whoo
Flatiron
school,
yes,
so
I
feel
like
I'm
in
one
of
those
hair-growth
commercials
where
it's
like.
Not
only
am
I
the
president
but
I'm,
also
a
member
I'm,
not
by
the
way
it's
still
natural,
but
not
only
did
I
have
the
great
privilege
of
being
a
coach
at
the
Flatiron
school
for
a
little
bit
as
in
the
online
developer
program,
but
I'm.
Also,
a
graduate
of
the
Flatiron
school.
A
The
Flatiron
school
is
a
coding
boot
camp
based
in
New,
York
City,
but
now
with
branches.
Throughout
the
world,
the
one
branch
in
London
so
now
that
for
Americans
that
we
can
see
it's
throughout
the
world
and
an
amazing
online
developer
program
as
well,
and
that's
part
of
the
community
of
we
work
it
was
recently
acquired
by
we
worked,
and
so
the
Flatiron
school
from
it's
very
inception
incorporates
get
really
as
an
integral
component
of
the
educational
experience
of
their
pedagogical
methodology.
A
So,
for
example,
the
repository
where
the
curriculum
lives,
the
organization's
call
learn
code
students,
you
can
find
yourself,
it's
all
open
source
and
it
hosts
around
roughly
around
seventy
four
thousand
repositories.
That's
every
iteration
of
their
curriculum.
Throughout
the
years
of
the
existence
of
the
program,
you
can
see
the
entire
development
and
they
don't
only
use
version
control
to
track
and
to
maintain
their
curriculum.
They
actually
build
it
into
the
labs
into
the
exercises
itself.
So
let's
take
a
look
at
one.
This
is
the
Ruby
music
library.
A
This
comes
relatively
early
on
in
the
exercises
that
a
student
will
go
through
in
the
curriculum
and
at
this
point
in
the
curriculum.
Where
is
that
students?
Well,
they
have
started
learning
some
of
the
basics
of
object-oriented
programming
in
Ruby
they're,
starting
to
understand,
object,
inheritance
classes
and
instantiating
instances
of
classes
they're
starting
to
be
done,
some
labs
building
up
to
this,
and
now
this
is
their
first
time
where
they're
going
to
be
building
a
standalone
program.
That
does
something
that
not
only
has
one
class
in
one
instance,
but
actually
is
gonna.
A
Ask
the
students
to
build
three
different
models:
a
song
and
artist
in
a
genre
model,
and
that
these
models
have
relationships
to
each
other
and
they
also
have
to
build
another
model.
That's
going
to
have
a
method
that
will
extract
file
names
that
make
instances
of
the
song
and
the
artists
in
the
genre
model,
and
on
top
of
all
of
that,
they
also
need
to
make
sure
that
there's
a
CLI
that
the
user,
interacting
with
this,
can
do
something
and
does
not
just
lives
out
there
in
the
ether,
but
a
user
can
actually
use
it.
A
So
there
is
a
lot
into
this
lab
and
it
just
take
a
minute.
Take
a
step
back
feel
what
it
feels
like.
As
that
student
approaching
this
lab,
it
can
often
feel
like
this
I
have
absolutely
no
idea
what
I'm
doing
you
feel
like
you're,
a
dog
in
a
spacesuit
in
the
middle
of
space,
and
you
just
want
to
get
your
bone
and
you
just
have
no
idea
how
that's
going
to
happen
because
you
have
to
build
these
classes.
They
have
to
relate
to
each
other,
there's
methods
that
apply
to
all
them.
A
So
you
should
extract
those
and
make
them
abstract
so
there's
functionality
across
the
domains
if
they
build
a
CLI,
it's
a
lot
of
work,
but
thankfully
the
way
the
curriculum
is
designed
and
developed
intentionally
so
is
there
a
combat
is
a
combination
of
test-driven
development
and
get
as
the
way
to
structure
one's
thinking,
so
the
test-driven
development
and
here's
the
test
for
this
lab
the
test-driven
development.
What
that
does
is
it's
telling
a
student
describing
the
behaviors
of
what
this
programs
gonna?
Do?
A
It's
letting
them
know
and
understand
the
parameters,
the
expected
outcomes
for
this
exercise
and
what?
And
so
when
the
student
is
looking
at
this,
they
say:
okay,
take
a
deep
breath.
I
have
one
two
and
three
I
need
to
build.
My
classes.
I
need
a
song
class,
an
artist
class
in
a
genre
class
I've
done
that
before
in
earlier
labs,
I
know
what
that
feels
like
I
can
do
it
si
se
puede,
yes,
I
can
do
it.
I
can
build
my
models
and
then
they're
like
okay,
now
I
need
to
start
seeing
that
relationship.
A
So
what
are
the
relationships?
Well,
there's
a
songs
to
artist,
artists,
genres
and
songs,
artists
and
genres.
Okay,
one
step
at
a
time,
and
so
when
you
then
take
a
further
deep
dive.
Well,
what
does
it
mean?
What
does
it
mean
to
build
a
song
class?
Well,
it
probably
has
an
initialized
method
right.
Does
this
all
sound
a
little
familiar
Rubeus,
whoo,
yay
Ruby,
so
an
initialize
method,
and
this
initialize
method
will
define
the
parameters
for
the
instances
of
this
class.
What
will
each
new
baby
song?
A
A
It
takes
the
name,
it
gives
back
the
name
beautiful,
you
start
breaking
things
down
and
when
you
do
that,
what
you're
actually
doing
is
you're
using
the
tests
to
describe
the
behavior
and
as
we're
working
through
it
you're
thinking
and
get
which
is
breaking
it
down
to
its
smallest
component.
One
meaningful
commit
at
a
time
so
does
get
make
you
a
better
programmer.
That
was
another
question.
I
asked
and
I
actually
received
some
really
fascinating
responses
on
this
topic.
81%
of
people
said
yes,
some
other
people
said
well.
A
Actually
subversion
makes
me
a
better
programmer
I'm,
like
I,
don't
know
who
you
are,
but
that's
amazing,
you
do
you,
and
so
how
does
it
make
them
a
better
programmer?
So
take
a
look
at
some
of
these
responses.
Well,
it
gives
me
rhythm,
it's
integrated
with
our
automated
tests,
and
here
we
go
again
right
tests
version
control
tests.
Yet
there's
like
this
relationship
of
synchronicity
between
the
two
synchronicity,
that's
a
good
word.
I
should
remember
that
one.
It
gives
me
rhythm,
it's
integrated
with
automated
tests
with
our
management
tool
and
fits
perfectly
in
our
processes.
A
It
forces
you
to
structure
your
work.
You
can
commit
and
push
a
whole
week's
work
at
once,
but
if
you
stick
to
some
common
rules,
you
came
at
small
packages
and
you
push
once
and
since
I've
you
get
as
a
way
to
track
my
progress.
It
helps
me
to
think
in
blocks
so
rhythm
thinking
in
blocks,
structuring
or
work
thinking.
Well,
where
is
my
meaningful
commit?
When
is
the
time
when
of
I?
Actually,
what
is
the
time
where
I
can
say?
I've
defined
a
valuable
piece
of
work,
and
what
is
that
piece
of
work?
A
When
does
it
end?
What
are
the
boundaries
of
that?
These
are
incredibly
valuable
insights,
especially
for
aspiring
developers
who
are
trying
to
learn
how
to
think
how
to
structure
their
thought
processes
to
in
this
field
in
this
domain,
so
back
to
that
music
library.
So
when
you
have
learning
structured
as
a
series
of
tests
like
describe
the
initialize
method,
you
begin
to
break
things
down
to
its
smallest
parts.
A
You
begin
to
understand
that
big
problems
are
ultimately
smaller
problems
that
are
actually
encapsulating
smaller
problems,
that
as
they
build
their
solving
the
big
problem
and
get
becomes
the
tool
that
structures
that
thinking
so
here's
an
example
of
of
one
of
the
students
completing
this
exercise.
Anonymize
there
now
spider-man
it's
amazing,
and
so,
if
you
take
a
look
at
this
example,
you
see
some
the
thought
process.
That's
actually
it
that's
happening
in
the
moment
as
they're
working
their
way
through
this.
What
is
a
complex
lab?
A
So
you,
the
starting
code
Wednesday
morning,
all
green
through
four
five,
six,
seven,
eight,
nine!
You
feel
the
excitement.
Are
you
feeling
exciting?
I'm
feeling
excitement?
It's
all
green,
yes
for
God
to
create
a
new
branch.
It
may
be
a
little
messy
thirteen
failures.
Fifteen
failures,
green
really
is
a
color,
all
green
and
then
finally
done
Wow.
A
Just
that's
amazing,
I
kind
of
want
to
celebrate
with
that
person
like,
let's
have
a
toast.
That's
the
experience.
There's
a
confidence
building,
that's
happening
there,
you're
approaching
an
entirely
new
field.
You
don't
really
know
if
you
can
do
it
and
when
you
start
thinking
things
through
in
a
get
mindset,
breaking
it
down
and
commit
by
commit
by
commit
well
you're
actually
doing
is
building
that
iterative
process
where
you're
working
and
perfecting
your
code,
making
it
better
you're
developing
the
confidence
that
you
can
do
it.
A
You
can
really
really
do
it
and
and
you're
developing
skill
sets
all.
At
the
same
time,
the
software
development
is
ultimately
about
having
two
perspectives
simultaneously.
Thinking,
big
and
thinking
small,
at
the
same
time
being
up
here
at
the
balcony,
understanding
where
you
need
to
go
understanding
what
the
end
is,
but
also
keeping
in
your
head
simultaneously
how
what
are
and
how
are,
and
how
will
the
steps
be
structured
that
will
get
me
there.
A
So
it's
starting
with
that
broad
overview
understanding
the
world
in
which
you're
developing,
in
its
understanding
the
scope
that
actually
defines
the
parameters
of
your
program.
So
it's
not
just
the
world,
but
we're
talking
about
Europe,
it's
getting
the
specs
for
that
program,
understanding
what
the
boundaries
of
desire
behavior
are
and
what
are
the
things
I
don't
want
to
happen
in
my
program
and
realizing
that
all
these
things
ultimately
the
parameters,
the
specs
everything
will
ultimately
boil
down
to
the
Royal
Palace
of
Brussels,
that
all
of
those
things
will
lead
to
something
beautiful
and
elegant.
A
That
will
really
shine
forth
the
monarchy
of
Belgium
and
understanding
how
all
of
this
comes
together
and
seeing
that,
but
also
not
being
so
awed
by
it.
They
don't
forget
that
it
all
started
with
a
single
brick
and
other
building
blocks,
but
a
single
brick
that
this
is
really
built
of
these
and
oftentimes
as
a
new
developer.
All
you
can
see
is
that
all
you
see
is
the
palace,
you
and
you
know,
that's
by
the
way,
just
the
office
for
the
King,
that's
kind
of
crazy,
but
all
you
see
is
the
palace.
A
You
don't
understand,
and
you
don't
worry.
She
ate
that
it's
a
bunch
of
these
bricks
inelegant
bricks
that
built
that
and
that
insight
that
incredibly
powerful
insight
is
what
enables
resiliency.
So
another
example-
and
this
example
comes
from
my
current
work
now
at
next
MOU,
and
so
I'm
the
ruby
advocate,
if
you
haven't
noticed,
I
love,
ruby,
a
ruby,
rinse
wand,
ruby
is
nice
and
we
are
naive,
CA,
hey
Matz,
and
so
this
example.
A
So,
as
the
ruby
advocate,
I
also
helped
manage
the
next
Moe
developer
platform,
which
is
built
on
Ruby
on
Rails
yay
rails,
and
so
one
of
the
features
we
want
to
build
is
configurable
landing
pages,
and
what
does
that
mean
a
configurable
landing
page?
Well,
it
means
something
like
if
this
works,
something
like
this,
where
let's
say
you're
coming
to
the
next
one
developer
platform,
which
is
where
your
find
resources
on
our
API
is
etc,
and
you
are
coming
from
a
specific
conference
from
a
certain
meetup,
a
hackathon,
an
event,
a
lecture.
A
What
what
have
you
you
should
be
greeted?
This
is
the
big
idea.
You
should
be
greeted
as
you
as
who
you
are.
That's
a
we
that's
our
aim.
We
should
know
you
you
right
there.
We
should
know
who
you
are
and
we
should
appreciate
you.
We
should
know
what
you
like
and
we
should
be
able
to
give
you
the
tools
that
are
most
helpful
for
you
right
when
you
come
to
visit.
That's
the
big
dream,
so
we
want
to
have
an
event
specific
welcome.
A
That
tells
you
hey
welcome
from
whatever
conference,
and
if
it's
a
language-specific
conference,
let's
say
dotnet,
we
want
to
give
you
dotnet
tutorials
in
the.net,
client
library,
thought
that
sdk
and
all
other
kind
of
fun
net
stuff
and,
let's
say
you're,
coming
from
a
voice
conference.
What
will
give
you
the
voice?
Api
will
pick
the
products
that
make
the
most
sense
to
show
you
some
customization,
so
you
feel
like
you're
getting
to
what
you
want
to
get
to
relatively
quickly.
A
But,
as
anyone
knows,
a
big
dream
conceived
in
the
business
side
of
things
can
often
be
very
overwhelming
to
the
engineering
side
that
what
seems
simple
to
those
who
are
dreaming
of
it,
who
conceived
it
is
not
always
simple
to
implement,
is
not
always
simple
to
create
and
what
seems
like.
A
small
thing.
Can
rapidly
spiral
into
something
that
feels
utterly
utterly
overwhelming,
so
how
do
we
get
there?
Well,
we
get.
There
is
no
surprise
by
now
by
breaking
it
down,
breaking
it
down
to
its
smallest
and
meaningful
moments.
A
So,
for
example,
this
is
a
real
lie,
pull
request
from
our
from
our
next
one
developer,
repo
okay,
so
we
want
configural
landing
pages.
The
first
step
that
we
did
was
we
built
a
data
structure.
We
start
about
the
ways
we
would
structure
that
data
to
be
most
efficient
and
most
meaningful.
We
want
to
be
able
to
give
basically,
let's
say,
you're
a
community
manager,
and
so
we
want
to
be
able
to
say
community
manager
go
to
this
thing,
drag
and
drop
the
event
blocks
and
will
generate
a
website
for
you,
amazing,
beautiful.
A
So,
first
we
need
to
think
about
the
data
and
how
we
structure
the
data
the
next
step
after
that
is
what
that
data
needs
to
do
something
right.
It
needs
to
do
something.
What
does
it
need
to
do?
It
needs
to
render
rows
and
columns
do
I
care
what's
in
the
rows
and
columns
in
that
moment,
absolutely
not
all
I
care
about
at
this
moment
in
this
iterative
process
is,
can
I
take
that
data.
Can
it
get
read
and
can
the
right
divs
with
the
right
class
things
be
generated?
A
That
will
give
me
the
right
layout
that
is
being
called
for,
and
so
you
know
this
is
me
raw.
So
every
commit
message
there
is
not
absolutely
perfect,
but
it's
I'm
not
embarrassed
to
admit
that
I'm
not
always
a
perfect
committer,
but
it's
it's
me
as
I'm
working
through
this
process.
You
know
defer
accepting
the
default
with
making
sure
that
the
type
block
gets
rendered
all
the
kinds
of
stuff,
but
so
to
get
there
from
when
I
first
began
as
a
student
I.
This
made
me
think.
A
Well
what
was
my
actual
first
commit
message
and
I
was
hoping.
I
have
to
be
honest
with
you.
All
I
was
hoping
my
first
commit
message
as
a
new
developer,
with
something
brilliant,
totally
inspiring
something
gonna,
be
so
profound
you'd
be
like
wow,
my
first
kid
well.
This
is
basically
that
you
can
skip
that,
but
my
first
commit
message:
did
I
I
didn't
put
in
there?
Well,
whatever
my
first
commit
message
was
one
word:
one
word
which
was
done.
A
I'd
finished
the
prop
finished
a
project
and
I
just
wrote
done,
did
I
push
it
up,
as
I
was
integrating
that
I
think
about
the
building
blocks.
Did
I
do
all
of
this
stuff
that
I
made
a
nice
little
visual
for
absolutely
not
all
I
did
was
write
done,
but
from
done
to
be
able
to
think
about
problems
that
are
easy
to
visualize
the
business
side
but
complicated
to
build
from
the
engineering
side.
Well,
that
is
a
big
process.
So
how
do
we
ultimately
put
it
all
together?
A
Well,
as
we
mentioned,
programming
can
be
really
challenging
for
experienced
programmers
for
new
developers,
especially
people
coming
from
non-traditional
educational
backgrounds
in
this
field,
and
so
oh
there's
my
there,
it
is
there's
my
first
commit
done,
beautiful
I've
put
in
the
wrong
place.
It's
live
awesome
so
going
from
that
to
something
more
profound,
something
that
takes
a
little
more
complexity
can
be
a
road
that
has
a
lot
of
turns.
A
A
lot
of
twists,
it's
not
always
a
straight
path
and
but
ultimately,
if
you
embrace
the
ways
of
the
octocat,
and
what
do
you
mean
by
embracing
the
ways
of
the
octocat
by
thinking,
big
and
small,
by
breaking
it
down
not
getting
down?
But
you
can
do
that
in
a
few
minutes
at
the
party,
but
breaking
it
down
to
its
most
meaningful,
commit
to
thinking
in
hunks
or
chunks,
I
guess
we
heard
earlier
today,
hunks
thinking
and
hunks,
or
chunks
of
work
and
really
thinking
about
it.