eupraxia

eupraxia , 8 days ago

I will say, these days it's more or less impossible to release a game that'll run perfectly on every system and it's a good thing we're able to fix crashes and patch issues as they come up. This has naturally had its downsides as publishers squeeze devs for tighter releases, but outside of that it's a very good thing for devs and players.

eupraxia , 15 days ago (edited 15 days ago)

Generally, using their current preferred name/pronouns (or neutral pronouns) is best. She's still the same person, so it's true to say Caitlyn Jenner won the 1976 Olympic Decathlon. If any other facts about the event itself were directly relevant to the conversation, that'd be ok - e.g. it would be accurate and inoffensive imo to say she won the men's division.

But name/pronouns change all the time otherwise so it's more normal to use the current ones. If Ms. Jones gets married and is now Mrs. Smith, it wouldn't be inaccurate to talk about Mrs. Smith's car breaking down last summer.

eupraxia , 13 days ago

That's a good question! It's definitely very rare that a birth name is entirely necessary to use in conversation, but an occasional situation comes up where I'm talking to an old friend about someone who's since transitioned and I need to use a deadname to let them know who I'm talking about. Generally I say something like "so I ran into Denise, you knew her as Brett back in the day, etc etc etc" and just use Denise from there on. If the person I'm talking to isn't caught too off guard by that, it's a very smooth and natural way to handle that as a matter of circumstance and move on to using the preferred name quickly.

eupraxia , 13 days ago

Np, thank you for asking!

eupraxia , 21 days ago (edited 21 days ago)

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.

eupraxia , 4 months ago

Outer Wilds, to my estranged family. I think they could use a new religion and that game’s probably a better place to start.

eupraxia , 10 months ago

Catcalling is a good example. When I was early on in transition catcalling felt uncomfortable, but I’d often walk away feeling like someone saw me as an attractive woman, which was a new validating experience and ultimately that outweighed the discomfort. After some more time, now that that’s more common, the validation has worn thin and now it’s just uncomfortable.