1.
LEMİ ORHAN ERGİN
Managing Partner & Master Software Craftsman, ACM
thinking about motivation of developers
GUIDETO THE GALAXY
HAPPY DEVELOPER’S

2.
the talk will be about developers who really love their profession
caution

3.
is a common problem for everyone
Motivation
z
z
z
z z
z

4.
for me too

5.
improveI cannot myself
Nothing excited
Monotonous
Hard to focus
No innovation
Nothing to learn

6.
Feel alone
work for long hours
Cannot get help
Blame rules
No teamwork
workI cannot with people

7.
No trust
Arguing via emails
No care for feelings
I am an headcount
Monitored closely
controlledI am like a kid

8.
I FEEL
unmotivated
exhausted
tired
hopeless
sad
angry
lazy
depressed
stressed
alone

9.
Similar?

10.
I want to
succeed
feel valuable
trust
be trusted
be in decisions
feel improved
focused
be efficient
learn
feel proud

11.
only
passionate, disciplined and motivated people
can continuously deliver
well-crafted software and value
passionate disciplined motivated

12.
passionate
disciplined
motivated

13.
motivation
All you have your own preference for

14.
motivationAcceptance
Curiosity
Power
Honor
Social Contact / Relatedness
Idealism
Status
Independence / Autonomy
Order
Competence
instrinct

15.
motivation
extrinct
“We zombify people by using wrong practices”
Niels Pflaeging Management Exorcist
from his talk at Agile Turkey Summit 2014

16.
managersare not responsible for our motivation

17.
managersare not responsible for our motivation ??????

18.
managers have to build an environment that
improves motivation and happiness

19.
human
we have to build and use
centricpractices and processes

20.
Lean
focus on the human side of our work life to build better products
Agility
Craftsmanship

21.
Lean
Craftsmanship
Agility
Trust
Honesty
Teamwork
Self-Organization
Empowered Teams
Continuous Improvement
Retrospecting Regularly
Sustainable Pace
Proxy to InterRuptions
Face to face Communication
Collaboration
Efficiency
Removing Waste
Pairing
courage
Professionalism
No Blame Rule
Limiting multi-tasking
Mentorship
Fast Feedback Loops
Community of Professionals
Code of Ethics
Collective Ownership
Practicing to Master
Five Whys
Slack Time

22.
mindsetmakes the difference, not the tools

23.
mindset
practices and characteristics of the
improving motivation and culture

24.
be aware of god complexity
Trial and error might be the best way most of the time
Your “that’s just simple” solutions
might not be realistic in real complex world

25.
leave your ego
you have to be ready for being motivated
“Mix of youth and a bit of experience
can easily lead to arrogance”
Sandro Mancuso
Author of “The Software Craftsman”

26.
abandon learnt despairs
never work on a place where you have no hope

27.
innovation is about culture
continuously doing the same thing does not mean doing it in the same way
provide safe environment for trial and errors
do experiments, do it a lot

28.
stop producing mess
learn how to build high quality software

29.
learn your profession
software development might be something different that you think

30.
tools & rituals
are not what concepts are all about

31.
stop micro managing
checking social media improves productivity

32.
trust by default
no matter how senior or experienced your team is

33.
set goals to be proud of
creativity directly bounds to purpose and constraints you have

34.
watch conference videos
spend 2 hours every week for watching conference videos

35.
define mastery goals
stop pushing performance goals for difficult problems
Dr. Heidi Grant Halvorson
From the book “Succeed: How We Can Reach Our Goals”
http://amzn.com/0452297710

36.
be communicator & fighters
spend time to remove impediments, communicate to learn the complexity
Insanity: doing the same thing over and
over again and expecting different results.
Albert Einstein

37.
foster collaboration
organize brown bag sessions, work with foremen
pair programming
code reviews
mob programming
lunch and learn sessions
proof of concept projects
enlightement talks
technical backlog items
community of professionals

38.
invest in yourself
it’s your profession, own it!

39.
give back to communities
what you get is what you give
WYGWYG
these communities do not
have to be public ones

40.
manage your brand
define target audience
write blog posts
use social media effectively
give back to the community
attend conferences
contribute to open source
. .

41.
don’t be the guy in the corner

42.
deliver positive feedback
give special importance to thank people

43.
ask responsiblity of
what you create
don’t act as if you do, ask for re
design
architecture
code
testing
deployment
monitoring

44.
pay for a better place
stop cutting costs of the essentials of our profession
confotable chairs
at least 1 monitor
large enough desk
fresh air
silent area
day light
licenses for your tools

45.
document for the next developer
Commit messages
Branch names
Commit graph
Production code
Test code
Flow diagrams
API documentation
Release notes
Code review comments

46.
define definition of fun
define nerdy rituals, feed your sense of humor, enjoy your job

47.
never work for bad
behave unethical
treat people as resources
treat you as a dummy wheel
insensible to your feelings
ill intensioned
you lost your hope

48.
Blizzard developers John Lagrave, Ion Hazzikostas, David Kim, and Kaeo Milker are
signing autographs at the Blizzard booth at Developer Signing Sessions!
gamescon2012

49.
work with
correct people

50.
ENJOYremember
whatever you do
do not forget to
https://www.flickr.com/photos/fraserspeirs/3394902061
Joe O'Brien and Jim Weirich while doing ruby code review

51.
Icons made by FlatIcon
http://www.flaticon.com/authors/freepik
CC BY 3.0 http://creativecommons.org/licenses/by/3.0
CC Zero http://creativecommons.org/publicdomain/zero/1.0
Images made by Gratisography.com, Ryan McGuire
http://www.gratisography.com

52.
Lemİ orhan ergİn
agile software craftsman
/lemiorhan
https://www.linkedin.com/in/lemiorhan
@lemiorhan
https://twitter.com/lemiorhan
/lemiorhan
http://www.slideshare.net/lemiorhan
lemiorhanergin.com
Official site having personal information
www.acm-software.com