The document discusses what it means to be a technical lead and provides advice on how to become one. It states that a tech lead is the top engineer who owns the architecture and critical modules, assures implementation quality, and mentors other engineers. It emphasizes that passion, strengths, knowledge, experience, communication skills, creativity, and professionalism are important for becoming a tech lead. It advises engineers to build their careers based on their unique strengths and passions.

1. On
Becomin
g
a
Technical
L
ead
Buu
Nguyen
,
VP
Techno
logy
KMS
Techn
ology

2. What
is
meant
by
“tech
lead”?

3. Top
engineer
Assure
Own
implementation
architecture
&
quality
critical
modules
Mentor
other
engineers

4. Should
I
become
a
tech
lead?
Or
how
should
I
choose
a
career?

5. Passion
Reward
Strength

6. Passion
Passion
Passion
overcomes
challenges

7. Passion
Come
what
may
at
the
end,
you
will
have
had
good
time

8. Being
passionate
about
something
doesn’t
mean
you
can
be
really
good
at
it

9. Trying
real
hard
doesn’t
guarantee
being
top

10. Yourself
DNA
Environment

11. You
are
unique,
so
is
your
strength
Build
your
career
on
it

12. Is
the
REWARD
good?

14. What
makes
a
good
tech
lead?
Or
what
should
I
do
to
become
a
tech
lead?

15. Experience
Communication
Knowledge
Professionalism
Creativity

16. Experience
Communication
Knowledge
Professionalism
Creativity

17. Know
broad
"If
you
are
a
.NET
programmer,
learn
Java.
If
you
are
a
Java
programmer,
learn
Ruby.
If
you
are
a
C
programmer,
learn
Lisp.”
The
Clean
Coder,
Robert
C.
Martin

18. Know
deep
"You
need
knowledge
of
speciUic
technologies
to
do
your
job,
but
you
need
knowledge
of
software
engineering
principles
to
do
your
job
well.”
After
the
Gold
Rush,
Steve
McConnell

19. The
WHWHW
Framework
Level
Question
Hobbyist
What
is
it?
Apprentice
How
to
use
it?
Competent
Why
is
it
built?
Advanced
How
is
it
built?
Master
Why
is
it
built
that
way?

20. Stay
current

21. Experience
Communication
Knowledge
Professionalism
Creativity

22. The
10,000-­‐hour
rule
“Practice
isn't
the
thing
you
do
once
you're
good.
It's
the
thing
you
do
that
makes
you
good.”
Outliers,
Malcolm
Gladwell

23. Not
all
10,000
hours
are
equal
“The
bottom
line
on
experience
is
this:
If
you
work
for
10
years,
do
you
get
10
years
of
experience
or
do
you
get
1
year
of
experience
10
times?”
Code
Complete,
Steve
McConnell

24. Be
open-­‐minded

25. Experience
Communication
Knowledge
Professionalism
Creativity

26. Experience
Communication
Knowledge
Professionalism
Creativity

27. Reject
the
status
quo

28. Work
hard
on
your
real
needs

29. Get
exposed
to
ideas
“Whenever
human
beings
Uirst
organized
themselves
into
settlements
that
resembled
liquid
networks,
a
great
Ulowering
of
innovations
would
have
immediately
followed.”
Where
Good
Ideas
Come
From,
Steven
Johnson

30. Experience
Communication
Knowledge
Professionalism
Creativity

31. Take
and
accept
responsibility
“I
will
prescribe
regimens
for
the
good
of
my
patients
according
to
my
ability
and
my
judgment
and
never
do
harm
to
anyone.”
Excerpt
from
the
Hippocratic
Oath

32. Career
development
is
your
responsibility
“You
should
plan
on
working
60
hours
per
week.
The
Uirst
40
are
for
your
employer.
The
remaining
20
are
for
you.”
The
Clean
Coder,
Robert
C.
Martin

33. Takeaway
0 Is
“tech
lead”
for
you?
0 Know
your
passion,
strength
and
reward
0 How
to
become
one?
0 Work
on
your
knowledge,
experience,
communication,
creativity
and
professionalism

34. Thank
You!
0 buunguyen@kms-­‐technology.com
0 www.buunguyen.net/blog
0 Online
nick:
buunguyen
0 Twitter,
Facebook,
LinkedIn
0 Github,
CodePlex
0 SlideShare,
The
Code
Project