Help me, help you

Quick background on myself; I am a full time developer looking to share my knowledge and interest in development and tech. I have many years both in fulltime and freelancing roles developing sites, apps and services.

I want to start a newsletter, but want to ask my target audience first:

What do dev's want to read about? If you don't mind either commenting or answering the poll below of what you would want in a weekly/daily newsletter.

Content in a 'dev' newsletter
  1. Trends in software (new technologies, emerging tech)
  2. Career advise (specific to dev's)
  3. Tech Startup information
  4. Other - comment below!
  1. 4

    i’m looking for a collaborator for my foss project on Github. 🥳

  2. 4

    I voted "trends" but I'd clarify that I really only care about trends with my preferred development stack. I'm a .NET C# developer so I really only care about new things coming out of that world of programming.

    1. 2

      I would agree with David but I care more for Frontend technology.

      1. 1

        Agreed. I'm clueless with backend and would ignore the issue if it was all about it. Frontend is more my style. 😎

    2. 1

      Appreciate the feedback David! That’s funny, I’m a C# .Net developer as well!

      1. 1

        Nice! I thought about starting a C# daily newsletter with coding techniques but I wasn't sure if there was any audience.

  3. 1

    Trends - (C# .NET)... Consider something unique like this... (https://textnews.pythonanywhere.com/english) the value is in the actual information, remove the noise.

  4. 1

    Trends, just as everyone else. Ideally, it was one newsletter where you tick checkboxes next to categories (frontend, backend, specific framework(s) etc.) and get a personalized feed based on what you want to see. I cant think of how you would monetize it though

  5. 1

    Food for thought: you may want to focus on a more specific part of your audience. "Devs" in general is very wide; when asking what devs want to read about, you'll hear a lot of different things, as you can see in the comments on this thread.

    You might want to focus on a particular stack, topic (trends is good; I'd personally get even more specific to start if possible—"trends for front-end tools" for example) or a specific niche (content for enterprise Rails devs).

    The reason for this is differentiation, since there's so much content out there. That way you can build a strong audience in one specific topic before you branch out to other topics.

    1. 2

      Thanks @mikecavaliere , I appreciate the feedback!

      That’s makes complete sense - definitely helpful!

  6. 1

    I voted trends for similar reasons as everyone else, but I wouldn't subscribe to a newsletter for this stuff, unless that newsletter takes on some serious personalization for just ME.

    Currently I get my trends info from what the community is doing by following people on Twitter to see what new hotness they are talking about is, and communities on Reddit such as r/javascript and r/nodejs.

    Outside of that I subscribe to release notifications to every library (that is significant) repo on GitHub and when a notification comes in, I see what has happened in the changelog.

    1. 1

      Thanks @joshmanders! Appreciate the feedback

  7. 1

    Trends but mostly for front-end technology

  8. 1

    Trends would be pretty cool. Let me know when you make it.

Trending on Indie Hackers
Aim to be valuable and you'll be indispensable. 21 comments How hard should you work? 16 comments Do you have a writing habit? 13 comments 10 Reasons To Be Bullish On The Creator Economy In 2021 9 comments I made $804 in February 6 comments Tesla closes its forums and raises the anger of fans 5 comments