While this is true to an extent, from experience this line of thinking has its limits and is very easy to misapply. On the one hand, yes you can tell people their ideas do not gel with the vision of the project, and sometimes that’s the right call. And sometimes doing this a lot is best for the project.

On the other hand, even if a majority of the work is coming from one person, not only does your community learn your project, they also spend time contributing to it, fixing bugs, and helping other people. I feel it’s only to a project’s benefit to honor them and take difficult suggestions seriously, and get to the root of why those suggestions are coming up. Otherwise you risk pissing off your contributors, who I feel have the right to be annoyed at you and maybe post evangelion themed vent blog posts if you consistently shut down contributors’ needs and fail to adapt to what your users actually want out of your software. And forking, while freeing and playing to the idea of freedom of choice, also splits your userbase and contributors and makes both parties worse off. It really depends on the project, but it pays to maintain buy-in and trust from people who care enough to meaningfully contribute to your project.

Yep absolutely!

For me, it felt like my life was quickly progressing away from a youth I was not ready to leave for inexplicable reasons. In the end I ended up taking a nuclear option once I realized how uncomfortable I was with my future, and while it’s not been easy it’s been absolutely worth it.

Even though you may be stuck in the same habits and mistakes, they can be rewritten and you’ll be surprised how quickly life changes once you find what makes you authentically happy. A lot can happen in 3 years and I guarantee you’ll still be young at 24. You can still be young at twice that. There’s a lot of life ahead of you, especially once you take calculated risks to improve your future and make the most of the youth you still have. You may not know what exactly will make you happy, but trust in yourself and your judgement to find it as you go.

Yeah, I think that’s pretty much all that is generally needed. I’ve had people assume but ask me first, just asking “she/her?” as a question, I respond yes, we go about our business. If you don’t want to assume, you can also pretty much universally use they/them in passing, or if it’s someone you interact with more frequently, people really don’t tend to mind if you ask.

I mean I’m trans, I get around quite a bit in queer spaces, I haven’t met anyone who would get super mad about initially assuming pronouns rather than just saying “hey I prefer XYZ” and moving on. Generally when people react strongly to being misgendered, it’s due to ongoing conflict over their identities, having to deal with people who use pronouns to casually disregard your Identity, familial abandonment, etc. It is often a response to complex trauma from elsewhere. That’s not really your responsibility, but I’ve been there and if you can offer them any grace in those moments, it’s extremely helpful.

Borderlands?

Do you know who ate all the function candidates?

If it were up to me I’d be avoiding templates altogether. Sadly, I don’t get that choice with 3rd party code.

I love gcc but it can’t make nested template errors any less horrifying