Confessions of an ex-Android Developer (2 Part Series)
Hello Berlin Kotlin Meetup,
Here are the slides for the presentation I did on 2019-10-17
Here is its companion article
dev.to is a cool place, you should create your account today and you can follow me here!
Here are some relevant links from the talk:
- Tony Hoare - Wikipedia
- Israel Ferrer Camacho - the Burrito design pattern
- android/camera-samples Camera2Burrito
- Google Authenticator super Burrito activity
- Beethoven - Symphony No.9 (10000 Japanese) - Freude schöner Götterfunken - YouTube
- reddit#androiddev Which areas of Android development are bad and need to change?
- The infamous video: The price of ENUMs #PERFMATTERS https://www.youtube.com/watch?v=Hzs6OBcvNQE
- Here is an insightful, sad and honest answer from Dianne Hackborn (Android team) to the answer: "How should I design my Android application? What kind of MVC pattern should I use? What should I use for an event bus?"
"We often see questions from developers that are asking from the Android platform engineers about the kinds of design patterns and architectures they use in their apps. But the answer, maybe surprisingly, is we often don't have a strong opinion or really an opinion at all."
Here is the quote of Tony Hoare showing what the right way to own your mistakes
I call it my billion-dollar mistake. It was the invention of the null reference in 1965. At that time, I was designing the first comprehensive type system for references in an object oriented language (ALGOL W). My goal was to ensure that all use of references should be absolutely safe, with checking performed automatically by the compiler. But I couldn't resist the temptation to put in a null reference, simply because it was so easy to implement. This has led to innumerable errors, vulnerabilities, and system crashes, which have probably caused a billion dollars of pain and damage in the last forty years.
Tony Hoare at QCon London in 2009