►
From YouTube: Non-Technical Roles to Technical Roles
Description
Sarah Daily, Senior Marketing Operations Manager and Sid Sijbrandij, CEO and Co-Founder of GitLab chat about making a career change from a non-technical role to a technical role.
A
B
B
B
Yeah,
I'm
reminded
of
a
few
people
I'll
start
close
to
home.
My
wife
made
a
career
change.
She
did.
She
studied
social
and
work
psychology.
She
was
working
in
sales
and
she
taught
herself.
She
had
an
idea
for
startup
and
nobody
to
hire
anybody.
So
she
taught
herself
how
to
program
and
I
think,
there's
lots
of
good
ways
to
learn
it.
There's
free
code
camp
there's
lambda
school,
which
is
paid
but
good.
B
So
there's
tons
of
ways
to
learn
it.
I
think
I've
seen
a
ton
of
people
do
that.
We've
done
my
wife
and
organization
called
rails.
Girls
in
the
netherlands
and
we
frequently
kind
of,
went
to
meet
ups
together
and
hosted
people
together,
and
it's
it's
a
lot
of
fun
to
learn
how
to
program.
But
it's
kind
of
at
some
point
you're
also
going
to
be
super
frustrated
because
it's
hard
to
make
progress.
B
B
Another
good
avenue
is
like
coursera
courses
which
come
with
instructors.
Who
can
help
you
get
unstuck
and
then
the
hardest
thing
is
to
kind
of
maintain
motivation
like
takes
a
while
and
the
schools
nine
months.
I
think
coding
boot
camps.
That
say
they
can
do
it
in
three
months.
I'm
not
a
big
fan
of
that.
I
think
it
takes
longer
to
get
to
a
level
where
you
can
be
hired
and
then
it's
hard
to
find
an
entry-level
developer
position
like
when
you're
entry
level.
It's
almost
like
a
p
organization.
B
Hires
you
as
an
investment
in
the
future,
much
more
than
for
what
you're
able
to
produce
today,
like
you'll,
so
find
that
role
where
you
can,
where
you're
in
a
working
environment-
and
it
might
not
be
immediately
that
developer
role,
so
it
might,
for
example,
be
a
support
role
where
you
are
working
with
code,
but
you're,
also
answering
tickets,
so
you're
like
adding
a
ton
of
value
and
you
you
get
to
kind
of
refine
your
coding
skills
in
the
course
of
your
work
and
then
make
that
transition
from
support
to
development,
which
a
couple
of
people
on
our
support
team
have
done.
B
It's
super
hard
to
say,
I'm
a
junior
developer
and
I
want
to
work
at
like
a
great
tech
company.
That's
that's
going
to
be
tough.
The
old
other
alternative
like
work
for
some
company,
that's
not
known
for
tech
kind
of
company,
that's
not
known
as
a
software
company
that
just
is
very
desperate
for
new
programmers.
B
I
think
zooming
out
a
little
bit,
I'm
also
reminded
of
great
tech
ceos
like
andy
jesse,
who's,
now
transitioning
from
aws
to
amazon,
proper
who's
like
not.
I
don't
think
his
background
is
as
a
as
a
programmer
or
something
like
that,
so
you
can
be
very
effective
as
a
non-developer
in
in
managing
a
tech
company
yeah.
I
hope
that
was
helpful
and
look
forward
to
the
other
questions.
A
Yeah,
that
was
super
helpful.
Thank
you
so
for
my
next
question.
Sometimes
as
I'm
navigating
you
know
kind
of
what
languages
to
learn,
it's
difficult
to
know
what
area
you
should
go
to.
For
instance,
I
understand
that
like
sql
python,
those
are
really
more
related
to
data
science
and
html.
Css
and
javascript
are
more
related
to
web
development.
A
B
Yeah,
so
if
you're
on
an
existing
project,
it's
whatever
they're
already
using
and
in
gitlab
that's
ruby
for
most
of
the
things
and
then
it's.
If
it
needs
to
be
high
performance,
it
would
be
in
go
and
then,
if
you're
starting
a
new
project,
you
look
at
what
the
community
is
using.
So
you
start
a
new
project
around
machine
learning.
You
do
it
in
python,
because
that's
the
potential
contributors
and
colleagues
on
the
project
would
be
familiar
with
that.
A
Do
some
developers
specialize
in
in
several
programming
language
or
do
they
focus
their
expertise
on
one
or
two?
And
I
I
had
this
on
the
agenda,
but
I
think
you
might
have
answered
it
when
you
mentioned
that
you
know
only
learn
as
much
as
you
need
for.
B
B
Everyone
has
knows
different
languages
to
some
extent.
Some
some
programmers
are
super
proud,
they're
polyglot
like
they
know
multiple
languages
really
well
and
that
that
enables
you
to
be
better
in
whatever
whatever
you
do,
because
you
you
got
to
your
own
kind
of
a
new
layer
of
abstraction
and
some
people
like
me,
I
only
know
ruby,
so
more
more
is
better,
but
there's
a
big
variance
and
you
can
be
a
very
effective
and
highly
paid
developer
by
and
only
know
one
language
well,
gotcha.
B
B
It's
so
hard
to
like
that.
The
hard
part
about
programming
is
like
the
amount
of
stuff
you
have
to
learn:
it's
not
just
the
programming
language.
It's
also
like
testing
strategies,
ci
strategies,
how
web
servers
work,
how
servers
work,
how
how
aws
should
be
configured?
It's
just
people
think
it's
about
the
programming
language,
but
there's
all
this
additional
stuff-
and
that
is
kind
of
that
makes
it
very
overwhelming
so.
A
B
Don't
feel
like
you
have
to
become
an
expert
in
anything.
Basically,
everyone
is
just
messing
around
trying.
Googling
stack,
overflow
copy,
pasting,
stuff
and
seeing
what
works
and
and
that's
that's,
okay,
and
I
would
even
have
the
mental
image
like
everything
you
know
becomes
outdated.
So
if
you
would
know
you,
if
you
would
know
everything
about
like
10
languages,
your
knowledge
would
become
outdated
faster
than
you
could
learn.
A
B
B
A
Cool
great
follow-up
question
I
have
for
exactly
what
we're
talking
about
is.
I
understand
that
being
a
developer
is
not
all
about
coding,
so
what
soft
skills
do
you
feel
are
important
for
people
in
these
roles
to
have.
B
Yeah,
I'm
gonna
talk
about
the
specific
soft
skills
like
there's
a
whole
lot
of
soft
skills
that
you
need
to
work
on
a
professional
environment.
I
assume
you
already
have
them,
because
if
you've
shown
that
you
have
them
to
be
so
far
in
our
interaction
but
also
like
you're
you're
fulfill,
you
have
a
current
job
and
then
the
additional
things.
I
think
it's
really
helpful
as
a
developer
to
be
good
in
written
communication.
B
A
lot
of
the
communication
is
through
issues
through
merge,
requests,
comments
so
being
effective
there
being
concise
and
clear,
but
also
encouraging
and
open
and
giving
suggestions
and
talking
about
the
work
and
not
the
person
and
all
those
things.
I
I
think
that's
really
important.
We
link
to
a
bunch
of
resources
but
like
if
you
can
do
a
co,
there's
a
lot
of
hints
of
how
to
do
a
code
review
right.
I
think
that's
helpful
and
how
to
write
good
issues
or
feature
requests,
feature
requirements,
feature
proposals,
they're,
sometimes
called
so
talking
about
code.
B
A
And
my
last
question
is,
after
spending
some
time
observing
you
in
the
program,
you
do
a
really
great
job
of
explaining
and
describing
highly
technical
concepts
to
non-technical
folks.
I
often
do
this
in
my
current
role
as
a
senior
marketing
operations
manager.
Sometimes
I'll
use
analogies.
So
I
was
curious
if
you
had
any
tricks
or
tips.
Do
you
find
helpful
when
you're
explaining
some
of
these
more
technical
concepts
to
non-technical
folks.
B
Yeah
testing
testing
testing,
so
you
were
part
of
the
non-deal
road
show
and
then
the
non
deal
road
show
you
might
have
noticed.
I
tell
the
same
thing
over
and
over
again,
and
I
first
thought:
oh
I'm
going
to
be
so
annoyed
by
this
because
you
know
internally.
B
I
cannot
stand
it
when
something
is
not
prepared
well
or
reduplicate
things.
But
I've
learned
to
appreciate
these
things.
First
of
all,
you're
dealing
with
very
smart
humans
at
the
other
side.
So
that's
great,
but
they
just
don't
have
the
knowledge,
and
now
it's
up
to
you
to
transfer
that
in
the
shortest
amount
of
time
and
with
the
most
enthusiasm,
I
got
lots
of
to
learn
there
about
being
enthusiastic
when
relaying
a
message,
but
also
like
it's,
I
think,
you're
kind
of
like
you're,
like
a
comedian
testing
jokes.
B
These
analogies,
like
you,
want
to
see
the
aha
moment
and
if
they're
like,
do
you
mean
xyz?
You
know
you
fail,
but
you
listen
like.
Maybe
they
use
an
analogy
that
does
work
so
I'm
still
working
on
like
the
real
estate
agent
and
the
escrows
escrow
servers,
but
I'll
it's
it's
constant.
A
b
testing,
and
then
this
repetition,
like
we
did
five
kind
of
the
same
meetings
in
the
same
day,
actually
becomes
useful
because
you
do
it
in
another
way.