Struggle against marketing to win

After MVP was shipped, I've been reading code using Read it easy. Tips for code reading and some ideas for improvements are piling up.

Another aim of this code reading is to solve a marketing problem. I began to develop Read it easy for programmers who aren't or don't feel good at code reading. But according to my investigation, they rarely post tweets, blogs or comments in SNS about their complaints. Aren't they interested in code reading? Or are there no programmers who would like to get skilled in code reading? How will they become more conscious of their own problems about code reading? This is the marketing problem I face.

The solution is source code reading in public as content marketing. I sometimes use the hashtag "#readinpublic" in tweets and post the proceedings. This content focuses on my challenge that I read all the source code over 10k or 100k lines. Now I'm reading the source code of Ace (Ajax .org Clould9 Editor). If some programmers were interested in this challenge, they would be also interested in code reading itself. Additionally I expect they will start to think of their own problems about code reading.

However this solution doesn't promote Read it easy directly to prospects. It indirectly prompts them to notice their problems about code reading. Now I spent most of time on this content marketing than development. Is it right? As other indie hackers do, should I build in public only without such attempt? Or make haste slowly?