Every weekend, I spend a few hours assembling the newsletter issue that comes out on Tuesdays (my time).
The articles and posts that I link to come from ones that I encounter during the week, plus some specific searches (e.g., Medium). If you would like to have your post be considered, besides reaching out to me directly, just publicize the post in a typical spot (e.g.,
#JetpackCompose hashtag in Twitter), and I am likely to encounter it. The same holds true for the GitHub repositories and other code resources that I link to.
For articles and posts, mostly I review them to see if they are readable in English and are of reasonable length. Posts that are very short, or add little value to some link or code dump, usually do not “make the cut” for an issue. However, I rarely judge posts based on some concept of correctness, as I am not an arbiter of what is or is not good in the world of Compose. Besides, “what is or is not good” in Android overall changes over time.
Note that I have cut back on linking to videos. Videos are wonderful, but they are very tedious for me to review for this newsletter. So, recently I have been limiting videos to:
- Official ones from Google
- Ones containing Googlers (or prominent ex-Googlers)
- Conference presentations
For GitHub repositories, mostly I focus on whether or not the project has a decent
README, explaining what the repository contains and how it might be used. Those lacking adequate documentation usually get ignored. However, I do not do a code review of those repositories, or of any sample projects referenced by an article or post. Most of those repositories probably contain some bad code, because every repository contains some bad code.
In short, links are not endorsements. My role is to highlight what is new.
If you see that I linked to an article, post, repository, etc. that you dislike, talk to the author of the article, post, repository, etc. Try to help the author improve their work. If you want to complain to me about things that I wrote, that is perfectly reasonable and you are welcome to do so.
I run this newsletter as a public service. This is not part of my day job, as CommonsWare is now “a hobby with a logo”, and my current employer is not involved with this. There are no ads. There is no subscription fee. I do not participate in referral programs. Heck, if you get the newsletter through the main
, there should be zero tracking cookies
. I get no immediate benefit from this newsletter other than a vague sense that I am being useful.