NewsletterSide-HustleEngineering

[Starting Newsletter] Getting to first 100 subs

Mar 09, 2026

This is the first of many posts I plan on writing on this topic. It is also the one in which I am going to try and write a raw outline of the steps I plan on taking to start the newsletter for the first time.

Since article is going to contain the raw strategy it might be updated from time to time. Depending on which path I choose to go with or if I find out something new along the way. So keep an eye on it occasionally...

Outline

  • Newsletter Topic
    • What I am going to write about
    • Audience potential
  • Outreach strategy [article comming up]
    • How I plan to get subscribers
    • Plan on managing them
  • Website [article comming up]
    • Place to publish my writings on
    • Place to collect subscribers
  • Newsletter design [article comming up]
    • Newsletter Design & subscribing flow

Newsletter topic & name

The decisiong of picking a subject for the newsletter always revolved around "tech" or "dev" space. It had to be something I have experience in, so naturally, software engineering was the subject for me.
Then I asked myself what is something I do everyday and care about in my job that I could translate to the blog. The answer was Developer Experience. Things that helped me build faster. Tools I found useful and more productive for my worfklow.

Daily trying out new tools, libraries, different frameworks, code writing principles, AIs, etc., I might as well write about them. I found that reading about different people's experience with the tooling I plan on using was extremely benefitial to me. Helpful as it is, I thought putting my 2 cents in the space might be benefitial for someone else.

Having said all that, I decided to go with the name: "The Patch Notes".

What if no one reads? Small reflection on the audince topic

Major benefit of going with this subject was the premise: "If no one reads, would it still have the point?" And for me, the answer is yes. I picked a subject that even tho it never reaches a huge group of people, I would still be pleased that I wrote about it. Because I genuienly cared about the developer experience and helping someone, the sole goal of it was enough for me. Sometime putting your thoughts in the written word is useful. It shapes your thoughts, it almost gives them meaning and helps you get a different perspective on things you are working on. That feeling itself was enough, so I picked a subject that resonated with me, my way of thinking and the message I want to send. I picked a subject that I would write about anyways.

Other topics like How Do I Plan on Reaching People and Newsletter Design outlined will be documented in the upcoming post... Subscribe to the Patch Notes to stay in the loop