►
From YouTube: From CLI to GUI: Overcoming Challenges to Advance Git, John Haley & Hamid Shojaee - Git Merge 2016
Description
Git was designed with the command line in mind, but does that hold the application back? John Haley, Product Owner of Axosoft GitKraken and Hamid Shojaee, Founder of Axosoft, argue that the CLI can be complicated and confusing, with a steep learning curve even for developers. That’s why they’ve created a Git client that is not only beautiful and easy-to-use, but actually translates Git concepts into visually understandable processes.
Hamid Shojaee is addicted to the high of making great software. He is founder of two tech companies, Axosoft and Pure Chat, and has been a leader in the Arizona tech community for over 20 years.
John Haley has been writing software for over 25 years and is currently Product Owner of Axosoft GitKraken. John loves bridging the two worlds of art and science in order to create software that, like a good piece of art, leaves the user feeling an emotional connection to it.
About Git Merge:
Git Merge is the pre-eminent Git-focused conference: a full-day offering technical content, user case studies and training workshops for Git users of all levels.
Visit: http://git-merge.com/
A
A
A
A
We
we
take
those
opportunities
to
learn
about
node
and
web
sockets
and
all
sorts
of
stuff
that
sort
of
comes
all
the
time
at
us
as
developers
that
our
techniques
and
skills
would
be
outdated.
If
we
didn't
do
those
things
after
five
years
right
so
18
months
ago,
John
and
another
colleague
max
come
to
me
before
the
start
of
one
of
these
30
day
projects
and
they
say:
hey
hameed.
We
want
to
create
a
git
client,
one
that
sort
of
takes
the
normal
and,
of
course,
the
normal
sort
of
get
graph.
A
This
is
a
CLI
representation
of
interactions
with
your
git
repository
and
turns
it
into
something:
that's
a
little
bit
more
human
readable
as
opposed
to
machine
readable
that
is
visually
pleasing
to
look
at
and
ideally
allows
you
to
interact
with
it
using
the
graph,
and
my
response
was
why:
why
do
we
need
another?
Get
client
essentially,
aren't
there
already
a
bunch
of
them
out
there
and
their
response
was
yes,
but
they
all
rely
on
the
CLI.
They
can't
do
anything
to
CL.
A
I
can't
do
they're
all
terrible
performance
and
they
all
have
this
problem
and
that
problem
all
the
stuff,
basically
that
everybody
else
hates
all
the
sort
of
get
clients
for
their
regurgitate
it
back
to
me
and
our
goal.
We
we
want
to
create
something
that
doesn't
suck
right
and
that's
just
that's
the
bar
that
we're
going
after
and
I
said.
Well,
if
you're
going
that
high
you're
going
to
try
to
create
something
that
doesn't
suck,
then
it
let's
do
it.
Can
you
do
it
in
30
days
right,
because
that
was
sort
of
my
main
concern?
A
Can
it
be
done
in
30
days
and
they're
like
yeah?
We
can
probably
get
a
prototype
going
in
30
days,
but
to
create
a
real
good,
solid
product
that
can
be
used.
You
know
we
probably
need
more,
like
three
months
right,
like
famous
last
words
of
developers
who
are
like
predicting
and
scheduling
software.
So
of
course,
six
months
later,
nothing
and
I
was
like
nine
months
later,
I
check
in
and
they're
like.
A
Oh,
we
had
to
write
this
other
library
called
node
get
and
yeah
we've
been
working
on
that
12
months
later
we
had
to
rewrite
everything
from
scratch.
We
now
know
so
much
more
yeah,
now
I'm
thinking,
okay,
should
I
fire.
These
guys
because,
like
this
is
going
nowhere
fast,
but
there
was
a
glimpse
of
hope.
There
was
something
special
that
was
already
sort
of
visible
and
we
decided
no
we're
going
to
double
down
on
this
thing
and
week
watch.
A
In
fact,
we
quadrupled
the
team
size
and
we
put
like
a
ton
of
resources
into
it
and
we
sort
of
made
it
a
mission
to
solve
this
problem
and
then
18
months
later,
so
that
was
12
months.
Oh
point
point:
18
months
later.
Finally,
we
saw
this
on
Twitter,
so
Felix
Meyer,
who
I
don't
know,
is
Felix
in
the
audience
today,
no
ok
cool,
so
he
tweets
out
I,
really
love
get
crackin.
B
A
Victory
we
created
something
that
doesn't
suck
with
the
gate,
gate,
community
and,
of
course,
Felix
wasn't
the
only
one.
We
literally
get
hundreds
of
tweets
every
week
about
how
people
love
the
interactions
that
they
do
with
get
crackin,
and
it
feels
really
good,
but
really
we're
thinking
wow,
how
bad
the
software
in
a
category
have
to
be
that
in
order
to
get
lots
of
people
to
fall
in
love
with
it,
you
just
have
to
sort
of
reach
this
bar
of
not
sucking,
so
that
was
really
cool.
A
But
of
course,
a
lot
of
you
guys
are
thinking
why
a
GUI
at
all
right
like.
Why
do
we
need
a
graphical
user
interface?
On
top
of
this
thing,
so
undoubtedly
all
of
you
guys
have
probably
tried
to
explain
it
to
someone
else,
or
someone
has
explained
it
to
you
and
how
it
works,
and
everyone
starts
with
this.
You
know
directional
asynchronous
or
what
is
it?
A
a
cyclical
excuse
me
graph
right,
directional,
AC,
a
cyclical
graph
that
represents
source
control
repositories
and
your
snapshots
and
your
branches,
and
your
merges
right.
A
You
could
try
to
describe
this
graph
to
people
instead
of
just
drawing
one
out
but
drawing.
It
is
a
lot
easier
to
allow
people
to
understand,
and
our
thinking
is
that
you
know
how
awesome
would
it
be
to
actually
work
with
that
graph
for
your
day-to-day
interactions
with
get,
and
it
not
only
makes
it
easier
to
understand
but
easier
to
interact
with,
and
that
has
been
the
sort
of
mission
of
the
get
crackin
project.
A
B
B
So
you
know
I've
been
a
long
time
get
user
and
in
that
time
I
I've
seen
gets
popularity
just
skyrocket.
It's
been
fantastic
and
exciting,
and
an
amazing
to
watch
and,
as
Chris
said
earlier,
we
want
to
put
svn
out
to
pasture
and
its
kind
of
happening.
So
that's
that's
good.
You
know
every
seems
like
every
day.
Every
week
we
hear
about
another
company
and
other
service
moving
to
get,
and
you
know
it's
just
been
fantastic
to
be
part
of
this
community.
B
One
thing
I'm
not
excited
about,
though,
is
that
there
is
this
growing
kind
of
gap
that
we
we
all
have
noticed.
You
have
the
super
user
and
the
user
of
get.
You
know
the
super
user
can
come
through.
They
can.
You
know,
parse
the
ref
log
to
undo
changes
that
you
lost.
They
can
filter
out
the
branch
so
that
when
you
publish
your
production
key
to
a
public
repo,
it's
like
that,
never
happened,
never
happens.
And
then
you
have
a
user
and.
B
We
are
basically,
you
know,
these
are
the
things
we
need
to
do
to
get
our
changes
out
to
people,
and
this
is
this-
is
you
know,
kind
of
people's
introduction
to
get
at
first
hey?
This
is
get
it
tracks
collaborative
work
on
projects
through
a
beautiful
distributed
graph
through
your
eat,
remodel,
oh
cool.
How
do
we
use
it?
I
have
no
idea
memorize
these
cell
commands
and
type
them
to
sync
up.
If
you
get
errors,
save
your
work
elsewhere,
nuke
the
project
and
clone
it
again.
B
Yes,
I
mean
this
resonates
with
so
many
people,
randall
Munroe
really
hit
a
nerve
with
this
comic.
It's
very
popular
and
it
plays
out
through
offices,
time
and
time
again
so
get
does
have
a
learning
curve
problem
with
get
we
kind
of
have
a
starter
kit.
This
is
what
you
need
to
get
going.
You
can
learn
these
commands
and
start
working
with
get
collaborating
with
other
people,
and
it's
great
and
it's
you
know
it's
a.
A
B
World
and
all
this
stuff-
and
you
know
you
can
get
by
with
just
a
small
amount
of
effort
and
humans
are
lazy
and
I'm
lazy
too,
and
they
say
lazy
devs
make
the
best
devs.
So
I
like
to
do
the
minimum
amount
of
work
for
the
maximum
amount
of
result
and
if
I
can,
if
I'm
learning
something
and
I
can
get
pretty
competent
with
it,
you
know
really
fast,
then
I
I
will
and
if
there
is
a
serious
roadblock
to
getting
past.
B
That
point,
that's
probably
where
I'll
stop,
and
this
is
where
a
lot
of
lot
of
users
stop
they.
You
know
they
have
this,
and
this
is
their
fisher
price.
My
first
get
kit
and
it
makes
them
knowledgeable
enough
to
do
something
and
dangerous
and
they're
dangerous,
and
they
don't
even
know
why
they're
dangerous
they
can.
They
can
break
something
and
not
know
how
they
did
it
and
worst
of
all,
they
don't
know
how
to
do
it.
How
to
not
do
it
again
in
the
future,
so
say
they
come
along
and
they
break
something.
B
Well,
maybe
your
first
instinct
is
to
go
to
the
official
documentation,
so
you'll
go
to
that
and
it's
hard
to
parse.
It
reads
like
people
took
random
English
words
abstracted
their
meaning
out
to
nothing
randomly
arranged
them
onto
a
page
and
I
have
to
have
a
computer
science
scientist
decoded.
So
what
we're
looking
at
right
now
is
actually
a
generated
man
page
that
is
such
a
spot-on
parody.
We
have
to
have
a
banner
at
the
top,
so
let
people
know
this
isn't
real.
B
However,
this
generated
man
page
is
about
is
useful
to
a
new
user
as
the
real
deal.
So,
okay,
I'm
a
new
user
I
just
broke
something
I'm
in
trouble.
I'm
going
to
call
the
office
get
guru.
Probably
somebody
in
this
audience,
you're
going
to
come
in
you're
going
to
you
know,
basically
sit
down
and
say:
well
you
see
when
you
tiptoe
through
a
branch,
we're
gonna
do
a
t-test
history,
which
means
you
have
British
it
and
usually
going
to
be
like
I
have
no
idea
what
you're
talking
about
what
the
hell
are.
B
These
words,
like
I,
just
need
this.
This
fixed
and
I
need.
It
pushed
like
we're
going
into
production.
Things
are
broken,
give
me
a
hand,
so
we're
going
to
come
in
we're
going
to
solve
their
problem,
we're
going
to
fix
it.
Then
we're
going
to
fly
away
and
then
the
next
time
something
breaks,
we're
going
to
come
back
in
like
Superman
and
we'll
just
keep
going
again
and
again
and
again,
and
nothing
ever
gets
better.
Now
these
users,
they
aren't
what
I
would
call
computer
illiterate
people
like
these.
B
Almost
all
of
them
are
comfortable
on
the
COI,
but
they
still
find
get
difficult.
You
know
this
is
this
is
kind
of
disconcerting.
Get
is
almost
becoming
a
required
technology
to
use
as
a
developer.
It's
so
ambiguous.
We,
you
know
the
the
adoption
rate
has
just
exploded.
We
use
it
everywhere.
You
know
if
I,
if
I'm
hiring
somebody
out
of
college
and
they
and
they
don't
know,
get
it's
like
well
holy
crap.
We
have
a
lot
to
go
over.
You
know
when
you
get
hired
or
whatever.
B
B
You
know
it's
like
I
said
it's
hard
to
recruit
new
devs,
and
we
we
have
a
problem
in
this
field
with
with
new
blood
coming
in,
and
people
kind
of
taking
up
the
reins
and
finding
new
talent.
So
we
need
to
keep
development
as
as
hard
as
it
needs
to
be
and
not
harder.
We
would
like
to
make
it
as
easy
as
possible
for
for
people
to
understand
these
concepts.
B
You
know
development
works
best
when
you
collaborate
with
other
people
and
collaborating
with
other
people
works
best
when
you
have
a
growing
community
to
do
that
with
and
get
itself
is
made
so
that
you
can
work
with
other
people
better.
So
you
know
we,
you
probably
all
know
this
and
if
not
I'm,
just
hoping
that
you're
at
least
entertaining
the
idea,
so
I
don't
want
to
get
up
and
talk
about
a
problem
and
not
kind
of
go
over
a
little
bit
of
the
solution
that
we
we
came
up
with.
B
So
what
we
did
is
we
wanted
to
kind
of
get
back,
get
to
the
core
of
get.
What
is
the
core
of
get
like
everyone's
been
saying?
It's
a
directional,
a
cyclical
graph,
it's
a
graph,
it's
a
collection
of
edges
and
nodes.
It's
directional,
you
have
a
flow
between
them.
You
can
go
from
A
to
B,
but
not
back
and
it's
a
cyclical
a
to
b
to
c,
but
you
can't
go
back
to
a,
and
this
is
the
core
of
get
it.
B
It
might
not
be
useful
for
teaching
someone
right
off
the
bat,
but
this
is
the
core.
Everything
else
is
built
up
off
of
this,
so
graphs
naturally
want
to
be
graphical,
and
it
makes
sense.
Get,
however,
is
exclusively
used
as
a
COI
tool
and
gooeys
are
almost
always
considered
to
be
second-class
citizens
in
in
gooeys.
You
know
you,
you
have
to
shell
out
to
the
command
line
and
if
you
want
to
stay
in
the
command
line
and
get
a
graph,
you
have
to
use
this
command,
which
is
totally
obvious.
B
B
But
you
have
a
CLI
interface,
which
is
I
mean
it's
really
not
graphical,
so
you're
forced
to
work
outside
of
of
what
I
would
argue,
gets
natural
environment
and
you
have
to
keep
another
model
of
data
in
your
head,
and
if
this
model
is
wrong,
we
can
get
into
a
lot
of
trouble,
so
else
attack.
So
soft.
We
wanted
to
take
a
new
approach.
We
wanted
to
distill
get
down
and
just
get
to
the
core
concepts.
We
wanted
to
figure
out
what
you
know.
What
was
it
that
you
really
needed
in
get?
B
You
know
just
break
it
all
down
and
start
from
scratch.
Now,
when
I
say
to
still
get
I,
don't
mean
we
want
to
get
get
light
or
sort
of
get
or
get
for
dummies,
but
just
get
down
to
the
core
concepts.
This
is
our
starting
point
and
from
here
we'll
build
up
so
get
gooeys
like
I
was
saying
they
all
show
up
to
the
CLI.
B
So
a
lot
of
goodies
is
basically
a
series
of
forms
you
fill
out
which
take
an
input
and
then
take
that
input
and
go
submit
it
to
the
CLI
command,
run
that
and
then
come
back
with
the
result,
and
it
begs
the
question
that
a
lot
of
people
ask
why,
even
why
do
this?
Why
learn
a
GUI
when
that's
all
you're
doing
you're
going
out
to
the
CLI
just
bypass
the
middleman?
B
Go,
learn
real
get
and
and
that's
what
you
should
do
and
you'll
tell
this
to
you
know
somebody
that's
coming
in
so
I
mean
it's
learning,
get
for
the
first
time
and
they'll
say
yeah
yeah
this
that
that
sounds
good.
I
want
to
learn
real
kid.
I
wanted
to
use
the
actual
application
that
everyone
else
uses
and
and
they'll
start
using
it,
but
they
really
won't
be
able
to
grok
the
concepts,
because
it's
not
graphical,
it's
not
showing
them
what's
happening.
B
It's
a
black
box,
you're,
just
piping
things
in
and
then
seeing
some
shot
at
the
end
and
okay,
that's
cool!
So
that's
that's
what
it
did.
You
know
ef-2
for
a
blah
blah
blah,
and
you
know
we.
We
wanted
to
throw
all
this
out
challenge
all
of
these
assumptions
and
start
from
scratch.
So,
like
I
said
get
is
just
a
graph,
that's
the
heart
of
death,
so
this
is
the
basis
for
forget
cracking.
We
wanted
to
kind
of
make
the
fundamentals
easy.
B
We
wanted
to
optimize
for
that
and
doing
so
dictated
to
us
that
we
made
the
graph
the
center
of
the
user
experience
we
wanted
to
show
users
were
half
what
was
happening,
not
just
be
a
black
box.
We
wanted
to
allow
them
to
interact
rack
graphically
with
their
get
repo
and
we
wanted
to
even
show
users
what
action
they
were
due
and
and
how
that
would
affect
the
repo
if
they
were
to
do
it.
B
So
you
could
see
like
hey
if
I'm
going
to
merge
these
two,
these
two
branches,
you
can
see
that
not
your
repo,
not
only
as
it
is,
but
as
it
will
be
if
you
perform
the
action.
So
you
know
when,
when
we're
doing
this
Max
and
I
when
we
started
it
was
just
the
two
of
us
we're
not
designers,
you
know
we're
coders
at
heart
and
we're
not
very
visually
artistic.
So
we
needed
something
more
we
needed
to
we
needed
to
make
get
beautiful.
B
If
we
may
get
beautiful,
we
thought
that
we
could
have
a
captive
audience
and
with
a
captive
audience,
it
would
be
easier
for
for
the
user
to
learn,
so
we
needed
a
skilled,
visual
artist
that
could
come
in
and
help
us.
So
we
had
a
pretty
primitive
you
I.
We
we
just
moved
really
fast.
We
iterated,
we
got
a
design,
refined,
it
reimplemented,
it
blah
blah
blah
and
we
moved
really
fast
and
we
just
try
to
get
something
that
we
thought
could
help
people
learn
and
experiencing
use
get.
So
here
we
are.
B
This
is
the
graph.
Now,
what
are
the
top
things
that
we
really
need
to
see
when
we're
using
it?
We
need
to
see
where
things
are.
We
need
to
see
who
did
what
and
we
need
to
see
what
they
did.
So
with
this
we
thought
we
have
the
beginnings
of
something
beautiful,
something
that
could
captivate
a
user
and
make
them
want
to
use
this
application,
not
because
their
boss
said
so
or
their
lead.
Dev
said
so
or
it
was
from
on
high
or
the
internet
says.
B
This
is
what
they
should
be
doing,
but
because
they
wanted
to
and
if
they
want
to,
then
we've
kind
of
fought,
half
the
battle.
You
know
learning
is
now
an
uphill
uphill
battle.
We
can,
we
can
start
helping
people
learn
the
concepts
a
little
bit
easier.
So
there's
still
something
missing
yet
doesn't
really
lead
to
exploration.
B
You
know
when
your
when
your
code
base
is
on
the
line,
and
things
can
break
that,
doesn't
really
give
you
a
a
good
motivating
factor
for
like
exploring
what
the
capabilities
of
this
tool
are.
So
we
knew
we
needed
something
else.
We
needed
an
undo
button,
a
bailout
switch
that
allows
the
user
to
get
back
to
where
things
were
good
back,
get
back
to
when
things
weren't
broken
and
I
didn't
accidentally.
You
know
discard
all
of
my
changes.
You
know
we
had
this
try
and
stop
letting
get
be
scary.
The
users
curiosity
can't
be
stifled.
B
Another
thing
that
does
stifle
curiosity,
our
modal
popup
boxes.
You
when
you
use
gate,
it's
always
like
well,
are
you
sure,
do
you
want
to
stash
Oh
muwah
like
these
things?
They
break
the
flow
and
they
make
using
get
a
chore.
So
with
an
undo
button
we
can
kind
of
remove
a
lot
of
this
stuff
and
when
we
remove
it
it
makes
you
know
it
dramatically.
Improves
using
get
just
overall
I
mean.
Can
you
imagine
if
you
were
in
in
a
word
processing
application,
and
you
were
prompted
every
time
you
tried
to
delete
a
word.
B
You'd
go
mad
I
would
I
would
never
do
that.
So
you
know
we
have
to
you
know
it
just
felt
natural
to
kind
of
remove
these
from
the
application.
We
also
knew
it
had
to
be
cross-platform.
I
use
all
three
operating
systems
all
of
the
time
and
Linux
can't
be
an
afterthought.
So
luckily,
for
us,
when
I
when
I
started,
writing
get
crack
and
I
actually
moved
over
to
get
hubs.
B
Fantastic
Adam
editor,
and
that
was
one
of
the
first
dev
tools
that
really
gave
me
a
solid,
consistent
experience
across
all
of
the
machines
that
I
used-
and
you
know
thankfully,
github
open
sourced
Adam
and
the
core
of
Adam
is
an
engine
called
electron.
So
we
use
electron
to
give
us
this
cross
cross
platform
capability,
and
you
know-
and
thank
you
very
much
github
for
doing
that.
So
we
we
had
a
rule
in
get
crackin
and
that
and
the
number
one
rule
is
never
shell
out
to
the
CLI.
B
So
without
shelling
out
to
the
CLI
we
had
to
bring
in
some
requirements
and
luckily
for
us,
some
very
talented
people
were
already
hard
at
work
at
a
library
called
Libya
too,
and
now
we
had
a
problem
of
how
do
we
bring
Libya
to
into
electron
and
that
problem
was
solved
partially
by
node
get
and
when
we
started
no
get
was
it
wasn't
complete?
You
know
there
was
a
lot
of
really
good
work
done
on
it,
but
it
wasn't.
It
wasn't
ready
for
primetime.
B
Yet
so
the
get
cracking
team
we
became
head
maintained
errs
on
it
and
we
started.
You
know
working,
I
am
bringing
it
up
and
making
it
better
and
and
actually
now
lybb
get
to
or
no
get
is
the
most
popular
lib
get
to
bindings
library,
which
is
really
exciting,
and-
and
that
means
a
lot
to
me-
cuz,
I
very
much
value
giving
back
to
the
community
and
it's
great
to
see
something
that
you
use
get
get
a
lot
of
or
something
that
you
may
get
a
lot
of
use
out
there
in
the
community.
B
So
when
hameed
said
that
this
was
going
to
take
three
months,
so
we
blew
way
past
that
deadline,
you
know
I
mean,
has
anybody
else
ever
like
gone
over
over
time?
No,
okay,
I
hate
you
so
but
I
mean
we
think
it's
worth
it.
You
know
we
spent
a
lot
of
time.
We
we
did
all
this
stuff,
you
know
and
and
just
kind
of
we
try
to
think
differently
about
how
get
should
be
used.
B
B
This
is
great,
like
I'm,
actually,
understanding
what's
happening,
and
you
know
I've
tried
to
before
and
for
whatever
reason
it
never
clicked,
but
now
it's
starting
to
and
it
was
reinforcing
these
concepts
and
that
helped
drive
better
use
of
the
of
the
interface
and
helped
drive
them
kind
of
diving
deeper.
It
was
a
positive
feedback
loop,
which
was
just
fantastic
I'll,
just
grab
this
guy.
B
So
if
I
could
kind
of
leave
you
with
anything
today,
I'd
like
to
leave
you
with
this,
is
the
CEO
I,
truly
the
ideal
for
how
most
users
should
use
the
get
application,
or
is
that
just
how
we've
always
done
it
to
reference
the
late
Grace
Hopper,
the
most
dangerous
phrase
in
our
language?
Is:
we've
always
done
it.
This
way
and
I
try
to
fight
that.
I'm
john
haley,
I'm
part
of
the
get
cracking
team
and
we
also
try
to
fight
that
thang.
A
Very
cool,
so
can
you
guys
hear
me
as
well
all
right
awesome?
So
we
have
two
minutes
for
questions
and
we
have
we're
going
to
bribe
you.
We
have
these
t-shirts
that
my
colleagues
over
here
are
going
to
be
throwing
at
you.
One
of
them
is
very
aggressive,
so
she
might
throw
it
at
your
face.
Let's
start
over
here
go
ahead.
A
A
B
A
Team
used
it
right
away,
but
we
have
other
dev
teams
that
resisted
for
some
time
but
they're
all
on,
because
it
didn't
work
initially.
You
know
like
12
months
and
it
was
like
really,
but
no
it
eventually.
No,
no,
it's
a
it
became
solid
to
where
now
everybody
is
on
get
crackin.
Let's
do
one
more
question
real
quick
over
here
in
the
Wolves.