I'm building an IoT product on Amazon Web Services. Which, if you've tried navigating AWS before you will know that documentation is all over the place and difficult to wrap your head around.
I've figured out how to route the core services needed to have my IoT device stream real-time data to a web-app I wrote in React. My first reaction (sorry) is to write a blog post about all the steps I took to make it work. I know the Indie Hacker mantra is to build everything in public, but don't some folks put paywalls in front of their blog posts?
I have a group of folks interested in the end-product, which I will definitely show (ie. customers that don't care about how it's built). But I'm sure there are other developers that would be interested in easier AWS guides.
I would like to build credibility in the space but I'm also thinking of every avenue I can take to make money for the work I've put in. Thank you for any input!
if you're optimizing for revenue this early then you're doing it wrong.
sorry (not sorry).
revenue is the result of a great customer experience... you have to earn the right to sell before they'll buy... so, better to start blogging free and giving people a chance to read your shit (or awesomesauce!!) and then walk them towards your product, right?
i've been writing a public blog for 19+ years. lmk if you have questions.
Thanks! I needed that reminder. No matter how many times you hear "no one will steal your idea" it just doesn't stick sometimes lol.
I just joined this AWS slack group and found some new motivation to write my blog!
sweet! there you go! you could literally do that once a day... small content, bite-sized!
@8bit one additional question, do you have any recommendations for word count? Thank you
no. it matters more that you hit the
publishbutton as often as you can.I'm currently getting up to speed on some technologies, and I've seen that there is SO MUCH free tutorial content available. I think if you plan on charging for this type of content, it would have to be really niche or way better than everything else there is.
That's a good point, it would probably need to be on par with "e-course" level of commitment. Which I don't think I want to go that path.