Slide 1

Slide 1 text

The Bleeding Edge of Android Development by Alberto Ballano Android Developer @ XING

Slide 2

Slide 2 text

A common sickness among developers

Slide 3

Slide 3 text

A common sickness among developers ● Libraries ● Patterns ● Frameworks ● Languages

Slide 4

Slide 4 text

A common sickness among developers Hail to acclaim enthusiastically

Slide 5

Slide 5 text

A common sickness among developers Hail to acclaim enthusiastically Idealize to regard as perfect

Slide 6

Slide 6 text

A common sickness among developers Hail to acclaim enthusiastically Idealize to regard as perfect Prejudice to form an opinion before enough info is available

Slide 7

Slide 7 text

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

Slide 8

Slide 8 text

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

Slide 9

Slide 9 text

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

Slide 10

Slide 10 text

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

Slide 11

Slide 11 text

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

Slide 12

Slide 12 text

A common sickness among developers H I P S T E R H I P S T E R

Slide 13

Slide 13 text

A common sickness among developers H I P S T E R H I P S T E R syndrome

Slide 14

Slide 14 text

How to identify if you are "infected"

Slide 15

Slide 15 text

How to identify if you are "infected" Do you…

Slide 16

Slide 16 text

How to identify if you are "infected" Do you… ● Try to avoid getting hyped by technology trends?

Slide 17

Slide 17 text

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?

Slide 18

Slide 18 text

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?

Slide 19

Slide 19 text

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?

Slide 20

Slide 20 text

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 ;)

Slide 21

Slide 21 text

Time investment

Slide 22

Slide 22 text

Time investment Value (for your company)

Slide 23

Slide 23 text

Time investment Value (for your company)

Slide 24

Slide 24 text

Time investment Value (for your company) Risk

Slide 25

Slide 25 text

The usual suspects ● EventBus/Otto ● Picasso/Glide ● Agera/RxJava ● Scala/Kotlin ● Any ORM/Realm

Slide 26

Slide 26 text

The balance bar Old school Hipster

Slide 27

Slide 27 text

The opposite extreme: Old School Dev

Slide 28

Slide 28 text

The opposite extreme: Old School Dev ● Time investment is bigger

Slide 29

Slide 29 text

The opposite extreme: Old School Dev ● Time investment is bigger ● Value (for the company) could be bigger

Slide 30

Slide 30 text

The opposite extreme: Old School Dev ● Time investment is bigger ● Value (for the company) could be bigger ● Risk is much higher

Slide 31

Slide 31 text

The balance bar Old school Hipster

Slide 32

Slide 32 text

The balance bar Old school Hipster Pragmatic

Slide 33

Slide 33 text

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)

Slide 34

Slide 34 text

RESPONSABILITY

Slide 35

Slide 35 text

By the way…

Slide 36

Slide 36 text

By the way… we’re hiring! CVs are always welcome! [email protected]

Slide 37

Slide 37 text

Thank you https://speakerdeck.com/shyish/the-bleeding-edge-of-android-development Twitter: @Aballano Github: https://github.com/Shyish