[ThrowawayR2]

Previously submitted 5 times in the past 4 days.

- Show HN: What are your thoughts on this? (npmjs.com) 1 point by chrilleweb 1 day ago

- How do you get meaningful feedback on early-stage open source tools? (github.com/chrilleweb) 1 point by chrilleweb 2 days ago | 1 comment

- Seeking feedback from senior JavaScript engineers (github.com/chrilleweb) 1 point by chrilleweb 3 days ago | 1 comment

- How do you get more exposure for your open-source project? (github.com/chrilleweb) 10 points by chrilleweb 4 days ago | 4 comments

- CLI tool that scans your codebase for environment variable issues (npmjs.com) 1 point by chrilleweb 4 days ago 4 comments

Ironically, observe also that the user says in a sibling post "I’m explicitly not trying to market it aggressively..."

[chrilleweb]

Hi HN,

I’ve been working on a small open source CLI tool in my spare time and recently reached a point where it feels “done enough” to share — but I’m unsure what the right next steps are.

So far I’ve tried: - Writing a clear README with examples - Adding documentation and usage guides on my docs website - Sharing it in one or two relevant discussions (without spamming)

I’m explicitly not trying to market it aggressively — I’d rather get it in front of the right people and receive honest feedback.

For those of you who’ve shipped open source projects that actually got adopted: What made the biggest difference early on? What do you wish you had done sooner?

If it helps, the project it's the link if you have any tips

Thanks!

[kgwxd]

Making the text of the link to it completely irrelevant, so people are fooled into clicking it, is 1000 times worse than self-promotion. You've done it more than once.

[fsflover]

What's wrong with self-promotion? Just make a post starting with "Show HN:" here:

https://news.ycombinator.com/shownew