Why I Mothballed my Newsletter

By

I include below the text of the last issue of my Practicing Google newsletter, in which I announced I discontinued the publication and explained why. It feels at the same time sad because it's a failure, and energizing as the it frees up resources for new projects.

This is the last issue of Practicing Google.

I’m ceasing publication of the newsletter, or at least suspending it indefinitely. I might resume at some point, but not in the short term. If so, I’ll notify the readers still subscribed or announce related projects.

The Practicing Google Newsletter was discontinued
I discontinued my Practicing Google Newsletter.

I’m sorry this comes out of the blue, but it was inevitable. I’ll explain below why I took this decision I had been considering for a long time.

Thank you very much for your attention and support.


There's no interest

With billions of Google users, without research or validation I assumed at least a few hundred would subscribe to Practicing Google. Almost two years and 87 issues later, the subscriber count has been flat around 50 with no growth since the first issues in early 2020.

I didn’t get much reader engagement either.

I personally emailed a welcome note to most new subscribers, but only a couple replied. I sent out a survey, which only 3 readesr filled. I asked countless questions in many issues, but no answers came. Only a couple of readers clicked the like button at the end of the issues. Nearly no one emailed or reached out to me with feedback, positive or negative. If there ever was word of mouth or sharing of the issues, it didn’t have any impact on the subscriber count. Over the past few months, link clicks began to decrease.

Even the least successful of my blog posts or tweets get 3-5X more eyeballs than the couple dozen active readers of Practicing Google.

It’s a failure, it couldn’t be more clear.

All this silence means the newsletter didn’t reasonate and there’s no interest in it, at least in the current form. Not even among Google enthusiasts. Therefore, keeping Practicing Google alive is not worth the effort.


Growth is hard

Stating that growing an audience is hard for creators is an understatement. It’s actually damn near impossible.

When starting out, everything happens at a snail’s pace and nothing seems to move the needle. Best practices, popular growth strategies, what worked for other creators, advice from gurus, the works. Nothing makes a difference.

Until you hit a critical mass. Then, a self-sustaining chain reaction kicks in and pretty much anything you throw at the wall sticks.

It takes an audience to build an audience.

I’m no celebrity and I still don’t have a significant online footprint, which didn’t help with growing Practicing Google.


Marketing is not an option

In order to grow, creators are supposed to follow the “best practices” of marketing such as luring potential readers with freebies, pressing them with calls to action, teasing with clickbait, writing for SEO instead of humans, and otherwise poking and prodding readers as if they were lab rats.

I did the opposite.

I assumed potential readers would be adults capable of deciding whether Practicing Google was valuable to them. All I did was genuinely tell why I thought my content was interesting or helpful. Everything suggests the readers decided they don’t want to subscribe.

Fair enough, back to the drawing board.


Thank you, one last time

I wish to thank you twice. First, for sticking with the newsletter. Second, for being interested enough in this post-mortem to read this far.

If you still want to keep in touch with me online, I have a blog, a Twitter profile, and a GitHub profile.

So long, and thanks for reading.

Popular posts from this blog

Using a Bluetooth Keyboard on Android

By
Image
Two years ago I bought a cheap Bluetooth keyboard from Amazon.it. At €14, it was mostly an impulse buy for exploring mobile typing on the go and in similar settings , such as workstations with reduced desk space. My FREALL 7INKEYBD-BK Bluetooth keyboard. I initially used the keyboard with the Android tablet and smartphone I had, a 7” Lenovo Tab E7 and a Pixel 2 XL. I later repurposed the keyboard for the devices I replaced those with, a Lenovo Tab M8 HD 8” tablet and a Pixel 4 XL smartphone. Despite the simplicity of operation, it took me some trial and error to figure out how to pair the keyboard with an Android device and what keystrokes insert the characters I need, such as accented letters when writing in Italian. Moreover, I realized I never blogged about my experience with the unit. So I’m posting these notes in case you come across the same or similar keyboards. The keyboard The keyboard is a cheap, compact, plastic chiclet unit that comes with a small foldable stand for a ta
Read more

Lenovo Tab M8 HD Review

By
Image
I bought a Lenovo Tab M8 HD , an 8” Android tablet. It comes with a MediaTek Helio A22 SoC, an IPS panel, 2 GB of RAM, and 32 GB of storage. I ordered the device from Lenovo’s Italian online store for €134. In this post I’ll share my early impressions on the device. The packaging box of the Lenovo Tab M8 HD tablet. Motivation The Lenovo Tab M8 HD replaces the Lenovo Tab E7 7” tablet I bought almost a year and a half earlier. After enjoying the Google Nexus 7 2012 and 2013 tablets I left Android slates for several years. My return to tablets with the November 2019 purchase of the cheap Lenovo Tab E7 was a sort of impulse buy. I wanted an affordable Android slate small enough to be compact but with a large enough screen to help productivity . I also figured it would double as an ebook reading device and let me explore the Android ecosystem. The Tab E7 was nice but limited. The screen didn’t have good touch sensitivity, performance was poor, there was a lot of lag, and the screen was no
Read more

How to Add Code Syntax Highlighting to Blogger

By
Image
On my blog I always wanted to format source code in Python and a couple more languages, but couldn’t find a convenient way. Until I read a tutorial on adding syntax highlighting to Blogger blogs like mine. The Blogger post composer actually provides the monospace Courier font that may be used for source code, but it works well only for inline text . If I apply the Courier font to a block of code, the composer renders each line as a separate paragraph. This leaves too much vertical space that makes the code look ugly. A workaround is to switch to the HTML view in the composer and wrap the block within <pre> ... </pre> tags, which insert the correct line spacing. However, the code doesn’t stand out on the page and there’s room for improving its scannability and visual impact. Fortunately, Blogger is an old dog I can teach new tricks to, like the setup the tutorial I found presents. A Python code snippet with syntax highlighting rendered by highlights.js in a post of the Moo
Read more