I think you must be careful: many people are volunteer complainers about things that don't affect them at all. Many people complain about "Python not being scalable" or "Jupyter notebooks", and when you engage them and want to know what problems they have exactly, they'll make it obvious they're only repeating things they've heard, have not really used either, etc.<p>I'm not saying that Python or Jupyter don't have problems, I'm saying that many who complain are not necessarily the people you want to talk with, and it's better to be deliberate and conscious about targeting people who are actually having problems.<p>For example, one complained that a notebook didn't work on JupyterLab and that it worked seamlessly on Google Colab. Interesting. I asked whether it was a hardware issue or a JLab vs Colab issue: did they have enough RAM, a GPU on their local machine or they ran it on JLab + CPU + a bit of RAM on their local machine and then ran it on Colab + GPU + more RAM on Colab.<p>Would you be against learning about others' problems for a living? You can be in consulting. You'll have plenty of problems to solve. Here's a sort of mini blueprint[0]. I've worked on problems in different sectors and industries such as telecommunications, energy, banking, employment, healthcare, social work, communications and public relations, etc.<p>It is good to talk with people for whom the problem is <i>actually</i> a problem, not just blogging or tweeting about it or "building an audience", which you see a lot of creatures doing [X influencers/X thought leaders/X enthusiasts/motivational gurus]. You won't find good problems talking with these people because they're not the people "doing the deed", and problems to solve usually stem from doing something in life.<p>- [0]: <a href="https://twitter.com/jugurthahadjar/status/1310668293305499653" rel="nofollow">https://twitter.com/jugurthahadjar/status/131066829330549965...</a>