►
From YouTube: Version control for visual learners - Git Merge 2019
Description
Presented by Veronica Hanus, Software Engineer
"Can you remember the difference between two hex color values? Me neither! Entering visual representations of recently-changed elements into version control makes review of past changes easier & speeds acclimation to a new web project, especially for visual learners.
Surprisingly, methods for including images in your version control aren’t standardized and are rarely used outside of large companies, and the rest of us are left checking out every major commit and viewing changes locally! Join me for a review of methods currently in use and discuss the benefits and drawbacks of each."
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
Thank
you
so
much.
This
is
my
first
time
in
front
of
such
a
large
audience
and
my
first
time
traveling
more
than
two
time
zones,
so
I'm
really
excited
to
be
here.
So
thanks
for
those
thanks
for
that
introduction,
so
I'm
a
self-taught
second
career
developer,
who
has
managed
a
try
on
a
lot
of
different
hats.
A
Today,
I'm
going
to
talk
about
a
problem
I
encountered
as
I
started
to
shift
from
scripting
to
front-end
roles,
how
I
developed
a
solution
for
this
problem
and
what
can
be
learned
about
communication
and
allowing
ourselves
to
build
the
tools
we
wish
we
had.
So
this
talk
is
a
little
bit
about
tooling
and
a
lot
about
opening
yourself
up
to
making
the
software
you
need
to
make
to
make
your
gift
flow.
Workflow
work
for
you,
so
not
everyone
uses
get
in
the
same
way.
A
So
before
I
talk
about
my
git
venture,
were
the
gift
adventure
worried
about
to
embark
on
together?
We
should
take
a
moment
to
review
what
my
ideal
workflow
at
the
time
I
started.
Working
on
this
project
was
and
where
I
was
as
a
user
get
user
when
I
when
I
got
started,
so
I
I
got
used
to
get
the
way
a
lot
of
people.
Do
a
loving
and
very
patient
friend
sat
me
down
and
explained
those
five
commands.
I
would
really
need
to
know.
A
That's
ad
commit
push
clone
status
and
after
54
or
so
requests
over
messenger.
Can
you
just
tell
me
one
more
time
my
friend
reasonably
decided.
It
was
time
for
to
give
me
a
cheat
sheet
and
kind
of
cut
the
cord
a
little
bit
so
I've
added
to
this
cheat
sheet
piece
by
piece,
but
I've
never
done
a
get
intensive.
So,
as
you
might
guess,
I
had
at
the
time
a
little
bit
of
discomfort
with
the
time
travel
aspects
of
get.
A
My
strategy
was
to
keep
things
linear
or
at
least
moving
in
the
same
direction
at
the
time
I
could
push/pull
and
check
out,
but
nothing,
but
anything
fancier
felt
out
of
the
question.
I've
included
what
my
typical
git
workflow
was
at
the
time
and
listed
some
steps
that
someone
who
is
more
comfortable
with
get
and
more
useless
software
engineering
might
have
in
theirs
to
kind
of
give
you
an
idea
of
what
some
of
those
differences
were.
A
So
I
had
to
force
myself
to
revert
to
previous
versions.
After
many
of
these
loops,
you
know
making
changes,
making
mistakes
having
to
go
back
I
began
to
wonder
what
I
could
do
to
make
this
back
and
forth
easier.
I
relied
on
my
commit
messages
to
guide
my
time,
travel
and
researched.
How
to
make
the
strongest
skip
net
commit
messages.
I
could
but
because
I
was
making
such
small
changes
in
experimenting.
I
found
myself
struggling
to
find
the
right
commit
to
check
out
and
I
started
wondering
if
there
was
a
better
way.
A
So
a
little
bit
about
me
before
I
was
a
developer.
I
was
a
lab
geologist
whose
work
relied
heavy
heavily
on
photo
documentation
of
rock
orientations,
and
before
that,
I
was
building
maps
for
the
Mars
Curiosity
rover.
So
even
more
visual,
as
was
mentioned
in
my
entry
I'm,
a
strong
visual
learner
and
for
me
taking
in
information
visually,
is
much
easier
than
any
other
format.
A
So
when
I
was
thinking
about
this
time-travel
problem,
I
was
having
I
contributed
to
an
outreach
project,
creating
a
dashboard
in
a
language
that
was
new
to
me
and
realized
that
when
I
was
learning
anything
else
new
and
is
there
ever
a
day
when
we're
not
having
to
learn
something
new
I
really
had
difficulty,
both
imagining
the
changes
described
in
a
ticket
and
started
and
learning
a
new
language.
So
I
started
to
wish
that
I
could
so
the
cognitive
load
of
having
to
imagine
and
learn
was
really
weighing
on
me.
A
So
for
me
and
others
that
were
would
have
been
aided
by
these
visual
cues.
There
was
a
real
hole
in
the
documentation
and
reaching
out
to
devs
on
my
project.
I
learned
that
it
was
really
unusual
in
the
industry
to
keep
strange
screenshots.
So
there
was
a
whole
industry
that
didn't
think
like
me
at
all.
A
So
I
could
have
felt
really
bad
about
this
and
taken
a
step
back,
but
I
had
already
become
a
fan
of
you
know
letting
your
users
needs
letting
your
needs
dictate
how
you
use
documentation.
What
you
do
with
your
software
and
I
did
internalize.
Just
enough
of
that
hacker
ethos
that
we
all
aspire
to,
that
I
felt
I
should
be
pushing
forward
and
you
know
making
something
to
solve
the
problem.
So
I
started
thinking
about
what
might
have
helped
me
in
all
the
Veronica
similar
folks
that
would
come
along.
A
My
next
project
is
where
I
started
to
take
action.
Although
I
was
hired
as
a
web
developer,
many
of
my
tasks
relied
on
design
skills,
I
didn't
have,
while
I
googled
and
imagined
icons
and
layouts
and
tried
to
grasp
what
would
make
a
website
useful,
appealing
and
intuitive
to
user
I
made
many
many
mistakes.
A
Often
I
would
go
to
bed
a
certain
that
I
was
on
the
right
path
and
wake
up
only
to
find
that
my
layout
felt
like
the
web,
equivalent
of
pairing,
polka,
dots
and
plaid,
and
neither
me
nor
my
client
were
ready
to
make
that
bold
of
a
choice
or
sometimes
I'd,
move
forward
for
a
week
or
more
only
to
find
that
my
client
on
seeing
exactly
what
they
had
asked
for
wanted
to
go
in
a
different
direction.
So
who's
had
that
moment.
Anybody
else
doing
client
work
in
this
room.
A
I
see
a
couple
of
hands
like
that:
we
we,
we
have
all
been
there
so
above
you'll,
see
variations
of
a
logo
I
made
for
one
client
at
the
time.
I
made
these
I
didn't
know
the
research
that
design
entails.
So
after
an
initial
conversation,
I
was
turning
out
variations
and
believed
that
I
was
practicing.
Design
has
any
one
ever
built,
something
without
considering
all
the
parts
of
the
project
that
they
didn't
know
how
to
build
individually.
A
Anyone,
so
many
folks,
not
just
me
having
a
reach
passion
project,
is
a
great
motivator
but
having
to
go
back
to
tutorial
level
foundational
projects.
As
you
start,
each
component
makes
the
process
of
learning
and
finally,
building
long
and
slow.
This
was
the
position.
I
was
in
as
I
tried
to
learn
design
principles
on
the
fly.
A
You'll
notice
that
the
steps
that
I
was
doing
are
all
the
way
down
the
list.
I
had
skipped
all
the
deep
information
finding
and
gone
straight
to.
Let's
build
stuff
honestly
I
had
internalized
some
toxic
ideas
like
ideas
are
cheap,
make
it
or
it
didn't
happen,
and
those
ideas
undersell
the
importance
and
foundational
investigative
work
that
helps
us
ask.
What
should
we
be
building
and
because
I
wasn't
taking
those
steps?
A
I
was
making
many
many
changes
in
reverting
many
many
times
all
this
iteration
and
redesign
after
feedback
put
me
in
a
special
kind
of
version
control
hell.
It
was
extremely
hard
to
track
these
changes
with
commit
messages,
and
especially
with
my
memory
having
to
throw
myself
into
the
design
face-first
the
hard
way
I
wouldn't
recommend.
It
opened
me
up
to
new
ideas
about
how
to
use
get.
A
So
this
back
and
forth
meant
I
had
to
do
a
lot
of
get
time.
Travel
and
I
was
again
relying
on
my
commit
messages,
two
problems
with
this
one.
We
all
know
what
happens
to
commit
messages
when
we've
been
working
too
long.
Yes,
I
had
some
trash
commit
messages
to
decipher
as
much
as
I
reached
as
as
I
researched,
how
to
make
the
most
helpful
get
cos,
and
there
are
some
guidelines
up
there.
I
still
fell
into
that
dark
place
that
this
comment
references.
A
A
I
had
all
these
long
descriptions
that
had
me
wondering
if
it
was
the
lighter
green
or
the
lighter,
lighter
green
or
the
really
light
green
or
maybe
the
light
neon
green.
It
was
a
mess
that
was
a
mess
and
also
my
get
history
was
messy
and
hard
to
navigate
I
had
to
mentally
manually
roll
back
to
several
points,
just
to
find
the
version
that
I
needed
if
I
had
made
a
mistake.
A
There
were
a
few
things
that
I
could
try.
I
could
use
the
tools
that
I
had
better,
such
as
trying
to
write
better
commit
messages.
I
could
find
tools
that
give
my
brain
the
visual
cues
I
needed
or
I
brainstormed
about
this.
For
some
time
to
address
the
problem,
our
design
friends
might
tell
us
we
need
to
define
the
problem.
The
difficulty
was
that
I
didn't
know
how
far
back
I
would
be
going
and
I
hated
the
process
of
doing
it.
A
Look
at
all
those
steps
understand
that
as
a
visual
person
and
others
experimenting
with
any
back
and
forth,
visual
work
may
have
the
same
experience
and
as
a
relatively
new
developer,
I
was
mentally
recreating
an
image
in
my
brain
from
these
commit
messages.
The
loop
of
going
back
and
forth,
and
maybe
going
to
the
wrong
place,
was
frustrating
for
me
and
put
me
took
me
outside
of
my
productive
flow,
which
has
a
relatively
new
programmer.
Is
a
scary
place
to
be?
A
A
I
was
already
keeping
screenshots
to
show
clients,
so
it
seemed
natural
to
keep
my
own
personal
folder
of
screenshots.
Sometimes
I
would
flip
through
these,
like
a
flipbook,
to
look
for
trends
that
might
inform
me
of
where
I
should
go
next,
but
when
I
had
to
look
for
a
specific
image
like
I
need
that
for
link
nav
bar
without
underlines
I
still
struggled
looking
through
timestamps
or
tiny
icons,
really
I
realized
that
I
need
those
those
images
to
be
connected
to
my
version
control.
To
do
me
any
good.
A
Meanwhile,
I
had
learned
about
in
the
editor
hex
color
previews,
which
are
amazing,
and
everyone
should
try
some
even
let
you
select
add
different
colors
from
UI,
so
you
can
experiment
even
faster.
These
helped
me
when
I
was
coding,
but
to
open
rolled
back
code
in
my
editor.
I
would
already
have
already
needed
to
do
that.
Get
checkout
dance
which
messed
up
my
flow
and
I
didn't
like
so
I
started
thinking
about
a
more
programmatic
solution.
A
A
Control
for
shift
for
I
might
forget
to
add
a
screenshot
or
add
the
wrong
one,
and
suddenly
I
was
back
at
that
giant
folder
that
I
described
earlier
I
had
the
time
spent
renaming
and
linking
my
screenshots
and
the
time
I
spent
wondering
how
often
to
take
screenshots
in
the
first
place.
It
was
a
pain.
It
was
slowing
me
down,
and
this
was
all
made
worse
by
the
fact
that
I
had
started
to
worry
about
this
wasted
time.
I
didn't
know
how
to
address
this.
A
I
had
used
the
tools
that
I
knew
of
like
an
engineer.
I'd
put
them
together
to
solve
a
problem
in
a
creative
way,
but
I
had
made
new
problems
too,
and
I
was
starting
to
think
I
didn't
know
what
problem
to
solve.
I'd
start
I
started
talking
to
other
developers
about
my
idea,
and
people
disagreed
Oh.
What
such
strong
reactions
told
me
that
I
should
look
into
this
more.
Interestingly.
A
Usually
those
working
with
agencies
said,
but
we
don't
have
time
for
that
kind
of
documentation.
Individual
contractors,
that's
me
we're
excited
because
they
would
have
an
additional
form
of
documentation
for
themselves
and
folks
and
large
companies.
Surprisingly,
to
me
at
least
said:
oh,
we
have
that
I
had
to
talk
to
these
folks
more
so
the
developers
in
the
in
the
in
these
companies
really
had
something
to
say,
and
we
talked
about
screenshot
diffing,
which
is
used
by
honestly
I.
A
Think
every
large
company
that
I've
spoken
to
eBay
and
Google
are
a
few
and
they
use
screenshot
to
come,
comparing
screenshots
as
part
of
their
testing
process,
so
screenshot
diffing
for
who
uses
screenshot
diffing
in
their
work
in
life,
regression
testing
any
I,
see
a
bunch
of
hands
and
that's
super,
and
you
can
take
a
little
nap
during
the
slide.
If
you
want
or
correct
me
if
I'm
wrong.
A
So
in
one
example,
I
used
a
nice
picture
up
here
to
make
to
keep
things
simple,
but
if
we
have
these
two
images
to
our
naked
eye,
they
look
the
same.
But
if
we
are
to
compare
them
with
a
computer,
we
can
see
that
there's
areas
that
are
different,
perhaps
there's
a
filter,
and
we
and
so
what
happens
with
screenshot
dipping
is
we
have
our
golden
right
up
there
in
the
top
corner
and
we
compare
these
two
images
and
if
there
are
a
certain
of
percent
difference.
A
Yes,
you
know
it's
brought
down
to
a
human
and
our
poor
human
has
to
look
and
decide
either.
This
is
the
correct
image
I'm
manually,
making
this
the
new
golden,
our
new
image,
or
they
say.
Oh,
this
is
wrong.
They
change
whatever
they
believe,
needs
to
be
changed
and
send
it
right
back
up
through
the
process.
A
So,
interestingly,
I
went
to
known
about
this
at
all.
I
had
never
used
or
heard
of
this
before
and
I
would
have
never
known
if
I
hadn't
gone
through
the
process
of
talking
to
a
whole
bunch
of
developers
about
50%
of
which
told
me
my
idea
was
the
stupidest
thing
they'd
ever
heard
of,
and
they
didn't
need
it
so,
but
I
talked
to
that
other
50%
and
they
really
had
something
to
say
so.
There's
a
lot
to
be
gained
from
talking
to
folks
who
work
with
different
tools
and
different
settings,
etc.
A
A
So
the
thing
that
surprised
me
most
about
discussing
this
idea
with
design
folks
is
how
quick
they
were
to
point
me
to
tools
that
they
had
used
and
how
much
curiosity
they
had
about
get
and
other
tools
used
by
developers.
We
heard
early
in
a
previous
talk
how
powerful
can
be
for
a
design
tool,
but
for
a
design
person
to
use
developer
tools
and
to
share
that
experience.
A
We're
working
so
closely,
sometimes
just
desks
away
from
our
designer
mates,
but
we
often
don't
understand
what
they're
doing,
how
they're
doing
it
or
what
we
could
learn
from
each
other.
So
in
all
cases
my
designer
chats
were
extremely
eye-opening.
If
you
haven't
already
I,
definitely
encourage
you
to
talk
shop
with
some
folks
who
work
on
a
different
aspect
of
your
projects.
You
might
be
surprised
what
you
learn
in
conclusion:
don't
be
this
cat
he's
not
having
any
fun
and
he's
not
learning
anything
new.
A
In
my
case,
I
learned
that
designers
had
already
solved
my
problem,
so
sketches
pages,
which
you
see
on
the
right
is
similar
to
the
idea
that
I
had
with
a
folder
that
you
flipped
through,
and
that
is
how-
and
so
it
was
a
very
visual.
You
say
like
here's,
what
we
had
at
Point,
a
here's.
What
we
had
at
point
B
and
a
lot
of
folks
would
usually
serious,
would
use
it
as
a
flip
book.
A
A
So
far,
I
had
taken
some
steps
I
had
made
like
we
might
call
it.
An
early
prototype
I
had
seen
some
problems.
I
had
confirmed
that
other
people
had
these
problems.
They
were
common
and
I
had
researched.
How
other
folks
had
solved
related
problems
and
kind
of
gotten
the
lay
of
the
land?
So
what
are
our
pain
points?
We
have
still
the
time
to
take
the
screenshots.
A
They
aren't
all
proprietary
and
two
of
those
are
pipe
a
tear
if
you
are
into
Python
one
of
my
favorite
languages
or
puppeteer,
and
so
that-
and
so
those
are
often
connected
to
screen,
shot
dipping
and
will
allow
you
to
to
create
those
those
images.
So,
as
far
as
remembering
just
try
to
take
the
screenshots,
we
learned
a
little
earlier
about
get
hooks
and
which,
if
you
weren't
in
those
discussions,
are
it's
basically
a
script
that
allows
other
things
to
happen
when
you
take
an
action
with
inget.
A
So
in
this
case,
when
we
do
a
commit
within
get
get
return
and
kind
of
tap
pipe
a
tear,
and
let
them
know
that
it's
time
to
take
a
screenshot
I'm
still
working
on
this
third
step,
and
if
anyone
has
ideas,
I'm
happy
to
hear
them.
But
my
idea
right
now
is
to
you
know,
have
a
terminal
prompt
I
enjoy
using
the
terminal
to
encourage
you
to
save
by
hand
like
hey.
Have
you
done
this?
But
if
other
folks
have
other
ideas,
I
will
be
around
after
the
talk
and
I
would
love
to
chat.
A
So
we
can
think
of
each
of
these
kind
of
like
a
wrapper
of
this.
That
calls
other
steps.
So
one
part
of
this
exploration
for
me
has
been
realizing
the
value
of
my
experience,
both
as
a
geologist
in
my
past
life
and
as
a
visual
learner
in
my
always
life
and
what
those
can
bring
to
my
work.
It's
a
hard
realization
to
come
to
because,
as
I
started
to
transition
careers,
many
folks
could
couldn't
hide
their
shock.
They
said
a
geologist.
Well,
that's
a
shift.
A
Similarly,
when
I
started
to
explore
screenshots
and
guess
get
I
heard
some
very
strong,
we
don't
do
that.
This
is
rough
stuff
for
people
to
hear
and
I
felt
as
if,
as
I
was
working
towards
my
first
job.
That
I
would
need
to
put
my
past
life
behind
me,
so
I
could
be
successful
in
this
one.
The
shame
of
that
is
is
that
I
now
realize
that
I
was
most
able
to
contribute
that
I
was
most
able
to
contribute
when
I
realized
the
value
of
my
past.
A
So
this
affects
a
lot
of
people
as
I
was
writing
this
talk.
I
I
got
a
Twitter
message
out
of
the
blue
from
a
career
shifting
academic.
That
thanked
me
just
for
talking
openly
about
my
academic
research.
You
know
the
research
I
had
done.
Anyone
went
on
just
and
I
was
really
surprised
by
this
because
who
isn't
able
to
talk
about?
You
know
their
research
that
they've
done
in
the
past,
but
it
really
can
matter
a
lot
to
to
folks
and
also
allows
you
to
do
your
best
work.
A
So,
at
whatever
point
you
can
bring
your
whole
self
to
work.
I
encourage
you
to
to
do
that
so
being
able
to
use
our
paths
and
our
skills
is
powerful
and
is
going
to
make
us
better
programmers
and,
frankly,
better
people
too.
So
should
you
be
using
screenshots
in
your
version?
Control
I,
don't
have
an
answer
for
you.
A
The
nearly
50/50
love-hate
split
that
I
found
as
I
was
talking
to
developers,
definitely
indicates
that's
an
idea
worth
chewing
on
and
I
can't
help,
but
notice
that
since
there's
roughly
65%
of
humans,
that
are
visual
learners
and
about
50
50
people
who
strongly
loved
or
hated
this
idea,
that's
there
might
be
a
whole
lot
of
overlap
there.
We
could
get
into
a
whole
correlation
causation
discussion
at
some
other
time
and
I
don't
have
the
data
for
that,
but
this
is
a
thing
that
might
be
happening.
A
A
So
here
are
some
tools
that
I
used
as
I
was.
You
know
in
my
exploration
that
you
might
find
helpful.
There's
no
question
no
time
for
questions
today,
but
I
really
hope.
There's
a
conversation
that
grows
around
this
and
I
strongly
encourage
you
to
tweet
or
find
me
at
the
break
and
I
wanted
to.
Thank
you
all
for
being
such
a
great
audience.
I've
never
spoken
to
more
than
20
people
before,
so
it
was
really
nice
to
have
a
supportive
crew.