2
5 Comments

Roast my Post! 🔥 I want to post this on HackerNews but want your scrutiny first 🧐

Hey Fellow Indie Devs,

Can you roast my post?

https://medium.com/@jones.spencera/monetizing-js-packages-as-easy-as-npm-publish-ea4df601c3d5

I'm trying to frame my product in the current open source ecosystem and how it benefits JS developers—I'd love your honest feedback

I'd like to post this on HackerNews tomorrow ... (Friday, May 13th ... maybe I should rethink! Isn't Friday the 13th supposed to be unlucky??)

Cheers,
Spencer

on May 12, 2020
  1. 1

    Some misc feedback:

    • add more images 😄
    • people skim articles like these, so don't be afraid to bold important points aside from h1/h2s
    • i'm happy to share this with the SustainOSS community which is your best bet for getting feedback from other people who really care about OSS sustainability
    • are you looking to help authors monetize or for sustain? they're related but not necessarily the same thing and peeps in the OSS community are sticklers about this sort of distinction
    • your link to premiumjs on the bottom isn't an actual link
    • i think the strongest part of your message is the fact that your workflow is the same as npm. npm publish, npm install, and most importantly npm payout or something that shows the single additional command (whatever you'll actually call it) in the same framing as the original npm workflow

    best of luck! 😄

  2. 1

    Two quick things:

    1. It's Wednesday the 13th tomorrow. We're all mixing up days though, I get it. =)
    2. I heard that it's a lot easier for posts to get traction on the weekend, and from my experience, that bears out. I originally posted early Tuesday and got nothing. Reposted middle of Saturday and hit front page.

    Good luck, that's a great article!

    1. 1

      @DanHulton—ah right, time ... clearly I don't have a good grip on it!

      Appreciate the insight about the timing of posts. I'll save this until Saturday :)

  3. 1

    Ping @saasify because I know you have thoughts that I’d love to hear :)

    And @jakeprins and @DanHulton who are working on stuff in this domain!

    1. 1

      Sort of? I'm rolling my own private licensing option for Nodewood partially to "eat my own dogfood" - the Nodewood site will of course be built with Nodewood. But I definitely have thought of making any sort of additional features to Nodewood as both a library that can be licensed outside of Nodewood and an integrated feature inside of Nodewood, so I'll keep PremiumJS in mind for those libraries.