Développeur: Quelles compétences clés faut-il maîtriser pour être meilleur Conférence donnée à Agile Tour Bordeaux 2018 http://agiletourbordeaux.fr/2018/index.html

1. Développeur:
Quelles compétences clés
faut-il maîtriser pour être
MEILLEUR
HOussam Fakih
@houssamfakih

3. Projects I’m currently involved in
@socrates_fr &
@socratesday_fr
Organizer
@lelion_vert
CTO
@arollafr
Software Developer

5. All content appearing in this presentation
are not from fictitious or novel. All
characters are real Not from any
imaginary world. Any resemblance with
the sport's world should not be
considered as purely coincidental
Disclaimer:

6. Why Are We
Interested
in Skills ?

7. Why Are We
Interested
in Skills ?

10. Skills of Developer
Agile
Software
Crafter
Lean
Startup
Lean
Tech
Geek
DevOps
XP

11. What is the purpose
of our job?

13. Create Positive Business Impact
Dan North - @tastapod
#craftconf
#2016
The purpose of software development

14. #Objective
Deliver the
Right
Product
Increase
Value for
your final
user

15. #Objective
Deliver
No Defects
Do It Right
the First
Time

16. #Objective
Deliver
Fast
Keep It
Simple
to
Make It
Fast

17. Let’s Put It
All Together

18. High Quality
Fast
Create Positive Business Impact

19. Software Quality
is the absence of defects
Defects cause the application:
- to stop working, or
- to produce incorrect results
Capers Jones

20. Speed
is the cadence
at which you deliver
"production-ready" software
Diego Lo Guidice

22. How to embrace
Speed and Quality?

23. @aloyer’s Training
1’ Exercise:
Draw a 12
points Star

25. Speed
≄
Rush

27. Skills to serve our
objectives

28. Skills recognised in
our industry
DDDBDD
SOLID
Design Patterns
Refactoring
Simple Design
TDD
XP
Agile
Pair-Programming
Mob-Programming
FP
DCVS
IDE

29. Skills
Craft &
Best Practices
Technical
Expertise
Agility
Soft
Skills
Extra
Skills

30. Time for Training

32. Conscious
vs
Unconscious

33. Three training steps
1. Master the basics
2. Be consistent
3. Add intensity

34. Mastery, Consistency & Intensity

35. Mastering the basics
Do it Right & Efficiently
Quality over time

36. Refactoring - Mastering Step
● What is refactoring? What are the code smells?
● How to use the refactoring Catalog?
● Testable Code before refactoring
● Readings:
○ “Refactoring: improving the design of existing code” Martin Fowler’s book
○ Uncle Bob article about The Transformation Priority Premise
● Master the refactoring Catalog/Shortcuts in your IDE
● Katas for practices : Gilded Rose, Tennis, Yahtzee,
Racing Car,...
Reminder : Quality is the goal not Speed

37. Developing
Katas

38. exercism.io

39. Pairing

42. MEETUPS / HANDS-ON

44. Three training steps
1. Master the basics
2. Be consistent
3. Add intensity

45. Be consistent
Practice regularly and
repeat with accuracy

46. PRACTICE

47. Refactoring - Consistency Step
Try to apply what you learn in step 1
● On new katas:
○ Trip Service Kata (by S. Mancuso)
○ Trivia Kata (by J.B. Rainsberger)
● On your project
Reminder : Quality is the goal not Speed

48. Three training steps
1. Master the basics
2. Be consistent
3. Add intensity

49. Add Intensity
Feel comfortable in the
uncomfortable
Develop faster

50. Add Metrics
Don’t trust
your feeling

51. Refactoring - Intensity Step
○ Measure your time to develop a
kata
■ Improve it
Speed and Quality
are the goal here

52. High Interval Intensity Training

54. Challenge-based training
platform for programmers
codingame topcoder

56. Next
Step

58. Have Rest
& Sleep Well

59. Remember the hardest part
is the training