Some guidelines I have collected over the years from a number of different projects.

Authoring Pull Requests

#1. Keep em small

While learning to use Coroutines and Flow in several different projects (including my own), I noticed some common anti-patterns that tend to arise while coming to terms with structured concurrency and reactive streams. In this article, I will outline how to recognise and refactor four of the most common cases.

Keep your eyes open! A Tarsier I met near Bitung, Sulawesi

1. Using Flow instead of a suspend function


Photo by CHUTTERSNAP on Unsplash

Using Kotlin’s callbackFlow builder on Android

Photo by Michal Matlon on Unsplash
  • setOnClickListener
  • addOnCompleteListener
  • addOnScrollListener
  • addUpdateListener

Photo by Tim Gouw on Unsplash

Some specific tips for designing a technical test for your candidates.

Technical testing guidelines

Photo by rawpixel on Unsplash

Some general tips for interviewing candidates for a dev team position. Particularly for developers who are finding themselves on the other side of the interview table for the first time.

General Interviewing Guidelines

Remember the 7P’s

Photo by Drew Hays on Unsplash

Excellent software teams are naturally motivated to protect the quality and value of team membership. All you need to do is leave them to it.

#4 You don’t need to go to classes

Nick Skelton

Freelance Android Dev. Google Developer Expert. Full Time Remote. Part Time Buzzword Hacker.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store