Kotlin and Statefulness
Join waitlist?
8 on waitlist
2101 4th Ave
2101 4th Ave · Seattle, Wa
How to find us
We'll be using the Mason office on the 15th Floor of the Fourth and Blanchard Building. A Seattle Kotlin organizer will let you in to the building and the elevator (on the right side of the lobby).
Details
Welcome to the first Seattle Kotlin Meetup of 2019!
Statefulness is fun! Except when it gets cumbersome.
We will be talking about how being stateful in your applications can be useful (especially with Kotlin's help), some pitfalls and not so great stuff that can come up as you go, as well as how it greatly benefits testing for both UI and Unit tests.
Daniel Gruici is the Lead Android Developer for Geocaching. Here's a bit about Daniel:
I have a plaque on my desk that says, "Weeks of programming can save you hours of planning" to remind me to slow down every once in a while.
Reusable, non-flaky, automated tests are my favorite thing in the world. Robots pattern forever!
----
Schedule:
6:00pm - 6:30pm: discussions/food&drinks
6:30pm - 7:30pm: "Kotlin and Statefulness" talk/q&a
5-min break
7:35pm - 8:30pm: "A deep dive into adb" talk/q&a
----
Stick around after the Kotlin talk for a bonus Android talk by Ravi Subramanian: "What does `adb lolcat` do? A deep dive into adb"
If you've been an Android developer for any length of time, sooner or later you will have encountered adb -- the Android Debug Bridge. Part of the Android SDK, it is most commonly used to view the logs continuously being emitted within a device (via adb lolcat) or to run commands directly on device via a shell. But it is, as its name suggests and as you might already know, also a bridge to a variety of other functionality and information.
Have you ever wondered how adb does its magic? Or what _actually_ happens when you type in `adb shell`? In this session, we'll dive right into the deep end and take a peek under the hood to understand how every Android developer's favorite tool works.
