5 ms·
It’s worked out so far. I knew it would be tough to scale up myself as support so I set down as couple of policies: 1. Do it in public if possible via GitHub i
by mperham 5y ago
It’s worked out so far. I knew it would be tough to scale up myself as support so I set down as couple of policies:
1. Do it in public if possible via GitHub issues so others can also answer and search in the future.
2. Don’t allow more than N questions per year per customer. A few have drowned me with requests. Nope, you are buying a product, not a trainer or teacher. Read the docs, watch the videos.
3. Pour everything I know into the wiki docs. Note each wiki page will talk about semantics, edge cases, etc. That’s all there to get ahead of the support inquiries.
- aaronmiler 5y ago#3 is one of my favorite things about Sidekiq. Anything I'm trying to do with Sidekiq, I check the wiki first, and it's usually there. Any time I've introduced the library to a team, the docs and wiki are always my recommendation for answering questions. Even Pro/Ent features are covered there, which is so much nicer than having the docs hidden behind a login/paywall. Thanks for the hard work you've poured into them Mike!