Charla de Javier Martínez Head of Development en Telefónica I+D ofrecida al Ecosistema Smart_ de TID Chile

1. Good practices to build good
software at XXI
A personal vision by Javier Martínez Álvarez (@jamaa)

2. 2

3. Developer
Manager
University
Professor
Researcher
Eternal
learner
+20 years of experience in 5 different companies

4. 4
I learning, fell in love
and good , enjoy design
,support the best
Crazy about
and fan of almost all stuff.
and .

5. Head of Development of
Telefonica I+D
Lead the adoption of
technologies, architectures,
sw development practices
and tools across all product
areas.
Design and build TI+D
development service
platform.
Promote that CCDO
products are developed with
the best architectures,
practices, people and tools.
Report and manage
software development
status (code metrics,
practices, technology
adoptions) across multiple
products.
Help company in main
strategic technical
decisions.

6. What are the key elements to
build good software?

7. Organization
Technology
& tools
PeopleProcess
Users

8. 0
10
20
30
40
50
60
Organization Users People Technology Process
Project successful keys

9. What does a developer look like
more? To an engineer or to a
painter or a writer?

10. software developers are like
artists

11. understand what software
development is

12. Organizations

13. “Any organization that designs a system (defined more
broadly here than just information systems) will inevitably
produce a design whose structure is a copy of the
organization’s communication structure.”
Conway’s Law. Melvin Conway Datamation magazine in April 1968

14. “If you have four groups working on a
compiler, you’ll get a 4-pass compiler.”
Eric S Raymond in The New Hacker’s Dictionary

15. be small

16. be small, flat

17. be small, flat, and agile

18. get talent

19. get talent, freedom

20. get talent, freedom and hacker-
centric culture

21. Do the right things is
important…

22. ..however there is something
even more important

23. Doing the right thing

24. Team

25. Team, code reviews

26. Team, code reviews,
openness

27. Team, code reviews, openness
and mission

28. Users

29. It’s not what the software
does. It’s what the user does

30. Eat your own dog food

31. Eat your own dog food,
exploratory test

32. Eat your own dog food,
exploratory test and metrics

33. People

34. self-learning

35. self-learning, passion

36. self-learning, passion and soft
skills

37. productivity

38. productivity, gamification

40. work, family, body and soul

41. Technology & Tools

42. Better few bad than many good

43. It takes approximately 10,000 hours of deliberate
practice to master a skill = 5-6 years of 8h day work
 Elite = 10000 hours
 Good = 8000 hours
 Average=4000 hours
The 10,000 Hour Rule. Malcom Glassgow form an study of K. Anders Ericsson

53. Use XaaS

54. Openstack, “Linux” of the cloud

55. IoT Platform

56. Process

57. What kind of methodologies
do you use?

58. Scrum

59. Scrum, scrumban

60. Scrum, scrumban and
Kanban

61. Stakeholders
Development Team
Demos
and
Releases
Feedback
and
Requests
Delivery frequency = Speed of learning

62. Release
seldom
Release
is big
Release
is hard
Release is a drama!!!

63. Release
often
Release
is small
Release
is simple
Release is a routine!!!

64. Code &
Commit
Build
Test &
Integrate
Deploy to
staging
Not
functional
tests
Test: is
everything
OK?
Deploy to
production

65. Maximize Value, not Output

66. Coding Styles, TDD and BDD

68. Measure process and
applications

69. Q&A