►
Description
Software developers bring highly valuable skills and experience to an Organisation. Typically, software developers analyze customer needs and then develop and test software to meet those requirements. But, it is also vital for software developers to meet the needs and requirements of their co-workers. Gone are the days when the only expectations from developers were centered around their software development skills and technical skills. As the software industry becomes integrated with business, the expectations from developers evolve. Engaging in meaningful interactions and forming strong professional relationships is vital. That element of a developer’s professional life requires a range of soft skills. This talk will focus on: (i) the state of software development in today’s highly distributed work environment (ii) the challenges organisations and developers face (iii) the importance of soft skills for developers (iv) useful soft skills developers can build.
B
A
Two
event,
so
I
think
the
next
session
is
going
to
be
on
soft
skills
that
make
a
great
software
developer.
So
I
think
this
is
something
which
is
really
generic,
and
it's
kind
of,
irrespective
of
your
technical
track,
will
all
be
interested
to
hear,
and
I'm
really
happy
to
welcome
wilson,
who
is
with
me
who's
running
as
a
speaker
for
the
day.
So
he's
a
vice
president
at
software
services
factory
and
he's
currently
working
at
infinite
computer
solutions
and
there's
a
lot
more
to
talk
about
him.
A
He
has
around
22
years
of
experience
in
r
d
and
which
includes
global
delivery.
Pre-Sale
solution
architecture
ims,
delivery,
india,
leader
at
alpha,
alcatel,
recent
india
and
he's
also
head
in
india
iptc
in
alcatel,
and
he
is
expert.
His
expertise
is
in
operations,
management
and
transformation,
and
he
has
a
success.
So
he
has
been
successful
in
creating
offshore
teams
and
leading
people
and
he's
proficient
in
resource
management,
analytical
skills,
mentoring,
skills,
presentation,
what
not
leadership
and
budgeting
and
interpersonal
skills.
So
I'm
really
happy
to
welcome
you
wilson.
B
Thank
you
pavitra
good
afternoon,
friends.
I'm
I'm
really
really
happy
to
be
part
of
this
event,
and
it
gives
me
an
immense
pleasure
to
be
here
to
talk
to
you
about
some
of
my
experiences,
some
of
the
learnings
that
I
have
got
in
the
software
industry,
and
I
know
this
is
a
saturday
and
it's
it's
around
two
o'clock
people
are
wanting
to
go
for
lunch.
B
What
I'll
do
is
I'll
go
through
the
slides
I'll,
allow
you
to
ask
questions
whenever
it
is
possible,
either
through
slack
or
through
pawitra,
and
will
interact
as
much
as
possible
even
after
the
session.
Okay.
The
reason
why
I
chose
this
topic
is
guys.
I
had
been
very,
very
passionate
about
training
people,
mentoring,
people.
I
have
brought
in
lots
and
lots
of
good
passionate
software
developers,
and
I
know
this
industry
ever
since
in
1992,
when
I
took
my
first
gw
basic
class,
where
I
started
writing
code.
B
When
my
mentor
said,
computers
are
all
about
idiot
box
and
they
don't
do
anything
other
than
what
you
tell
them
to
do,
and
from
that
time
onwards
this
has
been
a
passionating
industry
and
what
india
is
today
is
because
of
there
there
has
been
millions
of
software
developers
who
have
gone
around
the
world
have
proved
that
india
is
the
best
place
for
software
development.
So
what
I'll
do
is
I'll
quickly
go
through
this
agenda?
B
Do
what
you
want
them
to
do
for
you
right,
it's
a
communication
between
your
brain
and
the
and
the
silicon
chips
which
have
no
animate
life,
which
do
not
have
any
life
in
themselves,
but
they
are
programmed.
They
are
controlled
in
such
way
that
there
is
a
beautiful
output
that
comes
out
of
it,
which
is
used
for
the
service
of
mankind.
B
Right.
Remember
again,
the
words
of
my
own
mentor,
who
said
computers
do
not
do
anything
anything.
You
know
you
know
you
talk
about
ml.
You
talk
about
ai.
You
talk
about
orchestration
all
these
words
today,
but
computers
and
networks.
The
systems
do
not
do
anything
other
than
what
you
tell
them
to
do.
That
is
the
power
of
software
engineering,
and
that
is
the
power
of
software
developers.
B
We
have
created
this
industry
and
this
industry
has
seen
a
massive
growth
from
1990s
from
1980s
onwards.
Ever
since
we,
the
first
computer,
was
invented
from
there
and
today
what
we
see
it
is
all
the
brain
of
the
developers
which
has
gone
in.
It
is
all
the
skills
of
the
developers
which
has
gone
in,
and
computers
are
just
boxes
or
silicon
chips
all
right
in
in
all
this.
What
we
have
done
is
remember
guys.
This
is
something
that
we
need
to
remember.
B
We,
as
superior
human
being,
have
gone
down
below
our
intelligence.
We
have
gone
way
below
our
intelligence
to
talk
to
the
computer,
to
make
it
understand
to
make
it
work.
The
call
flow
that
we
want
that
to
work
and
then
have
been
very,
very
successful
in
making
it
work,
and
that
is
the
tremendous
change
that
you
are
seeing
in
the
world
today.
Computers
are
doing
all
that
now
we
see
and
for
which
the
computers,
which
has
got
no
intelligence.
B
We
have
made
it
intelligent,
not
by
bringing
up
the
computers,
but
we
going
below
with
our
soft
skills
to
make
computers
understand
what
we
want
them
to
do
all
right,
and
if,
if
that
is
the
case,
what
is
that
we
miss
and
soft
skill?
If
you
are
able
to
talk
to
inanimate
things
and
make
a
powerful
industry
out
of
these
inanimate
things,
what
are
we
talking
about?
Lack
of
soft
skills
and
in
software
engineering
right?
Let's
go
to
the
evolution
of
software
engineering.
B
Guys?
If
you
remember
the
pressman
book
on
the
software
development
life
cycle
software
engineering,
we
had
seen
waterfall
as
a
methodology
for
developing
software.
Remember
in
software
development
process
in
waterfall
methodology
we
used
to
talk
to
the
customers,
understand
what
they
wanted
to
do
and
develop
software,
and
it
was
a
pretty
successful
model.
There
were
lots
of
computer
systems
and
computer
applications
which
were
created
using
waterfall
model.
There
was
absolutely
no
issue.
We,
we
had
seen
multiple
ways
in
which
we
talked
to
the
customer.
B
We
used
methods
like
observations,
interviews,
focus
groups,
all
the
soft
skills
that
we
used
to
understand
what
the
customer
wanted
and
then
we
built
systems
and
it
was
a
pretty
successful
model.
There
were
some
features
which
were
not
used
when
we
were
building
a
big
bang
approach.
There
were
issues
that
were
coming
up
and
then
we
said:
hey,
let's,
let's
improve
our
soft
skills
better.
Let's
talk
to
the
customer
better.
Let's
understand
the
requirements
of
the
customer
better.
Then
we
move
on
to
agile.
Again
it
is
soft
skills
bringing
in
the
customer
into
our
premises.
B
Are
we
going
into
the
premises
of
the
customer
having
an
iterative
way
of
development,
creating
a
prototype
showing
to
the
customer
and
saying
hey
customer?
Is
this
what
you
like?
Is
there
a
change
that
you
want?
We
spoke,
we
understood
we,
we
understood
what
he
wanted,
what
he
had
in
mind.
It
is
all
about
soft
skills
right,
so
waterfall
agile
was
a
natural
evolution
and
you
know
there
were
lots
of
good
things
that
started
happening
on
agile.
B
We
we
created
bigger,
agile,
safe
agiles,
and
there
were
bigger
frameworks
which
were
created
for
software
development,
and
then
we
still
saw
that
there
are
some
more
soft
skills
that
can
be
bring
brought
in
and
what
is
that
the
requirements
are
collected
from
customers.
As
software
engineers,
we
understood
we
had
that.
You
know
skills
to
understand,
develop
the
product.
B
There
was
a
software,
but
software
connected
the
person
who
created
the
software
engineer
and
the
end
customer
and
the
end
user
of
that
and
between
these
two
people
we
wanted
to
have
less
of
less
of
gaps.
We
wanted
to
bridge
them
more.
Then
it
was
a
natural
evolution
on
devops.
If
you
see
all
these
three
models
and
then
today
we
have
dev's
sega.
We
have
other
methodologies
that
might
come
in,
but
all
that
we
are
seeing
today
is
the
methodology
in
which
we
started
writing.
B
The
software
is
based
on
the
soft
skills
based
on
identification
of
gaps
that
we
had
with
users,
and
it
is
all
human
there
are
technologies,
I'm
not
talking
about
technologies
and
tools
and
frameworks
which
have
been
there,
but
it
is
all
bridging
gaps
in
terms
of
our
soft
skills
between
the
creators
of
the
software,
which
is
software
development,
community
and
the
users
of
the
software,
and
that's
what
these
evolutions
have
taught
us
now.
Just
one
point
about
devops
that
one
that
I
liked
I
took
this
definition
again.
B
Devops
is
a
combination
of
software
developers
and
operations.
Look
again,
we
are
talking
about
not
about
frameworks.
We
are
not
talking
about
the
tools
we
are
talking
about.
The
combination
of
two
people
there
is
a
there
is
a
middleware
in
between.
We
call
that
as
a
software,
but
it
is
the
creators
and
the
uses,
and
it
is
defined
as
a
software
engineering
methodology
which
aims
to
integrate
the
work
of
software
development
and
software
operations
team
by
facilitating
a
culture
of
collaboration
right.
Take
a
note
of
this
word.
B
Collaboration
is
the
soft
skill
that
we
are
talking
about
shared
responsibility.
Accountability
is
what
we
are
talking
about.
Methodologies
might
be
different,
but
ultimately
the
creator
of
the
creator
of
the
software
and
the
user
of
the
software
should
have
a
kind
of
an
understanding.
There
is
when
we
talk
about
soft
skills
and
there
are
around
65
soft
skills
that
a
person
can
have.
If
you
have
read
a
book
called
for
your
improvement,
it
talks
about
the
skills
that
you
need
to
have
as
a
leader.
B
There
are
64
skills
that
they
talk
about,
and
one
of
them
is
collaboration.
That's
a
soft
skill
which
makes
you
very
successful
in
whatever
you
do,
accountability
responsibility,
which
tells
you
that
what
kind
of
maturity
we
have
as
a
human
being
right
so
devops
is
all
about
collaboration
of
people.
Collaboration
is
a
soft
skill.
Shared
responsibility
is
a
soft
skill.
Look
at
what
are
the
goals
of
devops.
It
says
it
represents
a
change
in
mindset
and,
of
course,
there
are
changes
in
frameworks.
We
have
got
better
way
of
storing
the
repository.
B
We
have
better
way
of
integrating
continuous
integration,
but
all
that
is
okay,
but
it
has
created
a
change
in
mindset.
The
change
in
mindset
is
it's
a
culture.
That's
a
soft,
that's
the
soft
skill
that
I'm
talking
about
in
building
on
top
of
the
agile
and
lean
practices
which
have
given
a
way
to
new
frameworks
and
new,
newer
tools.
Devops
focuses
on
incremental
development
and
rapid
delivery
of
the
software
so
that
the
end
user
can
use
it.
The
success
relies
on
the
ability
to
create
a
culture
of
accountability.
Just
take
a
note
of
this.
B
If
you
want
to
be
a
great
developer,
if
you
want
to
be
a
world-class
developer,
if
you
want
to
be
recognized
as
the
best
person
in
your
company
in
your
industry,
one
thing
that
we
need
to
cultivate
is
accountability
right,
so
success
relies.
Success.
Of
devops
itself
relies
on
the
person's
accountability
on
how
we
are
able
to
collaborate
with
a
team.
It's
not
one
single
person.
We
are
not
creating
software
for
a
person
living
in
an
island,
improved
collaboration,
empathy,
empathy
is
again
a
soft
skill.
Empathy
is
now
it's
not
written
anywhere.
B
Empathy
is
understanding
what
the
end
user
wants
to
do
and
then
creating
a
code
sitting
with
the
computer,
creating
algorithms
creating
this
code.
In
such
a
way
that
we
understand
the
ultimate
goal
of
using
that
software
empathy
and
joined
responsibility
for
business
outcomes,
so
that
is
the
definition.
It
tells
you
how
important
it
is
for
us
to
have
soft
skills
of
accountability
of
collaboration
of
empathy.
We
might
be
a
fantastic
coder.
B
We
might
be
a
fantastic
person
in
terms
of
our
python
skills,
our
java
skills,
but
unless
we
understand
the
reason
why
customer
has
come
to
us
why
the
customer
has
paid
us
to
create
that
code,
we
wouldn't
be
able
to
be
a
good
software
developer
right.
So
therefore,
the
reason
why
software
soft
skills
are
important
for
a
software
developer
like
us,
is
when
people
work
together
on
a
software
project.
B
Other
skills
are
necessary
to
implement.
Of
course,
there
are
techniques
and
tools
and
frameworks
that
we
need
to
use.
But,
apart
from
that,
our
ability
to
understand
people
our
ability
to
communicate
what
we
have
in
our
brain,
our
ability
to
interact
with
the
team
each
person
has
got
a
ego.
Everybody
in
in
this
world
who
is
born
has
got
an
ego
that
that's
what
sigmund
freud
tells
us
right.
B
Not
the
big
bang
approach,
not
doing
everything
that
we
can
do,
but
not
communicating
presenting
the
progress
of
the
project
negotiating
with
the
customers
in
terms
of
what
feature
needs
to
go
on
priority.
What
feature
can
be
held?
What
are
what
are
the
things
that
we
can?
We
can
improve
in
the
product,
so
this
is
negotiating
skills
with
the
customers
solving
problems
for
which
you
know
we
are,
we
are
paid
and
we
are
respected
in
this
world
as
problem
solver.
Every
software
developer
is
a
problem.
B
Solver
every
customer
comes
to
you
with
a
problem
statement
and
what
we
do
is
we
create
pro.
We
create
programs
to
solve
problems,
making
decisions,
decision
making
is
important
skill
among
others,
so
that
is,
that
is
the
importance
of
soft
skill
so
guys
there
are,
as
I
told
you,
there
are
64
skills.
A
B
You
need
to
have
as
a
software
developer
as
a
software
engineer,
and
there
is
a
big
list
of
probably
the
soft
skills
are
getting
increased
these
days
because
of
the
technology
that
we
are
working
on
and
so
on.
But
allow
me
to
talk
about
few
skills
that
I
had
seen
as
most
important
for
software
development
community
today,
number
one
to
survive
in
the
industry
number
two
to
excel
in
the
industry
number
three
to
be
the
best
in
the
industry,
and
these
are.
B
These
are
the
important
skills
that
I
talk
about
number
one,
our
ability
to
pay
attention.
That's
soft
skill
that
we
need
to
that.
We
need
to
inculcate
number
two
our
ability
to
speak
and
transfer
the
message
that
we
have
in
our
brain
to
another
person.
Communication
number
three
ability
to
live
this
life
within
24
hours
a
day.
B
B
How
do
we
manage
time
management
of
time
and
organization
of
activities,
collaboration
getting
that
mindset
of
collaboration,
teamwork,
adaptability,
self-learning
and
accountability?
These
are.
These
are
some
of
the
importance
that
that
I
prioritize
for
software
developers
right.
So,
let's,
let's
move
on
to
paying
attention
guys
in
this
era,
where
we
have
millennials
coming
in
there
are
researchers
happening
on
how
long
a
person
can
pay
attention
to
anything.
B
The
span
of
attention
itself
is
shrinking,
but
as
software
developers
we
need
to
remember
that
we
are
creators.
We
are
creators
of
programs.
We
are
creators
of
solutions
so
therefore
to
be
on
top
of
this
profession,
we
need
to
pay
attention
to
detail.
Just
take
a
note
of
this.
Paying
attention
to
details
will
put
you
on
on
the
right
track
to
your
growth.
B
We
need
to
pay
attention
to
problems.
There
is
lots
of
times
that
we
assume
certain
things
right.
Assumption
has
become
a
big
problem
these
days
it
has
become
a
big
challenge,
while
training
people,
while
while
coaching
people
paying
attention
to
details,
maybe
it
is
in
the
customer
problem,
the
problems
that
we
are.
B
We
are
approached
with
paying
attention
to
solutions
and
seeing
where
the
solutions
can
break,
where
the
solutions
need
to
be
integrated,
with
other
solutions,
paying
attention
to
the
solution
that
we
build,
paying
attention
to
risks
that
we
have
not
seen
but
might
approach
us
at
any
point
of
time.
A
risk
is
an
even
that
can
happen
at
any
point
of
time,
paying
attention
to
risk
paying
attention
to
vulnerabilities.
B
B
We
all
work
in
a
political
environment,
the
environment
environment
in
which
the
project
is
executed.
If
you
see
the
pmbok
the
project
management
body
of
language
knowledge,
it
talks
about
environment,
consists
of
multiple
things:
external
environment,
internal
environments
and
political
environments.
We
need
to
pay
attention
to
that.
Look
at
the
changes.
Look
at
the
changes
that
that
might
happen
in
the
project.
Look
at
the
political
surroundings,
look
at
the
technical
factors,
pay
attention
to
the
environment
and
pay
attention
to.
B
This
is
my
favorite
statement
that
I
tell
in
all
mighty
matrix
pay
attention
to
what
is
not
spoken.
That
is
the
ultimate
soft
skill
that
one
can
develop.
Somebody
might
come
and
say
yes,
I
will
do
this,
but
that,
yes
may
not
be
yes.
If
you
have
looked
at
the
language,
if
you
have
looked
at
the
tone,
probably
is
saying
he's
not
interested,
but
he's
being
compelled
right,
yes,
can
be
interpreted
into
a
different
way.
So
therefore,
as
developers
as
we
are
growing
in
our
career,
you
know
in
software
industry
what
we
need
to
inculcate.
B
B
Who
may
not
understand
the
importance
of
paying
attention
paying
attention
is
one
of
the
great
skills
that
software
development
community
needs
to
have
based.
Communication
is
another
soft
skill,
very,
very
important
for
some
reason.
I
believe
that,
instead
of
increasing
our
maturity
in
communication
because
of
the
hurry,
the
urgency
in
which
we
are
living
because
of
the
busy
world
that
we
are
living
communication
has
deteriorated.
B
Remember
today,
all
of
us,
whoever
is
working
from
india
today
on
some
software
projects,
is
not
because
of
your
credit.
It's
not
because
of
our
credit
in
1980s,
when
the
software
engineering
branch
started,
opening
up
in
the
world,
indians
around
the
world
went
to
u.s
went
to
europe
started,
telling
started,
proving
that
india
has
got
the
best
of
brains
and
that's
how
indian
industry.
B
Today,
indian
software
industry
has
grown
and
lots
of
credit
to
people
who
have
done
this
in
1980s
99
right
and
they
were
able
to
communicate
and
today
what
what
we
think
is
we
have
selective
listening.
You
know
we
don't
listen
to
the
entire
statement.
We
don't
listen
to
the
core
message.
We
are
all
interested.
People
have
misunderstood
communication,
as
speaking
english
people
have
misunderstood
communication
us
in
a
in
a
group
meeting
group
discussion.
You
need
to
be
pretty
bossy,
fairest.
You
need
to
be
loud
so
that
people
think
that
you
are
communicating.
B
Communicating
is
not
that
communicating
is,
is
ability
to
put
what
you
have
in
your
brain
to
the
other
person.
That's
what
communication
is
all
about,
so
animals
communicate
babies
communicate
without
language.
It
doesn't
need
words
for
communicating,
but
when
we
are
when
we
are
in
this
industry,
where
the
vocabulary
is
big,
the
grammar
is
big.
We
need
to
speak
with
clarity
understand.
We
need
to
warn
what
we
are
speaking
speak
with.
Conviction
speak
with
confidence.
People
will
trust
you
only
when
you
appear
trusted
right.
B
B
B
You
need
to
have
the
perfection
versus
what
is
required
for
for
delivery
right.
Sometimes
we
we
tend
to
spend
lots
of
time
trying
to
perfect
what
we
are
trying
to
deliver,
and
then
we
miss
our
timelines
as
well.
So
how
much
time
do
you
spend
in
planning?
How
much
time
do
you
spend
in
actually
writing
the
code?
How
much
time
do
you
spend
working
with
your
team
to
come
up
with
new
ideas?
Managing
your
own
time
efficiently
allows
you
to
focus
on
what
is
most
important
and
get
the
task
some
of
the
time.
B
Wasters
right,
you
know
if
you
had
seen
there
are.
There
are
events
that
will
waste
your
time
and
that's
what
we
need
to
pay
attention
to
the
spam
news.
The
spam
mails,
some
of
the
social
media,
videos,
whatsapp
groups
that
you
get
you
know
people
forwarding
some
some
hen
and
chicken
playing
together.
We
spend
lots
of
time
right
so
paying
attention
to
unneeded
meetings,
unwanted
the
news,
spam
mails,
social
medias.
That
can
give
you
lots
of
hour.
B
B
Very
important,
as
I
said
for
those
of
you
who
have
read
the
seven
habits
of
highly
effective
people
by
stephen
arkawy,
he
says
synergy
habit.
Number
five
is
synergy.
If
you
have
read
13
principles
of
success
by
napoleon
hill,
he
talks
about
principle
number
two,
which
is
mastermind
when
you
are
by
yourself.
The
amount
of
things
that
you
can
achieve
is
lot
lesser
than
when
you
have
collaboration
with
somebody
else.
B
So
whenever
you
get
a
chance
to
talk
to
your
customer,
take
him
as
your
collaborator.
He
is
part
of
your
team,
a
collaboration
when
you
are
working
with
your
team
collaborate
with
your
team.
It
is
not
easy
now.
It
is
not
easy
because,
as
I
told
you,
every
human
being
have
got
their
own
understanding,
they
are
seasoned
with
the
experience
that
they
have
got.
B
You
might
have
difficult
people
to
work
with,
but
that's
where
our
intelligence,
our
emotional
intelligence,
should
come
in
and
that's
where
we
need
to
make
conscious
decisions
saying
that
everybody
has
got
their
own
value
system.
I
have
open
mind
I'll,
accept
the
other
person
as
it
is.
I
tell
you
guys,
collaboration
and
teamwork.
The
best
way
to
increase
that
is
teach
to
somebody
something
on
everyday
basis,
learn
something
by
yourself.
B
Go
to
the
team,
teach
something
be
it
as
small
as
a
poem
that
you
read
from
shakespeare.
Right:
go
teach
to
them
when
you
teach
them
when
you
mentor
them.
When
you
become
a
go-giver
collaboration,
the
rest
of
the
world
universe,
rest
of
the
people
will
start
reacting
to
you
in
a
positive
way.
That's
how
we
can
handle
teams,
that's
how
we
can
get
better
collaboration
with
teams
kind
of
last,
but
one
slide
adaptability
and
self-learning,
a
skill
which
is
required
very
soft
skills.
A
B
Days
I
used
to
learn
a
program
programming
language
called
prologue,
which
was
an
artificial
intelligence
language.
I
used
to
learn
cobalt.
I
used
to
learn
foxpro
I
used
to
learn
vb
4.0.
All
this
is
dead.
All
this
is
not
used
anywhere
right,
given
this
nature
of
technological
sector
in
which
we
are
in
in
the
envious
position
that
we
hold
in
the
industry.
A
developer
with
an
adaptable
and
self-learning
attitude
has.
A
B
Today,
I
need
to
learn
kubernetes,
I
need
to
learn
openshift
and
that's
a
mandate
of
this
technical
sector.
We
have
to
learn
as
long
as
we
work
in
this
industry.
The
day
you
decide
to
stop.
Learning
is
the
day
you
hear.
You
are
heading
for
path
of
excellence.
You
become
obsolete.
Very,
very
quickly,
do
not
be
afraid
of
learning.
Something
do
not
be
afraid
of
experimenting
with
some
new
technologies.
B
New
frameworks,
new
tools
create
code
on
a
daily
basis,
even
if
you
have
become
a
manager,
even
if
you
have
become
a
director
put
your
hands
dirty,
make
your
hands
dirty
by
quoting
something
I
I
know
my
own
manager
called
adrian
who
was
who
was
working
with
me
in
one
of
the
earlier
companies
used
to
code.
He
was
writing
code
for
argumented
reality
when
argument
of
reality
was
not
even
in
scenes
and
today,
argumentative
reality
is
everywhere
right
being
able
to
keep
with
times
and
work
on
upskilling
once
oneself
to
adapt
to.
B
The
current
scenario
is
one
of
the
best
soft
skills
that
we
require
in
this
specific
industry.
We
are
not
driving
mtc
buses
for
40
years.
The
steering
remains
the
same
for
40
years.
The
brake
remains
the
same,
whereas
here
the
languages
change
the
frameworks,
change
the
tools,
change
and
if
I
don't
learn
on
a
daily
basis,
I
become
obsolete,
I'll
be
thrown
out,
and
how
do
we
increase
our
value
by
by
being
with
the
with
the
right
technology
accountability?
My
last
slide
guys.
I
know
I'm
running
short
of
time.
B
Accountability
is
what
distinguishes
a
software
developer
from
a
programmer.
Take
accountability.
The
code
that
I
write
is
my
own
code.
The
code
that
I
write
is
is
going
to
be
used
in
an
airplane.
The
code
that
I
write
is
going
to
be
used
in
an
elevator.
Do
I
want
to
get
elevator
struck?
Do
I
want
to
have
a
mishap
in
any
of
my
software?
Take
accountability
to
grow
as
a
software
developer.
You
must
accept
and
take
ownership
of
your
mistakes
of
your
learnings.
B
Accountability
is
all
about
first
step
towards
our
leadership
in
industry.
I'm
not
talking
about
positional
leadership.
I'm
talking
about
you
as
a
software
developer
leadership,
personal
accountability,
is
the
first
step
and,
as
the
saying
goes,
let's
stop
working
today,
let's
start
enjoying
our
habi
hobby,
our
hobby
is
to
create
code.
Our
hobby
is
to
solve
problems
and
therefore
I
love
what
I'm
doing.
Therefore,
I'm
not
tired
of
working
I'm
not
going
to
office
to
work,
I'm
going
to
offers
to
play
my
hobby,
which
is
writing
of
code
and
solving
of
problems.
A
Hey
thanks
a
lot
thanks,
lord
wilson.
I
think
it
was
a
really
great
session.
You've
consolidated,
so
many
things
which
everybody
every
one
of
us
needs
to
buy
from
college
students
and
professionals
and
everything.
So
I
think
everybody
would
have
really
enjoyed
and
a
lot
of
key
takeaways.
I
should
say-
and
it's
all
kind
of
life
lessons
more
than
you
know
the
technical
stuffs.
It
is
all
life
lessons
and
all
of
us
should
definitely
know
and
invite
by
it.
So
it
was
really
great
having
you
on
our
event,
wilson.