I chose the niche because 1) it was small, 2) underserved, and 3) because it was misunderstood.
It was a risk, sure, but it is a side project - a place for risks. No overthinking required. Plan, work, review.
I believe you could do the same thing for many modules in the python standard lib or most popular third party libraries. Python docs everywhere are not helpful and newer dev's think it's their fault. Help them. Serve.
Consider: "would o’reilly write a book on the module/lib?" If not, you can stake out a monopoly. If so, then there's probably already cashflow there and you can join them.
Hmm. I think of my self as a collaborator not an educator, if that helps. A peer that has a few more years (decades) in pointing some stuff out with working code examples.
I chose the niche because 1) it was small, 2) underserved, and 3) because it was misunderstood.
It was a risk, sure, but it is a side project - a place for risks. No overthinking required. Plan, work, review.
I believe you could do the same thing for many modules in the python standard lib or most popular third party libraries. Python docs everywhere are not helpful and newer dev's think it's their fault. Help them. Serve.
Consider: "would o’reilly write a book on the module/lib?" If not, you can stake out a monopoly. If so, then there's probably already cashflow there and you can join them.
Hmm. I think of my self as a collaborator not an educator, if that helps. A peer that has a few more years (decades) in pointing some stuff out with working code examples.