The bleeding edge of Android Development

Hyped by that new library? Do you want to follow the trend and implement a new technology because of reasons?

With this talk I try to show a different point of view of all this trends regarding new technologies and the price of using them without proper thinking.

Transcript

1. The Bleeding Edge of Android Development by Alberto Ballano Android Developer @ XING
2. A common sickness among developers
3. A common sickness among developers • Libraries • Patterns • Frameworks • Languages
4. A common sickness among developers Hail to acclaim enthusiastically
5. A common sickness among developers Hail to acclaim enthusiastically Idealize to regard as perfect
6. A common sickness among developers Hail to acclaim enthusiastically Idealize to regard as perfect Prejudice to form an opinion before enough info is available
7. A common sickness among developers Hail to acclaim enthusiastically Idealize to regard as perfect Prejudice to form an opinion before enough info is available Sacrifice to stop having something good in order to achieve something
8. A common sickness among developers Hail to acclaim enthusiastically Idealize to regard as perfect Prejudice to form an opinion before enough info is available Sacrifice to stop having something good in order to achieve something Tear to move or behave with force, violent haste, or energy
9. A common sickness among developers Hail to acclaim enthusiastically Idealize to regard as perfect Prejudice to form an opinion before enough info is available Sacrifice to stop having something good in order to achieve something Tear to move or behave with force, violent haste, or energy Early adopt to be one of the first to start using a new product
10. A common sickness among developers H I P S T E R Hail to acclaim enthusiastically Idealize to regard as perfect Prejudice to form an opinion before enough info is available Sacrifice to stop having something good in order to achieve something Tear to move or behave with force, violent haste, or energy Early adopt to be one of the first to start using a new product Reject to refuse to accept or agree with something
11. A common sickness among developers H I P S T E R Hail to acclaim enthusiastically Idealize to regard as perfect Prejudice to form an opinion before enough info is available Sacrifice to stop having something good in order to achieve something Tear to move or behave with force, violent haste, or energy Early adopt to be one of the first to start using a new product Reject to refuse to accept or agree with something
12. A common sickness among developers H I P S T E R H I P S T E R
13. A common sickness among developers H I P S T E R H I P S T E R syndrome
14. How to identify if you are "infected"
15. How to identify if you are "infected" Do you…
16. How to identify if you are "infected" Do you… • Try to avoid getting hyped by technology trends?
17. How to identify if you are "infected" Do you… • Try to avoid getting hyped by technology trends? • Consider the pros and cons of including new technology in a project?
18. How to identify if you are "infected" Do you… • Try to avoid getting hyped by technology trends? • Consider the pros and cons of including new technology in a project? • Evaluate your needs and the project needs to select the best technology?
19. How to identify if you are "infected" Do you… • Try to avoid getting hyped by technology trends? • Consider the pros and cons of including new technology in a project? • Evaluate your needs and the project needs to select the best technology? • Admit when some trendy technology doesn't fit and drop it?
20. How to identify if you are "infected" Do you… • Try to avoid getting hyped by technology trends? • Consider the pros and cons of including new technology in a project? • Evaluate your needs and the project needs to select the best technology? • Admit when some trendy technology doesn't fit and drop it? Hint: If you answer is NO to any of those, you are partially infected ;)
21. Time investment
22. Time investment Value (for your company)
23. Time investment Value (for your company)
24. Time investment Value (for your company) Risk
25. The usual suspects • EventBus/Otto • Picasso/Glide • Agera/RxJava • Scala/Kotlin • Any ORM/Realm
26. The balance bar Old school Hipster
27. The opposite extreme: Old School Dev
28. The opposite extreme: Old School Dev • Time investment is bigger
29. The opposite extreme: Old School Dev • Time investment is bigger • Value (for the company) could be bigger
30. The opposite extreme: Old School Dev • Time investment is bigger • Value (for the company) could be bigger • Risk is much higher
31. The balance bar Old school Hipster
32. The balance bar Old school Hipster Pragmatic
33. How? Sum up Regarding new technology(libs/patterns/frameworks/languages): • Implementation and maintenance always comes with a cost, don’t just include them because of the “trend” (Time investment). • They provide solutions for problems, consider using them when they solve one or when the benefit is bigger than the cost (Value). ◦ ButterKnife ◦ Kotlin ◦ Rxjava • Think about how complicated is the implementation (+is it a big change?). Plus check how well maintained is the lib (+do you understand it?) (Risk)
34. RESPONSABILITY
35. By the way…
36. By the way… we’re hiring! CVs are always welcome! alberto.ballano@xing.com
37. Thank you https://speakerdeck.com/shyish/the-bleeding-edge-of-android-development Twitter: @Aballano Github: https://github.com/Shyish