►
From YouTube: Git to empower your instinctive skills and your collaboration culture - Git Merge 2022
Description
Presented by Carlo Gilmar Padilla Santana
Although nowadays we need to use git to manage the version control in our code projects, we forget git is more than a tool to upload and share our code. During my journey as a developer I've seen how software projects evolve and grow in many ways: more code, more features, more people, more business rules, more complexity than any software project. I´d like to share my experience as a joiner in new projects who have to deal with this complexity for the beginning.
If you only use git to commit your changes and allow it to integrate, you´re probably losing the opportunity to take advantage of all the things that you can do with git. When I used to teach git to young developers I say git is more than six commands, because it's about how you and your team are building software. So using git you´re able to discover all the collaborative dynamics in your current project.
During this talk I’ll share how you can use git as the magnifier to learn not just about code, to learn about how your team is collaborating together, how to reconstruct parts of your project, understand how your team is building features, how git could gives you the answer to many questions for your team, I’ll share how it’s a powerful tool for new joiners, and how git could become you to a better team player.
About Git Merge:
Git Merge is dedicated to amplifying new voices in the Git community and showcasing the most thought-provoking projects from developers, maintainers, and teams around the world. Git Merge 2022 took place at Morgan Manufacturing in Chicago, IL on September 14th and 15th.
A
Hi
everyone
today
I
would
like
to
share
with
all
of
you,
not
your,
not
just
part
of
my
story
about
how
I
learned
it
I
would
like
to
give
you
some
insights
about
why.
For
me,
it
is
a
catalyst
in
my
culture,
in
my
constant
in
my
context.
In
my
life
I'm
Carlo
gilmart
I
was
born
and
raised
in
Mexico
City
I
started
informatics
engineering,
I
studied
sociology
as
well.
A
It's
really
complex
because
you
have
to
deal
with
many
things.
You
have
to
deal
with
our
repository
with
the
application
with
their
programming
language.
You
have
to
deal
with
a
context
around
how
your
team
is.
Building
these
applications
and
for
me,
I,
was
really
scared
about
that
situation.
My
first
assumption
was
that
I
can
make
many
copies
of
my
first
project
to
start
to
break
it
down
and
start
to
understand
what
was
happening
inside
this
Repository
one
day
my
mentor
decided
to
pair
with
me.
A
We
wrote
some
likes
our
code
and
after
that
he
realized
that
we
were
on
one
of
my
many
copies
of
that
repository
and
he
asked
me
why
I
have
so
many
copies
of
that
project
and
I
explained
my
feelings
and
my
Sensations
about
that.
My
I
was
afraid
to
break
the
project
and
he
told
me:
okay,
that's
no
problem,
because
we
have
a
gold
tool
for
this.
We
have
git.
So
let
me
introduce
you
to
git.
A
In
the
pragmatic
programmer,
Andy
Hunt
and
Dave
Thomas,
just
the
term
software
entropy,
to
explain
how
software
encouraged
its
complexity
in
many
ways,
software
is
really
complex
and
make
many
copies
of
that
project
was
my
way
in
that
moment
of
my
life
as
a
young
developer,
to
start
to
understand
this
complexity
and
my
sensation
about
that
was
this
moment
in
my
life.
That
I
was
really
scared
about
to
understand
many
things
around.
A
That
means
a
lot
for
me,
because
that
means
that
you
can
experiment
with
your
own
codes
that
you
can
start
to
boil
this
a
place
in
your
project,
that
you
can
make
mistakes,
and
it
doesn't
matter
because
you
can
go
back
in
the
time,
and
that,
for
me,
was
really
incredible
was
awesome
was
was
my
first
introduction
to
software
development.
It
doesn't
matter
if
you
are
not
the
best
developer,
because
you
can
make
mistakes.
You
can
experiment
with
this
and
get
show
me
this.
A
A
A
But
nobody
told
me
that
git
is
really
complex
to
learn
in
their
first
time
because
as
a
Mexican,
my
first
assumption
is
start
to
look
for
resources
in
Spanish,
so
there
are
less
a
content
in
Spanish
and
the
content
in
English
is
really
complex.
I,
remember
my
first
experience.
Reading
a
blog
post,
it
was
a
tutorial
and
I.
Don't
know
why,
but
they
wanted
to
show
how
a
commit
is
working,
but
also
how
to
make
branching
and
merch
strategies,
and
that
was
really
complex
to
me.
A
A
So
this
was
my
first
drawing
to
try
to
understand
to
me
how
git
is
working
and
made
this
a
many
years
ago,
I
tried
to
explain
how
the
basic
commands
working
in
my
mind.
This
was
the
way
that
I
found
to
understand
to
me
all
of
this
complexity
and
after
that,
I
realized
that
I
love
this
way,
because
this
allowed
me
to
boil
my
own
learning
narratives
behind
how
technology
is
working,
and
also
this
allowed
me
to
share
this
to
my
colleagues,
to
my
friends
to
my
other
colleagues
in
the
University.
A
Thanks
to
these
illustrations,
I
could
become
a
campus
expert
and,
after
that,
I
realized
the
power
behind
git,
because
git
comparison,
wine
tool
for
tracking
my
own
learning
process,
and
let
me
explain
this
point
I
remember
that
I
have
like
experience
learning
my
first
JavaScript
framework,
which
was
embroidery
yes
after
code.
Many
examples,
I
realized
that
I
was
able
to
start
tracking
just
a
part
of
the
concept
of
this
framework
in
the
commit
descriptions.
A
So
after
that,
I
realized
that
all
my
building
story
was
in
the
commits
writing
as
a
bullet
list
and
I
understand
this
as
a
powerful
technique,
because
I
was
able
to
try
to
model
this
in
my
mind
in
this
way,
using
these
drawings
to
have
the
whole
concept
about
how
a
technology
Works.
How
are
the
components,
how
I,
what
are
the
concepts
Behind
These
and
after
that
I
was
able
to
go
more
further
in
the
commit
messages,
using
the
commit
description
as
a
concept
in
code.
A
That
was
my
first
assumption
to
use
this
technique
and
after
that,
I
I
wanted
to
share
I
I
and
create
a
training
for
my
colleagues
to
explain
how
Amber
is
working
so
I
create
an
exercise.
I
made
some
bullet
points
to
follow
and
replicate
and
I
create
a
repository
where
you
can
find
the
same
bullet
list
in
the
comment
descriptions.
A
If
my
colleagues
wanted
to
check
what
was
happening
inside
these
commits,
they
just
need
to
take
the
hash
and
make
it
show,
and
they
will
see
a
the
the
lines
of
code
to
achieve
that
point,
and
for
me
this
was
really
simple,
but
it
was
really
powerful
because
this
converts
into
a
learning
experience
use
it
simple
this
for
me,
Empower.
Your
instinctive
skills
is
about
this.
It's
about
to
be
confused.
It's
about
to
find
mentors.
It's
about
understand
that
you
are
not
alone,
that
you
are
part
of
a
team.
A
Spoiler
is
not
enough,
because
software
complexity,
it's
really
really
really
complex,
because
it's
not
just
about
Version
Control.
It's
about
a
programming
languages.
It's
about
CI,
CD,
automation,
unit,
testing,
business
rules.
There
are
many
other
things
that
you
have
to
keep
in
mind
when
you
are
calling
software,
but
I
learned
that
also
it
is
not
enough
to
be
your
only
tool.
It
gives
you
your
first
step
to
start
to
understand
this
complexity,
because
you
are
not
alone,
because
software
is
built
by
people,
because
git
allows
you
to
understand
you
as
a
part
of
this
theme.
A
For
me,
I
learned
that
using
it
you
are
able
to
become
a
better
team
player,
because
you
can
start
to
build
your
autonomy
and
your
confidence
through
exploring
a
git
Repository,
and
this
will
give
you
better
questions
to
ask
to
your
team.
That's
what
I
like
it,
because
getting
forced
you
to
ask
to
your
team
to
ask
for
support
to
recognize
what
things
you
are
understanding
and
which
things
you
can
understand.
You
are
forced
to
face
your
hypothesis
with
the
reality
with
their
project
with
the
people
with
the
clients.
A
Remember
that
I
was
joking
with
the
name
because
for
me
was
in
the
same
way
that
test
driving
development,
because
your
test,
first
and
after
that,
you
write
your
your
lines
of
code
and
for
me
was
like.
Oh
my
God.
This
is
like
a
commit
driven
development
use
git
to
tell
how
you
are
building
software
after
that.
A
I
I
really
like
this
this
technique,
because
it
was
really
simple
to
have
this
Clarity
before
code
and
to
start
to
communicate
how
you
are
understanding
software,
how
you
are
building
your
own
understanding
around
a
situation
and
most
important
how
you
are
a
building
this
this
over
features.
For
me,
this
was
part
of
the
log
history
for
Michael
challenge
for
airline
solution.
My
actual
job
I
wanted
to
share
how
I'm
building
software
using
this
and
for
me
was
really
available,
because
I
found
this
way
to
communicate
to
each
a
developers
and
to
my
managers.
A
For
me,
git
becomes
a
common
point
to
converge
and
become
a
better
team
player,
because
your
phone,
you
can
phone
many
of
these
techniques,
not
just
for
you
also
for
share
with
with
your
colleagues,
I
think
that
all
of
these
reasons
are
enough
to
become
a
better
team
player
and
I
discovered
these
things.
Thanks
to
to
get-
and
probably
in
that
moment,
I
really
feel
ready
to
face.
My
next
software
project,
I
remember
when
I
joined
to
Airline,
Solutions
I
was
in
my
first
project
and
I
was
really
scared,
because
I
didn't
understand
nothing.
A
I,
remember
that
it
was
my
first
project
in
English
outside
Mexico
and
I.
Remember
one
night.
I
was
really
scared,
because
I
didn't
understand
nothing
about
my
onboarding
saying:
okay,
what
can
I
do
to
understand
this
project
because
it's
it
will
in
Elixir
I'm
an
Elixir
developer,
but
I
can
understand
this.
What
is
happening
inside
this
and
suddenly
I
I
got
an
idea.
What
about
to
take
one
PR
merch?
A
A
I
will
be
able
to
have
the
code
merge
and
my
solution
and
I
will
be
able
to
compare
how
my
team
is
working
and
how
I'm
understanding
this
project
and
comparing
these
two
features
I
will
be
able
to
understand
the
things
that
I
need
to
understand
from
this
culture
that
really
bailable,
and
that's
really
simple,
because
it's
just
about
read
the
comments.
Read
the
PR's
merge
and
that's
all.
A
This
is
really
simple,
but
it's
really
powerful
simple
technique,
but
this
allows
you
to
understand
how
your
team
is
building
software,
but
it's
not
everything,
because
also
you
can
create
your
hypothesis.
How
about
a
piece
of
software
was
developed
by
your
team
and
again
you
need
to
face
this
with
the
reality.
You
need
to
ask
questions
you
need
to
ask
for
support.
A
This
is
the
way
that
I
got
better
questions
to
ask.
My
team
I
learned
this
to
give
and
get
allows
me
to
be
to
become
a
better
team
player
thanks
to
thanks
to
this
and
nowadays
I'm
exploring
another
kind
of
techniques
about
how
to
verify.
My
hypothesis,
for
example,
I
like
to
throw
in
my
understanding
in
the
PRS
just
for
say
to
my
team:
hey
I,
I,
don't
have
enough
context
about
these
business
rules,
but
here
is
my
understanding.
A
A
Allow
me
to
understand
all
of
these
stages
in
my
life,
because
for
me,
it's
really
important
to
be
clear
and
sincere
with
this
emotional
stage
of
My
Life
as
a
software
developer,
it's
important
to
me
talk
about
values.
It's
important
to
me.
Talk
about
techniques!
How
you
are
building
software
is
about
you,
it's
about
your
autonomy,
but
also
it's
about
your
team.
A
A
A
in
this
year
in
February,
I
was
invited
to
to
be
a
part
of
a
program
by
Microsoft
and
the
Mexican
Government
to
create
a
three-month
bootcamp.
It
was
a
full
stacked
book.
Bootcamp
and
I
was
invited
to
build
and
design
and
give
a
six-week
training
to
learn
a
back-end
practices
using
no
judges
too
many
graduate
students
for
any
career
in
Mexico.
A
So
let
me
share
with
you
part
of
the
resource
when
I
was
designing.
This
bootcamp,
of
course,
I,
took
a
all
of
these
stations
that
I
present
and
I
mentioned
before,
to
create
my
own
safe
place
to
experiment,
to
make
mistakes
to
learn
because,
as
a
Mexican
I
understood
that
our
context
is
pretty
different
than
other
ones,
and
we
need
to
take
care
of
these
values
to
create
our
safe
place
and
I
draw
this.
A
His
name
is
Rupa
to
to
try
to
model
this
experience.
I
like
this
idea,
because
I
remember
that
Joseph
Campbell
a
famous
Anthropologist
after
studying
many
cultures,
he
discovered
that
they
are
sharing
a
common
Museum,
the
museum
about
how
a
normal
human
becomes
to
a
hero,
and
after
that
I
realized
that
he
could
model
all
of
this
story
into
many
stages.
A
People
like
George
Lucas
use
this
model
to
create
a
movies
like
Star
Wars,
for
example,
and
I
was
amazed
because
I
say
okay.
This
is
this
looks
pretty
similar
that
the
thing
that
I'm
doing
here
and
I'm
discovering
using
it.
So
maybe
if
Joseph
Campbell
created
the
hero's
journey,
maybe
I
can
try
to
model
not
the
hero's
journey
in
software.
Maybe
I
could
try
to
model
the
apprentices
Journey.
This
was
my
assumption
to
create
this.
A
This
was
why
it's
important
to
realize
this
stage
and
let
me
share
the
results
of
this
I
have
more
than
a
1
000
of
students
in
in
this
boot
camp.
With
me,
we
just
get
a
GitHub
to
mount
and
create
a
static.
A
web
patients
we
created
more
than
a
hundred
of
blog
posts,
is
using
git
GitHub
patients,
a
GitHub
actions,
anger
Hugo.
A
We
shared
some
common
repositories
to
code
our
activities.
One
of
these
repositories
with
the
exercise
have
a
more
than
a
hundred
of
forks.
We
use
it
since
the
first
day
and
the
participants
must
read
code
and
download
Open
Source
repositories.
A
I
like
the
idea
about
to
create
this
safe
place,
to
create
our
domain
example,
repositories
to
encourage
to
my
students
to
make
Forex
to
open
PRS
to
solve
issues
to
create
their
own,
their
first
contributions
to
software
a
to
open
source
software.
A
A
lady
about
to
mentorship
all
of
these
students
using
git
behind
scenes
all
our
coding
sessions
were
about.
How
can
you
can
use
it
and
combine
in
in
indeed,
in
that
case,
using
node.js,
and
we
combine
this
with
other
techniques
like
it
is
driving
development.
We
use
git
to
lose
the
fear
to
download
Open,
Source
repositories
and
start
to
scratch.
A
I
would
like
to
say
that
for
me,
for
my
perspective,
it
is
not
about
this.
It's
not
about
how
you
can
become
the
weather
developer
is
about
this.
It's
about
how
you
can
be
a
weather
developer,
how
you
can
be
a
better
human.
How
can
you
understand
you
as
a
part
of
the
team?
How
can
you
create
this
empathy
to
you
and
to
your
colleagues?
How
can
you
build
this
confidence
and
you?
How
can
you
boil
your
own
safe
place,
and
how
can
you
build
this
a
place
to
other
ones?
A
A
It
is
about
us,
that's
the
the
good
part
of
this.
So
if
you
want
to
empower
your
instinctive
skills,
I
recommend
you
write
your
commits
before
code
build
your
narratives
using
git
as
a
as
your
learning
diary
and
Rick.
Often
your
commits
history
to
make
sure
what
this
have
to
say
to
you.
If
you
are
looking
to
empower
your
collaboration,
culture
in
your
team,
I
recommend
you
to
things.
Work
on
boil
features
that
would
be
able
to
be
boiled.
Just
look
in
the
commits
and
include
rebuilding
features
done
in
your
reporting
of
new
team
members.
A
A
I
talk
about
balance,
I
talk
about
techniques,
I
talk
about
my
experiences
using
a
learning,
git
and
I.
Don't
want
to
close
this
presentation
before
to
talk
about
what
is
important
about
to
talk
this
because
for
me,
as
a
Mexican,
I
have
to
deal
with
many
challenges
in
my
life,
not
just
a
I
have
to
learn
how
to
speak
in
English,
because
that
was
a
the
the
language.
Gap
is
really
big
challenge
for,
for
any
Mexican
I
have
to
deal
with
many
other
kind
of
of
things.
A
I
have
to
deal
with
emotional
stage
in
my
life.
I
have
to
deal
I
have
to
face
this.
This
part
about
to
be
paralyzed
in
front
of
Technology,
about
to
feel
alone,
and
how
important
to
me
is
today
talk
about
balance,
talk
about
ethics
behind
technology,
how
you
are
using
this
as
a
developer,
but
also
as
a
part
of
the
team.
For
me,
it's
really
important
to
make
this
clear,
because
at
the
end
of
the
day,
software
is
built
by
people.
We
are
people.
This
is
part
of
my
collaboration.
A
This
allows
me
to
break
with
my
culture
in
Mexico,
because
our
culture
is
a
little
bit
different,
because
we
have
fear
to
fail
and
learning
it.
I
found
that
I
have
to
lose
this
fear
to
create
this
a
place
and
I
learned
that
using
tools
like
it
and
able
to
create
a
new
collaboration
for
my
colleagues,
that's
why
it's
important
talk
about
this.
That's
what
I
consider
by
level
be
here
today
to
share
all
of
these
experiences
with
all
of
you.