►
From YouTube: How legal Hubbers GitHub - GitHub Universe 2017
Description
Presented by Meena Polich & Brooke Roundy, GitHub.
To most, GitHub is a platform by engineers, for engineers. The truth is, anyone can be a developer. Our legal team has embraced using GitHub to pioneer innovative legal practices for our business. We’re going to give you an overview and brief demo on why and how we use GitHub. The beauty of the platform is that anyone can learn how to use it. We’re going to show you how legal professionals can use GitHub to collaborate meaningfully, building the best businesses and software in the world.
About GitHub Universe:
GitHub Universe is a two-day conference dedicated to the creativity and curiosity of the largest software community in the world. Sessions cover topics from team culture to open source software across industries and technologies.
For more information on GitHub Universe, check the website:
https://githubuniverse.com
A
We're
gonna
be
talking
today
about
how
illegal
hovers
use
github,
but
before
we
get
started
and
before
we
introduce
ourselves,
we
want
to
get
an
idea
of
who
is
here
in
the
audience
today
and
so
I'm
gonna
ask
a
few
questions
and
with
the
raise
of
hands,
if
you
could,
let
us
know
how
many
people
here
are
in
a
non-technical
role
in
their
organization.
Oh
great,
all
right,
we
have
quite
a
few
then,
and
are
there
any
legal
professionals
in
attendance
today.
A
Okay,
I,
like
that,
that's
not
on
the
legal
team
at
github,
so
maybe
maybe
one
and
is
there
anyone
here
who
uses
github
to
collaborate,
but
not
necessarily
on
the
development
of
software
code?
All
right
great!
We're
really
excited
about
that,
because
I
think
we're
gonna
be
hoping
to
get
some
some
thoughts
from
you
later
so
to
get
started
here
like
to
talk
a
little
bit
about
ourselves,
we're
on
the
legal
team.
A
As
we
said,
my
name
is
Brooke
Roundy
my
handle
is
brookie
noodle
I'm,
a
legal
project
manager
here
at
github,
I,
was
hired
over
two
years
ago
in
the
paralegal
support
role.
So
I'm,
not
a
lawyer.
I've
worked
in
a
wide
variety
of
legal
matters
over
that
time
from
employment,
immigration,
subpoena
compliance,
privacy
operations,
content
management,
equity,
administration,
corporate
governance,
lots
of
different
things
so
sitting.
What
might
seem
obvious
is
that
I
hold
a
non-technical
role
within
the
company.
The
entire
legal
team
is
essentially
in
a
non-technical
role.
A
Now
this
is
an
important
distinction
to
make,
because
what
we'll
be
talking
about
today
is
how
the
legal
team,
with
a
broad
range
of
technical
ability
and
backgrounds
from
computer
science,
to
robotics
engineering
to
business
and
corporate
law
and
all
the
way
over
to
nursing,
has
adopted
an
embrace.
Github
is
the
platform
which
we
work.
A
Github
is
where
we
work
is
where
we
get
our
work
done
and
then
I'd
like
to
say
a
little
bit
about
what
my
background
is
specifically
and
the
way
that
I
used
to
work
before
coming
to
get
hub
prior
to
joining
github
I
worked
as
a
paralegal
at
a
big
law,
firm
first
in
litigation
and
then
in
the
corporate
practice.
Both
areas
of
my
work
were
characterized
by
very,
very
heavy
email
use,
especially
during
my
time
in
IIP
litigation,
I
lived
and
breathed
email
with
a
healthy
dose
of
two-way
I
am
a
lot
of
meetings.
A
Conference
calls
and
I
was
always
surrounded
by
reams
and
reams
of
paper.
Then
I
came
to
github,
where
we
just
we
don't
do
paper,
don't
do
paper
at
github
and
we
don't
usually
shoot
off
emails
every
two
seconds
we
operate
amongst
a
wide
array
of
apps
centered
around
an
awesome
platform,
and
mostly
all
of
these
things
happily
exist
in
some
place
called
the
cloud.
I
am
not
entirely
sure.
I
ever
even
heard
the
word
workflow
before
I
came
to
github,
which
we
need
to
change.
It
was
a
vastly
different
landscape
from
what
I
knew.
B
B
Nothing
wait,
wait,
I
heard
an
echo
there,
you
go
there.
We
go
all
right.
Sorry
about
that
me
and
polish
managing
operations,
Council
I
started
here.
Doing
commercial
transactions.
I
came
here
to
work
on
our
licensing
and
to
negotiate
our
deals
with
our
various
customers,
and
vendors
and
I
also
helped
launch
our
channel
programs
when
I
started
so
now,
I'm
doing
a
little
bit
more
to
help
our
legal
teams
scale
and
support
of
the
business
immediately
prior
to
joining
github
I
was
working
at
a
large
manufacturing
hardware.
B
Company
that
may
or
may
not
have
made
lots
and
lots
of
routers
and
switches
huge
company
and
my
day-to-day
involved
use
of
a
very
familiar
set
of
tools:
email
chat,
apps,
video
conferencing
and
phones.
Internally,
it
was
more
of
spread
across
all
of
those
and
externally
it
was
pretty
much
phone
and
email.
My
typical
legal
workflow
for
negotiating
a
matter
would
basically
involve
all
of
that
labyrinth.
Increasing
estat
you
see
on
the
screen
right
there
and
everything
came
back
and
forth
through
email
had
to
document
every
conversation
in
email.
B
If
you
had
an
email
with
one
person
and
he
needed
to
contact
another
stakeholder,
he
had
to
have
another
separate
email.
If
I
wanted
approval
on
some
language,
I
was
going
to
have
to
email
the
one
person
who
could
email
the
other
person.
Who
could
then
direct
me
to
someone
else?
Who
would
tell
me
you
need
to
give
me
a
reason
for
the
thing?
Oh,
but
I'm,
not
in
this
role
anymore.
So
you
should
actually
go
talk
to
that
person
over
there
and
several
emails,
chat,
messages
and
webex's.
B
Later
I
would
have
approval
for
that
one
provision
in
the
contract
and
then
I'd
get
to
start
that
process
over
again
and
mine
knew
this
was
a
company
who
is
actually
at
the
forefront
of
legal
operations
and
really
works
hard
to
make
our
work
more
efficient
and
productive.
But
again
we're
constrained
with
these
technical,
typical,
traditional
technical
tools.
B
So
when
I
came
to
get
hub,
I
thought
I
was
going
to
be
doing
more.
The
same.
That's
what
all
of
my
counterparts
that
my
customers
and
vendors
were
doing
everywhere
else,
working
on
email,
a
matter,
negotiation
tool,
matter,
management
tool,
shad.
All
those
things
I
came
to
get
hub
and
I
said:
oh
no,
no,
no.
We
use
github
for
everything
here.
So
if
you
want
something
done,
you're
gonna
have
to
open
an
issue
or
create
a
pull
request.
A
Before
we
get
into
the
way
that
we
use
github
I'd
like
to
talk
a
little
bit
more
about
legal
transformation,
the
way
that
we
use
github
to
collaborate
is
interesting
for
the
feedback
cycle
that
it
creates
and
the
possibilities
it
uncovers,
but
it
is
particularly
interesting
given
current
trends
in
the
legal
industry
and
the
industry
as
a
whole
has
been
slow
to
change.
That's
not
news,
but
its
transformation
is
finally
unfolding
with
a
focus
on
innovation
to
drive
value
in
2015
ultimate
wheels.
A
Annual
survey
of
chief
legal
officers
revealed
that
cielos
believe
in-house
legal
departments
will
drive
40
percent
of
that
change,
while
20
percent
believe
that
it
will
be
technology
that
moves
things
forward.
We
both
recently
attended
a
corporate
legal
operations,
consortium
or
clock
annual
conference
at
o'clock.
Many
legal
tech
companies
were
in
attendance
and
many
of
them
legal
tech
startups,
undoubtedly
building
their
products
on
github
working
to
deliver
technological
solutions
to
the
industry.
The
themes
from
nearly
every
conversation
at
that
conference
will
sound
familiar
workflow
collaboration,
AI
and
machine
learning,
data
analytics
automation,
transparency,
value.
A
The
question
is:
how
do
we
make
better
decisions
and
get
to
solutions
faster,
thereby
driving
the
value
all
the
way
through
the
business?
Indeed,
how
do
we
do
that?
We
have
an
answer
through
transformation
of
the
corporate
legal
team,
from
a
reactive
siloed
business
unit
to
an
embedded,
informed
and
proactive
business
partner.
A
How
do
we
become
that
proactive
business
partner
while
working
at
a
software
company
with
developers?
We
we
don't
see
ourselves
as
non
developers.
We
recognize
we
are
part
of
the
developer
ecosystem.
The
way
we've
used
the
product
can
be
adopted
to
any
non
developing
organization
in
a
company
that
creates
or
uses
software,
and
for
that
matter,
any
organization
in
any
company.
As
Chris
noted
in
his
keynote
get
help
was
built
for
developers
first,
but
not
developers.
A
Only
the
idea
was
to
reduce
the
barrier
to
entry
to
anyone
who
wanted
to
program
or
even
just
move
things
or
make
things
move
on
a
screen.
Our
founders
may
never
have
imagined,
but
github
has
reduced
the
barrios
so
far
that
we
don't
have
to
just
build
software
on
it.
We
can
actually
design
and
change
how
people
like
ourselves.
Legal
professionals,
work,
we're
all
github
users
and
collaborators,
and
now
Mina
is
going
to
demonstrate
how
we
do
that.
So.
B
The
easiest
way
to
show
you
how
we've
made
it
work
for
us,
at
least
in
mice,
in
my
realm
of
contract
negotiation,
is
to
show
you
the
workflow
that
we
now
have
for
contract
review,
as
you
saw
before,
it
was
a
mishmash
of
craziness
and
back-and-forth
and
and
and
sidebars
and
back-channel
conversations
that
finally
eventually
lead
to
the
end
result.
Using
github
we've
been
able
to
condense
and
consolidate
all
of
that
communication,
primarily
into
one
place,
the
platform
that
is
github
and
our
repository
on
it.
We
do
still
use
chat.
B
B
So
we
have
a
form,
and
the
nice
thing
about
working
at
a
company
for
developers
made
up
of
developers
is
they're,
always
happy
to
make
little
programs
and
scripts
for
us
so
that
we
can
actually
get
our
stuff
done.
So
one
of
our
colleagues
Ben
Walter,
kindly
created
an
intake
form
that
allows
us
to
actually
should
be
playing
right
now.
B
It
allows
us
to
actually
take
in
the
information
that
we
need
for
the
deal
we
want
to
know
who
it
is
that
we're
negotiating
the
contract
with.
We
want
to
know
what
kind
of
deal
it
is
and
what's
the
context
of
how
we're
working
with
the
customer
on
this
I'm
gonna
see.
If
I
can
get
this
to
play
here,
there
we
go
so
once
this
is
actually
completed,
the
form
is
actually
completed
and
the
requester
submits
the
form
it
automatically
opens
an
issue
in
our
contract
review,
repository.
B
Without
having
to
open
up
the
document,
we
can
attach
the
document
and
issues,
and
we
do
that
because
we
want
to
preserve
the
context
and
the
versioning
of
our
documents,
but
we're
also
able
to
preserve
we're,
also
able
to
elevate
that,
through
the
conversation
with
markdown
and
with
the
use
of
these
conversations,
we
go
through
the
process.
I
can
bring
anyone
in
the
company
as
a
stakeholder
in
to
comment
on
the
issue.
So,
if
I
need
to
know
if
we
can
actually
operationalize
a
request
from
our
customer,
I
can
bring.
B
Somebody
from
sales
operations
in
I
can
bring
somebody
from
engineering
in
and
they
can
weigh
in
right
there.
They
can
approve
right
there.
I
don't
have
to
send
a
separate
email.
I,
don't
have
to
send
put
anything
in
an
intake
tool
and
we
can
get
our
results
and
our
answers
back
to
our
clients
and
our
customers
faster.
B
B
B
Oh
now,
it's
playing
there
all
right,
I
think
we
got
the
idea
move
on
so
what
this
has
done
us
being
able
to
use
the
tool
in
this
way-
and
this
is
just
one
example
of
many
and
as
to
how
the
legal
team
uses
the
tool,
its
flipped,
the
developer,
non-developer
paradigm
for
our
team.
We
don't
see
ourselves
as
non
developers,
because
we
are
prolific
github
users
and
we're
able
to
do
the
same
thing
with
github
that
software
developers
are
doing.
We
have
become
developers,
we
developed
legal
content
instead
of
Ruby
instead
of
Rails.
B
We
collaborate
on
that
code
with
each
other.
We
deploy
and
ship
our
content
to
our
customers
to
the
company
in
the
form
of
policies
executed
contracts.
This
has
enabled
us
to
become
embedded
business
partners.
We
are
no
longer
reacting
to
a
last-minute
request
to
go
ahead
and
hurry
up
and
make
sure
that
what
we're
doing
is
legal.
Where
can
you
please
make
sure
that
I'm
not
gonna
go
to
jail,
we're
already
in
there
long
before
it
ever
has
to
get
to
that
point?
B
All
of
github
collaborates
to
the
platform,
which
makes
it
that
much
easier
for
us
to
have
access
to
everything
anybody
else
is
doing
or
asking
about
it
gives
everybody
else
access
into
what
we're
doing
and
what
we're
thinking
about,
there's
also
very
levels
of
access,
so
we're
still
able
to
preserve
the
protection
of
sensitive
information
when
we
need
to.
There
are
certainly
certain
issues
that
shouldn't
be
visible
to
an
entire
company.
B
We
can
in
that
that
that
applies
to
any
team,
not
just
the
legal
team,
but
we're
able
to
protect
the
information
that
is
sensitive,
that
we
need
to
protect
and
we're
easily
able
to
then
reach
out
to
everybody
in
the
company
when
we
need
to
to
make
sure
that
what
we're
doing
moving
forward,
how
we're
supporting
the
company,
how
we're
supporting
our
clients
is
actually
effective.
We
have
a
culture
of
adoption
at
github
and
particularly
on
the
legal
team.
B
We
have
all
embraced
use
of
the
platform,
and
it
is
through
that
embrace
through
that
willingness
to
adopt
anything
new
that
comes
along
that
were
able
to
be
successful.
Along
with
that
is
the
multi-layered
communication
that
basically
enables
us
to
get
to
an
answer
faster
and
to
be
able
to
ensure
that
don't
slip
through
the
cracks
and
at
the
end
of
all
this,
we
have
constant
iteration.
It's
not
enough
to
simply
sit
on
the
platform
and
hope
it
does
what
we
need
it
to
do.
We
work
with
our
colleagues.
B
We
work
with
the
developers
to
say:
hey,
wouldn't
it
be
great?
If
we
could
do
this,
it
would
really
help
our
workflow
for
the
legal
team
and
I
even
had
one
of
our
engineers
from
Houston
will
come
up
to
me
yesterday
and
say:
I
love
what
you
all
are
doing
in
the
legal
and
the
legal
team
with
our
repos.
A
A
So,
let's
start
with
repositories
where
everyone
knows
that's
where
the
magic
happens.
Everyone
to
get
habit
on
github
works
in
a
repository
for
github
legal
using
repos
transforms
our
ability
to
manage
our
content
and
our
knowledge
and
organize
how
we
support
the
company.
In
one
best
example,
the
principal
example
of
how
we
engage
with
the
company
is
through
github
the
legal
repo
integrated
with
our
chat
application.
A
Of
course,
it's
a
principled
way
in
which
we
engage
on
legal
issues,
and
this
can
be
questions
from
the
company
about
intellectual
property
assets
to
our
dog
policy
to
event
codes
of
conduct.
The
legal
repo
is
where
helpers
can
directly
and
transparently
engage
with
the
legal
team.
It's
the
inner
sourcing
of
legal
questions
in
a
company
facing
forum
that
allows
any
hover
to
benefit
from
an
issue
opened,
question
posed,
discussed,
answered
and
then
closed,
and
just
by
simply
watching
the
repo
or
more
directly
through
individual
or
team,
app
mentions.
A
A
A
That's
me
so
some
of
the
other
ways
that
we
collaborate
and
specifically
through
issues
I
think
that
issues.
This
is
my
opinion.
I
love
issues.
This
is
where
I
do.
The
majority
of
my
work
is
in
issues
in
the
way
that
that
issues
work
so
well
and
the
way
that
really
as
a
legal
professional
when
I
encountered
the
issue
and
what
it
could
do
and
how
it
can
replace
email
as
that
primary
way
of
communicating
and
reaching
decisions
is
when
I
saw
the
power
of
github.
It's
because
issues
create
its
contextual.
A
Do
you
have
all
the
information
you
need
there?
It's
not
disparate,
where
you
might
have
information
and
different
email
threads.
It's
all
centered
in
in
one
issue.
Now,
even
if
it's
actually
in
another
issue,
the
beauty
of
it
is,
you
can
link
the
issues
it's
archivable
and
searchable
within
the
repository.
It's
really
a
central
area
where
you
can
search
if
you,
if
you
need
to
find
a
particular
issue,
that's
already
been
been
handled
and
it's
transparent,
as
we've
noted
again.
That
word,
transparency,
I
think,
is
really
important.
B
So
one
other
thing
to
add
about
issues
that
it's
important.
We've
talked
a
lot
about
emails
to
issues.
Issues
replaces
our
email
as
use
of
communication
issues.
Don't
simply
replace
email
issue
really
facilitates
our
entire
workflow.
We
can
use
issues
to
project
manage.
We
can
create
a
tracking
issue
that
actually
tracks
an
initiative
where
we
might
actually
have
several
different
sub.
The
problem
with
the
word
issues
is
its
kind
of
use
it
for
lots
of
things.
B
Any
sub
topics
that
we
want
to
discuss
in
order
to
accomplish
the
actions
for
a
particular
initiative
or
build
a
process
or
a
policy.
We
can
track
all
of
that
in
one
issue
so
that
we
have
actionable
items
and
deadlines
associated
with
that
we
have
check.
We
can
check
it
off
in
the
tracking
issue
and
we
can
always
link
back
to
that
tracking
issue.
So,
even
if
a
question
and
the
sub
topic
is
going
a
bit
off
the
rails,
we
always
have
that
tracking
issue
to
bring
it
back
to
where
we're
originally
focused
on.
B
A
Also,
you
can
also
use
issues
in
different
ways
and
different
repos,
depending
on
what
your
project
is
and,
depending
on
what
your
need
is
I
work
in
lots
of
different
areas
for
the
legal
team
and
I've
used
issues
in
different
ways.
So,
if
you
want
to
have
a
specific
way,
you
use
an
issue
in
a
particular
ebook
repo.
You
can
have
a
contributing
file
or
you
read
me
that
tells
you
exactly
how
you
want
to
use
it
use
the
issue
or
just
have
you
issue
template.
B
So
the
others,
the
other
major
subset
of
the
repos
that
we
use,
is
the
ability
to
create
to
actually
create
content
and
to
version
that
content
in
github.
So
here
we
talk
about
content
to
code.
As
most
of
you
probably
aware,
pretty
much,
the
entire
legal
profession
is
all
content.
It's
all
words
and
again,
like
chris
mentioned
in
his
talk
yesterday,
is
and
meet
you
as
well.
Is
there
really
a
difference
between
words
and
coding,
they're
all
languages,
so
it's
just
the
way
that
we're
communicating
in
the
way
that
we're
structuring
our
thoughts.
B
That
differs
so
even
with
the
legal
team.
We've
converted
content
to
code
with
the
ability
to
use
to
create
files
and
pull
requests
within
github
we're
able
to
have
way
more
advanced,
consistent
and
detailed
versioning
than
any
sort
of
word,
processing
and
legal
tracking
tool
that
I've
seen
we're
able
to
work
asynchronously
so
that
if
I
need
feedback
on
a
document,
I
don't
have
to
sit
at
my
computer
anxiously
waiting
for
somebody
to
hurry
up
and
log
on
and
do
it.
B
B
We
use
files
to
create
policies
that
we
disseminate
throughout
the
company.
We
use
files
to
create
documents.
We
use
files
to
create
blogs.
We
use
files
to
create
our
contract
templates.
Our
latest
version
of
the
toss
was
initially
created
as
a
pull
request,
which
we'll
show
you
how
that
looks
in
a
minute
as
a
pull
request
in
the
legal
repo.
So
we
can
create
the
file
and
then
we
can
go
ahead
and
save
it
and
post
it
and
share
with
our
team
that
we
would
like
their
feedback
on
whatever
it
is
that
we're
creating.
B
B
So
I
I've
made
this
file
and
somebody
sees
it
and
they
say:
hey
you've
made
a
mistake
in
the
way
that
you
structured
the
instructions,
so
they
open
up
the
fight
after
they've
opened
up
the
file
and
they
say
hey,
looks
like
you
should
have
had
section
three
after
section,
four,
whatever
it
is,
so
feel
free
to
watch
this
carry
on
as
I'm
as
I'm
talking.
So
what
happens
is
my
colleague
is
able
to
make
the
change
themselves.
They
don't
need
me
to
give
them
a
secret
password.
B
A
B
And
procedures
yeah,
and
what
you
see
here
too,
that
is
also
key,
is
we
have
the
ability
to
show
dips?
So
while
it's
not
the
same
capability
as
lining
and
say
a
word
processing
document,
we're
still
able
to
show
the
differentiation
between
the
original
document.
What
we
took
out
in
red
and
the
new
document
will
be
added
in
green
and
with
every
version,
we're
able
to
show
those
dips
from
version
to
version.
I
can
go
back
in
and
approve
those
comments.
B
A
A
So
I
think
that
are
we
I
think
we
are
coming
up
to
the
end
of
our
our
presentation
and
I
just
wanted
to
say
a
few
things.
I
think
that
this
conversation
is
just
getting
started
when
I
first
came
to
github,
it
was
a
vastly
different
landscape,
then,
and
very
different
than
the
way
that
I
used
to
work.
But
what
was
so?
It
was
scary
at
times,
but
it
was
really
really
exciting.
A
It
was
it's
incredibly
exciting
because
all
of
the
pain
points
of
my
past
practices,
particularly
at
a
law
firm
I,
could
see
the
power
of
how
github
the
product
could
really
smooth
out
many
of
those
and
ease.
Many
of
those
pain,
points
and
I'm
still
really
excited
today
continue
to
work.
It
yet
haven't
seen
how
we
can
iterate
on
the
way
that
we
work
using
github
the
tool
and
and
I
feel
like
this
conversation
is
just
getting
started.
A
Yesterday,
Ptolemy's
of
our
colleague
talked
a
little
bit
about
how
we
have
open
sourced
some
policies
on
github
in
this.
So
there's
a
no
whole
nother
conversation
to
be
had
about
how
legal
professionals
can
use
github,
because
I
believe
that
that
github
is
not
just
for
developers.
Github
for
legal
professionals
skip
get-ups
for
lawyers
as
well,
so.
B
What
we've
found
what
we've
given
you
today
is
just
a
taste,
it's
a
very
small
sampling
of
how
we
use
the
product,
but
I
think
it's
demonstrative
of
how
we've
transformed
our
ability
to
work
effectively
efficiently
productively
and
collaboratively
with
our
stakeholders.
We
have
become
trusted
business
partners,
people
know
they
see
us
github.
They
see
us
all
over
the
issues.
They
see
us
all
over
the
repos.
They
know
we're
there
for
them.
They
know
we're
paying
attention.
B
They
know
that
we're
not
gonna
come
in
and
ask
a
bunch
of
questions
without
context,
and
we
encourage
them
to
do
that
in
our
repo.
We
encourage
our
colleagues
to
come
and
do
the
same
thing
with
us.
So
they
know
they
can
trust
us
to
have
a
real
two-way
collaborative
conversation
coming
to
github
was
a
really
difficult
transition
for
a
lawyer,
at
least
but
I.
B
Think,
as
we
heard,
and
Chris
and
miggy's
talked
yesterday,
it's
one
of
the
scariest
things
for
anybody,
because
when
you
get
on
github
and
you
put
something
out
there,
that's
going
to
be
visible
to
everyone,
you
open
an
issue.
You
comment
on
an
issue,
that's
visible
to
everybody.
It's
very
terrifying
to
think
that
they're
gonna
see
you
do
a
wrong
thing,
especially
in
week
one
and
guess
what
week
one
I
comment
on
and
commented
on,
an
issue
and
I
was
immediately
challenged.
How
many
of
you
think
that
that
challenge
was
from
a
lawyer?
B
How
many
of
you
think
that
challenge
was
from
an
engineer
they,
admittedly
they
may
be.
As
you
see
here,
I'm,
not
a
lawyer,
but
and
in
fact
they
don't
even
spell
it
out
anymore.
It's
another
acronym
I'm,
not
a
lawyer,
but
what
you're
saying
is
totally
illogical.
The
first
time
I
saw
that
it
gave
me
pause.
It
was
jarring
I'm,
like
they
hired
me
to
come
here
and
give
legal
counsel.
B
It
would've
been
really
easy
if
it
was
on
email
for
me
to
shoot
back
a
very
polite
or
passive-aggressive
email,
citing
my
legal
credentials
that
qualified
me
to
make
the
combat
and
can
you
please
go
sit
in
the
corner.
Mr.
engineer,
guy
or
miss
engineer,
lady,
but
the
beauty
and
scary
thing
about
github.
B
Is
that
because
it's
out
there
for
everybody
to
see
because
you're
being
transparent,
you
have
to
recognize
that
what
you
put
out
there
now
is:
what's
gonna
stick
with
people
and
it
makes
you
stop,
it
makes
you
reflect
and
it
makes
you
interact
with
your
colleagues
very
thoughtfully.
Do
I
want
to
be
the
person
who
cares
more
about
being
the
expert
or
do
I
want
to
work
with
my
colleague
to
find
a
bed
a
more
creative
solution.
Like
Chris
said
yesterday,
software
development
isn't
about
coding
anymore.
B
We're
gonna
have
robots
doing
that
in
about
five
minutes.
Software
development
and
anything
that
goes
along
with
it
and
anything
that
we
do
in
life
as
humans
is
about
solving
problems
and
being
creative
to
me
coming
here
and
knowing
that
I
can
be
part
of
that
process.
That
I
can
be
part
of
that
environment
of
working
together
and
solving
problems
that,
on
the
one
hand,
I
can
say
you're
right,
MS
engineer
it's
totally
illogical,
but
that's
the
law,
which
is
always
our
I,
should
say.
B
Often
illogical
or
I
can
go
and
say
you
know
what
you're
right
I
never
thought
about
that.
I'm!
Gonna
step
out
of
my
siloed
world
vision
and
think
about
what
you
said:
let's
actually
try
to
make
this
work
and
to
me
more
than
anything,
that's
the
power
that
github
has
for
all
of
us
and
I.
Think
that's
it.
Thank
you.