Upgrade to Pro — share decks privately, control downloads, hide ads and more …

The bleeding edge of Android Development - Frea...

The bleeding edge of Android Development - Freakend

Lightning talk version of https://speakerdeck.com/shyish/the-bleeding-edge-of-android-development made with love for the #Freakend2017

Video (in spanish): https://www.youtube.com/watch?v=PI3_drvENEI

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.

Alberto Ballano

February 23, 2017
Tweet

More Decks by Alberto Ballano

Other Decks in Programming

Transcript

  1. Bleeding Edge Development Do you… • Try to avoid getting

    hyped by technology trends? • Consider the pros and cons of including new technology in a project?
  2. Bleeding Edge Development 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?
  3. Bleeding Edge Development 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?
  4. Bleeding Edge Development 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 those, you are a Hipster
  5. 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)