A title with no of
fi
cial/
standardized de
fi
nition is
useless.
Slide 14
Slide 14 text
Titles are only useful
when changing jobs.
Slide 15
Slide 15 text
No content
Slide 16
Slide 16 text
Junior developer
Slide 17
Slide 17 text
No content
Slide 18
Slide 18 text
• Focus should be trying your best to lear
n
• Needs directio
n
• Needs supervisio
n
• Needs mentorin
g
• You can still be a junior even after a decade in the industry
Junior developer
Slide 19
Slide 19 text
A junior developer is
code focused, not
development focused,
and doesn’t understand
the distinction.
Slide 20
Slide 20 text
Junior developers are
not responsible for the
projects!
Slide 21
Slide 21 text
Intermediate developer
Slide 22
Slide 22 text
On the mission of finding
the Right way of building
the software
Slide 23
Slide 23 text
No content
Slide 24
Slide 24 text
• They understand project, goals and teamwor
k
• They can estimate thing
s
• They can participate in improving things and process around the projec
t
• Systems built by intermediate will work far longer, but will lead to some sort of
disaster
• The sad fact is that vast majority thinks they are senior developers
Intermediate developer
Slide 25
Slide 25 text
They can be trusted to
raise issues of code
design, and play a
valuable role in design
discussions. They are
also the “workhorses” of
the dev team.
Slide 26
Slide 26 text
Senior developer
Slide 27
Slide 27 text
• They wrote under and over designed systems. And both failed
.
• They are solving issues -
fi
re
fi
ghter
s
• Hates complexity and it is obsessed with simplicity
They know how failure
looks like
Slide 28
Slide 28 text
A high-level
understanding of how
systems work
(closed systems, design
patterns, why, how, not
hype-driven)
Slide 29
Slide 29 text
They fully understand
that their job is not just
writing code but solving
problems
.
Slide 30
Slide 30 text
Knowledge about the
business' problem is
essential!
Slide 31
Slide 31 text
They fully understand
context when applying
theory!
Slide 32
Slide 32 text
There is no “right way”
to build software.
Slide 33
Slide 33 text
The only way to build
good software is by
adapting theory to
fi
t the
needs of the client,
budget, codebase, team,
tools, and organization
.
Your team members are
humans too
…
Teamwork. Be nice. Care.
Slide 39
Slide 39 text
Making other humans in
the team better!
Slide 40
Slide 40 text
Be the senior you needed
when you were a junior.
Slide 41
Slide 41 text
Being able to
communicate clearly in
business language - not
tech jargon - with
business people / non-
technical co-workers
.
Slide 42
Slide 42 text
No content
Slide 43
Slide 43 text
They understand it is not
about them, but about
customers.
Slide 44
Slide 44 text
Old people in the
Industry?
Slide 45
Slide 45 text
No content
Slide 46
Slide 46 text
"The most important skill in the future will
be the ability to "connect the dots" in your
own way!" - Fabio Moioli
Slide 47
Slide 47 text
“You can know all the cool functional
programming techniques in the world, but if
you are unable to communicate well with your
team, or you are not able to focus on
delivering actual value to a customer, you are
not a senior developer.”
Slide 48
Slide 48 text
Thank you!
Slide 49
Slide 49 text
Questions?
Antonio Perić-Maža
r
t: @antonioperi
c
m: [email protected]