Earlier this year, I got an opportunity to work on Big Nerd Ranch’s acclaimed Guide to Kotlin Programming.
David and Josh, the authors of the first edition, had already put together a great set of materials, and it was an exciting task to update them for the next generation of Kotlin learners.
Now that we’re inches away from crossing the finish line, I’m thrilled to tell you all about the second edition of Kotlin Programming: The Big Nerd Ranch Guide.
Back in January, I gave a brief update about Jockey, the open-source music player that kickstarted my career as an Android developer.
I specifically commented on how I was working on a full re-write and that I’d have more to share in the “coming months”.
Boy was I naieve in January.
Lifecycles are what drive your Android apps, but developers often overlook edge cases that lead to lost user inputs and mysterious crashes.
This talk will focus on assumptions that you might be making in your Activities and Fragments, where those assumptions fall apart, and what you should do to avoid deviously subtle lifecycle-related issues in your apps.
These are details that trip up both junior and experienced developers, so regardless of your experience, this talk will bring a new perspective to how you think about lifecycles.
I recently published Difference, a Kotlin library that lets you compare two lists to determine a sequence of change operations between the two.
Many Android developers have already been generating diffs to animate changes in their RecyclerViews, but there are many other reasons you might want to compare two lists.
Maybe you’re working on an app that needs to detect differences between two files like git does.
Or maybe a backend you’re integrating with sends you a before and after state, but your app needs to show only what changed.
Regardless of your use-case, Difference is here to help.
I created the Marverenic GitHub profile in February 2015 to host Jockey back when I was a freshman in college.
The goal was to create a unique brand name for the profile while retaining some anonymity.
A lot of things have changed since November 2014, which is when I wrote the first lines of code that would eventually become Jockey.
I’ve since graduated with a degree in computer science and I’ve been working at Big Nerd Ranch full-time for a year and a half after working there twice over the summers before.
The original goal of creating the Marverenic profile was to create a separation between my personal life and my side projects.
But this barrier no longer makes sense — and in hindsight it probably didn’t really make sense in the first place.
It only added complexity to the two identities, and the professional side bore the brunt of the awkwardness.
So starting now, I am sunsetting the name Marverenic.
From now on, I am just going to be Andrew Bailey.