Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That's exactly how I treat publishing my own OSS now (probably on a smaller scale though).

I had started by hoping (almost assuming) people would be amazed at how useful my library was. But mostly they didn't notice it, or (and this was harder to accept): didn't even recognize or understand the issues it was addressing in the first place.

5 years later, the issues are generally much better understood in android world, but still. I know some teams are using it, but it's probably not that many.

So publishing it has just become a hobby, it's something I can be proud of, it works nicely, I often use it (or the knowledge gained while writing it) to speed up whatever I'm doing and make my life easier. I also publish articles about said issues, and they seem to be helpful to the people that read them, and I enjoy explaining things I understand.

I'm not on the engineering manager track, and I hope to be programming until I retire, so I'll probably just keep supporting it.

If I had any advice for the OP I'd say set your expectations at: personal pride in doing a good job

(I'm definitely not the best person to dispense any kind of marketing advice anyway)



Yeah, expecting accolades (especially for things like code Quality and documentation) is invitation to disappointment.

In fact, it has been my experience, that high Quality actually makes the repo "radioactive."

Go figure.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: