Much of the development of Thimbleweed Park was spent at home with my 18 month old daughter on my lap, just watching. I think it was a bonding experience for us both that we wouldn't have had if I was stuck in an office. I dread to think how many kids she dropped spoilers on in nursery.

Admittedly, this has been on long term projects and developers have always had the opportunity to request more information. This isn't always an options when outsourcing, but as an internal QA, it's good to follow up on your stuff.

Bug reports are for humans. Treat the reader like one. Describe the issue clearly, like you're talking to them. Keep it simple, skip the fluff—9 times out of 10, they just want to investigate and move on. (I know this doesn’t apply to every team, but it's worked for me.)

Also, for the record: I firmly advocate that QA are game developers. If you help shape the game or improve the experience, you’re developing the game. Simple as that.

store.steampowered.com/app/1082190/...

Every step we took in crafting this world felt like a small healing process, seeing it come to life has been an incredibly cathartic experience. I’m proud to share it with you all, and hope it resonates with anyone who’s ever faced loss, uncertainty, or a need for a little hope.

It was as if the game gave me a space to process my grief, to find meaning in the chaos, and to reconnect with a part of myself that had felt lost. The characters journey helped me navigate my own.