| I think this is a massive issue for both of you and I don't know how we can resolve it. Because it's an issue for you because you don't have time to work on it and you can't always work for free. But most people are on the other side. They work for a company and the company want them to use a package. But the package doesn't work or doesn't have the feature they need. The can't fix it or add the feature because their company don't give them time to read thousand of line of code and fix the bug or even worse, they just don't have the skill for it. What are they suppose to do ? Their company will put pressure on them and they are stuck so they ask you to fix the bug/add the feature. In the head of the manager the library is "famous", it is suppose to work and thousand of developer are using it. If it doesn't work it's because the company's developer is bad. But it's not his fault too. So everybody is in the same shit. And it's a very recurring situation. I'm an average python developer, yesterday my task was to add celery to our django project. Celery is an old and massive "famous" project. It is suppose to work. But what happened when you follow the tutorial ? The tutorial doesn't work. What do I say to my manager ? Sorry the project sucks it doesn't work. He will not understand me. I had to follow another tutorial made by someone else and their install guide was different from the official one, and it kinda works. "Kinda" because it didn't work, to start Celery, celery needs to load the django settings. My django settings was using environment variable. It works for all of them except the django.SECRET_KEY. Why ? I have no idea, so I had to hardcoded the secret key in the settings which is not a good solution, but at least it works and I can progress on the feature I have to do. What am I suppose to do ? Create an issue in celery asking for "please, can you fix your getting started because my company want me to use celery but it doesn't work ? Can you create a tutorial for using celery beat with django because my company want me to use it and I don't know how to do it ?" Of course I didn't create an issue because I know I will not have an answer and it's always my fault because I can't debug the library for hours to find a solution to the shitty tutorial who doesn't work. And that's just the type of the iceberg, I use all my day to make it work and I didn't manage to do it. I had to try different package, downgrade setuptools because one package wasn't compatible etc. At the end of the day, my environment was fucked up, django didn't even start anymore and I had to erase my environment and create a new one. And that's the day of every average developer (so not HN developers). We get angry because nothing work, our company put pressure on use, and at the end, we ask coldly on github for bug fix or feature. |