Welcome to the very first edition of my newsletter.

Note: This issue was first published on Substack on December 30th, 2020, but since then I have moved to Revue hence re-posted here as part of the migration. Subscribe to my newsletter to find out what I think of Revue and why I moved to it in a subsequent issue.

With every edition of my newsletter I would like to bring up one discussion point that I would like to share my thoughts on and discuss and get feedback by way of comments from my readers.

I read a lot of technical blogs and books and over the years have become familiar with most of the options used by various authors. One pattern that I have noticed is some platforms become hip for a period of time, then fall out of favor which results in the authors writings having either less traffic or them having to move their blogs.

As a result, what I think is best is to own your content and the platform it’s on as the source of truth that never changes. By all means, other platforms can be used to give your writings a wider audience.

For my blog I use Hugo, which enables me to write my blog using markdown. I publish it on AWS s3 via GitHub. Of course, there are other options open to you for hosting your own content, including even using Wordpress.

I see a lot of technical authors use medium.com to publish. They make it easy to get up and running with writing and immediately you have an audience. Don’t fall for this though, easy is not always the best option.

They fall under the category of hip today, not necessarily still hip tomorrow (look at Tumblr and blogger for examples).

Also, as a reader, I find their user experience pretty poor, mainly caused by their paywall system to the point that I have stopped using them all together and have removed all apps. This is a shame, as I am missing out on some authors publications that only post there. Their paywall system exists to be ad free and to help authors make some money from their publications, but quite honestly for the normal average author and reader it doesn’t work. The amount an author will earn from a readers subscription is nominal in my opinion for most authors. It can only mount to anything worth talking about, if you have a global following like a celebrity or a politician. As a result their subscription doesn’t present enough value to the reader in my opinion.

However, on a positive note, they do support canonical urls. If you post the same blog on more than one site you will be penalized by search engines such as google. However by supporting canonical urls (a url that points to the original posting of your article) you won’t be penalized. This is great as it means you can have you posts elsewhere on a platform that you own, but then have a copy of it on medium for the audience. They even make it easy for you to import your post from your site to medium for this purpose and automatically adding the canonical url for you. Their import functionality is quirky though I have never been able to just import and publish, it always has issues that end up requiring manual editing for me and hence due to lack of time I haven’t posted anything on there yet.

I always wanted to have a newsletter and/or have a means of informing the readers of my blog that I have something new posted, however I never took the plunge as I didn’t want to be responsible for managing users info myself and I was worried about its legal requirements. Substack handles all that hence I finally took the plunge and now have a newsletter here on Substack.

I really like Substack. Don’t just look at it as platform for running newsletters. It is actually a very viable option for publishing on. I am not a lawyer, but looking at its legal terms, I own my content and am able to export it and take it with me elsewhere with ease. Just this one point means I would be content to have my posts here as the source of truth with the only compromise being I don’t own the platform. Its builtin newsletter functionality enables you to build an audience and gain new audience immediately.

Also, note that for a one time fee you can even have your own custom domain with them.

If you wish to monetize your content, you have the option to create your own subscription options, make your own decision on whats available to free subscribers and what content available to paying subscribers. The amount you charge for your plans is up to you and Substack just takes a small percentage of it for processing the payments. This model is, in my opinion, better for content creators. It even overlaps on providing some of the benefits Patreon provides content creators.

I might consider moving all of my content to Substack in the future. For now I am sticking with keeping my technical blog as is for the benefit of owning its platform and I prefer to write technical posts using markdown and using the git PR flow for publishing my technical work.

One thing to note is that Substack currently do not support canonical url’s (hope they will one day). Hence I would not use Substack to crosspost duplicates of your posts from elsewhere.

I am new to dev.to and have no experience of using it as an author, but I thought it is worth a mention.

It is very focussed on software developers and engineers and is easy to join via your GitHub SSO. Their service is all open source and there is no paywall.

They even support the canonical url I mentioned that medium.com supports. Which means you have no reason to not to cross post your posts there.

According to their FAQ page you do own your articles too.

You can combine options 1 and 2 and just have Substack as your source of truth blogging platform with the only compromise being that you don’t own the platform yourself.

Where do you currently publish your blog? What are your thoughts?

I will be announcing my upcoming events here on my newsletter first before anywhere else.

You can find out about the technical talks and meetups I organize by visiting https://www.sfbayareatechies.com/ where you can join our slack and discord communities. If you would like to do a talk at one of my meetups please send me details via this form.

All the events are online at the moment due to Covid19 so you can attend from were ever you are on Twitch (follow me to be notified).

We have the great privilege of welcoming Adam Rosien of Inner Product to San Francisco Scala Meetup with a talk on:

Exact date and time to be confirmed.

We have the great privilege of welcoming back Sandeep Virdi to San Francisco Scala Meetup on February 4th, 2021 at 5.30pm with a talk on:

Alvin Alexander wrote an introduction to Scala book. He has kindly donated it to the Scala Center and the Scala community. Read about it here where you can download the ebook versions for free. The book is also available online now on Scala’s website here. It is also my understanding that he has spent time contributing to the Scala 3 Book online also.

Thank you Alvin for contributing so much to the Scala community.

Also, Alvin has his book

Functional Programming Simplified on Sale on amazon.com for Christmas. We should all thank Alvin by buying his book.

The Scala community has always been famous for using gitter for keeping in touch. Great news is, to offer choice, a Discord community was also setup about a year ago. This alternative is now official and now listed on the Scala community page. Coinciding with this, discord was kind enough to provide a vanity URL for the community.

To join discord visit: https://discord.gg/scala

Big thank you to Seth Tisue for this.

Jakub Kozłowski and Ocado Technology open sourced a new Scala library to provide easy integration with OAuth2 providers using the awesome http client library from Softwaremill sttp. Details: sttp-oauth2

I continue to enjoy Scala Metals. This month saw a new release Metals v0.9.8 adding:

Details: Upgrade to Scala 2.13.4 to improve exhaustivity

Magnolia is gaining a lot of property which is well deserved of course. In this post, Calvin Fernandes shows you how to make the most of magnolia.

It is really nice seeing Swift grow on the server side and Apple investing in this. Exciting news I found out about was their Concurrency roadmap which outlines actors being part of the solution. It is also not surprising to learn that Konrad ‘ktoso’ Malawski of akka team fame will be part of the team pushing this forward. Super excited about this. Details: announcement.

Thank you all for taking the time to read my first ever newsletter. Hope you all found it useful. I will try to improve on its format as we go along and looking forward to receiving feedback from my readers. In the meanwhile, if there is anything you think I should include in future newsletters please do not hesitate to get in touch with me.