I found the announcement (quoted in the article) interesting and worth sharing, even without knowing or seeing the game.
Excerpts (I recommend reading the full thing):
My primary inspirations were the Japanese living doll myth and my experiences urban exploring in Germany (many backgrounds were crafted from photos I had taken).
The final act obviously deals with a difficult topic, sexual assault. I wanted the ending to be shocking, that was intentional, but never to cause harm. Instead, I thought I had crafted things in a way that would act as a jumping off point for some difficult discussions.
Secondly, the girl was never meant to look underage. In retrospect, I should have been more careful to ensure there was no ambiguity. Because she’s a doll (not human), I didn’t consider the possibility of misinterpretation as thoroughly as I should have.
This was also written long before the #MeToo movement, and I was a lot less educated on all the nuances of topics like these at the time.
If I had written it now, in my mid-30s, in 2025, it would be very different. Still, some choices I stand behind:
Do you have experience representing difficult topics in art? Weighing or deciding on respectful or acceptable representations, on the degree of deliberately shocking or uncomfortable representation?
Or do you remember scenes in games or otherwise in art that you found uncomfortable or shocking? In a good (well-represented or tactful) way or a bad way?
If you're a project and want to receive (good) bug reports, don't do it like GitLab.com.
A huge list of ticket templates, asking you to to select a "group" label a "category label" and some other such label from very long lists with unfamiliar names.
I almost gave up even filing and just went YOLO at the end.
For me, issue templates are barriers and annoyances most of the time, that make my report less concise and less useful. At least that's my strong opinion. Of course, I'm not the reason and target audience of what these templates try to protect against and guide submitters. Or maybe I am the target, who knows.
At work I remember a company managing our Jira migration set up a service desk that I found absolutely awful. When I wrote the exact same thing in four separate text fields, it's just stupid. The end-user first level support guard being used for us software developers felt like the completely wrong tool for the job.
In German, we have the acronym DAU for dümmster anzunehmender User - stupidest user to expect. Is there an EN term for DAU?