Earlier quoted context omitted.
A good way to understand how much we thanklessly rely on some professions, Google pictures of any garbage disposal strike
Garbage disposal and oss is an amusing comparison.
Burnout is real for open source maintainers
51–60 of 75 posts
Re: Burnout is real for open source maintainers
#52Re: Burnout is real for open source maintainers
#53If you have a hobby project like writing a blog, crocheting, or almost any other creative hobby, you can dip in and out however it suits you. If you deal with major life events, sicknesses, etc., you can leave the hobby and come back. Nobody is paying you for it, so nobody can complain (maybe the friends who miss you, but it's not actively impacting the real world). Open source is one of those weird things where your…
When I was a kid, we always had New Year's (read: Christmas) decorations (the maximum that wouldn't be out of place in a mostly Muslim country) on a small park in my neighborhood. One year they never appeared, and people were enraged . The guy the city hired every year had a mob in front of his door. People's letters to the authorities got no answer, so suddenly he apparently became their contact person. I was buying…
Re: Burnout is real for open source maintainers
#54If you have a hobby project like writing a blog, crocheting, or almost any other creative hobby, you can dip in and out however it suits you. If you deal with major life events, sicknesses, etc., you can leave the hobby and come back. Nobody is paying you for it, so nobody can complain (maybe the friends who miss you, but it's not actively impacting the real world). Open source is one of those weird things where your…
When I was a kid, we always had New Year's (read: Christmas) decorations (the maximum that wouldn't be out of place in a mostly Muslim country) on a small park in my neighborhood. One year they never appeared, and people were enraged . The guy the city hired every year had a mob in front of his door. People's letters to the authorities got no answer, so suddenly he apparently became their contact person. I was buying…
And I think he was apologizing to placate angry crowd, not necessary because genuine guilt.
Re: Burnout is real for open source maintainers
#55I wrote recently about bringing back my open source project back from the dead. It's more than a decade old. Many life events occured during that time. It's tough. It's nothing like Lodash but honestly these things ebb and flow. It operates in cycles just as life does. Wish him all the best. Sounds like he had many tough years personally and I can relate. https://go-micro.dev/blog/27
Re: Burnout is real for open source maintainers
#56If you have a hobby project like writing a blog, crocheting, or almost any other creative hobby, you can dip in and out however it suits you. If you deal with major life events, sicknesses, etc., you can leave the hobby and come back. Nobody is paying you for it, so nobody can complain (maybe the friends who miss you, but it's not actively impacting the real world). Open source is one of those weird things where your…
Don’t take shit just because you release software under a permissive license.
Re: Burnout is real for open source maintainers
#57Re: Burnout is real for open source maintainers
#58Re: Burnout is real for open source maintainers
#59Earlier quoted context omitted.
That sounds almost surreal. Pretty wild how my model of society doesn't account for this.
The society is built on informal expectations like that. People assume that things will go on as before, and they will start relying on it. They assume that for every thing they rely on, there is a bureaucrat somewhere responsible for making it happen. But unless you are that bureaucrat yourself, you probably don't need to be aware of the specifics. Many things in the society depend on volunteer work. Open source sof…
Re: Burnout is real for open source maintainers
#60Why not simply ignore all this stuff by the maxim "my software - my vision":
- If some request does not serve your vision for the software: close it.
- If you cannot handle the workload: work less on the program.
- If issues exist which you cannot fix very fast: take your time to fix it. Nobody is willing to pay you big money for fixing the issue, so a fix does not seem to be very urgent for the users.
- Too much responsibility: if the software was indeed such an important piece of infrastructure, people would pay you big money for you to maintain it.